IBM Support

PM63322: MYFACES HANGS IN DEFAULTRESTOREVIEWSUPPORT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • MyFaces hangs in DefaultRestoreViewSupport.handlePrefixMapping
    while executing thread in a portlet environment:
    
    Stack trace :
    ----------------------------------------------------------------
    at java/lang/String.substring(String.java:1105(Compiled Code))
    at org/apache/myfaces/lifecycle/DefaultRestoreViewSupport
    
    .handlePrefixMapping(DefaultRestoreViewSupport.java:290(Compiled
    Code))
    at org/apache/myfaces/lifecycle/DefaultRestoreViewSupport
         .deriveViewId(DefaultRestoreViewSupport.java:222)
    at org/apache/myfaces/lifecycle/RestoreViewExecutor
         .execute(RestoreViewExecutor.java:150)
    at org/apache/myfaces/lifecycle/LifecycleImpl
         .executePhase(LifecycleImpl.java:171)
    at org/apache/myfaces/lifecycle/LifecycleImpl
         .execute(LifecycleImpl.java:118)
    at org/portletfaces/bridge/BridgeImpl
         .doFacesRequest(BridgeImpl.java:402)
    at org/portletfaces/bridge/GenericFacesPortlet
         .doView(GenericFacesPortlet.java:181)
    at javax/portlet/GenericPortlet
         .doDispatch(GenericPortlet.java:328)
    ----------------------------------------------------------------
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server Versions   *
    *                  8.0 and 8.5 users of JavaServer Faces(JSF)  *
    *                  MyFaces.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: A Thread hang occurs in the MyFaces     *
    *                      DefaultRestoreViewSupport.handlePrefixM *
    *                      apping method.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A Thread hang, caused by an infinite loop, can be seen in the
    WebSphere Application Server logs.  Here is an example of a
    similar message:
    3/14/12 11:34:12:953 EDT] 00000024 ThreadMonitor W
    WSVR0605W: Thread
    "WebContainer : 0" (00000022) has been active for 749937
    milliseconds
    and may be hung.  There is/are 1 thread(s) in total in the
    server that
    may be hung.
    at java.lang.String.substring(String.java:1105)
    at
    org.apache.myfaces.lifecycle.DefaultRestoreViewSupport.handlePre
    fixMapping(DefaultRestoreViewSupport.java:290)
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM63322

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-25

  • Closed date

    2012-06-07

  • Last modified date

    2012-07-17

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

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

    PM80277

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

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

Document Information

Modified date:
28 October 2021