Created attachment 1194015 [details] servlet async jmeter test plan Description of problem: Under load, client does not get a response from Async Servlet Version-Release number of selected component (if applicable): 6.4.9, 6.1.1 How reproducible: use the quickstart async servlet and a jmeter test Steps to Reproduce: 1. deploy async servlet from quickstart 2. create jmeter test with 50 clients ramp up period 1 on http://localhost:8080/jboss-servlet-async/AsynchronousServlet Actual results: Http errors: org.apache.http.NoHttpResponseException Expected results: no error Additional info:
It works after adding a delay after readData method // the actual execution will run in a separate thread. longRunningService.readData(asyncContext); Thread.sleep(50);
Created attachment 1194030 [details] async servlet war
Created attachment 1194037 [details] source code
According to comments the main point of this bz is that the request should end within the time specified in the timer. So I used little bit different steps to reproduce: 1. deploy async servlet from quickstart 2. ab -c 150 -n 10000 http://localhost:8080/jboss-servlet-async/AsynchronousServlet Verified with EAP 6.4.11.CP.CR1 because there are not any failed requests.
Fedor, I use java 8 in my environment. But this issue I tested with java 6, java 7 and java 8. It works everywhere for me.
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.