PI08812: NULLPOINTEREXCEPTION IS THROWN WHEN USING A JMS OBJECT WHICH HAS ALREADY BEEN DESTROYED

8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
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.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.14: WebSphere Application Server V8.5.5 Fix Pack 14
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

• In some cases, if a JMS object handle has been destroyed and is
  no longer valid, but the application is still using it,
  NullPointerException will be thrown which is not reflecting the
  root cause of the issue.
  
  An example call stack for this error is:
  
  StackTrace=java.lang.NullPointerException
   at
  com.ibm.ejs.j2c.ConnectionManager.associateConnection(Connection
  Manager.java:2883)
   at
  com.ibm.ejs.jms.JMSSessionHandle.getOpenSession(JMSSessionHandle
  .java:1322)
   at
  com.ibm.ejs.jms.JMSQueueSessionHandle.getOpenQueueSession(JMSQue
  ueSessionHandle.java:410)
   at
  com.ibm.ejs.jms.JMSQueueReceiverHandle.getOpenQueueReceiver(JMSQ
  ueueReceiverHandle.java:251)
   at
  com.ibm.ejs.jms.JMSQueueReceiverHandle.getOpenMessageConsumer(JM
  SQueueReceiverHandle.java:233)
   at
  com.ibm.ejs.jms.JMSMessageConsumerHandle.receiveNoWait(JMSMessag
  eConsumerHandle.java:612)
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  WebSphere Application Server users of JMS.  *
  ****************************************************************
  * PROBLEM DESCRIPTION: java.lang.NullPointerException          *
  *                      occurs in a JMS application.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a JMS object derived from a JMS Connection (such as a
  Session or QueueBrowser) is used after the JMS Connection has
  become invalidated, a java.lang.NullPointerException may
  occur.
  Instead, a javax.jms.IllegalStateException would reflect the
  problem more accurately.
  

Problem conclusion

• This APAR prevents the NullPointerException by ensuring that
  the JMS Session checks the JMS Connection that created it is
  still valid before performing an action that will fail if the
  Connection is invalid.  If it is not valid a
  javax.jms.IllegalStateException is thrown.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.3.  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:

• 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

• R850 PSY

     UP