Configure the "idleTimeout" to a high value, for instance :
Regards,
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Logentry-Setup-of-JMS-message-listener-invoker-failed-for-destination-tp4676507p4679226.html
Sent from th
;"?
> >
> >
> >
> >
> > --
> > View this message in context:
> http://activemq.2283324.n4.nabble.com/Logentry-Setup-of-JMS-message-listener-invoker-failed-for-destination-tp4676507p4676769.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
DMLC and
> ActiveMQ connection pools and debug it. My first question is "what logic
> can cause the log message 'The Session is closed'"?
>
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Logentry-Setup-of-JMS-message-l
View this message in context:
http://activemq.2283324.n4.nabble.com/Logentry-Setup-of-JMS-message-listener-invoker-failed-for-destination-tp4676507p4676769.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Does anybody have an idea what we can do about this?
Am 18.01.2014 14:12, schrieb Thorsten Höger:
> Hi,
>
> We use ActiveMQ 5.9.0 and are getting warn logs every 30 minutes in all our
> applications
> using Spring ListenerContainers
>
> WARN crest Sat Jan 18 13:16:00 CET 2014
> org.springframewor
Hi,
We use ActiveMQ 5.9.0 and are getting warn logs every 30 minutes in all our
applications
using Spring ListenerContainers
WARN crest Sat Jan 18 13:16:00 CET 2014
org.springframework.jms.listener.DefaultMessageListenerContainer Setup of JMS
message
listener invoker failed for destination 'poo
