PI44066: WSGRID ISSUE WHEN RESTARTING THE MESSAGING ENGINE INSIDE THE ADM INISTRATIVE CONSOLE

8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.0.0.5: WebSphere Extended Deployment Compute Grid V8.0 Fix Pack 5
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• When the messaging engine is restarted the JMS session is
  refreshed but the code was not getting a new JMS session
  producing an error and causing the WSGrid client to hang in a
  time-wait state
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  Users of IBM WebSphere Extended Deployment  *
  *                  Compute Grid 8.0 and the batch function     *
  *                  of WebSphere Application Server 8.5.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: WSGrid issue when restarting the        *
  *                      messaging engine inside the             *
  *                      administrative console                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When the messaging engine is restarted the JMS session is
  refreshed, but the code was not getting a new JMS session and
  was producing an Exception. This caused the WSGrid client to
  hang in a time-wait state indefinitely.
  

Problem conclusion

• A catch for the Exception was added and this closed the old
  JMS session and connected to the new one to allow for
  communication between WSGrid and the messaging engine again.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.7.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

• An interim fix is available upon request.
  

Comments

APAR Information

• 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