[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-users
Subject:    Closing a ActiveMQMessageProducer after publishing asynchronously
From:       rth <robert.huffman () gmail ! com>
Date:       2017-03-22 17:48:26
Message-ID: 1490204906992-4724001.post () n4 ! nabble ! com
[Download RAW message or body]

I am trying to determine if it is ok to close an ActiveMQMessageProducer
after it has been used to publish a message asynchronously. Presumably
publishing asynchronously uses a separate thread, which could be blocked
(perhaps because of flow control).

So, what happens if the publishing thread closes the producer before the
message was published?

For what it's worth, all my unit tests involving this scenario pass, but I'm
still not convinced.





--
View this message in context: \
http://activemq.2283324.n4.nabble.com/Closing-a-ActiveMQMessageProducer-after-publishing-asynchronously-tp4724001.html
 Sent from the ActiveMQ - User mailing list archive at Nabble.com.


[prev in list] [next in list] [prev in thread] [next in thread]