MQSeries.net :: View topic

ravish_rao · Posted: Fri Jan 20, 2006 4:46 am Post subject:

Hi All,

I am currently implementing a MB workflow which is being used to transform a message coming out of a 3rd party application (xyx V11) before forwarding the message to a similar application but of a different version (xyz V10). This 3rd party application provides JMS queues for interfacing.

I am trying to achieve transformation in MB v6 using JMSInput and JMSOutput nodes. For this we would require JMSInput and JMSOutput nodes to connect to two different JMS connection factories. However we found that in a given message flow, regardless the number of JMSInput JMSOutput node it has, it can only connect to one JMS connection factory. Take the JMS/MQ API for example, if the JMSInput node is connecting to the JMS connection factory serviced by Queue Manager QMGR1, then all the subsequent JMSOutput nodes can only connect to the connection factory serviced by the same Queue Manager.

When we traced the service trace we found out that broker caches the connection in the thread context, and all the subsequent JMS nodes will fetch the same connection from the same thread. So if the subsequent JMSOutput node tries to open a queue which is hosted in another queue manager, it will fail since the queue will not be accessible by the existing queue manager connection factory.

Please let me know if anyone is aware of any such limitations in MB and any possible workaround for the same.

Thanks in advance.

Best Regards.