Hi,
I am still having considerable problems with the generic jms ra when
testing failure scenarios.
If anybody can help I would very much appreciate it.
I am using glassfish v1_ur1_p01_b02, and the RA v.17
I am connecting to Tibco EMS, and have a hibernate persistance manager.
What I would like is for Tibco to manage message redelivery.
When a transaction fails due to hibernate's inability to commit the
transaction (say due to a non-unique constraint failure) - the messages do
not seem to be placed back on the queue for redelivery. However the
actually message delivery will have completed OK ( the onMessage worked
fine )
I have the following activation spec:
<activation-config-property>
<activation-config-property-name>RedeliveryAttempts</activation-config-property-name>
<activation-config-property-value>0</activation-config-property-value>
</activation-config-property>
<activation-config-property>
<activation-config-property-name>SendBadMessagesToDMD</activation-config-property-name>
<activation-config-property-value>false</activation-config-property-value>
</activation-config-property>
What I would expect under these circumstances is that the entire
transaction will be rolled back (this is an XA transaction) as hibernate
will vote out of the commit.
However what exactly happens has been hard to determine. It looks like
messages are lost - but never redelivered.
Has anybody seen this behaviour? or does anybody have any ideas?
I will try to get some log files of this happening.
Thanks!!!
James