On 1/30/07, Rob Davies <[EMAIL PROTECTED]> wrote:
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!
Agreed. To be honest, a JmsTemplate doesn't buy you a whole lot in terms of functionality (it often seems to cause more pain than its worth); its pretty easy to write a little spring bean which implements InitalizingBean / DisposableBean so it can create/destroy the JMS connection/session/producer, then reuse the same producer/connection for each message to ensure ordering. -- James ------- http://radio.weblogs.com/0112098/
