It seems activemq 5.0 clients must use JDK 1.5 (but we are using 1.4), am I
wrong ?
rajdavies wrote:
>
> you really need to move up to the latest snapshot of 5.0 - or don't
> use Kaha
>
> cheers,
>
> Rob
>
> On Jul 20, 2007, at 8:57 AM, smo wrote:
>
&g
veMQ 4.1.0-incubator.
Deleting the index-* files ActiveMQ restarts normally but I don't understand
how this files get corrupted. We are using activeMQ on 8 different servers
and they randomly get corrupted whitout any obvious reason that's a big
problem for us.
Tom Samplonius-2 wrote:
>
&
Hi!
I am facing a problem on restarting ActiveMQ.
The CPU is at 100% and ActiveMQ is not available. The console hangs on this
line :
INFO KahaStore - Kaha Store using data directory
c:\ActiveMQ\activemq-data\kaha.db
Here are the logs :
http://www.nabble.com/file/p11691575/act
Hi!
We are probably facing a lock in the thread sending the messages to
ActiveMQ.
Here is a part of a thread dump :
"ExecuteThread: '10' for queue: 'StrutsQueue'" id=21 idx=0x2c tid=3668
prio=5 alive, in native, waiting, daemon
-- Waiting for notification on:
edu/emory/mathcs/backport/java/ut
OK, thanx for your responses!
rajdavies wrote:
>
>
> On Jun 28, 2007, at 8:47 AM, smo wrote:
>
>>
>> OK, so the messages may have been delivered and then marked as
>> delivered in
>> this file.
>> Since they are still in the persistence file, is t
OK, so the messages may have been delivered and then marked as delivered in
this file.
Since they are still in the persistence file, is there any way to "remove"
this mark so that ActiveMQ deliver them a second time?
Tom Samplonius-2 wrote:
>
>
> - "smo" <
Hi!
I have a persistent file "data-queue-data-1" that seems to contain messages
(serialized JavaBean). May I assume these messages haven't been consumed
yet. In that case, how to force ActiveMQ to warn clients that messages are
waiting for being consumed?
In the case they have already been consume
