@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,
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
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
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:
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.
