Thanks Ivan,
That helps.
I will create one consumer per session.
Just to add to your argument, following link also suggests, what you have
suggested,
http://activemq.apache.org/multiple-consumers-on-a-queue.html
Thanks,
Manu
--
View this message in context:
http://activemq.2283324.n4.nabble.c
Is there any Camel component which could be used here to perform the hand off
of an event to a thread to encode into message and publish to a topic which
would perform optimally?
--jason
On Nov 18, 2011, at 2:27 AM, Dejan Bosanac wrote:
> Hi Jason,
>
> those operations are costly and if your
2011/11/22 manua :
> Each consumer is running in a different thread, though listening on the same
> queue.
> We dont see any concurrent access.
Consumers always belong to some session; session is thread-specific
(this is a generic principle of JMS, and as far as I know it's valid
both for ActiveM
Ivan,
Each consumer is running in a different thread, though listening on the same
queue.
We dont see any concurrent access.
Thanks
Manu
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-CPP-Same-message-being-consumed-by-two-consumers-tp4096080p4096622.html
Sent f
Thanks Tim,
We dont have a simple test case for this.
We will further investigate the issue in light of your inputs.
Thanks
Manu
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-CPP-Same-message-being-consumed-by-two-consumers-tp4096080p4096611.html
Sent from the
2011/11/22 manua :
>
> We have used activemq cpp and created a session. The session is set in the
> auto acknowledge mode.
> Multiple threads have been launched from that code and each thread has a
> consumer.All consumers are listening on the same queue, and sharing the same
> session.
Do you pro
On Tue, 2011-11-22 at 07:19 -0800, manua wrote:
> HI,
>
> We have used activemq cpp and created a session. The session is set in the
> auto acknowledge mode.
> Multiple threads have been launched from that code and each thread has a
> consumer.All consumers are listening on the same queue, and sha
Because in this case the DMLC is shut down normally.Messages will be acked
before consumers are closed.
It seems that you have to program to implement the mechanism you want by
youself.
At 2011-11-22 21:17:27,Eugene wrote:
>Yup - don't know why I said shut down the JVM. My bad.
>What I want
HI,
We have used activemq cpp and created a session. The session is set in the
auto acknowledge mode.
Multiple threads have been launched from that code and each thread has a
consumer.All consumers are listening on the same queue, and sharing the same
session.
It looks that a message on that queu
Hi,
I have activemq-cpp in production too, Could you explain the exactly
environment in which you fall into the bug? when the connection is
interrupted the producer cant switch to the next broker, or is the consumer?
When I had synchronous consumer, I had some problems with reconnection but
when
Yup - don't know why I said shut down the JVM. My bad.
What I wanted to say is that even if you shutdown/destroy the DMLC - the
message is NOT consumed by the other DMLC. IT IS Consumed only if I kill the
JVM that the now shutdown/destroyed DMLC was running in.
I just re-tested this.
Eugene.
--
stop on the DMLC will pause the consumers (not close)and stop the transport of
the connection,not exit the entire JVM.
shutdown on the DMLC will close all consumers and the underlying connection as
well,not exit the entire JVM too.
note that the messageListener is referenced all the time.when yo
Am 21.11.2011 08:56, Michael Justin wrote:
Am 19.11.2011 18:21, Timothy Bish wrote:
If you want to be sure that the message is processed, then you need to
add a receipt request, otherwise the delivery is not guaranteed. You
await the receipt an once received you know the broker had a chance to
stop is not really an option. stop will stop the MessageListener and not the
actual DMLC.
Restart either - if you call shutdown, I loose the entire JVM, thus no
controll after that with JMX.
So, my solution is to actually re-send the message to the Queue once they
end-up in the Listener that is not
14 matches
Mail list logo
