Transaction JMS Listeners in ESB 4.2?

[mwax]

I would like to enforce transactionality on a JMS listener: if a service fails, I want the message it has consumed to be pushed back onto the queue associated with the listener. Looking at the documentation and source code, it appears that this is not possible in the current GA release. Is this correct? If so, is this type of functionality slated for the next release?

[marklittle]

The "current GA release" of what? The transaction service doesn't know about JMS and shouldn't. It can be used to drive that you want, but this is more of a question for the JMS forums.

[kconner]

I think he needs to look at jms-jca-provider.

[mwax]

The GA release I am referring to jbossesb-4.2GA. I would have no trouble wrapping straight JMS calls in transactions, but using JBoss ESB, the JMS calls are out of my control.

I don't think I want jms-jca-provider. I want the transactional behavior for an arbitrary ESB service with a JMS listener.

[marklittle]

Use JCA.

[ghilling]

Just to get this straight:

Do I understand it correctly, that in "ESB, Release 4.2.1" a message is consumed just after being read from the JMS-System and not handled transactionally, i.e. it's neither possible to rollback a transaction manually nor is a message retained if a power failure occurs.

Best Regards,

-Gunnar

[kconner]

Hiya Gunnar.

Please create a new topic for this discussion and I will go into more details.

Thanks,
Kev