We are getting something similar - it seems that the Transaction Synchronization that is
being added is re-using the Session provided when the JobSession is constructed rather
than using DBPersistenceService to get it's own.
Does that sound like it might match your problem?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4049774#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...