dab4fe60d3
* Fixes #8558 - Idle timeout occurs on HTTP/2 with InputStreamResponseListener. The issue was that HttpReceiverOverHTTP2.ContentNotifier.offer() was racy, as a network thread could have offered a DATA frame, but not yet called process() -- yet an application thread could have stolen the DATA frame completed the response and started another response, causing the network thread to interact with the wrong response. The implementation has been changed so that HttpReceiverOverHTTP2.ContentNotifier does not have a queue anymore and it demands DATA frames to the Stream only when the application demands more -- a simpler model that just forwards the demand. Signed-off-by: Simone Bordet <simone.bordet@gmail.com> |
||
|---|---|---|
| .github | ||
| .mvn | ||
| apache-jsp | ||
| apache-jstl | ||
| build-resources | ||
| demos | ||
| documentation | ||
| javadoc | ||
| jetty-alpn | ||
| jetty-annotations | ||
| jetty-ant | ||
| jetty-bom | ||
| jetty-cdi | ||
| jetty-client | ||
| jetty-deploy | ||
| jetty-fcgi | ||
| jetty-gcloud | ||
| jetty-hazelcast | ||
| jetty-home | ||
| jetty-http | ||
| jetty-http-spi | ||
| jetty-http2 | ||
| jetty-http3 | ||
| jetty-infinispan | ||
| jetty-io | ||
| jetty-jaas | ||
| jetty-jaspi | ||
| jetty-jmx | ||
| jetty-jndi | ||
| jetty-jspc-maven-plugin | ||
| jetty-keystore | ||
| jetty-maven-plugin | ||
| jetty-memcached | ||
| jetty-nosql | ||
| jetty-openid | ||
| jetty-osgi | ||
| jetty-p2 | ||
| jetty-plus | ||
| jetty-proxy | ||
| jetty-quic | ||
| jetty-quickstart | ||
| jetty-rewrite | ||
| jetty-runner | ||
| jetty-security | ||
| jetty-server | ||
| jetty-servlet | ||
| jetty-servlets | ||
| jetty-slf4j-impl | ||
| jetty-start | ||
| jetty-unixdomain-server | ||
| jetty-unixsocket | ||
| jetty-util | ||
| jetty-util-ajax | ||
| jetty-webapp | ||
| jetty-websocket | ||
| jetty-xml | ||
| logos | ||
| scripts | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| .lgtm.yml | ||
| CODE_COVERAGE.md | ||
| CONTRIBUTING.md | ||
| Jenkinsfile | ||
| Jenkinsfile-autobahn | ||
| Jmh_Jenkinsfile | ||
| KEYS.txt | ||
| LICENSE | ||
| NOTICE.txt | ||
| README.md | ||
| SECURITY.md | ||
| VERSION.txt | ||
| header-template.txt | ||
| pom.xml | ||
README.md
Eclipse Jetty Canonical Repository
This is the canonical repository for the Jetty project, feel free to fork and contribute now!
Submitting a patch or pull request?
Make sure you have an Eclipse Contributor Agreement (ECA) on file.
Project description
Jetty is a lightweight highly scalable java based web server and servlet engine. Our goal is to support web protocols like HTTP, HTTP/2 and WebSocket in a high volume low latency way that provides maximum performance while retaining the ease of use and compatibility with years of servlet development. Jetty is a modern fully async web server that has a long history as a component oriented technology easily embedded into applications while still offering a solid traditional distribution for webapp deployment.
Webapp Example
$ mkdir base && cd base
$ java -jar $JETTY_HOME/start.jar --add-modules=http,deploy
$ cp ~/src/myproj/target/mywebapp.war webapps
$ java -jar $JETTY_HOME/start.jar
Embedded Example
Server server = new Server(port);
ServletContextHandler context = new ServletContextHandler(server, "/");
context.addServlet(MyServlet.class, "/*");
server.start();
Documentation
Project documentation is available on the Jetty Eclipse website.
Building
To build, use:
mvn clean install
Eclipse Jetty will be built in jetty-home/target/jetty-home.
The first build may take a longer than expected as Maven downloads all the dependencies.
The build tests do a lot of stress testing, and on some machines it is necessary to set the file descriptor limit to greater than 2048 for the tests to all pass successfully.
It is possible to bypass tests by building with mvn clean install -DskipTests.
Professional Services
Expert advice and production support are available through Webtide.com.