Re: Should I use a session per thread or individual acknowledge?

Hi Kevin - that sounds good as a nice simple solution - session per thread. Kevin Burton 11 June 2014 18:05 I need to acknowledge each message individually as they will take some time to process. I was thinking of creating on connection, and then a session per thre

Should I use a session per thread or individual acknowledge?

I need to acknowledge each message individually as they will take some time to process. I was thinking of creating on connection, and then a session per thread. Is this the right strategy? Is there significant session overhead? The other strategy is to use individual ack but that will constrain

Re: monitoring a 'blocked queue'

It's getting a bit more complicated then I thought because we are in reality using temporary queues, as described in http://www.onjava.com/2007/04/10/designing-messaging-applications-with-temporary-queues.html. The first 84 response messages for the load tester come in OK, but the next one is put o

Re: Out of Memory Error Apache apollo 1.6

Might be better to take a heap dump and let us know. On Wed, Jun 11, 2014 at 6:08 AM, Nate Sarr wrote: > Hi > > We are using apache apollo 1.6 and every so often we run into an out of > memory error - the following is the stack trace that was printed to the > log: > > java.lang.OutOfMemoryErr

Re: ActiveMQ connection leak

Usually means a client is churning through connections when they don't need to. On Tue, Jun 10, 2014 at 7:22 AM, rarun03 wrote: > Thanks for your reply. Do you have any idea why connections keep changing. > My > guess is because of idletimeout 30s. But in another application with > similar > c

Out of Memory Error Apache apollo 1.6

Hi We are using apache apollo 1.6 and every so often we run into an out of memory error - the following is the stack trace that was printed to the log: java.lang.OutOfMemoryError: Java heap space at scala.collection.mutable.ResizableArray$class.ensureSize(ResizableArray.scala:99)

Re: monitoring a 'blocked queue'

If the consumer has already ack'd the message, then no, it's not available anymore. On Wed, Jun 11, 2014 at 12:21 AM, erik wrote: > I suppose you can normally browse the messages that have not been > 'consumed' > by a client yet. Is it also possible, in jconsole or hawtio, to retrieve > the >

Re: How long do I have to acknowledge() a message?

The broker holds state about unacknowledged messages - and will hold that state until either the broker shuts down or the client disappears. Remember that acknowleding a message will acknowledge all messages consumed by the client's Session. Depending on what your doing, you may want to use indi

Re: Question on failover transport options

On Tue, 10 Jun 2014 11:07:43 -0400, Timothy Bish wrote: >On 06/10/2014 06:47 AM, spam trap wrote: >> On Tue, 10 Jun 2014 06:06:03 -0400, Timothy Bish >> wrote: >> >>> On 06/10/2014 04:42 AM, spam trap wrote: [ActiveMQ-CPP 3.8.2] I am unsure how to configure the failover transport

Re: monitoring a 'blocked queue'

I suppose you can normally browse the messages that have not been 'consumed' by a client yet. Is it also possible, in jconsole or hawtio, to retrieve the correlation id/content of the messages that are already consumed by the client? -- View this message in context: http://activemq.2283324.n4.n

Re: How long do I have to acknowledge() a message?

I think that is impossible, because the ack is part of tcp protocol. You can change some values for performance issues (listed below) but anyone is for time. http://activemq.apache.org/activation-spec-properties.html Why would you want to wait two minutes? It coud be a risk when your concurrency