-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.0.3RC2
-
None
We are using JBoss messaging backed by a DB2 database (though this issue exists with any variety of DB). In JBoss 4.0.2 all the persistence manager SQL can be configured in the mbean xml for the jboss.mq:service=PersistenceManager.
In JBoss 4.0.3.RC2 PersistenceManager.resolveAllUncommitedTXs() has one additional block of code:
// Now recovery is complete, clear the transaction table.
stmt = c.prepareStatement(DELETE_ALL_TX);
stmt.execute();
stmt.close();
However, in the PersistenceManager.startService() there is no matching line to get the sql string from the configured properties so it always uses the default, hard coded values.
This makes it impossible to use anything other than the default table names.
- relates to
-
JBAS-2056 JMS_TRANSACTIONS constraint violation is not completely fixed
- Closed