merge branch jetty-10.0.x into jetty-11.0.x
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
This commit is contained in:
commit
9982462a72
|
@ -184,7 +184,7 @@ jetty-9.4.35.v20201120 - 20 November 2020
|
|||
+ 5539 StatisticsServlet output is not valid
|
||||
+ 5562 ArrayTernaryTrie consumes too much memory
|
||||
+ 5575 Add SEARCH as a known HttpMethod
|
||||
+ 5605 java.io.IOException: unconsumed input during http request parsing
|
||||
+ 5605 CVE-2020-27218 java.io.IOException: unconsumed input during http request parsing
|
||||
+ 5633 Allow to configure HttpClient request authority
|
||||
|
||||
jetty-9.4.34.v20201102 - 02 November 2020
|
||||
|
|
|
@ -37,6 +37,7 @@ import org.eclipse.jetty.client.AbstractConnectionPool;
|
|||
import org.eclipse.jetty.client.HttpClient;
|
||||
import org.eclipse.jetty.client.HttpDestination;
|
||||
import org.eclipse.jetty.client.HttpResponseException;
|
||||
import org.eclipse.jetty.client.MultiplexConnectionPool;
|
||||
import org.eclipse.jetty.client.api.ContentResponse;
|
||||
import org.eclipse.jetty.client.api.Response;
|
||||
import org.eclipse.jetty.client.api.Result;
|
||||
|
@ -336,12 +337,28 @@ public class MaxConcurrentStreamsTest extends AbstractTest
|
|||
}
|
||||
});
|
||||
|
||||
int parallelism = 4;
|
||||
int runs = 1;
|
||||
int iterations = 32;
|
||||
|
||||
client.setMaxConnectionsPerDestination(32768);
|
||||
client.setMaxRequestsQueuedPerDestination(1024 * 1024);
|
||||
client.getTransport().setConnectionPoolFactory(destination ->
|
||||
{
|
||||
try
|
||||
{
|
||||
MultiplexConnectionPool pool = new MultiplexConnectionPool(destination, client.getMaxConnectionsPerDestination(), false, destination, 1);
|
||||
pool.preCreateConnections(parallelism * 2).get();
|
||||
return pool;
|
||||
}
|
||||
catch (Exception e)
|
||||
{
|
||||
throw new RuntimeException(e);
|
||||
}
|
||||
});
|
||||
// Prime the destination to pre-create connections.
|
||||
client.GET("http://localhost:" + connector.getLocalPort());
|
||||
|
||||
int parallelism = 16;
|
||||
int runs = 1;
|
||||
int iterations = 256;
|
||||
int total = parallelism * runs * iterations;
|
||||
CountDownLatch latch = new CountDownLatch(total);
|
||||
Queue<Result> failures = new ConcurrentLinkedQueue<>();
|
||||
|
|
|
@ -1,40 +0,0 @@
|
|||
|
||||
|
||||
This is the jetty websocket module that provides a websocket server and the skeleton of a websocket client.
|
||||
|
||||
By default websockets is included with a jetty release (with these classes either being in the jetty-websocket jar or in
|
||||
an aggregate jar (see below).
|
||||
|
||||
|
||||
In order to accept a websocket connection, the websocket handshake request is first routed to normal HTTP request
|
||||
handling, which must respond with a 101 response and an instance of WebSocketConnection set as the
|
||||
"org.eclipse.jetty.io.Connection" request attribute. The accepting behaviour is provided by WebSocketHandler or the
|
||||
WebSocketServlet class, both of which delegate to the WebSocketFactory class.
|
||||
|
||||
A TestServer and TestClient class are available, and can be run either directly from an IDE (if jetty source is
|
||||
imported), or from the command line with
|
||||
|
||||
|
||||
java -cp jetty-aggregate/jetty-all/target/jetty-all-7.x.y.jar:jetty-distribution/target/distribution/lib/servlet-api-2.5.jar
|
||||
org.eclipse.jetty.websocket.TestServer --help
|
||||
|
||||
java -cp jetty-aggregate/jetty-all/target/jetty-all-7.x.y.jar:jetty-distribution/target/distribution/lib/servlet-api-2.5.jar
|
||||
org.eclipse.jetty.websocket.TestClient --help
|
||||
|
||||
|
||||
Without a protocol specified, the client will just send/receive websocket PING/PONG packets. A protocol can be specified for testing other
|
||||
aspects of websocket. Specifically the server and client understand the following protocols:
|
||||
|
||||
org.ietf.websocket.test-echo
|
||||
Websocket messages are sent by the client and the server will echo every frame.
|
||||
|
||||
org.ietf.websocket.test-echo-broadcast
|
||||
Websocket messages are sent by the client and the server will echo every frame to every connection.
|
||||
|
||||
org.ietf.websocket.test-echo-assemble
|
||||
Websocket messages are sent by the client and the server will echo assembled messages as a single frame.
|
||||
|
||||
org.ietf.websocket.test-echo-fragment
|
||||
Websocket messages are sent and the server will echo each message fragmented into 2 frames.
|
||||
|
||||
|
Loading…
Reference in New Issue