#12 Deadlock?

[Anonymous]

Hi guys,

I am not sure if this is a known issue but under load we
are getting the connection pool "locking up", what
happens is that if you look at the thread dump of the
dead application ALL of the threads are waiting
on "getConnection", whilest only one of them is in:

"T81" id: 0x0x00003380 prio: 5 WAITING,
NONDAEMON, GCABLE
thread: 0x0914CBE0 lastj: 0x7F101004
pt_thr: 0x00002B08
at java.lang.Thread.doYield(Native Method)
@150D0A3E
at java.lang.Object.wait0(Unknown Source)
@150D21D3
at com.protomatter.pool.SimpleObjectPool.checkout
(Unknown Source)@1EE056DA
at
com.protomatter.jdbc.pool.JdbcConnectionPoolDriver.con
nect(Optimized Method)@34858EF9
at java.sql.DriverManager.getConnection(Optimized
Method)@2AA967BE
at java.sql.DriverManager.getConnection(Unknown
Source)@1D4ADA5B
at
com.protomatter.jdbc.pool.JdbcConnectionPoolDataSourc
e.getConnection(Unknown Source)@1EE05015

it really looks like on checkout the thread has gone to
sleep keeping a lock on the getConnection monitor
preventing anybody else from going in ange getting /
closing connections. What do you think?

Cheers

Marco

marco.santulli@voxsurf.com