Guillaume Nodet schrieb:
The Spring JMS layer contains two parts: the JmsTemplate which can be
used to send / consume messages, and the MessageListenerContainers
that can be used to consumer messages more efficiently. Caching is
configurable on the DefaultMessageListenerContainer, but the
JmsTemplate doesn't do caching, mainly because it is meant to work in
a Java EE environment, where the client is supposed to create a
connection / session / sender every time. Thus, a really good thing
is to configure a JMS pooled connection factory underneath (see
http://activemq.apache.org/spring-support.html).
Hi Guillaume,
what connection pooling do you use? I know there is one implementation
in http://commons.apache.org/pool/. Spring also contains Pooled Session
Factories but there
are several... Which would you suggest to use?
Best regards
Christian
--
Christian Schneider
---
http://www.liquid-reality.de
