Hi Gary,
Gary Tully schrieb:
> odd, that stack trace does not match with the 5.3.0 source.
That's funny, since I packaged the 5.3.0 into Sun Packages and used
kahaDB which hasn't been there before the 5.3.0 release (I never use
snapshots).
> Can you verify that it is
> 5.3.0 and that this insta
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
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 conne
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.
On 17 March 2010 12:43, Roland Thomas Lichti wrote:
> Hi,
>
> after a broker shutdown I get IOExceptions when starting again. The
> broker tries
Hi,
after a broker shutdown I get IOExceptions when starting again. The
broker tries to ack a message but since the broker restarted the session
is gone. We use a kahaPersistenceAdapter (after having to much problems
with kahaDB). It is no solution to switch to another store, since we
need the mes
