Troubleshooting
Error log
The MQ server creates one log folder for each queue manager.
Windows:
C:\ProgramData\IBM\MQ\
Linux:
/var/mqm/qmgrs/
This folder contains a subfolder named errors. Current and detailed error messages can always be found in the file AMQERR01.LOG.
Rights
If the MQ server and the client are not authenticated using a common validation service, you may experience problems accessing the queues. In this case, the client receives the message that the user is not authorised to access the queue. The error log of the queue will contain additional information.
On the test server, the user check of the operating system user can be deactivated as follows.
"JMSWMQ1080": No dead letter queue defined
This error message appears in the internal server log (Server logs → internal → error.log) if there are problems loading the message from the MQ server.
As soon as a certain number of attempts has been made at pickup, the MQ server tries to put the message on a DLQ (Dead Letter Queue).
The error message JMSWMQ1080 indicates that no DLQ is specified in the addressed queue. This must be set up in menu item Storage.
After this, further error analysis is possible via the logs of the queue manager of the respective queue and DLQ (./mqm/qmgrs//errors).
Message format "MQSTR" instead of "MQHRF2"
If after an update of the WebSphere MQ server the messages are transmitted in the wrong message format MQSTR instead of MQHRF2, the following JVM parameter must be set.
|
-Dcom.ibm.mq.cfg.MessageProperties.PropctlToFORCE_RFH2=Yes |
JUnit test project
The following ZIP file is an Eclipse project with a JUnit test that allows you to test the connection of the virtual machine to the WebSphere MQ server.
If necessary, depending on the local configuration, the JNDI path in the JUnit test must be adapted to the .bindings file.
