The tranql wrapper should be dealing with the autocommit state of the
connection automatically. Is there any chance your code called
setAutocommit(true)? Were there any sql errors before this?
Which tranql wrapper are you using? I expect its the generic one but
it doesn't hurt to check.
thanks
david jencks
On Jul 1, 2009, at 4:11 PM, David Blevins wrote:
> On Jun 23, 2009, at 7:46 AM, Michael Simons wrote:
>
>> Caused by: javax.resource.spi.LocalTransactionException: Unable to
>> rollback
>> at
>> org
>> .tranql
>> .connector
>> .jdbc
>> .ManagedJDBCConnection
>> .localTransactionRollback(ManagedJDBCConnection.java:113)
>> at
>> org.tranql.connector.AbstractManagedConnection
>> $LocalTransactionImpl.rollback(AbstractManagedConnection.java:197)
>> at
>> org
>> .apache
>> .geronimo
>> .connector.outbound.LocalXAResource.rollback(LocalXAResource.java:86)
>> ... 20 more
>> Caused by: java.sql.SQLException: rollback() should not be called
>> while in auto-commit mode.
>> at
>> net
>> .sourceforge
>> .jtds.jdbc.ConnectionJDBC2.rollback(ConnectionJDBC2.java:2031)
>> at
>> org
>> .tranql
>> .connector
>> .jdbc
>> .ManagedJDBCConnection
>> .localTransactionRollback(ManagedJDBCConnection.java:111)
>> ... 22 more
>
> This seems to be the root exception right here. Looks like the
> driver is complaining that rollback should not be used when the
> driver is setup with auto-commit enabled. Not familiar with the
> driver, but definitely auto-commit needs to be off for any
> environment with a transaction manager.
>
> Hope this helps!
>
> -David
>
