Bug 977913 - ExceptionMapper waits for timeout of AsynchronousResponse
Summary: ExceptionMapper waits for timeout of AsynchronousResponse
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: RESTEasy
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER3
: EAP 6.2.0
Assignee: Weinan Li
QA Contact: Petr Sakař
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-25 15:05 UTC by Travis Rogers
Modified: 2018-12-04 15:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:23:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
RESTEASY-736.zip (9.22 KB, application/zip)
2013-10-16 10:00 UTC, Petr Sakař
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RESTEASY-721 0 Major Closed ExceptionMapper waits for timeout of AsynchronousResponse 2019-06-26 02:50:25 UTC

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


Note You need to log in before you can comment on or make changes to this bug.