You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/08/24 12:05:01 UTC

[jira] [Commented] (AMQ-6799) IOExceptionHandler during the startup

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

ASF subversion and git services commented on AMQ-6799:
------------------------------------------------------

Commit c7291f1ecfefec7aad6fcf168e298e2ef0af8ed7 in activemq's branch refs/heads/master from [~dejanb]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=c7291f1 ]

https://issues.apache.org/jira/browse/AMQ-6799 - IOExceptionHandler during the startup


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