openejb-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From AndyG <andy.gumbre...@orprovision.com>
Subject Re: DBCP Connection pool blocks threads on open/close connections
Date Mon, 14 Feb 2011 08:15:05 GMT

This really needs a thread dump to analyse the locks, but it does sound like
connections are not being closed properly in your MDB, and this is leading
to starvation.

If you fire a new FutureTask from the MDB so that the entire db process
(your MDB method body) is disconnected from the JMS worker I think you'll
find that the new task will be the one that blocks - If so then then the
blocking is likely to be either in your code, or due to DBCP
misconfiguration. How are your pool and DataSource configured?

Make sure that 'DbHelper.closeConnection' has some implicit logging to see
what is going on in there...is the connection really getting closed?

An individual MDB method call can only be as fast as the code which it
executes. To actually test MDB performance run a test that simply prints the
message payload to System.out and does nothing else.
-- 
View this message in context: http://openejb.979440.n4.nabble.com/DBCP-Connection-pool-blocks-threads-on-open-close-connections-tp3303674p3304576.html
Sent from the OpenEJB User mailing list archive at Nabble.com.

Mime
View raw message