Hi Partick & all, Do you use jboss connection pooling? And can you send me your sap-dbservice.xml? Re the problem: JDBC Driver: Was the current driver on the Sap.org->interfaces->jdbc until yesterday but was out of date (see message in yesterdays mailing list) ver: package com.sap.dbtech.jdbc, SAP DB JDBC Driver, SAP AG, 7.3.0 Build 028-000-086-554 Jboss Ver:3.0 Problem:When using a Jboss connection pool with a jboss transaction manager(\java:\TransactionManager) in the xml file(note this is not an optional attribute). The transaction manager alternatively sets autocommit to true and false for every query(note:I am using autocommit=true in my app).(Tracked this by using the trace option in jdbc connection string). This causes some locks to be set and not released completely slowing down SAPDB.
Hope that was clearer :-). If you are not using connection pooling with jboss you should not have any problems. Note that the service.xml format for jboss 3.0 is not compatible/uses different parameters&atributes with jboss 2.x. I don't know if the issue will ocuur with jboos 2.0. (jboss.org does not have a connection pool version of sapdb-service.xml for jboss 3.0+) -Ajit Particks Message---> We have JBoss 2.4.4/SapDB 7.3.0.23 running an see apparent problems with the transaction manager, like: "[13:13:36,113,TxCapsule] Transaction XidImpl [FormatId=257, GlobalId=web01//8964, BranchQual=] timed out. status=STATUS_ACTIVE" The only thing which helps is restarting JBoss. Could this be a JDBC Driver problem? After restarting JBoss everything works fine again. On a bad day we have to restart JBoss three times or more often, sometimes the whole thing runs stable for a whole week or longer. The JDBC Driver version is package com.sap.dbtech.jdbc, "SAP DB JDBC Driver", "SAP AG", "7.3.0 Build 023-000-085-131" Thank you for your help, patrick _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
