Fix (APAR):  PK09237

Status:  Fix

Release:  5.1.1.3

Operating System:  All

Supersedes Fixes:  

CMVC Defect:  PK09237

Byte size of APAR:  202426

Date: 2005-08-08

Abstract:  JMSServer does not always auto-restart if the queue manager goes away

Description/symptom of problem:  When using the Embedded Messaging component with WebSphere Application Server Network Deployment, a separate application server is created whose sole purpose is to act as the JMS Provider. This server is known as the JMSServer.
  
If the underlying JMS resources are stopped unexpectedly, the JMSServer detects this and shuts itself down. When this happens, the following messages appear in the SystemOut.log file:

  MSGS0113E: The Queue Manager is no longer available - 
             MQException: com.ibm.mq.MQException:  MQJE001:
             Completion Code 2, Reason 2059      
  MSGS0017E: The JMS Server is performing a recovery
             termination due to a JMS Provider problem
  MSGS0054I: Stopping the Broker        
  MSGS0262W: Broker Manager unable to send shutdown message to
             Broker - MQException: com.ibm.mq.MQException:
             MQJE001: Completion 
  MSGS0251W: Broker Manager unable to disconnect from Queue
             Manager - MQException: com.ibm.mq.MQException:  
             MQJE001: Completion Code 2, Reason 2009
  MSGS0055I: Broker is stopped
  MSGS0056I: Stopping the Queue Manager
  MSGS0107E: End Command Server Server command failed with exit 
             code: 20
  MSGS0109E: End Queue Manager command failed with exit code: 40
  MSGS0057I: Queue Manager is stopped
   
At this point, the Node Agent process should attempt to automatically restart the JMSServer if the AUTORESTART=TRUE option has been specified. However, this does not happen, and the JMSServer must be restarted manually.       


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: