On 1/16/07, James Strachan <[EMAIL PROTECTED]> wrote:
On 1/16/07, Paul French <[EMAIL PROTECTED]> wrote:
>
> I'll implement your current comments and see what happens. I'm still not sure
> where to set Session.DUPS_OK_ACKNOWLEDGE since I am using the Spring
> JmsTemplate and the template creates the sessions for you on the fly.
You have to noodle the spring javadoc a bit to find it...
http://static.springframework.org/spring/docs/2.0.x/api/org/springframework/jms/support/JmsAccessor.html#setSessionAcknowledgeModeName(java.lang.String)
> I will
> have a dig about in the javadoc. Any other ideas how to make the whole
> process faster?
>
> On the client side I am using a pool of consumers (via the Spring
> SimpleMessageListenerContainer)
But the server side is where you want the pool of consumers. (There's
no real point having a pool on the consumer side unless you are doing
something heavy duty and single threaded after receiving the reply)
> Just FYI on the server side a number of threads are started where each
> thread reads from the main queue and then simply puts a response on the
> temp queue. I don't use a SimpleMessageListenerContainer on the server side
> just a number of pre-configured threads (8 threads) that use the same spring
> single connection factory and JmsTemplates.........
Ah...
Never ever use JmsTemplate for consuming messages. That should fix it.
http://incubator.apache.org/activemq/jmstemplate-gotchas.html
--
James
-------
http://radio.weblogs.com/0112098/
