[
https://issues.apache.org/jira/browse/OFBIZ-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890951#action_12890951
]
Adam Heath commented on OFBIZ-3867:
-----------------------------------
Bob brought up interesting points, when multiple tenants are active. Each
tenant has it's own pool of threads to do job management. So when lots of
tenants, you get lots of threads, and if each tenant has lots of jobs, the
system will go into an overload(both memory for each job, and thread
contention).
> JobManager.poll() enters an endless loop when it can't get a connection
> -----------------------------------------------------------------------
>
> Key: OFBIZ-3867
> URL: https://issues.apache.org/jira/browse/OFBIZ-3867
> Project: OFBiz
> Issue Type: Bug
> Reporter: Adam Heath
> Assignee: Adam Heath
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
