Re: It costs time when stopping ActiveMQ

2018-03-07 Thread Tim Bain
Anytime a JVM process (such as the ActiveMQ broker) is slow, my recommendation is to use JVisualVM to perform CPU sampling against the process to find out where the time is being spent. 20 minutes to shut down the process is a very long time, so I'll be interested to hear what you discover via tha

It costs time when stopping ActiveMQ

2018-03-07 Thread t-watana
I am now using ActiveMQ 5.13.1. When I tried to stop ActiveMQ, it cost more than 20 minutes. By checking the activemq.log, it looks like that "uptime XX minutes" were not outputted and it costs time when trying to stop KahaDB. Normal:   INFO | Stopping async topic tasks   INFO | Stopped KahaDB

Re: Migratiion of Queue data from HornetQ to Artemis 2.x

2018-03-07 Thread dharmendra
hi Clebert, Thanks for response . I am using Artemis 2.4.0 as we are going with this version in production so we didn't try on 2.5.0 . As you suggested i have raised JIRA for the same with broker.xml as well and all detail. If you need any more information then please let me know. JIRA id is : h

Re: java.lang.OutOfMemoryError: GC overhead limit exceeded

2018-03-07 Thread Tim Bain
1. http://activemq.apache.org/producer-flow-control.html, and yes, you should enable it. You should protect the broker (by preventing messages from over-filling its heap) first and foremost, and PFC does that. 2. When you're out of memory, it tends to manifest itself all over the place. There's no

Re: http://localhost:8161/api/jolokia/ returns 500

2018-03-07 Thread Tim Bain
This feels like a classloader problem. Do you have multiple versions of the json-simple JAR on the classpath? (Including any copies of those classes in uber-JARs...) On Mar 7, 2018 7:39 AM, "coopci" wrote: > As subject suggests, http://localhost:8161/api/jolokia/ and > http://localhost:8161/api

Re: Artemis 2.4.0 - Issues with memory leaks and JMS message redistribution

2018-03-07 Thread Clebert Suconic
Can you try master? On Wed, Mar 7, 2018 at 2:11 AM, Ilkka Virolainen wrote: > My setup is the same as described in issue #1 of the first message in this > thread: NMS clients listening to JMS topics for messages sent by Artemis > 1.5.4 clients, both connecting randomly to either of the two brok

Re: Artemis 2.4.0 - Issues with memory leaks and JMS message redistribution

2018-03-07 Thread Clebert Suconic
I see what is the issue. I am renaming ARTEMIS-1345 to the real cause and I'm submitting a fix. ARTEMIS-1345 is indeed related to this. On Tue, Mar 6, 2018 at 9:23 PM, Clebert Suconic wrote: > How do you run into this ? > > Are you running amqp messages? > > I was going to release 2.5 tomorrow

Re: Migratiion of Queue data from HornetQ to Artemis 2.x

2018-03-07 Thread Clebert Suconic
and please post a complete thread dump if you still see an issue on master. The ones you posted are just part of the pool. whatever is deadlocking would be somewhere else. There was quite a few fixes on 2.5.0 that would fix some issues like that. On Wed, Mar 7, 2018 at 11:49 AM, Clebert Suconic

Re: Migratiion of Queue data from HornetQ to Artemis 2.x

2018-03-07 Thread Clebert Suconic
If you could please use master (a snapshot).. there has been fixes around that. On Wed, Mar 7, 2018 at 9:47 AM, Erich Duda wrote: > Hi DKumar, > > this looks like bug to me. Please report it to Jira [1] and attach the full > thread dump. It also helps if you share details of your configuration an

Duplicate message detection on failover

2018-03-07 Thread mac.mik...@gmail.com
We have ActiveMq 5.12 in following configuration: PostgreSQL for persistance two Nodes, one in Standby JDBC Master Slave with shared Database static cluster discovery Everything seams to be fine, failover works as expected, but sometimes during failover (or restart of whole cluster) we are observ

Re: Migratiion of Queue data from HornetQ to Artemis 2.x

2018-03-07 Thread Erich Duda
Hi DKumar, this looks like bug to me. Please report it to Jira [1] and attach the full thread dump. It also helps if you share details of your configuration and use cases. Thank you. Erich [1] https://issues.apache.org/jira/secure/Dashboard.jspa Dňa 07.03.2018 o 06:12 dharmendra napísal(a

Re: java.lang.OutOfMemoryError: GC overhead limit exceeded

2018-03-07 Thread sathish.cre...@gmail.com
Hi artnaseef, i am facing same issue in my startup log after 5 days, similar to this, Exception in thread "ActiveMQ InactivityMonitor Worker" Exception in thread "pool-3-thread-121233" Exception in thread "pool-1-thread-1" Exception in thread "pool-3-thread-432434" java.lang.OutOfMemoryError: GC

http://localhost:8161/api/jolokia/ returns 500

2018-03-07 Thread coopci
As subject suggests, http://localhost:8161/api/jolokia/ and http://localhost:8161/api/jolokia/read/org.apache.activemq:type=Broker,brokerName=localhost return a 500 page. I’ve tried several POST requests found in http://www.jakubkorab.net/2013/11/monitoring-activemq-via-http.html, also got this 50

http://localhost:8161/api/jolokia returns status 500

2018-03-07 Thread coopci
As subjects suggests, http://localhost:8161/api/jolokia returns a 500 page. I'm using ActiveMQ 5.14.5. JMS, JMX works well. Did I miss something? I tried some POST requests found in this page http://www.jakubkorab.net/2013/11/monitoring-activemq-via-http.html, also get this 500 page. Can I find a