Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com
 designates 209.85.211.200 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=AGCZJlB4dhRgDgitHPEzL7UayV0i4/ZTOSGuLwsdx0Wl6vzICz7Zskjo/QScF+K5F3
         LXqNpg1Hda6f2Iz7U47AIslPGHjImnI0P1ZG691iXlog/qGp22Wc4/REgdUTM0VOHgxY
         Xfdvnm8illsYFNQmEVxq/bD6c2UEF+TuATauA=
MIME-Version: 1.0
In-Reply-To: <28607920.post@talk.nabble.com>
References: <015901caf5ae$f6e07420$e4a15c60$@de>
	 <AANLkTilum30H-6gaQBFtF2OINrP1YsFGVcS7bfQV8_eI@mail.gmail.com>
	 <28607920.post@talk.nabble.com>
Date: Wed, 19 May 2010 14:19:28 +0100
Message-ID: <AANLkTikyaF_UGGdQhVElBwIM7ZPrkSi-D35iV2LcVN47@mail.gmail.com>
Subject: Re: ActiveMQ freeze
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=000e0cd286a2c67a800486f24eca

--000e0cd286a2c67a800486f24eca
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

The master is blocked on a write, is some consumer having trouble? Would be
interested to know the state of the process on the other end of that
connection.
That pending write is blocking the next message dispatch on that connection=
.


"ActiveMQ Connection Dispatcher: /127.0.0.1:59497" daemon prio=3D10
tid=3D0x00000000486fa000 nid=3D0xcd0 runnable
[0x000000004152c000..0x000000004152ca90]
   java.lang.Thread.State: RUNNABLE
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at
org.apache.activemq.transport.tcp.TcpBufferedOutputStream.flush(TcpBuffered=
OutputStream.java:115)
at java.io.DataOutputStream.flush(Unknown Source)
at
org.apache.activemq.transport.tcp.TcpTransport.oneway(TcpTransport.java:181=
)
at
org.apache.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.ja=
va:243)
- locked <0x00002aaadca9dc98> (a java.util.concurrent.atomic.AtomicBoolean)
at
org.apache.activemq.transport.TransportFilter.oneway(TransportFilter.java:8=
5)
at
org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotia=
tor.java:104)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:40)
- locked <0x00002aaadca9ded8> (a java.lang.Object)
at
org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection=
.java:1224)
at
org.apache.activemq.broker.TransportConnection.processDispatch(TransportCon=
nection.java:802)
at
org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.=
java:838)
at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.=
java:98)
at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.ja=
va:36)

On 19 May 2010 14:02, Christian grobmeier <grobmeier@gmail.com> wrote:

>
> 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 thi=
s
> 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=FCller <prueller@aracom.de> 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 =96 I mean no new message=
s
> >> 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.
>
>


--=20
http://blog.garytully.com

Open Source Integration
http://fusesource.com

--000e0cd286a2c67a800486f24eca--