Bug 977913

Summary: ExceptionMapper waits for timeout of AsynchronousResponse
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Travis Rogers <trogers>
Component: RESTEasyAssignee: Weinan Li <weli>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Sakař <psakar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: lakagwu, myarboro, nobody
Target Milestone: ER3   
Target Release: EAP 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-15 16:23:29 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:
Attachments:
Description Flags
RESTEASY-736.zip none

Description Travis Rogers 2013-06-25 15:05:18 UTC 
When using AsynchronousResponse the client needs to wait for the specified timeout in case the ExceptionMapper is triggered. This is unexpected behaviour since the exception should be returned immediately. (In fact this is done, but the client keeps waiting for the server to close the connection).
Comment 3 JBoss JIRA Server 2013-07-15 21:14:06 UTC 
Bill Burke <bill> updated the status of jira RESTEASY-721 to Closed
Comment 4 Weinan Li 2013-09-23 10:21:15 UTC 
This has been fixed in 2.3.7.Final
Comment 8 Petr Sakař 2013-10-16 10:00:09 UTC 
Created attachment 812849 [details]
RESTEASY-736.zip

project to verify bug is fixed.
to see test failure run
  mvn clean test
to verify run
  mvn clean test -Dresteasy.version=2.3.7.Final-redhat-2