No errors when testing WebSphere MQ configuration, but messages do not display on outbound or error queues
You are setting up your WebSphere MQ configuration and in the WebSphere Commerce Additional Software Guide, there is a section called "Testing your WebSphere MQ configuration". In this section, you are instructed to put a test message into the hostname.inbounds queue.
The following activities will occur if WebSphere MQ is configured properly:
1. The test message was left on the serial inbound queue (hostname.inbounds).
2. An error message displays in the hostname.outbound queue.
3. The original message displays in the hostname.error queue.
However, only the first one occurs. The last two do not.
No errors are seen in the WebSphere MQ or WebSphere Commerce logs, even with WC_MESSAGING and WC_TRANSPORT_ADAPTER tracing turned on.
Resolving the problem
To resolve the problem:
- In the WebSphere Application Server Administrative Console, check the port number from
WebSphere MQ JMS Provider > WebSphere MQ Queue Connection Factories > JMSQueueConnectionFactory (or your customized name). The default queue manager port is 1414, and it might not be the listener port for the new queue manager you might have created for WebSphere Commerce.
- If the port number is 1414, change it to another number, such as 1415, or another value slightly bigger than 1414.
- Start the queue manager listener.
- Update the port number found under WebSphere MQ JMS Provider > WebSphere MQ Queue Connection Factories > JMSQueueConnectionFactory (or your customized name) to the value used in step 2.
- Restart WebSphere Commerce. Inbound message should be removed and messages should pop onto the error and outbound queues.
It is likely that a default queue manager was created when WebSphere MQ was installed. This default queue manager typically listens on port 1414, and by default, the listener starts up automatically. A new queue manager for WebSphere Commerce might use the same port number as the default.
In WebSphere_MQ_Install_directory\Qmgrs there is a subdirectory for each queue manager. If you have more than one subdirectory, it is possible that one of these additional queue managers might listen on the same port number that you choose. Check all these queue managers for conflict.
You can decide to either use the newly configured port, or disable or remove the default queue manager and listener so that you can use port 1414.
|Commerce||WebSphere Commerce Professional Edition||Install / Config|
|Commerce||WebSphere Commerce||Install / Config|
More support for:
WebSphere Commerce Enterprise
Software version: 6.0, 7.0
Operating system(s): AIX, Linux, Solaris, Windows
Software edition: Business Edition, Professional Edition
Reference #: 1232349
Modified date: 27 November 2012