[jira] Resolved: (AMQ-1042) The JMSConsumerTest interminitently failed on linux systems.
[ https://issues.apache.org/activemq/browse/AMQ-1042?page=all ] Jonas Lim resolved AMQ-1042. Resolution: Fixed fixed in 4.2 ( trunk) : r473647 4.1 branch : r473657 > The JMSConsumerTest interminitently failed on linux systems. > > > Key: AMQ-1042 > URL: https://issues.apache.org/activemq/browse/AMQ-1042 > Project: ActiveMQ > Issue Type: Bug > Components: CMS (C++ client) >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1, 4.2 > > > JMSConsumerTest fails on linux sometimes. -- 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
[Fwd: Re: Activemq 4.0.2 - stops sending message after some time (solved)]
Hi all, After further testing, I was able to to distill the problem to unconsumed messages in a durable topic subscription. The solution was to increase the "usageManager" limit, as described here: http://www.nabble.com/problem-with-durable-subscribers-tf2145613.html#a5923485 Although it must be noted that while using Stomp clients, large number of threads were created. Total Thread Started I now have further queries on this :) 1. How do I remove unused durable topic subscriptions ? 2. How to identify the PendingQueueSize for all subscriptions ? Thanks Sandeep
[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-1017) Build of current trunk with Maven2 fails
[ https://issues.apache.org/activemq/browse/AMQ-1017?page=comments#action_37406 ] Bernhard Wellhöfer commented on AMQ-1017: - A build using Debian Sarge works fine. But a 4.2 ActiveMQ version was build, not a 4.1. As I said I'm trying to compile https://svn.apache.org/repos/asf/incubator/activemq/trunk which is regarding to http://www.activemq.org/site/source.html) the 4.1 SNAPSHOT version. I just detected that https://svn.apache.org/repos/asf/incubator/activemq/branches/activemq-4.1 exists. Is this the 4.1 tree? > Build of current trunk with Maven2 fails > > > Key: AMQ-1017 > URL: https://issues.apache.org/activemq/browse/AMQ-1017 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.1 > Environment: Windows XP, Maven 2.0.4, Java 1.5.0_06 >Reporter: Bernhard Wellhöfer >Priority: Critical > Attachments: mvn-472933.log, mvn.log, mvn.log, mvn.log > > > A build of a fresh checkout from > https://svn.apache.org/repos/asf/incubator/activemq/trunk with Maven2 fails. > See the attached log of the build. -- 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
