Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 209.85.220.210 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=hIbV0ouF06uibZpgzykNFW7Gn0c9PVJ9EtOPPlntVbx0MLFzqGjNdkWaXbZGiNkLBr
         KGROa7dmXq2j7h8iRwb6cCRr39tvnbrkynWLSAaF7cL58KqeNk/NSo1nFTmNQSKR4dTS
         wZaOFkqP5J6lRjTmzhEGG0npid5EhfyCQsvtY=
MIME-Version: 1.0
In-Reply-To: <4BA248E0.70001@telefonica.de>
References: <4BA0CE7D.7010500@telefonica.de>
	 <3a73c17c1003180602h613003fbu9f1e032453364c91@mail.gmail.com>
	 <4BA248E0.70001@telefonica.de>
Date: Thu, 18 Mar 2010 16:52:50 +0000
Message-ID: <3a73c17c1003180952g27d31312m6d763bf6ed695412@mail.gmail.com>
Subject: Re: Problem reading kahaPersistence data store
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: multipart/alternative; boundary=00032555b2a2a81e6c0482160f6b

--00032555b2a2a81e6c0482160f6b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

odd, that stack trace does not match with the 5.3.0 source. I missing
subscription should be ignored during recovery. Can you verify that it is
5.3.0 and that this installation has no duplicate jars or anything odd like
that.

So the root cause seems to be connections not shutting down which forces yo=
u
to kill the broker, which leads to this state.
If you need to kill the broker again for this reason, can you first create =
a
thread dump so we can determine the cause for the connection that is
hanging/taking a long time to shutdown.


On 18 March 2010 15:38, Roland Thomas Lichti <roland.lichti@telefonica.de>w=
rote:

> Gary Tully schrieb:
> > what version are you using? this looks like
> > http://issues.apache.org/activemq/browse/AMQ-1712 but that is not
> consistent
> > with your reference to KahaDB.
> >
> Sorry. The broker is 5.3.0. We had no problems with our stores on 5.2.0
> but there we had problems with hanging connections. These hanging
> connections went away when we switched to 5.3.0. But now we loose
> messages due to corrupt stores.
>
> Today we lost another store (this time amqPersistence, to wich we
> switched after we lost the kahaPeristence store my first message told
> from).
>
> This time we had to kill the broker since there were connections hanging
> ("connection /xx.yy.zz.aa:12345 taking a long time ..."). I checked with
> netstat and there were no connections with that IP and port number -
> seems to be a hickup in AMQ. But without closing these connections the
> store does not get flushed. And since we needed a working broker we were
> forced to kill that broker. And we lost again a store.
>
> At the moment my decision to use AMQ is hardly challanged by my boss and
> his peers ...
>
> bye,
>    Roland
>
> --
> Roland Thomas Lichti
> IT Application Manager
>
> Telef=F3nica o2 Germany GmbH & Co. OHG
> H=FClshorstweg 30, 33415 Verl
> t: +49 5246 80 1121, f: +49 5246 80 2121
> m: +49 160 98949570
> roland.lichti@telefonica.de
> http://www.telefonica.de
>
> Bitte finden Sie hier die
> handelsrechtlichen Pflichtangaben:
> http://www.telefonica.de/pflichtangaben.html
>
>
>


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

Open Source Integration
http://fusesource.com

--00032555b2a2a81e6c0482160f6b--