Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1365906 - [GSS](6.4.z) IllegalStateException thrown when browser is refreshed [NEEDINFO]
Summary: [GSS](6.4.z) IllegalStateException thrown when browser is refreshed
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Peter Palaga
QA Contact: Nikoleta Ziakova
Depends On:
TreeView+ depends on / blocked
Reported: 2016-08-10 13:02 UTC by Yogesh
Modified: 2017-02-09 13:55 UTC (History)
5 users (show)

Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-02-09 13:55:11 UTC
Type: Bug
ppalaga: needinfo? (yvedpath)

Attachments (Terms of Use)

Description Yogesh 2016-08-10 13:02:41 UTC
Description of problem:
RestEasy is handling an exception and trying to reset the response to return an error. But it's too late to reset the response as response headers have already been written to the client. So the original exception is not being logged and IllegalStateException is thrown. 

Version-Release number of selected component (if applicable):
JBoss EAP 6.4.6

How reproducible:

Steps to Reproduce:

Actual results:
IllegalStateException is logged.

Expected results:
The original exception raised by RestEasy has to be logged. 

Additional info:
After enabling ByteMan logging on class org.jboss.resteasy.core.SynchronousDispatcher the original exception was detected.

Comment 1 Peter Palaga 2016-09-21 10:06:59 UTC
Yogesh, could you please provide a minimal application that reproduces the problem - e.g. take the rshelloworld quickstart [1] and modify it to reproduce the bug?


Comment 6 Peter Palaga 2017-02-09 13:55:11 UTC
Closing due to missing reproducer.

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