[ORACLE] :: JDBC Driver socket read lock ...!

From: Chithu <chitrapandian_at_yahoo.com>
Date: 10 Mar 2003 03:50:35 -0800
Message-ID: <9eb838c3.0303100350.17dd3274_at_posting.google.com>


Hi All,

Our application is an muti-threaded Java Application and uses JDBC for database operations. We are facing JDBC Driver dead lock problem,

Oracle JDBC Driver Version :: 9.2.0.1.0 & 8.1.7.0 (Both) Oracle 8.1.7

Following is the Thread dump trace ... while such a condition occurs ...

"VBJ ThreadPool Worker" daemon prio=5 tid=0x408e28 nid=0x38ab runnable [0xe1480000..0xe14819d8]

        at java.net.SocketInputStream.socketRead(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:86)
        at oracle.net.ns.Packet.receive(Unknown Source)
        at oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
        at oracle.net.ns.NetInputStream.read(Unknown Source)
        at oracle.net.ns.NetInputStream.read(Unknown Source)
        at oracle.net.ns.NetInputStream.read(Unknown Source)
        at oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java:931)
        at oracle.jdbc.ttc7.MAREngine.unmarshalSB1(MAREngine.java:893)
        at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:369)
        at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
        at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:1093)

- locked <ec196a70> (a oracle.jdbc.ttc7.TTC7Protocol)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:2047) at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1940) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2709) at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:589)
- locked <eef2e578> (a
oracle.jdbc.driver.OraclePreparedStatement)
- locked <ec196ae8> (a oracle.jdbc.driver.OracleConnection)
at com.management.transaction.ConnectionPool.executeUpdate(ConnectionPool.java:1778) at com.store.relational.RelationalAPI.executeUpdate(RelationalAPI.java:638)


Any clue .. or help to resolve this problem.

Regards,
Chithu ... Received on Mon Mar 10 2003 - 12:50:35 CET

Original text of this message