]
Adrian Brock closed JBAS-6510.
------------------------------
Fix Version/s: JBossAS-4.2.4.GA
Resolution: Done
Assignee: Adrian Brock (was: Clebert Suconic)
I've corrected the default SQL statements and updated the original instructions to
reflect this fix.
Wrong SQL for XARecovery in hard-coded default values and guideline
-------------------------------------------------------------------
Key: JBAS-6510
URL:
https://jira.jboss.org/jira/browse/JBAS-6510
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: JMS (JBossMQ)
Affects Versions: JBossAS-4.2.3.GA
Reporter: Rico Neubauer
Assignee: Adrian Brock
Fix For: JBossAS-4.2.4.GA
Affected: 4.0.5, 4.2.3, maybe others.
2 small SQL mistakes in description of
http://jira.jboss.com/jira/browse/JBAS-1341 how to
enable XARecovery and in its code:
DELETE_ALL_TX_XARECOVERY = DELETE FROM JMS_TRANSACTIONS WHERE XID = NULL
should be:
DELETE_ALL_TX_XARECOVERY = DELETE FROM JMS_TRANSACTIONS WHERE XID IS NULL
DELETE_MARKED_MESSAGES_WITH_TX_XARECOVERY = DELETE FROM JMS_MESSAGES WHERE TXOP=? AND
JMS_MESSAGES.TXID IN (SELECT TXID FROM JMS_TRANSACTIONS WHERE XID = NULL)
should be:
DELETE_MARKED_MESSAGES_WITH_TX_XARECOVERY = DELETE FROM JMS_MESSAGES WHERE TXOP=? AND
JMS_MESSAGES.TXID IN (SELECT TXID FROM JMS_TRANSACTIONS WHERE XID IS NULL)
The default SQL statements are also wrong in
org.jboss.mq.pm.jdbc2.PersistenceManager's code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: