[ https://issues.apache.org/activemq/browse/AMQ-1028?page=comments#action_37400 ] Adrian Co commented on AMQ-1028: --------------------------------
Could you provide more details of the setup? Are you using a cluster of brokers or a standalone broker? Are you using the default persistence adapter? Are you sending persistent messages or non-persistent messages? Do you have durable subscribers or non-durable subscribers? Are your subscribers connected all the time and is consuming messages every time? If you can provide a small test case to replicate this issue, it will make it easier to fix. :) > 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
