PI63633: THREAD-SAFETY ISSUE IN THE UNDERLYING (APACHE) JSF 2.0 CODE CAUSES WEBCONTAINER THREADS TO HANG

Fixes are available

APAR status

Closed as program error.

Error description

Apache JSF 2.0 are not synchronizing on their usage of
WeakHashMap in
org.apache.myfaces.view.facelets.impl.DefaultFacelet.getRelati
ve Path.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
*                  Full Profile versions 8.0, 8.5.5 and 9.0    *
*                  and                                         *
*                  Liberty Profile version 8.5.5 users of      *
*                  JavaServer Faces(JSF) MyFaces.              *
****************************************************************
* PROBLEM DESCRIPTION: An unsynchronized access (thread safety *
*                      issue) to a WeakHashMap is causing      *
*                      WebContainer threads to hang.           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
WebContainer threads can hang due to a thread safety issue in
the underlying JSF code. A non thread-safe WeakHashMap is being
used in the getRelativePath method of the DefaultFacelet class.
Usage of that WeakHashMap is not synchronized, and as a result
the following issue might be seen:
"WebContainer : 0" daemon prio=3 tid=0x00000001055c2800
nid=0x9c
runnable [0xffffffff46af9000]
java.lang.Thread.State: RUNNABLE
at
java.util.WeakHashMap.get(WeakHashMap.java:355)
at
org.apache.myfaces.view.facelets.impl.DefaultFacelet.getRelative
Path(DefaultFacelet.java:286)

Problem conclusion

The JSF MyFaces code was updated to fix the thread-safety issue
on the WeakHashMap.

The fix for this APAR is currently targeted for inclusion in
fix pack 8.0.0.13, 8.5.5.11 and 9.0.0.1 for WebSphere
Application Server and 16.0.0.3 for WebSphere Liberty.
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
PI63633
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-06
Closed date
2016-06-17
Last modified date
2016-08-10

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
R900 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.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI63633: THREAD-SAFETY ISSUE IN THE UNDERLYING (APACHE) JSF 2.0 CODE CAUSES WEBCONTAINER THREADS TO HANG

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

R900 PSY

Document Information

Share your feedback

Need support?