[ 
https://issues.apache.org/jira/browse/AMQ-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150360#comment-16150360
 ] 

Dejan Bosanac commented on AMQ-6799:
------------------------------------

Another issue in this scenario is that JMX Server Connector is started 
asynchronously and it can be missed for cleanup on the immediate stop.

> 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)

Reply via email to