[ https://issues.apache.org/jira/browse/AMQ-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-6065. ----------------------------- Resolution: Fixed > 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)