Fix (APAR):  PI08466

Status:  Fix

Release:  8.0.0.8

Operating System:  AIX,HP-UX,IBM i,Linux,Mac OS,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  255539

Date: 2014-04-02

Abstract:  nullpointerexception at com.ibm.ejs.jms.jmssessionhandle.getopensession after pm92408

Description/symptom of problem:  
PI08466 resolves the following problem:

ERROR DESCRIPTION:                                              
After applying maintenance that contains PM92408                
(inlcuding 8.5.5.1 and 8.0.0.8) a NullPointerException may      
be thrown.  The stack of the exception is:                      
                                                                
at                                                              
com.ibm.ejs.jms.JMSSessionHandle.getOpenSession                 
(JMSSessionHandle.java:1332)                                    
at com.ibm.ejs.jms.JMSQueueSessionHandle.getOpenQueueSession    
at com.ibm.ejs.jms.JMSQueueReceiverHandle.getOpenQueueReceiver  
at com.ibm.ejs.jms.JMSQueueReceiverHandle                       
.getOpenMessageConsumer                                         
at com.ibm.ejs.jms.JMSMessageConsumerHandle.receiveNoWait       
...                                                             
                                                                
This is due to regression introduced when PM92408 was ported    
from earlier releases.  The regression is only in v8.0          
upawards, v7.0 is unaffected.                                   

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
 All users of IBM WebSphere Application
Server

PROBLEM DESCRIPTION:
NullPointerException possible
following PM92408.

RECOMMENDATION:
None

An editting error when forward porting PM92408 from version 7
resulted in the inadvertent change of state maintained in the
JMSSessionHandle.  As a result, when the Session is reused by
an application across transaction boundaries the handle fails
to reassociate with a managed connection.  The
NullPointerException ensues when the Session handle is reused.

PROBLEM CONCLUSION:                                             
This APAR resolves the problem by correcting the state that     
was changed inadvertently.                                      
                                                                
The fix for this APAR is currently targeted for inclusion in    
fix pack 8.5.5.2 and 8.0.0.9.  Please refer to the Recommended  
Updates page for delivery information:                          
                                                                
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   


Directions to apply fix:  Fix applies to Editions:
Release 8.0
X Application Server (Express or BASE)
X Network Deployment (ND)
__ Edge Components
__ Developer

Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

Directions to re-apply fix:  
1) Shutdown WebSphere Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: