this seems like a good idea.
gtully: i've opened the issue here to be able to track it:
https://issues.apache.org/jira/browse/AMQ-4824
On Wed, Oct 23, 2013 at 2:49 PM, Gary Tully <gary.tully@gmail.com> wrote:
> it may make sense to have an option to determine the type of exception
> we throw when we are resource constrained.
> ResourceAllocation is a jms exception so it bubbles up to the app. But
> we could have an IO exception in that case
> that would trigger failover.
>
> If the persistence adapter hits a real IOException like a real no
> space error from the filesystem, the default
> IOExceptionHandler on the broker will stop the broker, but that can be
> configured to stop the transport connectors till space becomes
> available.
> In that case, failover will kick in on the clients. Maybe that is an
> option for you, don't use the store limit in this case, leave it to
> the OS limits.
> see: http://activemq.apache.org/configurable-ioexception-handling.html
>
> I think it is worth raising an enhancement for the sendFailIfNoSpace
> feature to allow an IOException to be raised
>
> On 23 October 2013 19:39, ByteFlinger <byteflinger@gmail.com> wrote:
> > Thanks ceposta.
> >
> > I was hoping that there was either an official solution to the issue or
> that
> > it was a confirmed bug.
> >
> > I hope this gets reviewed in the future because failover behaviour
> should be
> > consistent even in such a case.
> >
> >
> >
> > --
> > View this message in context:
> http://activemq.2283324.n4.nabble.com/Failover-on-no-allocated-disk-space-left-tp4672138p4673160.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>
> --
> http://redhat.com
> http://blog.garytully.com
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta