Hi Steven,
I think your spot on that the connection pooling could be causing you
problems. I would recommend that you use a dedicated connection - and
apart from seeing messages in order, you'll see performance
improvements too!
cheers,
Rob
On 30 Jan 2007, at 05:57, Steven Marcus wrote:
Hello!
I have a spring message-driven pojo (via SimpleMessageListener) that
is receiving messages out of order ('cancel' before 'new')
occasionally.
There is only one message producer, but it's using JmsTemplate, which
is configured with an activemq PooledConnectionFactory.
The example at http://www.activemq.org/site/total-ordering.html
focuses on two producers, but I am working on the theory that a single
producer may create out of order messages given connection pooling.
Is this correct?
Is there any way to configure the topic for total ordering via the
API?
Would it be better to stop using JmsTemplate and provide the single
producer a dedicated connection?
Thanks in advance from an activemq/jms newbie...
Steven Marcus
