[
https://issues.apache.org/jira/browse/AMQ-5018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364951#comment-17364951
]
Matt Pavlovich commented on AMQ-5018:
-------------------------------------
What was the network filesystem? The locking features of Windows Network File
Services (SMB, CIFS) are not suitable for this type of locking.
This issue is scheduled for closing in 30 days if there are no further updates
> LockFile unlock method not reliable in case of network issues
> -------------------------------------------------------------
>
> Key: AMQ-5018
> URL: https://issues.apache.org/jira/browse/AMQ-5018
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.9.0
> Environment: MS Windows Server 2003 R2 SP2
> Reporter: Oliver Holzmann
> Priority: Major
>
> We run ActiveMQ cluster with kahaDB persistence. Persistence store is located
> on a shared network folder.
> In case of a network glitch we have "java.io.IOException: The specified
> network name is no longer available" and the broker performs a restart.
> During shutdown the SharedFileLocker doStop method triggers LockFile to
> unlock. But due to the io error accessing the lockfile the system property
> created from "getVmLockKey()" could not be removed.
> On restart the still set system property leads to this exception: "File ...
> could not be locked as lock is already held for this jvm" and the broker
> keeps inactive until restarting the windows service.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
