+

Search Tips   |   Advanced Search

Messaging troubleshooting tips


These tips are to help you troubleshoot the WebSphere messaging configuration.

To help you resolve problems with messaging, use the WAS trace and logging facilities.

If having problems deploying or running applications that use the WAS messaging capabilities, see the following topics:

If we see WebSphere MQ error messages or reason codes in WAS messages and logs, refer to the WebSphere MQ Messages document.

Check to see if the problem has been identified and documented using the links in Diagnose and fix problems: Links.

Here is a set of tips to help you troubleshoot commonly-experienced problems. If we do not see a problem that resembles thes, or if the information provided does not solve the problem, contact IBM support for further assistance.

 

When you migrate WAS profiles between maintenance level 7.0.0.0 and later levels, manually adjust the WebSphere MQ resource adapter configuration

The code provided by the WebSphere MQ resource adapter is used by the WebSphere MQ messaging provider, and also by the WebSphere MQ link and WebSphere MQ server features of the default messaging provider. In profiles created at WAS maintenance level 7.0.0.0, the WebSphere MQ resource adapter binary files are located in each profile. In profiles created at WAS maintenance level 7.0.0.1 or later, these binary files are located in the APP_ROOT directory. When you apply maintenance to a WAS V7 installation, the maintenance pack only updates the WebSphere MQ resource adapter binary files in the APP_ROOT directory. This behavior gives rise to the following scenarios:

To resolve these issues, see Adjusting the WebSphere MQ resource adapter configuration when migrating profiles between maintenance level 7.0.0.0 and later levels.

 

Messages from WebSphere MQ for z/OS are not being consumed by JMS applications that are deployed into WAS and that use connection factories or activation specifications

There is a known restriction which means that, when you use the WebSphere MQ messaging provider to connect to a recent version of WebSphere MQ for z/OS, configure the connection factories and activation specifications to treat the WebSphere MQ for z/OS network as if it were a WebSphere MQ for z/OS V6.0 network. Specifically, configure the Provider version property of each associated connection factory or activation specification with a value of 6.0.0.0.

See about how to do this, see any of the following topics:

 

A JMS application can no longer send or receive messages, or a destination becomes full and can no longer receive messages

When you configure an application to use the default messaging provider, you associate it with either of the following resource sets:

To help resolve this problem, use the following admin console panels to inspect the configuration of the applications and JMS resources:

 

javax.jms.JMSException: MQJMS2008: failed to open MQ queue in JVM log

This error can occur when the WebSphere MQ queue name is not defined in the internal JMS server queue names list. This problem can occur if a WAS queue destination is created without adding the queue name to the internal JMS server queue names list. To resolve this problem:

  1. Start the WAS admin console.

  2. Navigate to Servers > Server Types > V5 JMS servers

  3. Add the queue name to the list.

  4. Save the changes and restart the server.

 

javax.jms.JMSException: MQJMS3024: unable to start MDB listener

This error can occur if an uninitialized client ID is used (that is a client ID not associated with a durable subscription). To resolve this problem, set the client ID in one of the following three ways:

 

SVC: jms.BrokerCommandFailedExceptfailed: 3008

One possible cause for this error is that you logged on to a Windows 2000 system as an administrator.

To resolve this problem, log out and log in again as a user, rather than an administrator.

 

An MDB listener fails to start

If an MDB listener deployed against a listener port fails to start, you should see the following message: 

WMSG0019E: Unable to start MDB Listener {0}, JMSDestination {1} : {2}

To help resolve this problem, check the following factors:

 

Problems running JMS applications with security enabled

When you try to run a JMS application with security enabled, we can encounter authentication problems indicated by one or more of the following error messages: 

WMSG0019E: Unable to start MDB Listener PSSampleMDB, JMSDestination Sample/JMS/listen : javax.jms.JMSSecurityException:
This example indicates that the security credentials supplied are not valid. To resolve this problem, check the security configuration: 

MQJMS2013 invalid security authentication supplied for MQQueueManager:

If we are using WebSphere MQ as a JMS provider, with JMS connection using bindings transport mode, and the user specified is not the current logged-on user for the WAS process, the JMS bindings authentication by WebSphere MQ generates an invalid security authentication error. To resolve this problem, check the security configuration. When you configure the WebSphere MQ JMS provider to use bindings transport mode, you set the property Transport type to BINDINGS on the WebSphere MQ queue connection factory. At this time, you also choose one of the following options:

See about messaging security, see Secure messaging.

 

Application server does not start when the zh_TW.EUC locale is set on Solaris

On Solaris, if we set the locale to zh_TW.EUC and we are using WebSphere MQ as a JMS provider, the appservers might not start up.

To resolve this problem, set the LANG and LC_ALL variables to zh_TW.

 

Server memory consumption and java.lang.OutOfMemoryError exception when processing JMS messages

When you use the default messaging provider, JMS messages are processed by a messaging engine within the appserver process. This approach consumes memory from the appserver's JVM heap. If there is significant concurrent processing of large messages, and the amount of memory available to the JVM heap is not enough to handle this event, then a java.lang.OutOfMemoryError exception is thrown and the application server terminates. To resolve this problem, estimate the potential number of concurrent processors or consumers of messages and the message sizes, then set the size of the appserver's JVM heap to handle the effect. For example:

  1. When you deploy a message-driven bean that processes messages concurrently, estimate the potential consumption of the application server's memory by concurrent endpoints. Note that each endpoint that is concurrently processing a message request adds at least two times the message size to the server's JVM heap and can add more, especially if a two-phase transaction is in place.

  2. Start the WAS admin console.

  3. Navigate to Servers > Server Types > WebSphere application servers > server_name > Java and Process Management > Process Definition > Java Virtual Machine, then configure the amount of memory available to the appserver's JVM heap by setting the Initial Heap Size and Maximum Heap Size properties.

  4. Navigate to Resources > JMS > JMS providers > Default messaging provider > Activation specifications > activation_specification_name , then configure the number of concurrent MDB endpoints that can process messages by setting the Maximum concurrent endpoints property of the activation spec for this message-driven bean.

 

TopicConnectionFactory attributes clash error when using "Basic" WebSphere MQ broker (MA0C SupportPac broker)

When you create a JMS topic subscriber that uses the WebSphere MQ messaging provider, the following error message can occur in SystemOut.log: 

WSVR0017E: Error encountered binding the J2EE resource, TopicConnectionFactory, as <JNDI_NAME>
   from file:<RESOURCES_FILE> com.ibm.ws.runtime.component.binder.ResourceBindingException: invalid
   configuration passed to resource binding logic. REASON: Failed to create connection factory:
   Error raised constructing AdminObject, error code:  TopicConnectionFactory attributes clash  : 
   TopicConnectionFactory attributes clash

This problem is caused by the configuration of the JMS topic connection factory used to create the subscriber, which specifies a broker version of "Basic" and a message selection value of "Broker". The "Basic" WebSphere MQ broker (MA0C SupportPac broker) does not support "Broker" message selection.

To resolve this problem, change the JMS topic connection factory to specify a message selection value of "Client", which is the only supported value for the WebSphere MQ Basic broker (MA0C SupportPac broker).

 

WSEC5061E: The SOAP Body is not signed exception is issued when running a secured Web services application using JMS transport and WebSphere MQ

When you run a secured Web services application that uses JMS transport under the WebSphere MQ messaging provider, the following error message can occur in the SystemOut.log file: 

com.ibm.wsspi.wssecurity.SoapSecurityException: WSEC5061E: The SOAP Body is not signed.; null

This problem occurs under the following circumstances:

The problem occurs when a request sent from the original application is processed through the same queue, but to the different appserver where security is not enabled. To resolve this problem:

  1. Create a unique queue manager with a unique port in the WebSphere MQ server.

  2. Reconfigure the JMS resources to use the new queue manager and port; for example, by using the WAS admin console to change the properties of the WebSphere MQ queue connection factory.

  3. Rerun the application.

 

Message MQJMS1006: invalid value for tempQPrefix is issued when trying to use a V5.1 client with a V5 default messaging provider queue connection factory on a Version 7 appserver

When you use a WAS V5.1 application client to connect to a queue connection factory defined as a "V5 default messaging provider"" resource on a WAS V7 appserver, the following message is displayed: 

com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI
   NamingManager was processing a javax.naming.Reference object.   Root exception is com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred
   while the JNDI NamingManager was processing a javax.naming.Reference object.   Root exception is javax.jms.JMSException: MQJMS1006: invalid value for tempQPrefix:

This problem occurs when the application client is using WebSphere MQ JMS client CSD 04 JAR files. WAS V7 sets the tempQprefix property to blank, and this value cannot be handled by the CSD 04 release of the setTempqPrefix method.

To resolve this problem:

 

When you use WebSphere MQ as an external JMS provider, messages sent within a user-managed transaction arrive before the transaction commits

When you use WebSphere MQ as an external JMS provider, and you send a message to a WebSphere MQ queue within a user-managed transaction, the message can arrive on the destination queue before the transaction commits. This problem occurs when the WebSphere MQ resource manager is not enlisted in the user-managed transaction.

To resolve this problem, use a container-managed transaction.

 

javax.jms.JMSException: MQJMS3024: unable to start MDB listener

This error can occur if we use an uninitialized client ID (that is, a client ID not associated with a durable subscription). To resolve this problem, set the client ID in one of the following three ways:

 

SVC: jms.BrokerCommandFailedExceptfailed: 3008

This error can occur when you log in to a Windows 2000 system as an administrator.

To resolve this problem, log out and log in again as a user, rather than an administrator.


Subtopics


WebSphere MQ connection and queue connection factory creation errors

 

Related tasks


Troubleshooting message-driven beans
Troubleshooting performance monitoring statistics
WebSphere MQ messaging provider topic connection factory settings
Troubleshooting messaging
Troubleshooting service integration technologies

 

Related


Application deployment troubleshooting tips
Messaging resources for this application
Application resources for this destination