Problem
| Potential solution / explanation
|
The connector delivers all messages with an MQRFH2 header.
| To deliver messages with only the MQMD WebSphere MQ header, append
?targetClient=1 to the name of output queue URI. For
example, if you output messages to queue queue:
//my.queue.manager/OUT, change the URI to
queue:
//my.queue.manager/OUT?targetClient=1. See Installing and configuring the connector
for more information.
|
The connector truncates all message formats to 8-characters upon delivery
regardless of how the format has been defined in the connector
meta-object.
| This is a limitation of the WebSphere MQ MQMD message header and not the
connector.
|
During pollForEvents, the connector shuts down after the following JMS
exception is reported: MQJMS1000: Failed to create JMS
message
| This error appears to relate to the MQSeries Java API and not the
connector itself. It often occurs when running the connector on the
same machine as the WebSphere MQ Integrator Broker product itself. To
remedy the problem, you need to perform the following:
- Unzip the file
%MQSIV2_INSTALL_FOLDER%\Dependencies\JRE_122_4.zip to folder
%CROSSWORLDS%\connectors\MQSIV2\Dependencies\jre_122_Rel4.
- Open
%CROSSWORLDS%\connectors\MQSIV2\start_MQSIV2.bat and
un-comment the following two lines:oset
PATH=%CONNDIR%\Dependencies\jre_122_Rel4\bin...oset
JAVA=%CONNDIR%\Dependencies\jre_122_Rel4\lib\rt.jar
- Restart the connector.
|
During pollForEvents, the connector shuts down after the
following JMS exception is reported: MQJMS1052: Unrecognised
[sic] JMS Message class
| This error can result from modifications made by WebSphere MQ Integrator
Broker to a message originating from a JMS-compliant application. To
correct this, remove remaining JMS information from problematic messages by
adding the following SQL statement to a WebSphere MQ Integrator Broker compute
node: SET OutputRoot.MQRFH2.jms = null;
|