Re: ActiveMQ Artemis: failure cause of DLQ messages

Thanks for quick response... Any plan for adding such feature as I can see that similar feature is available in ActiveMQ? https://issues.apache.org/jira/browse/AMQ-3236 Thanks, Vishal -- View this message in context:

Re: ActiveMQ broker becomes unresponsive after sometime

Shenandoah is aimed at large JVMs (the page that link points to says 20GB or bigger), so I wouldn't just go trying it without understanding what its strengths and weaknesses are. GCEasy looks interesting, but I'm curious how they make it free and whether there are catches. Are you associated with

Re: How can memory usage be at 10,000% of available memory?

That does sound suspicious, and I believe I've seen users describe similar (though not quite so extreme) behavior in the past, so there definitely might be something here. Can you please provide some additional information? What version of ActiveMQ are you running? What are the limits you're

Re: java.lang.IllegalStateException: Timer already cancelled

This looks like https://issues.apache.org/jira/browse/AMQ-5251, which is fixed in 5.10.1, 5.11.0, or any later version. Tim On May 22, 2017 2:05 PM, "prasadt" wrote: > Hi, > > > we are seeing this exceptions in the activemq log. Application is trying > to > add

Re: Bunch of connections to the same ActiveMQ server

Is connection pooling what you're looking for? Tim On May 22, 2017 11:14 AM, "czaban" wrote: > Is there any optimization of the connections number based on singleton with > URL connection string as a key or something similar mechanism to reduce > number of tcp connection to the

How can memory usage be at 10,000% of available memory?

I'm seeing messages like this in my logs: 2017-05-17 12:42:23.610+ | DEBUG | org.apache.activemq.usage.Usage  |  | main | default:memory:topic://some.topic:memory: usage change from: 10694% of available memory, to: 10695% of available memory Flow control is enabled, and messages are

java.lang.IllegalStateException: Timer already cancelled

Hi, we are seeing this exceptions in the activemq log. Application is trying to add listener and failing to add listeners. below is the activemq and jboss log jboss log 22:00:03,332 DEBUG [org.apache.camel.component.jms.DefaultJmsMessageListenerContainer] (Camel (camel-7) thread #305 -

Re: ActiveMQ Artemis: failure cause of DLQ messages

Are you asking if the broker can add some meta-data or something to the message in the DLQ about the failure which can then be read by your consumer? If so, the answer is no. Justin - Original Message - From: "vishal3007" To: users@activemq.apache.org Sent:

ActiveMQ Artemis: failure cause of DLQ messages

Hi All, Is there any way to know the failure cause of the messages in DLQ? PS: I am using the consumer.receive(); to read the messages. Thanks, Vishal -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-Artemis-failure-cause-of-DLQ-messages-tp4726423.html Sent

Bunch of connections to the same ActiveMQ server

Is there any optimization of the connections number based on singleton with URL connection string as a key or something similar mechanism to reduce number of tcp connection to the same ActiveMQ server? What will be the best approach to make it? -- View this message in context:

Re: Connection to activemq broker is lost within one second

Martin, Can you please describe how you're able to tell that the threads are being killed on your side (and what was killing them, if you were able to determine that), so that Aragoubi (and future readers) can see if he's seeing the same behavior? Thanks, Tim On May 22, 2017 4:20 AM, "Martin

Re: Connection to activemq broker is lost within one second

Thanks Morgan, In the end I figured out that the threads were killed and started by the code on my side hence the constant retries. Sorry for all the noise about this. M On Thu, May 18, 2017 at 4:51 PM, Morgan wrote: > MartinEden do you have the Inactivity Monitor

Re: Client compatibility of Artemis with AMQ and HQ

We have support for the HornetQ protocol which should work for both 2.3.x and 2.4.x clients. To connect older clients simply create an acceptor with the HORNETQ protocol enabled. As Clebert already alluded to, in HornetQ and Artemis 1.x JMS queues and JMS topics names are prefixed with