PK09237: AUTORESTART=TRUE ON THE JMS SERVER HAS NO AFFECT IN SOME CONDITIONS

 Fixes are available

PK09237; 5.1.1.3: AUTORESTART=True on the JMS server sometimes has no effect
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux



APAR status
Closed as program error.

Error description
Problem Description: EVen though the Auto Restart is set to
TRUE, the JMS Server will not restart under certain conditions.
i.e

We tried to kill the MQ processes using a kill -9. The JMS
Server shutsdown and won't restart.

Further analysis showed that terminate code currently has a
System.exit(99), which doesn't seem to be actually exiting the
JVM. j2ee.state.stopping or stopped notifications are sent out
causing the JMS server to gracefully shutdown and the nodeagent
does not see the need to restart it.

The JMSServer needs to terminate itself, essentially stop the
server without going through the normal shutdown so the
j2ee.state.stopping or stopped notifications are not sent out.
Local fix
NA
Problem summary
****************************************************************
* USERS AFFECTED: This problem affects customers who use the   *
*                 Java Message Service (JMS) functionality     *
*                 provided with WebSphere Application Server   *
*                 Network Deployment Version 5.1.x.            *
****************************************************************
* PROBLEM DESCRIPTION: 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.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the JMSServer stopped in this way, the master JMSServer
process was passing back a return code of 99 to the operating
system. As the process  had ended with a non-zero return
code, the AUTO_RESTART facility should have kicked in and
attempted to restart the JMSServer.

However, the application server Runtime was catching the
return code of 99, and performing a clean shutdown instead of
an immediate shutdown. Because of this, the Node Agent
assumed that the JMSServer had terminated normally, and would
not try to restart it automatically!
Problem conclusion
The mechanism used by the JMSServer to indicate to the Node
Agent that it has stopped due to a JMS Provider problem has
been modified. The new code causes the Node Agent to
automatically restart the JMSServer if it has stopped due to
an error with the underlying JMS Provider.

The fix for this APAR is currently targeted for inclusion
in Cumulative Fix 7 for WebSphere Application Server
Version 5.1.1. Please refer to the Recommended Updates page
for delivery information:


http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information
APAR number PK09237
Reported component name WAS NETWRK DEPL
Reported component ID 5630A3601
Reported release 10I
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-07-21
Closed date 2005-08-05
Last modified date 2005-08-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
MSGING RUNTIME        

Publications Referenced

Fix information
Fixed component name WAS NETWRK DEPL
Fixed component ID 5630A3601

Applicable component levels
R003 PSN    UP
R00A PSN    UP
R00H PSN    UP
R00I PSN    UP
R00P PSN    UP
R00S PSN    UP
R00W PSN    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 10I
Software edition:
Reference #: PK09237
IBM Group: Software Group
Modified date: Aug 5, 2005