Skip to Content
0
Former Member
May 27, 2008 at 02:27 PM

JDBC deadlock on DriverSapDB.connect

120 Views

Hi,

Today i get a JDBC dealock that i must shutdown and restart my application, i get the follow stack when investiganting the problem:

"http-80-exec-15" daemon prio=10 tid=0x0000000056fa8800 nid=0x4860 runnable [0x000000004292f000..0x0000000042930c90]
   java.lang.Thread.State: RUNNABLE
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.read(SocketInputStream.java:129)
	at com.sap.dbtech.rte.comm.BasicSocketComm.receiveData(BasicSocketComm.java:577)
	at com.sap.dbtech.rte.comm.BasicSocketComm.receive(BasicSocketComm.java:666)
	at com.sap.dbtech.rte.comm.JdbcCommunication.execute(JdbcCommunication.java:41)
	at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:536)
	- locked <0x00002aaafff16398> (a com.sap.dbtech.jdbc.ConnectionSapDB)
	at com.sap.dbtech.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:461)
	at com.sap.dbtech.jdbc.ConnectionSapDB.doConnect(ConnectionSapDB.java:398)
	at com.sap.dbtech.jdbc.ConnectionSapDB.<init>(ConnectionSapDB.java:109)
	at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:222)
	- locked <0x00002aaac64a7f48> (a com.sap.dbtech.jdbc.DriverSapDB)
	at java.sql.DriverManager.getConnection(DriverManager.java:582)
	at java.sql.DriverManager.getConnection(DriverManager.java:185)
        ...

"http-80-exec-122" daemon prio=10 tid=0x0000000059065800 nid=0x4bac waiting for monitor entry [0x000000004a6ac000..0x000000004a6add90]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at com.sap.dbtech.jdbc.DriverSapDB.connect(DriverSapDB.java:197)
	- waiting to lock <0x00002aaac64a7f48> (a com.sap.dbtech.jdbc.DriverSapDB)
	at com.sap.dbtech.jdbcext.DataSourceSapDBBase.openPhysicalConnection(DataSourceSapDBBase.java:333)
	at com.sap.dbtech.jdbcext.DataSourceSapDB.getConnection(DataSourceSapDB.java:40)
        ...

This is only one thread have many more but with same Stack.

JDBC version is 7.6.03.07

JVM version is:

java version "1.6.0_06"

Java(TM) SE Runtime Environment (build 1.6.0_06-b02)

Java HotSpot(TM) 64-Bit Server VM (build 10.0-b22, mixed mode)

any idea how to avoid this?

KR Clóvis.

Edited by: Clovis Wichoski on May 28, 2008 1:30 PM