[UNDERTOW-577] undertow java.lang.IllegalStateException: UT010019: Response already commited Created: 04/Nov/15  Updated: 23/Dec/15  Resolved: 05/Nov/15

Status: Resolved
Project: Undertow
Component/s: None
Affects Version/s: None
Fix Version/s: 1.4.0.Beta1, 1.3.10.Final

Type: Bug Priority: Minor
Reporter: David Zukerman Assignee: Stuart Douglas
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I'm not too sure whether this is a bug or an enhancement but just in case I will report it:
when the war.xml file contains the form-login-page element but that page defined does not exist, here's the Undertow behavior:
1. the war file is successfully deployed
2. when you try to access to a secured resource, you will get the following error:
ERROR [io.undertow.request] (default task-7) UT005023: Exception handling request to /app/login.html: java.lang.IllegalStateException: UT010019: Response already commited

I'm not too sure whether the behavior should be redirecting to the 404 page not found page.

I know is a minor thing but just wanted to point it out in case is useful.



 Comments   
Comment by Arjan t [ 16/Nov/15 ]

Incidentally, this also fixes the failure of this test: https://github.com/javaee-samples/javaee7-samples/tree/master/jaspic/status-codes which tests code such as this in a SAM:

  
HttpServletResponse response  = (HttpServletResponse) messageInfo.getResponseMessage();
response.sendError(SC_NOT_FOUND);
return SEND_FAILURE;

I noticed the fix was only applied to 1.4.x. Can it also be applied to the 1.3.x branch? I applied the fix manually there (tried 1.3.3.Final since that's what WF 10cr4 uses) and it seems to work great.

Generated at Thu Oct 18 02:12:40 EDT 2018 using Jira 7.12.1#712002-sha1:609a50578ba6bc73dbf8b05dddd7c04a04b6807c.