You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-user@db.apache.org by Ra...@gsk.com on 2005/01/21 10:49:48 UTC
SET TRANSACTION must be first statement of transaction
I have just recently started getting the error 'SET TRANSACTION must be
first statement of transaction' from my application. The error occurs on
Torque calls that are not using transactions. Can anyone suggest possible
causes? The application was working fine, so I presume that some change
that I made caused this. I am running Torque 3.1 with Oracle 9 on Solaris
and Linux. The base installation has not changed for some months.
I have checked that all transactions are properly committed/rolled back;
tried changing 'testOnBorrow' from 'true' to 'false'. Are there any more
usual suspects that I ought to investigate?
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org
Re: SET TRANSACTION must be first statement of transaction
Posted by Thomas Fischer <Fi...@seitenbau.net>.
Hi,
if you find out anything about the error please post it here. I remember
this problem was reported before to the users list but I do not remember
that the problem was solved.
You can try to log the SQL statements via P6Spy:
http://wiki.apache.org/db-torque/FrequentlyAskedQuestions#head-4658ec85746ef90e0d810fb85fd135d9dd30e264
I have never done this myself, though, so no idea whether this can help
you.
Thomas
raphael.x.mankin@gsk.com schrieb am 21.01.2005 10:49:48:
> I have just recently started getting the error 'SET TRANSACTION must be
> first statement of transaction' from my application. The error occurs on
> Torque calls that are not using transactions. Can anyone suggest possible
> causes? The application was working fine, so I presume that some change
> that I made caused this. I am running Torque 3.1 with Oracle 9 on Solaris
> and Linux. The base installation has not changed for some months.
>
> I have checked that all transactions are properly committed/rolled back;
> tried changing 'testOnBorrow' from 'true' to 'false'. Are there any more
> usual suspects that I ought to investigate?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org
For additional commands, e-mail: torque-user-help@db.apache.org