For the record, Rob has fixed this issue described in AMQ-2025 and I
have confirmed it seems to have fixed things.
Cheers,
David
David Sitsky <[EMAIL PROTECTED]> writes:
> Hi Rob,
>
> Thanks for your reply. It turns out I already set this property to true
> for both the broker and the client, as
Hi Rob,
Thanks for your reply. It turns out I already set this property to true
for both the broker and the client, as I have a requirement that the
same thread is used for processing messages..
I can only guess the issue is relating to the TcpConnection class
receiving both events from a topic
Hi David,
this is indeed strange - and I suspect the TaskRunnerFactory we use
maybe at fault.
Can you set the System Property
org.apache.activemq.UseDedicatedTaskRunner=true for your client
instead of the synchronized onMessage() - and let me know if it
behaves correctly ?
cheers,
Rob
Hi,
I think this might be an easy question, but I have an application where
my onMessage() handler is a consumer for both topic and queue messages.
The topic and queue consumer are derived from the same ActiveMQ session,
so I was under the impression that my onMessage() handler would not be
calle
