Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
JobManager.poll(), line 157, where it calls storeByCondition, can fail when there is no connection available from the database(due to a connection leak, or just load, or whatever). An exception then gets thrown by storeByCondition(deep inside ofbiz/commons-dbcp/postgres). The catch(Throwable) then logs the error, and the loop tries again. Since pollDone never gets set to true, this loop is very tight, and the log file starts to fill up very fast, each each thread of JobPoller tries the same thing over and over.
I'm filing this bug mainly to see if anyone else works on it, but if not, it's a reminder for me.