Common problems
- Client is unable to connect to server - it appears to hang
- Check that the communications protocol being used by the client matches
the protocol being used by the server.
- Messages are stuck
- Ensure that the channel timeout settings are appropriate for the network.
- Ensure that the adapter timeout settings are appropriate for the network
- Home server queue stops pulling messages from the store queue
- The home server queue has a polling interval that may be set. However
if the thread polling the queue terminates unexpectedly, no exception is thrown
to the application. An alternative approach is to set the poll interval to
zero, and implement a queue manager rule to loop on a call to trigger transmission.
- Asynchronous remote queue does not send message in a timely manner
- By default an asynchronous remote queue will attempt to send a message
when it is put to the queue. If the background thread is unsuccessful for
any reason, then no attempt is made to resend the message until another message
is placed on the queue. To avoid this, implement a queue manager rule to
loop on a call to trigger transmission.
- Cannot create bridge definitions
- Check that the MQe bridge classes are on the CLASSPATH
- Check that the MQ Java™ classes are on the CLASSPATH