We've been having something similar, using JBoss 4 on JDK 1.4 contacting an Ingres database.
The connections in the connection pool get used up as timed-out connections, but still get returned to the pool. Which means that it then tries to use the now-dead connections and falls over. By using the 'check-valid-connection-sql' tag in our datasource we can ensure the system continues to run, but this doesn't solve the original timeout problem.
Any advice gratefully accepted!
I have a very similar problem. I have a queue which i send about 200 messages to at once. Jboss JMS sends about 30 (back to back) then stalls, minutes later I start getting "transaction timed out globalid=..."
After that nothing works, the messages dont get delivered, even after restarting jboss.
Am I flooding the queue?
How can this be sorted out? Any help will be greatly appreciated