|
Problem(Abstract) |
Your application runs on IBM® WebSphere® Application
Server V5 or V6. It uses JMS to connect to a WebSphere MQ messaging system
and may receive an MQJMS2005 error with reason code 2059. |
|
|
|
Cause |
Reason code 2059 means that the queue manager is not
available.
The most likely cause of the problem is that the queue manager is not
running or that the queue manager listener is not running. Another
possible cause is that the queue manager name that is specified on the JMS
connection factory is incorrect.
The queue manager might fail to start due to the following
problems:
- The queue manager may have failed to start due to an error.
- If embedded messaging in WebSphere Application Server V5 is used, the
createmq script that creates the embedded queue manager may have
failed to complete successfully.
- If embedded messaging is used in a WebSphere Application Server V5
Network Deployment environment, the jmsserver may have not been
started.
|
|
|
Resolving the
problem |
This technote
has additional information on how to resolve reason code 2059 problems.
Confirm that the queue manager is up and running and that the listener is
running
- Ensure that the queue manager is running. You can use the
dspmq command to verify this. The status of the queue manager
should be Running.
- Check the MQ FDC files in the MQ_install_root/errors and
MQ_install_root/qmgrs/queue_manager_name/errors directories
to see what relevant error messages may be logged there.
- Check that the queue manager is the default queue manager. If there is
no default queue manager, then define one. This can be set in the mqs.ini
file. See the WebSphere MQ
System Administration Guide for more information.
- Ensure that the queue manager has a listener running and is listening
on the right port.
Start the listener program using the following command:
runmqlsr -t tcp -p <port_number> -m <qmgr_name>
Verify that the createmq script ran without
errors (when using embedded messaging)
Check the createMQ_nodename_servername.log file in the
WAS_install_root/logs directory. It contains the results of the
createmq script that WebSphere Application Server used to create
the embedded queue manager. Confirm that the crtmqm,
strmqm, runmqsc, wempscreatebroker, and
wempsservice commands all finish with rc=0. If you see errors,
you should run deletemq and createmq to recreate the
embedded queue manager. Note that if you have already run
deletemq and createmq since product installation, you
need to pipe the output of createmq to a file to get this output.
Verify that the jmsserver is started (when
using embedded messaging in an Network Deployment environment)
Use the serverStatus command to
confirm that the jmsserver JVM has started. Check the
SystemOut.log for the jmsserver to see if there are any errors
when starting it.
Other possible causes for the reason code 2059
If you are using the CLIENT transport type to connect to the
queue manager on an IPv4/IPv6 dual stacked machine, then refer to this technote.
If you set the CCSID, then check this technote.
For more information on the WebSphere Application Server createmq command,
refer to this createmq
command article in the WebSphere Application Server 5.1 Information
Center. This is the link for the deletemq
command. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|