First thing I'd do is settle on a single client (preferably the newest
Qpid JMS release) and then test, hard to say what is going one since you
somehow seem to be trying to use more than one at the same time.
On 03/07/2017 11:09 AM, Vince Cole wrote:
I am testing it, by means of making my client app send messages to a
non-existent queue on the broker, as a user which does NOT have admin
rights.
This fails as expected because the broker detects that the user is not
allowed to the create the queue. If I then manually create the queue and try
again, then it succeeds as expected, as the queue now exists and the client
can send to it.
The problem is that the failure (in the first case) is not caught in a
synchronous manner. My client's call to javax.jms.MessageProducer::send
returns immediately, as if everything was OK only for some moments later my
client's ConnectionListener to report the failure (a JMS security exception)
in the log.
What I want instead is for the call to javax.jms.MessageProducer::send to be
synchronous, so that the exception can be caught by the caller, not the
ConnectionListener.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Synchronous-message-production-tp4723171p4723214.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
