[jira] [Commented] (OFBIZ-5626) No lock can be acquired after ofbiz application crashes.

["Scott Gray (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OFBIZ-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988826#comment-13988826 ] 

Scott Gray commented on OFBIZ-5626:
-----------------------------------

This is definitely a pain.

I'd suggest to:
- add an "instanceId" field to ServiceSemaphore which is populated by the general.properties "unique.instanceId" value when a lock is acquired
- on startup an instance should check for any ServiceSemaphore rows that match instanceId=${unique.instanceId} and delete them

> 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)