[ https://issues.apache.org/activemq/browse/AMQ-1028?page=comments#action_37408 ] james strachan commented on AMQ-1028: -------------------------------------
A badly behaved consumer can't bring the entire messaging system down. Dealing with slow consumers on non-persistent messaging is a common problem though - either increase the RAM, enforce persistence or use slow consumer handling... http://incubator.apache.org/activemq/slow-consumer-handling.html > AMQ Stops dispatching messages after a period of time without errors/warnings > ----------------------------------------------------------------------------- > > Key: AMQ-1028 > URL: https://issues.apache.org/activemq/browse/AMQ-1028 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 4.0.2 > Environment: Os: Ubuntu Linux i386 - Java: J2RE SE 1.5.0_08-b03 > Reporter: Bas van Beek > Priority: Critical > Fix For: 4.0.2 > > > The ActiveMQ stand alone server seems to stop dispatching messages to topics > after a period of time. > New clients can connect... new subscriptions to topics can be made... no > errors are shown... messages are just not sent... including to and from the > new clients... > No errors or warnings can be found in the ActiveMQ.log (even in debug mode) > JConsole doesn't show the new messages coming in (EnqueueCount doesn't change) > Stomp Protocol is used exclusively -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
