After digging around I found this link:
http://activemq.apache.org/slow-consumer-handling.html
Since I don't mind if I lose messages (they have a 30 sec lifespan anyway)
it looks like I could set up a ConstantPendingMessageLimitStrategy to throw
away messagse so I don't block.
Should this work
Would there be a separate buffer per connection ?
Otherwise a broken listener would still cause all the others to block...
Also with the current release would a slow listener cause all the other
listeners to slow down because it is not clearing messages from the buffer
fast enough ?
Thanks
Jon
Oops that should have read:
"Yep if you kill off the JVM of the broken listener then"
On 3/7/07, rabidgremlin <[EMAIL PROTECTED]> wrote:
Hi Hiram,
Yep if you kill off the JVM of the broken publisher then things kick back
into action
Not sure this is good "e
Hi Hiram,
Yep if you kill off the JVM of the broken publisher then things kick back
into action
Not sure this is good "expected behaviour". A misbehaving listener should
not stop the publisher or other consumers from working.
I would have hoped that the connections between the broker and th
Hi All,
I have a production application that receives SOAP "event" messages,
converts them into JMS messages and publishes them to a topic. I then have
multiple subscribers listening to these "events".
Under high loads (500-1000 events a minute) messages stop been published. I
continue to receiv
