Bug or feature? Modifying the payload and redelivery...

[mclu]

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

[ataylor]

I'm assuming you're using an ObjectMessage. This sounds like http://jira.jboss.com/jira/browse/JBMESSAGING-1277.

[mclu]

Yes!
You are right! That's it.

I fixed it via creating a copy of my ObjectMessage Payload. I can remove my fix then if patch is part of next GA or SP release :-)