Do you have any explanation of the meaning of SET CHAINED or the sybase error message?
Is there any way to log with Sybase or the jdbc driver if and when setAutoCommit is being called on the underlying connection? My impression was that setAutoCommit(false) was always called on the underlying connection at the start of any managed transaction. (From your description of using transaction modes I assume you are using CMT).
More info would be helpful in tracking this down.
I'm running the same setup as clmichel (JBoss 3RC2, jConnect 5.2, CMT) and see the same error. It was working under RC1.
In Sybase, SET CHAINED = setAutoCommit(false) while SET UNCHAINED = setAutoCommit(true).
The methods I'm calling are setup as NotSupported and Required. I have one NotSupported method that seems to work but then other NotSupported and Required methods fail (they're not called in that order though).
I'm not sure about logging from the driver or database.
Sorry its not much to work from. BTW, JBoss 3 is looking really nice.
The problem occurs in LocalManagedConenction.cleanup(). Sybase throws the exception because setAutoCommit(true) is called before the connection closes. You can only perform this operation when the connection is first created. Maybe waiting until after the conn.close() would work.