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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

Nicolas Malin (Jira)

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

Jacques Le Roux commented on OFBIZ-5626:
----------------------------------------

Actually I remember now, I indeed crossed this issue and I remember I was cleaning the problem by hand. Scott's suggestion should be the way to go. Will you handle it Leon?

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