Fix (APAR):  JR27376

Status:  Fix

Release:  6.0.2.2,6.0.2.1

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  9353

Date: 2007-09-28

Abstract:  An UnsupportedCharsetException is thrown, when using Service Component Architecture (SCA) MQ binding.

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

ERROR DESCRIPTION:                                              
Our customer is using SUN 1.4.2 JDK, there is a limitation to   
support charset IBM850. Only 1.5 can support it. But now WPS    
only support JDK 1.4.2 level.                                   
                                                                
The following exceptions are thrown:                            
-----------                                                     
Exception processing JMS Message for MDB                        
export.ReceiveCIMResponseMQ,                                    
JMSDestination jms/QCprBalanceInquiryResponse :                 
java.nio.charset.UnsupportedCharsetException: IBM850            
        at java.nio.charset.Charset.forName(Charset.java:486)   
        at com.ibm.mq.data.impl.CharacterSet.<init>             
(CharacterSet.java:138)                                         
        at com.ibm.mq.data.impl.CharacterSet.forCCSID           
(CharacterSet.java:148)                                         
        at com.ibm.mq.data.impl.InternalMQDataInput.setCCSID    
(InternalMQDataInput.java:79)                                   
        at com.ibm.mq.data.MQDataInputStream.setCCSID           
(MQDataInputStream.java:63)                                     
        at                                                      
com.ibm.ws.sca.internal.mq.ReadingBindingHelper.getFunctionSelec
torStrea                                                        
m(ReadingBindingHelper.java:238)                                
        at com.ibm.wsspi.sca.mq.inbound.MQInboundImpl.onMessage 
(MQInboundImpl.java:192)                                        
        at                                                      
com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run    
(MDBWrapper.java:319)                                           
        at                                                      
com.ibm.ws.security.util.AccessController.doPrivileged          
(AccessController.java:63)                                      
        at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage    
(MDBWrapper.java:288)                                           
        at com.ibm.ejs.jms.listener.MDBWrapper.onMessage        
(MDBWrapper.java:266)                                           
        at com.ibm.mq.jms.MQSession.run(MQSession.java:1742)    
        at com.ibm.ejs.jms.JMSSessionHandle.run                 
                                                                
-------------------------                                       

LOCAL FIX:                                                      
No local fix                                                    

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server and WebSphere
Enterprise Service Bus 6.0.2.1 and 6.0.2.2
users

PROBLEM DESCRIPTION:
An UnsupportedCharsetException is
thrown, when using Service Component
Architecture (SCA) MQ binding.

RECOMMENDATION:
None

In a solaris environment, if Service Component Architecture
(SCA) MQ binding is used with CCSID 850,
java.nio.charset.UnsupportedCharsetException is thrown.

PROBLEM CONCLUSION:                                             
This problem has been fixed by handling char set correctly in   
Service Component Architecture (SCA) MQ binding.                


Directions to apply fix:  
Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system.
Also 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

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. 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

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: