[
https://issues.apache.org/jira/browse/OFBIZ-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017638#comment-14017638 ]
Scott Gray commented on OFBIZ-5626:
-----------------------------------
Definitely not in DatabaseUtil, that's part of the entity component whereas this is a service component function. This should take a similar approach to JobManager.reloadCrashedJobs() which is called when the ServiceDispatcher is initialised (via JobPoller initialisation).
I would add a protected method to ServiceDispatcher and call it from the constructor (before the call to runStartupServices()).
> No lock can be acquired after ofbiz application crashes.
> --------------------------------------------------------
>
> Key: OFBIZ-5626
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5626> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Leon
> Priority: Critical
>
> We have a service which semaphore set to "fail". Someday, while it was running, the whole ofbiz crashed. After the restart, the service is unable to run anymore since the lock file (database record in ServiceSemaphore entity) is already there.
> Is there any way to cleanup the unused lock files during ofbiz startup? How about the cluster environment?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Locked
