This content has been marked as final. Show 3 replies
Thanks - I'll give that a try.
We found the problem.
Our database (SQL Server) is a little flaky and likes to not answer from time to time. Just doesn't scale well.
And by default, JTDS doesn't set a query timeout.
to the JTDS URL, to make sure the connection pool has a chance at refreshing iteself, and added:
private static final int SQL_QUERY_TIMEOUT = 2; // by query ... callableStatement.setQueryTimeout(SQL_QUERY_TIMEOUT);
to all of our DAOs for scheduled jobs.
I made these changes last night, and as expected the jobs threw several query timeout exceptions, and the jobs restarted on the next scheduled interval.
So - hopefully - this is the entire issue we're experiencing. We'll be able to confirm after a couple of days in production.