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.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885449#3885449 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885449 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
