Transaction Id is always null in JMS_MESSAGES AND JMS_TRANSA

vishak_s Jul 19, 2005 8:19 AM

I am using JBoss 3.2.3. JMS application threw the Primary key violation and PersistenceManager was modified as per JBoss 3.2.4 patch. Transaction Id was stored as SynchronizedLong instead of prmitive type long. In our application I see that TransactionId is always persisted in database as null and message id is not sequential. Can you please explain why is this behaviour.

1. Re: Transaction Id is always null in JMS_MESSAGES AND JMS_TR

genman Jul 20, 2005 12:27 AM (in response to vishak_s)

If the message is not for a particular XA transaction, it is null.
Actions
2. Re: Transaction Id is always null in JMS_MESSAGES AND JMS_TR

vishak_s Jul 22, 2005 12:58 AM (in response to vishak_s)

HI GENMAN,

Can you please explain elaborately why transaction_id is set as null for a non XA Transaction.
Actions

Go to original post