You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, the "Started" log is emitted whilst the context is still Starting, so if the client response is quick it will arrive at the context and be handled by:
if (handler == null || !isStarted())
returnfalse;
So the client loses the race and the request is 404'd
A fix for this is to turn on debug for the deployer and wait like:
// Wait for start contextassertTrue(run2.awaitConsoleLogsFor("Started oeje10w.WebAppContext@", START_TIMEOUT, TimeUnit.SECONDS));
// wait for deployer node to complete so context is Started not StartingassertTrue(run2.awaitConsoleLogsFor("Executing Node Node[started]", START_TIMEOUT, TimeUnit.SECONDS));
ContentResponseresponse = client.GET("http://localhost:" + port + "/test/sometest.txt");
The text was updated successfully, but these errors were encountered:
Jetty version(s)
12
Jetty Environment
all
Description
We have many distribution tests that do something like:
However, the "Started" log is emitted whilst the context is still
Starting
, so if the client response is quick it will arrive at the context and be handled by:So the client loses the race and the request is 404'd
A fix for this is to turn on debug for the deployer and wait like:
The text was updated successfully, but these errors were encountered: