2 Replies Latest reply on Jul 22, 2005 12:58 AM by Vishak Shanmugam Pillai

    Transaction Id is always null in JMS_MESSAGES AND JMS_TRANSA

    Vishak Shanmugam Pillai Newbie

      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.