Thanks gary,
In our case we are using kaha-db here is the exact config in broker.xml file
We would have expected a drop in throughput may be 30-40%, but not 90%. The
file system that the kaha db directory is pointing to is fairly beefy raid10
local disks.
What we
Hello,
Sorry for the repost I don't think I was subscribed properly with my
previous attempt.
I have a question regarding some messages that are appearing in the
activemq.log and what they actually mean. I've recently setup a server
running AMQ5.5.0. I've got stomp+nio setup as the transport c
I understand that when using MASTER, SLAVE scenario NFSV3 is not
recommended because of the way V3 works. But is this also the
recommendation when using simple broker of clusters with persistence?
updating to 1.5.1 did not help, although it was extremely old version, no
idea where i got that :)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/NMS-producer-slow-tp3768632p3768702.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
but the queue is empty when the producer tries to enqueue a message.
So drainage problems should not be effecing producer when there is nothing
to consume at the moment of the producer trying to enqueue right?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/NMS-producer-slo
On Thu, 2011-08-25 at 08:50 -0700, iceball12 wrote:
> NMS 1.1.0.1642 and activemq 5.4.1
>
That version of NMS is extrememly old, you'd be wise to update to the
latest release 1.5.1 of the NMS.ActiveMQ lib.
> Sometimes when producer messages to a queue it takes a long time for the
> message is ac
NMS 1.1.0.1642 and activemq 5.4.1
Sometimes when producer messages to a queue it takes a long time for the
message is actually enqueued.
The weird thing is that when i produce multiple messages to the same queue
quickly then all messages are enqueued quickly
the Delay is only when 1 message is en
Hi,
Is the transaction mechanism in ActiveMQ is for the whole broker or concerns
only the queues involved in the transaction ?
Regards
Hervé
2011/8/16 Hervé BARRAULT
> Hi,
> I have the following configuration :
> 2 producers send message in a queue using camel producer template.
> I have
Thanks for the reply, Gary. We're not doing anything specific
persistence-wise with the messages themselves. Broker-wise, persistence is
enabled on the external broker, but persistence is disabled on the embedded
broker.
I believe this problem occurs regardless of persistence being
enabled/disab
Hi,
This is probably a somewhat unusual use case for ActiveMQ. I am not aware of
anyone who has implemented something similar before.
I am concerned about delays and jitter when dealing with voice data streams.
Don't see how you can map these to the abstraction of a single message.
ActiveMQ wa
@dan,
Are you using persistent messages?
If yes, typically dispatching is faster than persisting messages and
when the consumers are fast we can by pass storing and syncing to disk
if the consumer acks before the disk write has started. As a result,
through put can be very high.
When we persist,
11 matches
Mail list logo