[jboss-jira] [JBoss JIRA] (WFLY-3584) internal server error after jsf conversation time out
Farah Juma (JIRA)
issues at jboss.org
Fri Jul 4 16:11:24 EDT 2014
[ https://issues.jboss.org/browse/WFLY-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982453#comment-12982453 ]
Farah Juma commented on WFLY-3584:
----------------------------------
As mentioned in WFLY-2691, the error page doesn't get displayed because of the way Undertow's development mode works (for more details, see the explanation [here|https://issues.jboss.org/browse/WFLY-2691?focusedCommentId=12942763&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12942763]). To allow your error page to be displayed, set the 'stack-trace-on-error' attribute in the <servlet-container> element in the Undertow subsystem to 'none' as follows:
{code}
<servlet-container name="default" stack-trace-on-error="none">
<jsp-config/>
</servlet-container>
{code}
Also, the location of the error page needs a leading forward slash, e.g.,
{code}
<error-page>
<location>/default.xhtml</location>
</error-page>
{code}
With these two changes, the configured error page should be displayed when the session times out.
> internal server error after jsf conversation time out
> -----------------------------------------------------
>
> Key: WFLY-3584
> URL: https://issues.jboss.org/browse/WFLY-3584
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF, Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Martin Welss
> Assignee: Farah Juma
> Attachments: webapp.war
>
>
> when the session times out on a page backed by a conversation scoped bean, the server shows "505 internal server error" when the button on the page is clicked instead of showing the configured error page
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the jboss-jira
mailing list