PQ80524: JMSSERVER IN NETWORK DEPLOYMENT ENVIRONMENT DOES NOT START UP DUE TO QUEUE MANAGER NAME AND PORT BEING NULL

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Starting up JMS Server in an Network Deployment environment can
result in an Abend A03.  This can be seen in JMS Server job
output:

BBOO0222I MSGS0050I: Starting the Queue Manager
BBOO0222I MSGS0056I: Stopping the Queue Manager
BBOO0222I MSGS0057I: Queue Manager is stopped
IEA995I SYMPTOM DUMP OUTPUT
SYSTEM COMPLETION CODE=A03
 TIME=11.01.56  SEQ=00312  CPU=0000  ASID=03EA

After turning on tracing,
startupTraceSpecification="JMSServer=all=enabled"
You can see that the queue manager name and port number are
null:

Trace: 2003/11/05 18:24:11.254 01 t=7FF140 c=UNK key=S2
(13007002)
FunctionName: com.ibm.ws390.messaging.JMSEmbeddedProviderImpl
SourceId: com.ibm.ws390.messaging.JMSEmbeddedProviderImpl
Category: DEBUG
ExtendedMessage: Queue Manager Name; nullnull

There has been a problem of this in the ND environment.  This
would work on Base since the display name of the base server
is server1 the same as the server name.  But in ND, the JMS
configuratoin is in a server of its own, which has the display
name of JMSServer, but the actual server name is 'jmsserver'.
As you see, the configuration is then looked into
'JMSServer/server.xml' which does not exist.  Changing the
JMSServer display name from 'JMSServer' to 'jmsserver' would
cause the configuration to be looked at 'jmsserver/server.xml'
which does exist in the HFS.

MD18273
Local fix
A jar file fix can be obtained from WebSphere Level 2 through
normal IBM support process.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: Cannot start MQ Queue Manager in an ND  *
*                      configuration.                          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the server tries to start the queue manager it fails to
start the queue manager. The message MSGS0001E is shown. This
problem is caused when the Display Name of the JMSServer is
different from the actual JMSServer Server Name. During JMS
registration, the JMSServer short queue manager name and prefix
properties cannot be read from the server.xml causing the
usage of null variables during the call to start the queue
manager.
Problem conclusion
Changed JMS registration logic to use the JMSServer Server Name
instead of the JMSServer Server Display Name.

APAR PQ80524 is associated with SERVICE LEVEL W502000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ80524
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-11-05
Closed date 2003-12-07
Last modified date 2004-01-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 UQ82904    UP03/12/15 P F312

  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: swg1PQ80524.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 #: PQ80524
IBM Group: Software Group
Modified date: Jan 3, 2004