PI18604: UNCAUGHT APPLICATION EXCEPTIONS THROWN DURING A JSF AJAX REQUEST INSTEAD OF ERROR ELEMENT IN THE AJAX RESPONSE

Fixes are available

APAR status

Closed as program error.

Error description

Uncaught application exceptions during a JSF AJAX request when
there are error pages defined in the web.xml are not handled
according to the JSF specification.  According to the
specification (section 13.3.7 in the JSF 2.0 spec) they are
supposed to be encoded in a an  error  element in the AJAX
response, but instead they are being thrown uncaught to the
Servlet container which attempts to display the error page
(which does not work with an AJAX request ).
NOTE: this was fixed in MyFaces 2.0.8 under issues MYFACES-3053
(which is an umbrella issue for exception handling
improvements).

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V8.0 and V8.5                        *
****************************************************************
* PROBLEM DESCRIPTION: Ajax exception information is not       *
*                      handled correctly: it should be         *
*                      directly encoded in the AJAX response.  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When an Ajax exception is encountered in a JavaServer Faces
(JSF) 2.0 application, the JSF 2.0 specification dictates that
the exception information must be written directly into the
Ajax response.  Previously the WebSphere Application Server
JSF MyFaces implementation did not handle these exceptions in
the Ajax response, and they were thrown incorrectly.

Problem conclusion

The JSF MyFaces code was updated to allow for correct Ajax
exception handling.  To enable the specialized Ajax exception
handler, set the following context parameter to "true":
com.ibm.ws.jsf.enableAjaxExceptionhandler (true/false-default).

The fix for this APAR is currently targeted for inclusion in
fix packs 8.0.0.10 and 8.5.5.4.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PI18604
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-05-23
Closed date
2014-06-27
Last modified date
2014-06-27

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 April 2022

Tips

PI18604: UNCAUGHT APPLICATION EXCEPTIONS THROWN DURING A JSF AJAX REQUEST INSTEAD OF ERROR ELEMENT IN THE AJAX RESPONSE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?