This week's book giveaway is in the Agile and other Processes forum. We're giving away four copies of The Mikado Method and have Ola Ellnestam and Daniel Brolund on-line! See this thread for details.
All,
We have issue with connection pool in jboss. We are facing "No Managed Connections" issue. I can see some other also facing the same.
I guess, Connection pool workings well for normal cases.
But I have few queries,
1. Will connection return to pool if there connection got SQLException(Ex: be lock timeout)? We are closing resultset, statement & connection.
2. Do we need to take any extra pre-cautions when reading a "blob"(In Mysql "text) columns?
3. Is there any issue with jboss at destroying a connection and re-creating it? Like, when there are on-demand created connections, pool will destroy those and will create again when needed. I heard, Once a connection destroyed, jboss will hangup if attempt to create new connection. Is it right?
We are trying to see which connection executed for a long time from MySQL end. Because this is happening in production and we are not able to predict when it will be.
And we deployed a small war to take the threaddump, but not able to analyse it. can you please advise how to analyse threads holding the connection.
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.