[
https://issues.apache.org/jira/browse/OFBIZ-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021733#comment-14021733
]
Scott Gray commented on OFBIZ-5626:
-----------------------------------
Either instanceId (which I'd already suggested above) or lockedByInstanceId
would be fine by me. I agree runByInstanceId isn't ideal (but not necessarily
a bad choice).
I don't see why the instanceId needs to be part of the primary key though, the
original intent of the table should be maintained where the intent is one row
per service.
> 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
> Attachments: OFBIZ-5626.patch
>
>
> 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)
