[
https://issues.apache.org/jira/browse/AMQ-5162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009662#comment-14009662
]
Dejan Bosanac commented on AMQ-5162:
------------------------------------
I made additional fix for this, introducing the configuration parameter to
control this behaviour.
{code}<lease-database-locker handleStartException="true"/>{code}
By the default, we reverted to the old behaviour as some folks want the slave
to keep trying. There's no way to differentiate misconfiguration and server
unavailable, so one needs to decide how she wants to handle this.
http://git-wip-us.apache.org/repos/asf/activemq/commit/b5c6c1ea
> Slave broker does not shutdown after persistence store lockout.
> ---------------------------------------------------------------
>
> Key: AMQ-5162
> URL: https://issues.apache.org/jira/browse/AMQ-5162
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.9.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.10.0
>
>
> Adding the following exception handler to broker configuration suppose to
> shutdown broker when persistence store becomes unavailable.
> {code}<ioExceptionHandler>
> <jDBCIOExceptionHandler stopStartConnectors="false"/>
> </ioExceptionHandler>{code}
> This is seems to work for master broker but the slave broker seems to ignore
> it and continues to work.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
