|
Juergen Hoeller made changes - 22/Aug/08 02:23 AM
Juergen Hoeller made changes - 22/Aug/08 02:23 AM
Juergen Hoeller made changes - 22/Aug/08 02:24 AM
Juergen Hoeller made changes - 22/Aug/08 02:24 AM
This is generally speaking rather a bug in ActiveMQ, not in Spring. JMS Connections that are still in active use should keep delivering messages. If the JMS consumers throwed IllegalStateExceptions, that would be clearer... simply not returning any messages there is not acceptable for a JMS provider. The ideal case would of course be for a JMS Connection to keep its physical connection alive for as long as it is in active use. recommend reporting this issue to the ActiveMQ project. Juergen
Juergen Hoeller made changes - 05/Sep/08 08:49 AM
Juergen Hoeller made changes - 05/Sep/08 08:51 AM
Juergen Hoeller made changes - 20/Nov/08 04:12 PM
Juergen Hoeller made changes - 18/Feb/09 08:37 AM
Juergen Hoeller made changes - 03/Aug/09 10:56 AM
Juergen Hoeller made changes - 23/Sep/09 02:15 PM
Juergen Hoeller made changes - 10/Nov/09 04:00 PM
Juergen Hoeller made changes - 12/Jan/10 01:55 PM
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This seems to be related to SPR-5098, where a similar issue has been reported for the Sun JMS provider... This is very likely related to a JMS connection timeout that isn't propagated to DefaultMessageListenerContainer.
Juergen