[
http://jira.jboss.com/jira/browse/JBAS-3919?page=all ]
Adrian Brock updated JBAS-3919:
-------------------------------
Summary: JMS PersistenceManager: Could not resolve uncommited transactions
using MS SQL Server (was: CLONE -JMS PersistenceManager: Could not resolve uncommited
transactions using MS SQL Server)
Original Estimate: (was: 1 hour)
Remaining Estimate: (was: 1 hour)
Fix Version/s: (was: JBossAS-4.0.4.CR2)
Affects Version/s: JBossAS-4.0.5.GA
Affects: (was: [Compatibility/Configuration])
So why isn't this valid sql for MSSQL?
DELETE FROM JMS_MESSAGES WHERE TXID IN (SELECT TXID FROM JMS_TRANSACTIONS) AND TXOP=?
And please the leave the fields "FOR COMMITTERS USE ONLY" alone.
JMS PersistenceManager: Could not resolve uncommited transactions
using MS SQL Server
-------------------------------------------------------------------------------------
Key: JBAS-3919
URL:
http://jira.jboss.com/jira/browse/JBAS-3919
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS service
Affects Versions: JBossAS-4.0.5.GA
Reporter: Aladdin El-Nattar
Assigned To: Luc Texier
using mssql-jdbc2-service.xml from /examples/jms this warn is logged during a restart
2006-02-23 16:14:40,528 WARN [org.jboss.system.ServiceController] Problem starting
service jboss.mq:service=PersistenceManager
org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message
recovery may not be accurate; - nested throwable: (java.sql.SQLException:
[Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Line 1: Incorrect syntax near
')'.)
at
org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:442)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira