[
https://issues.apache.org/jira/browse/AMQ-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080766#comment-13080766
]
PK Tan commented on AMQ-3273:
-----------------------------
I encountered a similar problem but the problem happens upon startup. I would
like to know if it is due to the same problem cause. I have logged an issue
[AMQ-3432] Slave broker able to start together with Master broker (shared file
system master/slave setup). Can anyone familiar with this issue enlighten me on
whether the two issues (this issue and AMQ-3432) are the same?
Thank you very much.
> Slave broker acquires lock file when Master is still alive (shared file
> system master/slave setup)
> --------------------------------------------------------------------------------------------------
>
> Key: AMQ-3273
> URL: https://issues.apache.org/jira/browse/AMQ-3273
> Project: ActiveMQ
> Issue Type: Bug
> Components: Message Store
> Affects Versions: 5.5.0
> Environment: Windows 7, Windows Server 2008
> Reporter: Dariusz Szablinski
> Assignee: Dejan Bosanac
> Priority: Critical
> Fix For: 5.6.0
>
> Attachments: LockFile.java.patch
>
>
> The change introduced in AMQ-3237 has triggered issue with LockFile.lock() on
> Win7 and Win2k8. See comments to the JRE issue
> http://bugs.sun.com/view_bug.do?bug_id=6628575 (bottom of the page).
> Suggested solution is to use this construction instead:
> fc.lock( 0, Math.max( 1, fc.size() ), false );
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
