You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ofbiz.apache.org by "Leon (JIRA)" <ji...@apache.org> on 2014/06/07 15:22:01 UTC

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

     [ https://issues.apache.org/jira/browse/OFBIZ-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leon updated OFBIZ-5626:
------------------------

    Attachment: OFBIZ-5626.patch

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