Hello,The problem is caused because the 3.2 Transaction Manager, no longer restarts suspended resources during commit.You should use track by connection for resources that cannot commit from suspended. JBossMQ is one of those. Maybe there is another fix in 3.2.0beta2?
Is there a known fix to 3.0.2 (or 3.0.3)? We're currently running into this problem and not sure how to fix it. We're using database persistence (since file persistence for JMS didn't work), but running into txn problems mentioned here (XAER_RMERR) when trying to persist JMS message into db.
Any tips or hints?
Thanks very much!
Seth
-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
