Hi Rob
I'm using Kaha to manually spool messages on certain occasions, and using
4.1. Is there any chance of backporting this package to 4.1?
Or at least does it break any interfaces? in case I may want to do so...
What has been fixed anyway? I also had experienced some problems
on restart.
Th
Hi Po - afraid not 4.2 (to be renamed 5.0) - is jdk1 .5 only at the
moment
On 21 Mar 2007, at 22:22, Po Cheung wrote:
Thanks for the quick response.
When we switch the broker from 4.1 to 4.2, can the ActiveMQ client
(compiled
using JDK 1.4) continue to use 4.1 jars to talk to a 4.2 broke
Thanks for the quick response.
When we switch the broker from 4.1 to 4.2, can the ActiveMQ client (compiled
using JDK 1.4) continue to use 4.1 jars to talk to a 4.2 broker?
Po
rajdavies wrote:
>
> kaha is fixed in 4.2 - but we've also changed the default storage -
> to use a mix of the jour
kaha is fixed in 4.2 - but we've also changed the default storage -
to use a mix of the journal and kaha - I'll try document it soon!
cheers,
Rob
On 21 Mar 2007, at 19:12, Po Cheung wrote:
ActiveMQ was consuming 100% cpu for over 12 hours after the
restart. Here is
a partial thread du
ActiveMQ was consuming 100% cpu for over 12 hours after the restart. Here is
a partial thread dump:
"WrapperSimpleAppMain" prio=1 tid=0x08389780 nid=0x2847 runnable
[0xf19fd000..0xf19ff1b0]
at
org.apache.activemq.kaha.impl.index.IndexItem.read(IndexItem.java:141)
at
org.apache.active
