Fix (APAR):  JR28733

Status:  Fix

Release:  6.1

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  10998

Date: 2008-03-30

Abstract:  If a business object has no target namespace, MQ JMS binding would throw NullPointerException while parsing this object.

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

ERROR DESCRIPTION:                                              
"NullPointerException when working with MQ JMS Export"          
When an MQ JMS Export receives a Business Objects whose XSD     
definition has no namespace (i.e. null namespace), the          
following exception is generated at runtime:                    
                                                                
 [3/17/08 9:13:50:109 CET] 00000056 ServerSession W   WMSG0031E:
 Exception processing JMS Message for MDB                       
_export.DumpBOExportMQJMS,                                      
 JMSDestination jms/Q1 : java.lang.NullPointerException         
  at                                                            
com.ibm.wsspi.sca.jms.data.JMSParsableNativeDataHolder.getBody( 
                                                                
JMSParsableNativeDataHolder.java:269)                           
  at                                                            
com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.getBody(
                                                                
ManagedMessageImpl.java:1149)                                   

LOCAL FIX:                                                      
-                                                               

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server 6.1 users who use
MQ JMS binding with a business object
which has no target namespace.

PROBLEM DESCRIPTION:
If a business object has no target
namespace, MQ JMS binding would throw
NullPointerException while parsing
this object.

RECOMMENDATION:
None

The code was not checking for the business object's URI to be
null.

PROBLEM CONCLUSION:                                             
Checking code was added for the business object with no target  
namespace. The problem is resolved after applying the interim   
fix.                                                            


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

3) Run the UpdateInstaller and follow the prompts.

4) Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH THEY WERE APPLIED.  DO NOT REMOVE A FIX UNLESS  ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED FIX.

Example:  If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: