Can you check again with the cvs version of Branch_3_0? I fixed some problems with this over the weekend. You are required still to, if you set autocommit false, to commit any work you may have done before closing a connection handle. If you still have problems please post the exact code that is failing with stack trace and indication of where the failure occurs.
david jencks On 2002.06.18 09:31:35 -0400 Rodney Kite wrote: > com.sybase.jdbc2.jdbc.SybSQLException: SET CHAINED > command not allowed within multi-statement transaction > > I am getting a SET CHAINED exception when running > JBoss 3.0 and Sybase's jConnect 5.5. JBoss 2.4.4 and > jConnect works fine. I am assuming that the pool > JBoss uses is not setting the connections Chaining or > Autocommit to the proper setting. Is there some way > of making jConnect default to chained or unchained > connections? JBoss will not allow me to set the > connections autocommit in code which out giving me an > exception. > > Thanks > Rodney > > __________________________________________________ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com > > ---------------------------------------------------------------------------- > Bringing you mounds of caffeinated joy > >>> http://thinkgeek.com/sf <<< > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > ---------------------------------------------------------------------------- Bringing you mounds of caffeinated joy >>> http://thinkgeek.com/sf <<< _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
