I'm running into a rather odd and difficult issue to nail down and I believe it is associated to the way connections are cached.
 
iBatis: 2.3.0.668
Spring: 2.0
Transaction Manager: Bitronix
DB: Sybase ASE 12.0.0.8
JDBC Driver: Sybase JConnect 6.0
 
I've got a running transaction that I suspend prior to an insert into a given table. (Long story as to why I suspend) When I suspend the TX the insert that I perform needs to be on a clean connection, one not associated with the transaction. (It seems either ASE or JConnect is not really capable of running more than one transaction at a time on a single connection. This has something to do with implicit / explicit transaction demarcation. So when I need a connection to perform the insert I actually need a new connection.
 
Is there any way of configuring iBatis to do this type of behavior? As I debug the code I see in the UserProvidedTransaction class that it simply returns the connection it was given at time of instantiation, effectively this can be the same connection that was part of the TX.
 
Thanks for the help...
 
 
Chris Mathrusse
[EMAIL PROTECTED]
(925) 236-5553
 

Reply via email to