.nabble.com/ActiveMQ-CPP-Same-message-being-consumed-by-two-consumers-tp4096080p4097105.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
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
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
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
.2283324.n4.nabble.com/ActiveMQ-CPP-Same-message-being-consumed-by-two-consumers-tp4096080p4096080.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
