-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1
-
None
you are using mySQL 4.x as the persistence backend for JBossMQ
After a restart, while the JMS persistence manager is attempting to recover uncommited txs, you might get the following exception
2005-11-07 09:11:22,990 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Starting failed jboss.mq:service=PersistenceManager
org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (java.sql.SQLException: Every derived table must have its own alias)
at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:416)
- is related to
-
JBAS-2056 JMS_TRANSACTIONS constraint violation is not completely fixed
- Closed