I am a collegue of Andreas. It happened again on tuesday but again we don't know the reasons. Attached are two thread dumps. I cannot see anything in it, but maybe you are seeing more. http://old.nabble.com/file/p28607920/dumps.zip dumps.zip
We had also problems with KahaDB before which forced us to upgrade to this snapshot. But now I am tending to go back to Version 5.3. Are there other reports of this kind with this 5.4.x series? Christian Gary Tully wrote: > > If you can capture some thread dumps of both the master and slave brokers, > ideally a small series, with few seconds between each this would help > determine what is going on. > > Obviously, if this is repeatable, please open a jira issue to track it and > add your test case if you can. > > > On 17 May 2010 11:51, Andreas Prüller <[email protected]> wrote: > >> Hello, >> >> >> >> currently I have an ActiveMQ 5.4-SNAPSHOT running for a test. It is as >> pure >> master-slave configured. >> >> Last Friday the whole system stopped working – I mean no new messages >> were >> enqueued, no messages were dequeued. No exception was thrown, no warning, >> nothing. It just stopped working (and there were some hundred messages on >> the queues which had to be processed). >> >> In the log file of the ActiveMQ (master and slave) I can see it was still >> running, as it cleaned up the kahadb regularly. >> >> Only solution was at the end to stop the whole system and restart it. >> >> >> >> Anybody any idea what happened there? >> >> >> >> Hope somebody can help. >> >> Best, >> >> Andreas >> >> > > > -- > http://blog.garytully.com > > Open Source Integration > http://fusesource.com > > -- View this message in context: http://old.nabble.com/ActiveMQ-freeze-tp28581838p28607920.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
