jconsole using activemq

activemq : apache-activemq-5.14.0 jconsole using jdk1.7 I have started the activemq which comes with the jetty server. Minor change to make the jmx enable is just change default is false(activemq.xml) --- I am using the latest version 5.14.0 when i start i am seeing the message JMX consoles

Re: Potential memory leak with local queue consumer

Thanks, that was it. For some reason, I thought I had to set the element on a core configuration, but I've added that the the JMS configuration and it works fine. Mitchell -- View this message in context:

Re: KAHADB clean up old log files

I was going to write a JIRA enhancement request for that when I had some free time, but if you have time to write it before I get to it, that would be fine. Please put the link here if you do. On Sep 22, 2016 9:00 AM, "lichtin" wrote: > Changing trace levels and using the

Re: Potential memory leak with local queue consumer

My reading of your configuration indicates that you're actually creating the extra queue yourself. When you configure a JMS queue like this: This gets turned into a core queue named "jms.queue.interServerQueue" mapped to an core address also named

Potential memory leak with local queue consumer

Hi, I have a scenario where I have a queue, interServerQueue, for which I create a local connection and consumer. The queue is sent messages by local and remote producers. Messages sent to the queue are received and processed by the local consumer. A heap dump, however, shows 2 QueueImpl

Re: KAHADB clean up old log files

Ok, so I hooked up jconsole and looked at the queues, all of the queues were showing zero. Right underneath the queues there was a section that said "RecoveredXaTransaction". It had one entry XID_[1096044365_globalId3132362e392e312e3133392e746. There really is not very much more

Re: KAHADB clean up old log files

Changing trace levels and using the debugger is not always an option in production. I'm wondering why we could not revive the "KahaDBJournalReader" tool from https://issues.jboss.org/browse/MB-756 and ship it with ActiveMQ. Tim Bain wrote > Alternatively, you all could run the KahaDB file

Re: activemqmessageconsumer duplicate dispatch on connection

You're hitting one of a two possible problems. Most likely, you need to enable the replayWhenNoConsumers option described in the Stuck Messages section of http://activemq.apache.org/networks-of-brokers.html. You could also be hitting the max allowable number of times the message can be forwarded

Re: KAHADB clean up old log files

Apparently you can scratch the "but not impossible" bit from my reply. Thanks Tim, I didn't know it wasn't allowed. On Sep 22, 2016 7:07 AM, "Tim Bain" wrote: > Topics will only hold onto messages if 1) a consumer is currently > connected but hasn't consumed the messages,

Re: KAHADB clean up old log files

Topics will only hold onto messages if 1) a consumer is currently connected but hasn't consumed the messages, or 2) a consumer subscribed durably but is now disconnected. #1 indicates a slow (or intentionally misbehaving) consumer, and isn't likely to be a problem over the span of time you're

Re: Enterprise level Production Support

I have been working with Savoir Tech and have been very happy. Super knowledgeable and very responsive. http://www.savoirtech.com/ > On Sep 22, 2016, at 6:35 AM, ActiveMQ Investigation > wrote: > > Hello, > > I am looking for alternatives available for

activemqmessageconsumer duplicate dispatch on connection

hello guys this is my first post i want to ask about activemq i have 2 broker instances i sent queue to broker A,now there is 1000 in broker A. when i activate (turn on) the consumer(the consumer had a method failover) the queue started to be consumed by the consumer, after that i turn off

Re: KAHADB clean up old log files

On 09/22/2016 08:39 AM, Steve Hill wrote: After the comment about the TOPIC I decided to take a quick look at that in the web interface (just to make sure nothing had gone awry) In deed one of our "queues" had been created as a topic, not sure why as we use the same code to connect to the

Enterprise level Production Support

Hello, I am looking for alternatives available for Enterprise level 24/7 Production Support. I have seen Support Page on ActiveMQ web but would like to see what other support options are available in market. Specially UK time. SLAs are important along with proactive approach to solving a support

Re: KAHADB clean up old log files

After the comment about the TOPIC I decided to take a quick look at that in the web interface (just to make sure nothing had gone awry) In deed one of our "queues" had been created as a topic, not sure why as we use the same code to connect to the queues however once removed most of the data

Messaging for temporary connected systems

I am looking for a best practice to communicate between a central system and several remote systems that are only connected for certain time periods. The remote system sends logs to the central system, the central system can dispatch batch jobs running on the remote system. The job should

Re: KAHADB clean up old log files

Chris/Tim: Thanks for the ideas. Unfortunately neither are the case in our situation. The web client shows 0 messages in any of our queues and we are not using topics. We did set up the remote debug port and downloaded the source code if there is anything useful to further troubleshoot