Troubleshooting the Agent Plug-in › JMS Job Failure Messages

JMS Job Failure Messages

This section provides common JMS job failure messages returned by the agent plug-in.

Note: For more information about MQJMSxxx exception messages, see Appendix I. JMS exception messages in the IBM documentation.

com/ibm/mq/MQException

Reason:

The com.ibm.mq JAR file is missing from the classpath of the agent plug-in.

Action:

Add the JAR file to the classpath of the agent plug-in.

java.lang.ClassCastException

Reason:

The com.ibm.mqjms jar file is missing from the classpath of the agent plug-in.

Action:

Add the JAR file to the classpath of the agent plug-in.

com.sun.jndi.fscontext.RefFSContextFactory Exception

Reason:

The fscontext.jar file is missing from the classpath of the agent plug-in.

Action:

Add the JAR file to the classpath of the agent plug-in.

com/sun/jndi/toolkit/chars/CharacterDecoder

Reason:

The providerutil.jar file is missing from the classpath of the agent plug-in.

Action:

Add the JAR file to the classpath of the agent plug-in.

Status is class name

Reason:

In general, if any status message is the name of a specific class, the specific class is not in the classpath of the agent plug-in.

Action:

Find the JAR that the class resides in, and add it to the classpath of the agent plug-in.

Cannot instantiate class: class name

Reason:

The class name for the initial context factory is incorrect.

Action:

Review the class name for the initial context factory and correct it for the JMS server you are using.

javax.naming.NameNotFoundException; remaining name '/bad/location'

Reason:

The provider URL you specified in the JMS job definition is incorrect.

Action:

Open the JMS job that failed, review the provider URL field, and correct it.

jndi connection factory name

Reason:

If the status message contains the value you entered for the connection factory in the job definition, then most likely no binding exists for this JNDI name.

Action:

Verify that the binding is defined correctly for the JMS server you are using and that the connection factory is spelled correctly.

jndi queue name

Reason:

If the status message contains the value you entered for the JNDI destination in the job definition, then most likely no binding exists for this JNDI name.

Action:

Verify that the binding is defined correctly for the JMS server you are using and that the JNDI destination is spelled correctly.

MQJMS2005: failed to create MQQueueManager for user ID:QM_user ID

Reason:

This message appears for the following reasons:

• The MQ queue manager and listener are not running.
• The JNDI binding for the MQ connection factory is incorrect.
• The host or port is incorrect.
• The queue manager name is missing or incorrect.

Action:

Verify that the MQ queue manager and listener are running. If so, double review your JNDI binding for the MQ connection factory. You may have specified an invalid host or port. If no queue manager name has been specified, verify that the default queue manager has been defined.

MQJMS2008: failed to open MQ queue

Reason:

This message appears when there is a problem with the MQ queue definition.

Action:

Verify that the MQ queue has been defined. If so, the JNDI binding for the MQ queue is most likely incorrect. Review the definition for spelling mistakes or case sensitivity issues.

java.lang.MyObject: Unable to instantiate the object

Reason:

The message class you specified in the JMS job definition is incorrect or is missing in the classpath of the agent plug-in.

Action:

Open the JMS job that failed, review the message class and correct it if necessary. Also ensure the message class you specified in the job definition is included in the classpath of the agent plug-in.

Invalid format, Unknown parameter type

Reason:

The parameter type for one of the message parameters in the JMS job definition is incorrect or is missing in the classpath of the agent plug-in.

Action:

Open the JMS job that has the SUBERROR state, review the types of the message parameters and make corrections if necessary. Also ensure the parameter type you specified in the job definition is included in the classpath of the agent plug-in.

No such plugin

Reason:

The J2EE plugin is not enabled for the agent plug-in.

Action:

Open the agentparm.txt file and edit the plugins.start_internal_n parameter, where n is the next available agent plug-in number.