Troubleshooting Java and JMS problems

Use the advice that is given here to help you to resolve common problems that can arise when you are using Java or JMS applications.

Troubleshooting IBM MQ classes for JMS problems
You can investigate problems by running the installation verification programs, and by using the trace and log facilities.
JMS provider version troubleshooting
Use the advice that is given here to help you to resolve common problems that can arise when you are connecting to a queue manager with a specified provider version.
PCF processing in JMS
IBM MQ Programmable Change Format (PCF) messages are a flexible, powerful way in which to query and modify attributes of a queue manager, and the PCF classes that are provided in the IBM MQ classes for Java provide a convenient way of accessing their functionality in a Java application. The functionality can also be accessed from IBM MQ classes for JMS, but there is a potential problem.
JMS connection pool error handling
Connection pool error handling is carried out by various methods of a purge policy.
Troubleshooting JMSCC0108 messages
There are a number of steps that you can take to prevent a JMSCC0108 message from occurring when you are using activation specifications and WebSphere® Application Server listener ports that are running in Application Server Facilities (ASF) mode.
CWSJY0003W warning messages in WebSphere Application Server SystemOut.log file
A CWSJY0003W warning message is logged in the WebSphere Application Server SystemOut.log file when an MDB processes JMS messages from IBM MQ.
J2CA0027E messages containing the error The method 'xa_end' has failed with errorCode '100'
J2CA0027E messages appear in the WebSphere Application Server SystemOut.log containing the error The method 'xa_end' has failed with errorCode '100'.
2035 MQRC_NOT_AUTHORIZED when connecting to IBM MQ from WebSphere Application Server
The 2035 MQRC_NOT_AUTHORIZED error can occur when an application connects to IBM MQ from WebSphere Application Server.
Troubleshooting IBM MQ resource adapter problems
When using the IBM MQ resource adapter, most errors cause exceptions to be thrown, and these exceptions are reported to the user in a manner that depends on the application server. The resource adapter makes extensive use of linked exceptions to report problems. Typically, the first exception in a chain is a high-level description of the error, and subsequent exceptions in the chain provide the more detailed information that is required to diagnose the problem.
Using IBM MQ connection property override
Connection property override allows you to change the details that are used by a client application to connect to a queue manager, without modifying the source code.

Parent topic: Detailed troubleshooting

Related concepts

Using IBM MQ classes for JMS
Using the IBM MQ resource adapter
Using IBM MQ classes for Java

Related tasks

Tracing JMS/Jakarta Messaging and Java applications
Collecting troubleshooting information