Hi!
Don't know if this is a bug or feature.
I am using a plain consumer (MessageConsumer.receiver(long)) in an transacted session inside a sessionbean. So JTA is used. (1.4.0SP3)
I receive my payload and reuse it in my backend. There it fills a List with other objects.
Then I rollback my transaction or throw an runtime exception.
My database instance increases the delivery_count and the message is received again in a new transaction.
I expect a new payload object but no, its the already changed one.
Is this a bug or a feature? What says the spec?
:-)
Greets
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162554#4162554
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162554
> But no extra module should be needed.
Actually that depends exactly what version of the server you are running and what the transaction encompasses. JBM has its own recovery module, but it's not enabled by default. The JCA used for database connections also has one, but it's only bundled in recent versions of the EAP and even then it's not turned on by default. In short, you probably don't need to write one, but you do need to hunt down one or two existing ones and wire them up.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162553#4162553
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162553