[
https://issues.apache.org/jira/browse/AMQ-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13559458#comment-13559458
]
Petr Nídl commented on AMQ-4075:
--------------------------------
It seems that this issue was (accidentally or on purpose) resolved in version
5.7.0 by descending org.apache.activemq.store.kahadb.KahaDBPersistenceAdapter
from org.apache.activemq.broker.LockableServiceSupport. This wasn't present in
reported version 5.6.0 but in version 5.7.0 it already works. Maybe resolution
and fix version should change. But most of all, I'm happy that this
configuration is possible. Thank you.
> More transparent KahaDB file lock switch
> ----------------------------------------
>
> Key: AMQ-4075
> URL: https://issues.apache.org/jira/browse/AMQ-4075
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Message Store
> Affects Versions: 5.6.0
> Reporter: Petr Nídl
> Priority: Minor
> Fix For: 5.8.0
>
> Attachments: AMQ4075Patch.txt
>
>
> Would it be possible to change the way in which KahaDB file locking can be
> disabled? Currently this can be accomplished by setting
> 'java.nio.channels.FileLock.broken' system property. But system property
> settings can influence other parts of the system where this behavior is not
> desirable. This especially apply for enterprise systems where ActiveMQ is
> embedded in the application and therefore shares the same JVM.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
