jetty

问题 I'm using the atmosphere framework (https://github.com/Atmosphere/atmosphere) which runs on a jetty server and brings websockets to any browser. The problem that I'm having is that for some strange reason messages broadcasted to all connected clients only arrive on the webclient running on the same platform as the jetty server. (localhost:8080) Other clients only recieve their messages (all at once) when the server stops. (ip server:8080) I'm not sure weither this is an issue with jetty 8

问题 In my jetty configuration file I am using ExcludeCipherSuites tag to exclude some protocols and everything works fine and my jetty server supports all TLS versions (1.0, 1.1, 1.2). However when instead of excluding bad ciphers, I use IncludeCipherSuites to include only supported ciphers, my jetty server starts supporting only TLS 1.2. Other TLS versions (1.0 and 1.1) are becoming not supported. I even tried to whitelist all possible ciphers using IncludeCipherSuites like below: <Set name=

问题 Hello I am trying to setup a permanent redirect (301) from http to https in jetty 9. The solution I found everywhere is to add the following in my web.xml <security-constraint> <web-resource-collection> <web-resource-name>Everything</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>INTEGRAL</transport-guarantee> </user-data-constraint> </security-constraint> This sets up a 302 redirect and not a 301 redirect and it is a

问题 I'm trying to run my (seam and) wicket app on an embedded jetty server. I get the following exception: Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:366) at org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader

问题 I'm running integration tests using jersey, jetty 9.x, jetty-maven-plugin and the maven-failsafe-plugin. Integration tests worked well with jetty 9.2.0.M0 specified in jetty-maven-plugin. When using version 9.3.4.RC1, jetty starts, but no integration tests are run. Here's my pom.xml: <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

问题 I face the following problem: whenever i try to start Jetty with an application instance i need check if the application is running. I need to do that from an ant target. I want to have something behaving like the following pseudocode: ** <target name="target1" depends="run-jetty-with-application" description="Target1"> <--when run-jetty-with-application is ok(jetty is up and application is running)--> <antcall target="target2"/> <--end when--> </target> ** I should also mention that i have

问题 I'm using servlets 3 with jetty 8.1.1 and the SslContextFactory on an amazon ec2 machine (m1-small). The first HTTPS request from localhost (of the amazone machine) is about 150ms and further requests seem to get faster (down to ~40ms) but not as close as to the HTTP response time of only 20ms - why? Is encryption really that slow? Also when comparing HTTPS and HTTP from outside of the amazon cloud the difference gets even worse: HTTPS requests are at least 400ms slower!? How can that be? Is

问题 When I start server with jetty, the console will display this error information: Can someone help me ? 3Q. [2014-10-26 14:11:02 WARN org.eclipse.jetty.util.component.AbstractLifeCycle:204] FAILED org.eclipse.jetty.server.handler.HandlerCollection@3bbbbafc: java.lang.NoSuchMethodError: javax.servlet.ServletContext.getServletRegistration(Ljava/lang/String;)Ljavax/servlet/ServletRegistration; java.lang.NoSuchMethodError: javax.servlet.ServletContext.getServletRegistration(Ljava/lang/String;

问题 I am migrating from Jetty 8.1.17 to Jetty 9.3.9. Our application embeds Jetty. Previously we had a single XML configuration file jetty.xml which contained everything we needed. I felt that with Jetty 9.3.9 it would be much nicer to use the modular approach that they suggest, so far I have jetty.xml , jetty-http.xml , jetty-https.xml and jetty-ssl.xml in my $JETTY_HOME/etc ; these are pretty much copies of those from the 9.3.9 distribution. This seems to work well when I use start.jar but not

问题 I have a Scalatra with Jetty and it is serving REST API at the moment. No static context served at all. However, it seems I cannot skip setting resourceBase without getting java.lang.IllegalStateException: No resourceBase or war set for context Do I have to point it to some empty directory or is there some other option? 回答1: A resourceBase is required, and it is used for more than just static content. It's also the location for configuration that the ServletContext needs. Point it at an empty