You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2011/04/07 09:48:05 UTC
[jira] [Assigned] (AMQ-3273) Slave broker acquires lock file when
Master is still alive (shared file system master/slave setup)
[ https://issues.apache.org/jira/browse/AMQ-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac reassigned AMQ-3273:
----------------------------------
Assignee: Dejan Bosanac
> 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.5.0, 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