[
https://issues.apache.org/jira/browse/AMQ-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157167#comment-16157167
]
ASF subversion and git services commented on AMQ-6799:
------------------------------------------------------
Commit 93874514120b84eff7aee26ed21e3cbe0edf1d50 in activemq's branch
refs/heads/activemq-5.15.x from [~dejanb]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=9387451 ]
https://issues.apache.org/jira/browse/AMQ-6799 - stop the jmx server connector
properly
(cherry picked from commit 5e656d394ce73d6f7d9e72f46348ed7dc9b6240c)
> IOExceptionHandler during the startup
> -------------------------------------
>
> Key: AMQ-6799
> URL: https://issues.apache.org/jira/browse/AMQ-6799
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.15.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.16.0
>
>
> When the broker is starting and exception happens during persistence adapter
> startup (or its locker) an IOExceptionHandler will be called. This can lead
> to inconsistent state where the handler will stop the connector and launch a
> thread to check adapter, while the broker has been stopped due to startup
> error.
> The solution to this would be to allow handler only to work when the broker
> is fully stared.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
