[jira] Closed: (AMQ-1028) AMQ Stops dispatching messages after a period of time without errors/warnings
[ https://issues.apache.org/activemq/browse/AMQ-1028?page=all ] Bas van Beek closed AMQ-1028. - Fix Version/s: 4.0.2 Resolution: Incomplete major oops... I set ack:client in the stomp subscription header and acknowlegded incorrect message id's... Reason I didn't see anything in the logs was because of a filesystem error... after a reboot and filesystem fix the log informed me of used memory getting full... I do think it's a problem that a consumer behaving badly can bring the entire messaging system down... 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
[jira] Commented: (AMQ-1028) AMQ Stops dispatching messages after a period of time without errors/warnings
[ https://issues.apache.org/activemq/browse/AMQ-1028?page=comments#action_37410 ] Bas van Beek commented on AMQ-1028: --- Well at the moment it does bring the system down in a way... one consumer subscribed (with ack:client) on topic FOO behaves badly by not correctly consuming it's messages (not acknowledging them). Effect... the messaging system's RAM usage is increasing until it's depleted of available space and all subscribers (also the ones on topic BAR) stop receiving messages. Now imagine the badly behaving consumer being killed without closing the TCP transport like it should and the effect is the system is still not processing messages until that subscription times out (I'm not sure if it even does this... I have the distinct feeling I saw lingering subscriptions even when the connection was closed correctly... but I'll check that next week when back at the office again... in my opinion it should never be possible to let a consumer lock up the system like this... 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
[jira] Created: (AMQ-1028) AMQ Stops dispatching messages after a period of time without errors/warnings
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 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
