You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Denis Bazhenov <ba...@farpost.com> on 2009/08/29 02:30:32 UTC
ActiveMQ stops consuming messages after No space left on device
We have some strange situation. At some point IOException: "No space
left on device" occurs on server which is running ActiveMQ. We observe
following behavior: server accepts new messages but messages not
produced to consumers. Is anybody knows what's going on and how to
gracefully continue work after IOException?
Denis Bazhenov
Re: ActiveMQ stops consuming messages after No space left on device
Posted by Bruce Snyder <br...@gmail.com>.
On Fri, Aug 28, 2009 at 8:45 PM, Denis Bazhenov <ba...@farpost.com> wrote:
> Some additional information would clarify situation, I think. After that
> failure we restarted ActiveMQ and all goes ok (we clean up space on device).
> But before restart I take thread dump of broken ActiveMQ process. I realize
> that there is no "ActiveMQ Data File Writer" thread, which is present on
> normally working broker. If you look at source code of
> NIODataFileAppender.processQueue() you will see that this method stops
> execution if IOException occurred. Is there any possibility that ActiveMQ
> can continue work after IOExeception occurred.
Using JIRA, please create a new issue for this problem and make sure
to include all of this information as well as the thread dump.
http://issues.apache.org/activemq/browse/AMQ
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bruceblog.org/
Twitter: http://twitter.com/brucesnyder
Re: ActiveMQ stops consuming messages after No space left on device
Posted by Denis Bazhenov <ba...@farpost.com>.
Some additional information would clarify situation, I think. After
that failure we restarted ActiveMQ and all goes ok (we clean up space
on device). But before restart I take thread dump of broken ActiveMQ
process. I realize that there is no "ActiveMQ Data File Writer"
thread, which is present on normally working broker. If you look at
source code of NIODataFileAppender.processQueue() you will see that
this method stops execution if IOException occurred. Is there any
possibility that ActiveMQ can continue work after IOExeception occurred.
Denis Bazhenov
On Aug 29, 2009, at 11:30 AM, Denis Bazhenov wrote:
> We have some strange situation. At some point IOException: "No space
> left on device" occurs on server which is running ActiveMQ. We
> observe following behavior: server accepts new messages but messages
> not produced to consumers. Is anybody knows what's going on and how
> to gracefully continue work after IOException?
>
> Denis Bazhenov
>
>
>