RE: Bug in sap JDBC drivers and Jboss+SAP

[ajit_cus]

Hi, �Quick update could not get a jboss 3.0 connection pool working even with the latest alpha driver. Note:I do not want to use XA-Transaction manager. I just need a connection pool. (Have written a connection pool manager of my own and it works fine with sapdb). Anyone with a working sapdb-service.xml for jboss 3.0 and above please send it to me…. Thanks �Ajit   This might be useful to anyone wanting to identify the source of the problem:   �The dbtrace looks as below: Note the general messing around with the autocommit. My app sets autocommit=true in the connection string. I added a stack trace to the jdbc driver and found it was jboss TransactionManager setting the autocommits   [EMAIL PROTECTED] (false) [EMAIL PROTECTED] () => 2 [EMAIL PROTECTED] () => false [EMAIL PROTECTED] (true) [EMAIL PROTECTED] () => 2 [EMAIL PROTECTED] (1004, 1007) => com.sap.dbtech.jdbc.StatementSapDB@4b11e9 [EMAIL PROTECTED] (120) [EMAIL PROTECTED] () => true [EMAIL PROTECTED] () => true [EMAIL PROTECTED] (false) [EMAIL PROTECTED] (Select <XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX>) => com.sap.dbtech.jdbc.ResultSetSapDB@4ff20 [EMAIL PROTECTED] () => true [EMAIL PROTECTED] () => true [EMAIL PROTECTED] (<XXXXXXXX>) => DEFAULTCLASS [EMAIL PROTECTED] (<XXXXXXXX>) => 1 [EMAIL PROTECTED] () => false [EMAIL PROTECTED] () [EMAIL PROTECTED] () [EMAIL PROTECTED] (1004, 1007) => com.sap.dbtech.jdbc.StatementSapDB@62c9bf [EMAIL PROTECTED] (120) [EMAIL PROTECTED] () => false [EMAIL PROTECTED] (true) [EMAIL PROTECTED] (Select <XXXXXXXXXXXXXXXXXXX>) <next query will be executed with autocommit false> <next query will be executed with autocommit true>