Use this set of specific tips to help you troubleshoot
problems when using the WebSphere® MQ link or WebSphere MQ server components of the default
messaging provider to interoperate with WebSphere MQ.
Tips for WebSphere MQ link:
Tips for WebSphere MQ server:
The WebSphere MQ
link channels do not start
Error messages appear in the
SystemOut.log file
or, if you have turned on tracing, in the trace.log file.
Note: This topic references one or more of the application
server log files. As a recommended alternative, you can configure
the server to use the High Performance Extensible Logging (HPEL) log
and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use
HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access
all of your log and trace information using the LogViewer command-line
tool from your server profile bin directory. See the information
about using HPEL to troubleshoot applications for more information
on using HPEL.
- Verify that the channel names specified on the WebSphere MQ
link sender channel and/or the MQLinkReceiver definitions match those
specified on the sender and/or receiver channel definitions in the WebSphere MQ network.
Channel names
are case sensitive.
- Verify that the channel sequence numbers are not out of step.
If they are, then the channel will remain in a state of retry until
the sequence numbers have been reset.
For
a WebSphere MQ link sender channel, you can
reset the sequence number to 1 by using the WebSphere MQ
link sender channel administrative pages. This passes a reset instruction
to the WebSphere MQ receiver channel. You can
optionally reset the WebSphere MQ receiver channel
to a value that matches the WebSphere MQ link sender channel.
This does not result in any data being passed to the WebSphere MQ
link sender channel, and can be used to resolve sequencing issues.
For
a WebSphere MQ link receiver channel, you
have to reset the sequence number in WebSphere MQ through the WebSphere MQ
sender channel. If you are using the WebSphere MQ Explorer on a Windows system, you can right-click on the
channel and select .
Search for messages CWSIC3011E, CWSIC3015E.
- Verify that both ends of the channel have been defined and configured
correctly. It is possible that the channel at the remote end is currently
in a stopped state and therefore is currently unavailable. Start the
channel at the remote end if possible.
Search for messages CWSIC3018E, CWSIC3113E, CWSIC3114E, CWSIC3236E.
- Verify that the channel sequence number wrap values are the same
at both ends of the channel.
Search for message CWSIC3010E.
- Verify that the WebSphere MQ link sender channel
is not in an indoubt state. Resolve the channel if required. The
channel is resolved by WebSphere MQ.
On Windows, if you are using the WebSphere MQ Explorer, you can right-click
on the channel and select All Tasks>Resolve.
Search for message CWSIC3065E.
- Verify that the listeners have been started, and are listening
on the correct ports. By default, service integration listens on port
5558 for inbound connections, and the WebSphere MQ network listens on port
1414.
Messages sent across a WebSphere MQ
link are not delivered
Note: Error messages appear in the SystemOut.log file
or, if you have turned on tracing, in the trace.log file. You can
also look for equivalent messages in the WebSphere MQ error logs (or trace files
if you have turned on tracing in the WebSphere MQ network).
- If you are sending messages from a service integration bus to
a WebSphere MQ network, it is possible
that the messages are stored on the service integration bus and waiting
to be delivered, but that the WebSphere MQ link sender channel
has not been started or is in a retry state.
Verify that the WebSphere MQ link sender channel is started
and in running state.
- If you are sending messages from a WebSphere MQ network to a service integration
bus, it is possible that the messages are stored on the transmission
queue in the WebSphere MQ network
and waiting to be delivered, but that the sender channel in the WebSphere MQ network has not been started
or is in a retry state.
Verify that the sender channel in the WebSphere MQ network is started and in
running state.
- It is possible that the messages could not be processed or delivered
to the target destination and hence they have been placed either on
an exception destination on the service integration bus, or on the
dead letter queue in the WebSphere MQ network. Verify
that the WebSphere MQ Link on the
messaging engine is configured properly with the correct foreign bus,
queue manager name (service integration bus), sender channel and
receiver channel. The sender channel on the WebSphere MQ Link should match the receiver
channel on WebSphere MQ. The receiver
channel on the WebSphere MQ Link
should match the sender channel on WebSphere MQ.
Search for messages CWSIC3096I, CWSIC3098I, CWSIC3200E, CWSIC3209E.
Check
the exception destinations and the dead letter queue. It is possible
that the target destination has not been defined, or is full in which
case, determine why messages are not being processed from the target
destination.
- It is possible that the target destination and the exception destination
and/or the dead letter queue are full and that subsequent persistent
messages cannot be safely delivered. Under these circumstances the
channel is stopped to avoid any loss of messages.
Search for
message CWSIP0291W.
Determine why messages are
not being processed from the target destination.
- It is possible that the target destination and the exception destination
and/or dead letter queue are full and that subsequent nonpersistent
messages are discarded.
Check the persistence of messages being
generated by your applications.
- It is possible that the channel has stopped because the remote
system cannot accept messages for some reason.
Search for message CWSIC3080E.
The application server cannot shut down
If
a WebSphere MQ link sender channel does not
have any messages to deliver, it waits for its specified disconnect
interval before timing out. If the application server is shut down
while a WebSphere MQ link sender channel is in
a wait state, the application server waits for the WebSphere MQ
link sender channel to time out before shutting down. A long disconnect
interval might delay the server shutdown.
If the application
server shutdown is delayed by a WebSphere MQ
link sender channel in a wait state, you have two options:
- Attempt to put a message onto the transmission item stream for
the WebSphere MQ link sender channel. Note
that this might not take the channel out of its wait state if the
application server shutdown is already in progress
- Force the termination of the application server process.
To reduce possible delays during application server shutdown,
you can specify a smaller value for the disconnect interval. Note
that a discount interval of 0 indicates an indefinite wait. For more
information about setting the disconnect interval for a WebSphere MQ
link sender channel, see Adding or modifying a WebSphere MQ link sender channel.
JMS attempts to send a message to a WebSphere MQ server
The
JMS application attempts to send a message to a WebSphere MQ
server, a long list of internal error exception messages are issued.
This occurs when a WebSphere MQ server is configured
to connect to an unsupported version of WebSphere MQ.
In this situation,
any attempt by a JMS application to send a message to a service integration
bus destination that is a defined to a WebSphere MQ
server bus member results in a long list of exception messages. The
CWSJP0019E message indicates that it is a version problem:
com.ibm.ws.sib.remote.mq.exceptions.CorruptRMQSessionException:
CWSJP0019E: An attempt to connect to WebSphere MQ using the information that is
provided by the WebSphere MQ Server bus member MQServer1-BUS1 resulted in a
connection to a WebSphere MQ queue manager running on version MQCMDL_LEVEL_600
on platform MQPL_WINDOWS_NT. This configuration is not supported. Destinations
that are assigned to the WebSphere MQ Server bus member are not accessible.
Verify
that you have configured the WebSphere MQ server to interoperate
with a supported version of WebSphere MQ. For interoperation with WebSphere Application Server Version 7.0 or later, the version of WebSphere MQ must be WebSphere MQ for z/OS Version 6 or later, or WebSphere MQ (distributed platforms) Version 7 or later.