Bug 1370182

Summary: [GSS](6.4.z) Http response errors using Async Servlet
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: tmiyargi
Component: WebAssignee: Fedor Gavrilov <fgavrilo>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Cada <mcada>
Severity: high Docs Contact:
Priority: high    
Version: 6.1.1, 6.4.9CC: bmaxwell, fgavrilo, jbilek, jtruhlar, msochure, rhatlapa, rmaucher, socallag, tmiyargi
Target Milestone: CR1Keywords: Reopened
Target Release: EAP 6.4.11   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 13:07:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1316573, 1361648, 1377657    
Attachments:
Description Flags
servlet async jmeter test plan
none
async servlet war
none
source code none

Description tmiyargi 2016-08-25 13:04:49 UTC 
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:
Comment 1 tmiyargi 2016-08-25 13:08:54 UTC 
It works after adding a delay after readData method 
// the actual execution will run in a separate thread.
longRunningService.readData(asyncContext);
        
Thread.sleep(50);
Comment 2 tmiyargi 2016-08-25 13:09:57 UTC 
Created attachment 1194030 [details]
async servlet war
Comment 4 tmiyargi 2016-08-25 13:36:17 UTC 
Created attachment 1194037 [details]
source code
Comment 47 Jiří Bílek 2016-10-10 14:15:43 UTC 
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.
Comment 53 Jiří Bílek 2016-10-20 07:21:10 UTC 
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.
Comment 55 Petr Penicka 2017-01-17 13:07:50 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.