[jboss-jira] [JBoss JIRA] Commented: (JBAS-2905) Using Microsoft SQL Server 2005 JDBC Driver, getting "The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION"

[Luc Texier (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-2905?page=comments#action_12353800 ] 
            
Luc Texier commented on JBAS-2905:
----------------------------------


This issue has been fixed by Microsoft in the latest version 1.1 of the 2005 driver
http://www.microsoft.com/downloads/details.aspx?familyid=6D483869-816A-44CB-9787-A866235EFC7C&displaylang=en

release notes
http://blogs.msdn.com/angelsb/archive/2006/08/22/713417.aspx



> Using Microsoft SQL Server 2005 JDBC Driver, getting "The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION"
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-2905
>                 URL: http://jira.jboss.com/jira/browse/JBAS-2905
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JMS service
>    Affects Versions: JBossAS-4.0.4RC1, JBossAS-4.0.3 SP1
>         Environment: Microsoft SQL Server 2005 JDBC Driver
> http://www.microsoft.com/downloads/details.aspx?familyid=e22bc83b-32ff-4474-a44a-22b6ae2c4e17&displaylang=en
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAMSSQLDatasource
>            Reporter: Luc Texier
>            Priority: Minor
>
> Microsoft SQL Server 2005 JDBC Driver
> http://www.microsoft.com/downloads/details.aspx?familyid=e22bc83b-32ff-4474-a44a-22b6ae2c4e17&displaylang=en
> the datasource is a copy of the example available in the following wiki
> http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAMSSQLDatasource
> The problem occurs only after the tables are already created in the database i.e on the second and subsequent startups. 
> 2006-03-08 17:58:00,969 TRACE [org.jboss.resource.connectionmanager.TxConnectionManager] commit problem: 
> 2006-03-08 17:58:00,969 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
> 2006-03-08 17:58:00,969 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
> 2006-03-08 17:58:00,969 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
> org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.)
> 	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java:545)
> 	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.commit(LocalManagedConnection.java:75)
> 	at org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource.commit(TxConnectionManager.java:872)
> 	at org.jboss.tm.TransactionImpl$Resource.commit(TransactionImpl.java:2250)
> 	at org.jboss.tm.TransactionImpl.commitResources(TransactionImpl.java:1781)
> 	at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:337)
> 	at org.jboss.tm.TxManager.commit(TxManager.java:239)
> 	at org.jboss.mq.sm.jdbc.JDBCStateManager$JDBCSession.close(JDBCStateManager.java:613)
> 	at org.jboss.mq.sm.jdbc.JDBCStateManager.initDB(JDBCStateManager.java:465)
> 	at org.jboss.mq.sm.jdbc.JDBCStateManager.startService(JDBCStateManager.java:378)
> 	
> 	
> 2006-03-08 17:58:01,119 TRACE [org.jboss.resource.connectionmanager.TxConnectionManager] commit problem: 
> org.jboss.resource.JBossResourceException: SQLException; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The COMMIT TRANSACTION request has no corresponding BEGIN TRANSACTION.)
> 	at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkException(BaseWrapperManagedConnection.java:545)
> 	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnection.commit(LocalManagedConnection.java:75)
> 	at org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource.commit(TxConnectionManager.java:872)
> 	at org.jboss.tm.TransactionImpl$Resource.commit(TransactionImpl.java:2250)
> 	at org.jboss.tm.TransactionImpl.commitResources(TransactionImpl.java:1781)
> 	at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:337)
> 	at org.jboss.tm.TxManager.commit(TxManager.java:239)
> 	at org.jboss.mq.pm.jdbc2.PersistenceManager$TransactionManagerStrategy.endTX(PersistenceManager.java:215)
> 	at org.jboss.mq.pm.jdbc2.MSSQLPersistenceManager.createSchema(MSSQLPersistenceManager.java:99)
> 	at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1563)
> 	at org.jboss.mq.pm.jdbc2.MSSQLPersistenceManager.startService(MSSQLPersistenceManager.java:240)
> 	
> 	
> 	
> I've tested against MS SQL Server 2000SP4....which might explain why it breaks ;)
> NB: this problem does not exist when I use SQL Server 2000 Driver for JDBC Service Pack 3
> 	

-- 
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