Fix (APAR): WAS_Messaging_10-28-2003_5.0.2_cumulative_Fix Status: Fix Release: 5.0.2 Operating System: All Supersedes Fixes: WAS_Messaging_08-18-2003_5.0.2_cumulative_Fix CMVC Defect: PQ80087 Byte size of APAR: 26456 Date: 2003-10-29 Abstract: 2035 errors when using Access Manager for Business Integration Description/symptom of problem: When using transactions with Access Manager for Business Integration, the transactions frequently fail with reason code 2035 (OUT_OF_SYNCPOINT). This error comes about because the JMS wrappers provided by WebSphere Application Sever do not recognise the AMBI JMS classes as WebSphere MQ, which results in the wrong transactional behaviour being used. Directions to apply fix: NOTE: YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Fix Installer can be downloaded from the following link: http://www-3.ibm.com/software/webservers/appserv/support/index.html 1) Create temporary "fix" directory to store the jar file: UNIX: /tmp/WebSphere/fix Windows: c:\temp\WebSphere\fix 2) Copy jar file to the directory 3) Shutdown WebSphere 4) Follow the Fix installation instructions that are packaged with the Fix Installer on how to install the Fix. 5) Restart WebSphere 6) The temp directory may be removed. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE ORDER 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, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere 2) Follow the instructions that are packaged with the Fix Installer on how to uninstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Additional Information: To verify that the update has been installed successfully, dump the contents of the file messagingImpl.jar, and verify that the associated files have the size and timestamp shown: messagingImpl.jar 215 10-28-03 16:48 com/ibm/ejs/jms/JMSManagedConnection$1.class 2289 10-28-03 16:48 com/ibm/ejs/jms/JMSManagedConnection$JMSManagedConnectionMetaData.class 13367 10-28-03 16:48 com/ibm/ejs/jms/JMSManagedConnection.class 1739 10-28-03 16:48 com/ibm/ejs/jms/JMSManagedConnectionFactory$1.class 11299 10-28-03 16:48 com/ibm/ejs/jms/JMSManagedConnectionFactory.class 13356 10-28-03 16:48 com/ibm/ejs/jms/JMSSessionHandle.class 5890 10-28-03 16:48 com/ibm/ejs/jms/WSJMSManagedConnectionFactory.class