Home/ Questions/Q 8286745
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T11:51:36+00:00

So we run a Hibernate, Spring, Spring Webflow stack. From what I’ve read so

  • 0

So we run a Hibernate, Spring, Spring Webflow stack. From what I’ve read so far it might also be important to know we use c3p0-0.9.1.2.

Over the last couple of days we’ve noticed the server suddenly stop. Users cannot log into the website, nothing appears to happen, the browser simply sits loading the page forever. The server logs also simply halt.

When we notice this we shutdown the tomcat instance and all of a sudden quite a few of the following errors get logged;

13:05:57.492 [TP-Processor7]   WARN  o.h.util.JDBCExceptionReporter - SQL Error: 0, SQLState: null
13:05:57.492 [TP-Processor7]   ERROR o.h.util.JDBCExceptionReporter - An SQLException was provoked by the following failure: java.lang.InterruptedException

Any ideas what these mean? Google hasn’t been too helpful. Are we leaking db connections somewhere and the pool cannot gain a new session?

We have just put in a couple new Spring Webflow flows and are experiencing a slightly increased amount of website traffic but we haven’t seen this behaviour before.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I suspect those InterruptExceptions come from the actual shutdown of those threads by the container, and simply indicate that those threads are existant when Tomcat shuts down.

    Instead, I would grab a thread dump from Tomcat when it next freezes. I would also get a DBA to tell you what’s happening in the database. From the above I’m guessing you’re hung on a database resource, but a thread dump and analysis from a DBA will certainly point you in the right direction.

    Here’s a Thread Dump JSP as an alternative means of generating thread dumps.

    • 0