When you configured the connection factory in JNDI for the WebSphere MQ JMS provider, you set the TARGETCLIENT value to MQ. When WebSphere MQ JMS receives target messages, it translates them to WebSphere MQ message format. Messages in WebSphere MQ format contain header fields and a body field. They do not contain property fields.

To receive target messages with property fields, set the value for TARGETCLIENT to JMS in your JNDI configuration, and run the session again. For information about the format of property fields in WebSphere MQ JMS messages, see the WebSphere MQ JMS documentation.

When you have a mapping that passes JMS message header data from a JMS source to a JMS target and the source is WebSphere MQ JMS, WebSphere MQ JMS prepends data to the data in the JMSDestination, JMSReplyTo, and JMSMessageID header fields.

For example, the PowerCenter Integration Service writes data from the JMSDestination field in the source to the JMSDestination field in the target. The value for the JMSDestination field in the source is JMS_1. When the PowerCenter Integration Service writes the data to the target, the value is queue://QM_pcserv/JMS_1. The PowerCenter Integration Service rejects the message.

Use an Expression transformation in the mapping to extract the correct value and pass it to the target.

When you have a mapping that passes data from the JMSMessageID field in a JMS source to a non-JMS target, JMS includes the string “ID:” in the JMSMessageID field. To remove the “ID:” characters before the message ID, you must use an Expression transformation in the mapping.

When you run a session with a high commit interval to write message to an WebSphere MQ JMS target, the PowerCenter Integration Service writes messages to WebSphere MQ JMS. WebSphere MQ JMS writes the messages to a cache file. Because the commit interval is high, the cache file might run out of memory. As a result, the session fails. To prevent the session from failing, lower the commit interval. Or, increase the size of the WebSphere MQ cache file.

When you run multiple sessions simultaneously to read messages from multiple JMS sources and write the messages to a single target, the PowerCenter Integration Service might not read messages from the source for a few moments while it writes data to the target. As a result, the PowerCenter Integration Service meets the Idle Time terminating condition and ends the session. To make sure that each session reads the appropriate number of messages, specify a higher value for the Idle Time terminating condition.

This error message appears even if the session completes successfully. To prevent the error message from displaying, include the <WebSphere MQ JMS>\lib directory in the CLASSPATH.