Skip to main content

Setting up a JMS local transaction

This scenario applies only to Talend ESB, Talend Data Services Platform, Talend MDM Platform, Talend Real-Time Big Data Platform, and Talend Data Fabric.

For more technologies supported by Talend, see Talend Mediation Components.

In this scenario, a local transaction with three steps is performed to send, test, and consume a JMS message:

  1. The first Route is used to send a "hello world!" message to feed the queue.hello JMS queue.

  2. The second Route is used to test the received JMS message. This message is redelivered six times to the queue.hello queue and is then moved to the Dead Letter JMS queue. The Route is programmed to throw an exception every time an exchange is processed by the Route.

  3. The last Route is used to consume the "hello world!" message from the Dead Letter JMS queue.

In this use case, the local ActiveMQ server is used to handle messages between different Routes. The ActiveMQ server needs to be started before executing the Routes. For more information on installing and launching ActiveMQ server, see the Apache website

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!