Hi,
We recently upgraded to Clover 5.0 from 4.0. Due to the changes in how the JMS listeners works with our MQ environment (new 5.0 Listener is not committing transactions, causing memory issues on MQ). We need to set up a graph with the JMS Reader to consume transactions intermittently.
Our issue with the JMS Reader is that it does not seem to have an option to pass the "JMS_MSG_MESSAGEID" parameter to the executing graph (something the the JMS Listener can do).
Is there something Im missing the the JMS Reader? Is there a way to retrieve JMS_MSG_MESSAGEID?
We recently upgraded to Clover 5.0 from 4.0. Due to the changes in how the JMS listeners works with our MQ environment (new 5.0 Listener is not committing transactions, causing memory issues on MQ). We need to set up a graph with the JMS Reader to consume transactions intermittently.
Our issue with the JMS Reader is that it does not seem to have an option to pass the "JMS_MSG_MESSAGEID" parameter to the executing graph (something the the JMS Listener can do).
Is there something Im missing the the JMS Reader? Is there a way to retrieve JMS_MSG_MESSAGEID?
-
Hi,
taking advantage of the JMSReader requires that the transformation of JMS messages to records is written in Java. Please find an example graph attached that demonstrates how the JMS message ID can be harvested. In order to make the graph work on your end, you would need to create a working JMS connection. For more information about JMSReader, please review our documentation.
Best regards,
Please sign in to leave a comment.
Comments 1