PI85250: HUNG THREAD ISSUE IN MYFACES

Fixes are available

APAR status

Closed as program error.

Error description

When using MyFaces JSF implementation, a hang issue may occur.
Hung threads show the following callstack:

at java/util/HashMap.getEntry(HashMap.java:476(Compiled Code))
at java/util/HashMap.get(HashMap.java:429(Compiled Code))
at
org/apache/myfaces/view/facelets/tag/MetaRulesetImpl._getMetadat
aTarget(MetaRulesetImpl.java:219(Compiled Code))
at
org/apache/myfaces/view/facelets/tag/MetaRulesetImpl.finish(Meta
RulesetImpl.java:156(Compiled Code))
at
javax/faces/view/facelets/MetaTagHandler.setAttributes(MetaTagHa
ndler.java:65(Compiled Code))
at
javax/faces/view/facelets/DelegatingMetaTagHandler.setAttributes
(DelegatingMetaTagHandler.java:93(Compiled Code))

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server            *
*                  Traditional                                 *
*                  Profile versions 8.0, 8.5.5 and Liberty     *
*                  Profile users of JavaServer Faces (JSF)     *
*                  MyFaces 2.0                                 *
****************************************************************
* PROBLEM DESCRIPTION: Threads might hang when trying to       *
*                      access                                  *
*                      an unsynchronized HashMap object        *
*                      inside                                  *
*                      MetaRulesetImpl._getMetadataTarget      *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
With a highly concurrent workload, WebContainer threads might
hang inside MetaRulesetImpl when they are trying to access an
unsynchronized HashMap object.
The hung thread stack will look similar to the following
snippet:
at java/util/HashMap.getEntry(HashMap.java:476(Compiled Code))
at java/util/HashMap.get(HashMap.java:429(Compiled Code))
at
org/apache/myfaces/view/facelets/tag/MetaRulesetImpl._getMetadat
aTarget(MetaRulesetImpl.java:219(Compiled Code))
at
org/apache/myfaces/view/facelets/tag/MetaRulesetImpl.finish(Meta
RulesetImpl.java:156(Compiled Code))
at
javax/faces/view/facelets/MetaTagHandler.setAttributes(MetaTagHa
ndler.java:65(Compiled Code))
at
javax/faces/view/facelets/DelegatingMetaTagHandler.setAttributes
(DelegatingMetaTagHandler.java:93(Compiled Code))

Problem conclusion

The JSF MyFaces 2.0 code was updated to prevent threads from
hanging inside MetaRulesetImpl.
Fix details can be found at
https://issues.apache.org/jira/browse/MYFACES-3216

The fix for this APAR is currently targeted for inclusion in fix
pack 8.0.0.14 and 8.5.5.13 for WebSphere Application Server
Traditional Profile and 17.0.0.3 for WebSphere Application
Server Liberty Profile. 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
PI85250
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-07-31
Closed date
2017-10-02
Last modified date
2017-10-02

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:
03 May 2022

Tips

PI85250: HUNG THREAD ISSUE IN MYFACES _GETMETADATATARGET

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?