Ok.
Still have not found your workaround, but figured out my own.
The bug regarding getAutocommit and setAutocmmit in sybase jdbc jconn2 is solved:
| jConnect will no longer begin a transaction in chained mode when
| Connection.getAutoCommit() or Connection.getIsolationLevel() is called.
| This allows clients to use code such as the following:
|
| if (! Connection.getAutoCommit())
| {
| Connection.setAutoCommit(true);
| }
|
So this cannot be the problem.
With
anonymous wrote :
| BEGIN TRAN select 1 COMMIT TRAN
|
istead of
anonymous wrote :
| select 1
|
everything works fine. So in addition to the fact that the exception mentioned in the
first posting is only popping up with jboss-3.2.5 and not with jboss-3.2.3 I think
there must be a change in jboss. (Maybe a bug)
Just my 2 cents
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842394#3842394
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842394
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
