Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 martin@attivio.com does not designate 216.139.236.26 as permitted sender)
Date: Tue, 14 Feb 2012 09:55:53 -0800 (PST)
From: mserrano <martin@attivio.com>
To: dev@activemq.apache.org
Message-ID: <1329242153547-4387875.post@n4.nabble.com>
Subject: are session.commit() and consumer.receive allowed simultaneously in
 separate threads?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

>From the reading I have done on this list and the documentation, I have come
to the conclusion that if I:

* Need to call session.commit() or message.acknowledge() in one thread
* And need to called consumer.receiveNoWait() in another thread (consumer
was created from the session).

That I need to guard the session against multithreaded access.  So I am
currently doing:


and 


Is the synchronization on the consumer actually required?  I would prefer to
call one of the consumer blocking calls rather than receiveNoWait(), but
cannot allow the session synchronization to be held that long.


--
View this message in context: http://activemq.2283324.n4.nabble.com/are-session-commit-and-consumer-receive-allowed-simultaneously-in-separate-threads-tp4387875p4387875.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.