PQ79822: Timeout too short for JMSServer to initialize QueueManager, Channel Initiator, and Listener

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
JMS server fails BBOO0220E MSGS0001E appears as:
com.ibm.ws390.messaging.QueueManagerException

In the JMS log, these messages can be seen:

./bborjtr.cpp+812 ... BBOO0220E MSGS0001E: Starting the JMS
Server
failed with exception: com.ibm.ws390.messaging.QueueM
 anagerException:
 Error in MQConsole
  at
com.ibm.ws390.messaging.QueueManagerConsole.startQueueManager(Na
tive
Method)
  at
com.ibm.ws390.messaging.QueueManagerConsole.startQueueManager(Qu
eueManag
erConsole.java:68)
  at
com.ibm.ws390.messaging.QueueManagerManager.startQueueManager(Qu
eueManag
erManager.java:83)
  at
com.ibm.ws390.messaging.JMSEmbeddedProviderImpl.start(JMSEmbedde
dProvide
rImpl.java:155)
  at com.ibm.ws.messaging.JMSService.start(JMSService.java:266)
  at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(Conta
inerImpl
.java:343)
  at
com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.j
ava:234)
  at
com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:21
6)
  at com.ibm.ws.runtime.WsServer.start(WsServer.java:145)
  at com.ibm.ws.runtime.WsServer.main(WsServer.java:245)
  at
com.ibm.ws390.orb.CommonBridge.WsServerStartup(CommonBridge.java
:332)
  at
com.ibm.ws390.orb.ControlRegionBridge.initCSI(ControlRegionBridg
e.java:1
26)
  at
com.ibm.ws390.orb.ORBEJSBridge.initCSI(ORBEJSBridge.java:152)
  com.ibm.ws.messaging.JMSService
com.ibm.ws.messaging.JMSService


The current default timeout (of 30 sec) is too short for the
Queue Manager, Channel Initiator, and/or Listener to fully
initialize for the JMS server to come up.  This is dependant on
the performance of the system for these to come up successfully.
Local fix
Start up, manually, the Queue Manager, Channel Initiator, and
the Listener before starting up the WebSphere JMS server.


Stop any JMS server started and start these manually:

1. The Queue Manager,
 +WMQX START QMGR PARM(WMQXZPRM)
2. The Channel Initiator,
 +WMQX START CHINIT PARM(WMQXXPRM)
3. The Listener
 +WMQX START LISTENER PORT(5558)

Then start the JMS server.

 When WebSphere tries to start these jobs, the controller region
code should only get messages from the extended console saying
that these jobs are already started.  The reply back to the
extended console should be faster.  The initialization of the
server should be able to continue.

These are the completion messages that should be seen:

CSQ9022I +WMQX CSQYASCP 'START QMGR' NORMAL COMPLETION
S WMQXCHIN
CSQM138I +WMQX CSQMSCHI CHANNEL INITIATOR STARTING
CSQ9022I +WMQX CSQXCRPS ' START CHINIT' NORMAL COMPLETION
CSQM134I +WMQX CSQMSLIS START LISTENER TRPTYPE(TCP) COMMAND
CSQ9022I +WMQX CSQXCRPS ' START LISTENER' NORMAL COMPLETION

After these 3 JMS server components come up, you should be
able to start your JMS server.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: The JMS Server timeout value is         *
*                      currently set to 30 seconds. This value *
*                      can be too short for some systems. The  *
*                      timeout value needs to be modifiable.   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The JMS Server timeout value used for initialization of the
Queue Manager, Channel Inititator, and Listener is hard coded
to 30 seconds. This value can be too short for some systems and
cannot be changed. This problem surfaces with the following
message,
./bborjtr.cpp+812 ... BBOO0220E MSGS0001E: Starting the JMS
Server failed with exception:
com.ibm.ws390.messaging.QueueManagerException: Error in
MQConsole.
Problem conclusion
The variable control_region_jms_request_timeout was added to
specify the timeout value, in seconds, that the Controller
Region waits for a JMS request to complete. The requests include
starting or stopping the Queue Manager, Channel Initiator, and
Listener.

APAR PQ79822 requires a change to documentation. A change to the
InfoCenter will be made. To access the latest online
documentation, go to the product library page at:


http://publib.boulder.ibm.com/infocenter/wasinfo/

Created a new article titled "Common timeout settings":

Common timeout settings

This file lists common timer variables. Generally speaking,
increasing the timeout values should be your last resort, or
only a temporary action taken to prevent multiple timeout-abend
dumps from causing system performance problems.

control_region_jms_request_timeout

Specifies the time, in seconds, that the Controller Region waits
for a JMS request to complete. Requests include starting or
stopping the Queue Manager, Channel Initiator and Listener.

Data Type     Integer
Units         Seconds
Default       60
Range         0 to 2147040

APAR PQ79822 is associated with SERVICE LEVEL W502004 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ79822
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2003-10-20
Closed date 2004-03-10
Last modified date 2004-04-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UQ86037    UP04/03/17 P F403

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PQ79822.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ79822
IBM Group: Software Group
Modified date: Apr 3, 2004