activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-6065) Allow selective use of broker systemExitOnShutdown from DefaultIOExceptionHandler
Date Mon, 30 Nov 2015 12:54:11 GMT

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

Christopher L. Shannon edited comment on AMQ-6065 at 11/30/15 12:53 PM:
------------------------------------------------------------------------

Ok, no problem.  I was thinking it would be ok because it's just a test dependency and wasn't
being included with the release, plus it is the same license as older versions of JUnit.

As soon as you are done I will start the release process for 5.13.0.  


was (Author: christopher.l.shannon):
Ok, no problem.  I was thinking it would be ok because it's just a test dependency and wasn't
being included with the release, plus it is the same license as older version of JUnit.

As soon as you are done I will start the release process for 5.13.0.  

> Allow selective use of broker systemExitOnShutdown from DefaultIOExceptionHandler
> ---------------------------------------------------------------------------------
>
>                 Key: AMQ-6065
>                 URL: https://issues.apache.org/jira/browse/AMQ-6065
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, Message Store
>    Affects Versions: 5.12.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.13.0
>
>
> the broker attribute systemExitOnShutdown is useful in a karaf container or shared vm
where the broker is the primary occupant. If the broker dies, then the container should die.
> For the broker, if the store dies, then the broker should die, but for other scenarios,
like the broker is shutdown via jmx or for maintenance, exiting the container is not required.
> Allowing the DefaultIOExceptionHandler, which gets to handle store exceptions, flip the
systemExit bit allows a container to exit on this fatal condition. Ensuring that failover
of the store can occur due the the exit of the jvm that has the store lock.
> With karaf on windows, the file locker is not reliable on failback when the jvm remains
active.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message