PM41692: WHEN USING WEBSPHERE PROCESS SERVER 7.0.0.3, THE SERVER MAY HANG DURING SERIALIZATION OR XSLT PROCESSING.

8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• When using WebSphere Process Server or WebSphere Enterprise
  Service Bus (WESB) 7.0.0.3, the server may hang or you may get
  a Thread timeout during serialization or XSLT processing.
  This is due to internal corruption resulting in a cycle in the
  namespaces.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of the XML API for IBM WebSphere      *
  *                  Application Server V8.0                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: An internal cycle in the data model     *
  *                      may be introduced during certain        *
  *                      mutation operations.                    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  During some rare edge cases our internal data model may
  introduce a cycle in the namespace list which would cause an
  infinite loop for any applications that traverses it.
  

Problem conclusion

• These mutations are now correctly handled to avoid the
  introduction of any cycles in the internal data model.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.0.0.1.  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 is sysrouted FROM one or more of the following:

  PM23443

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

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R800 PSY