PH37169: NULLPOINTEREXCEPTION WHEN WMQ_JMS_CLIENT_DETAILS TAG IS MISSING IN OSGI BUNDLE

APAR status

• Closed as program error.

Error description

• When the messaging component is destroyed it tries to check
  whether the existing bundle in the cache should be removed from
  it. If WMQ_JMS_CLIENT_DETAILS tag was missing from the bundle's
  header then the following NPE is thrown:
  
  [4/21/21 18:27:08:277 MSK] 0000003f ContainerHelp E   WSVR0103E:
  An error occurred destroying,
  com.ibm.ejs.jms.JMSRegistration@ea3b1a04
  
  java.lang.NullPointerException
  
  	at java.util.StringTokenizer.<init>(StringTokenizer.java:210)
  
  	at java.util.StringTokenizer.<init>(StringTokenizer.java:232)
  
  	at com.ibm.ejs.jms.JMSRegistrationHelper.hasInstallContentChan
  ged(JMSRegistrationHelper.java:435)
  
  	at com.ibm.ejs.jms.JMSRegistrationHelper.destroy(JMSRegistrati
  onHelper.java:1164)
  
  	at com.ibm.ejs.jms.JMSRegistration.destroy(JMSRegistration.jav
  a:727)
  
  	...
  
  The NPE is ugly and also prevents that execution of the app
  server from un-installing the corrupted bundle when shutting
  down.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: In some cases, when the component       *
  *                      cache is being refreshed, the MQ        *
  *                      messaging component can throw a         *
  *                      NullPointerException.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If the WMQ_JMS_CLIENT_DETAILS tag is missing from the MQ
  messaging bundle (possibly because a fixed
  version of the code has been applied) then the check to see
  whether the files have changed will fail with a
  NullPointerException
  

Problem conclusion

• The code has been changed to avoid the NullPointerException
  and the component will be reloaded.
  
  The fix for this APAR is targeted for inclusion in fix pack
  8.5.5.22 and 9.0.5.12. For more information, see 'Recommended
  Updates for WebSphere Application Server':
  https://www.ibm.com/support/pages/node/715553
  

Temporary fix

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