Re: Consumer not able to consumer messages from queue

Mmm, I misunderstood what you'd written about where the bottleneck was occurring. Based on what you've said, it sounds like maybe your cursor is getting full of messages for which no consumer exists (maybe because they're in a session that was already closed?) and therefore the broker can't pull o

Re: activemq.xml Embedded Tomee redeliveryDelay

Broker redelivery kicks in when the client redelivery attempts are exceeded. The broker plugin intercepts the sendToDeadLetterQueue broker method. I think you will need to disable the default redelivery policy on your clietns if you want < 6 attempts. Set jms.redeliveryPolicy.maximumRedeliveryDela

Re: Consumer hanging after a producer fails for being inactive

It looks like the issue with the consumer hanging has something to do with duplicate messages after a producer comes back from a failover. I see the Producer reconnect after the network is restored. The broker receives a ActiveMQMapMessage. The ProducerBrokerExchange setting the last stored sequen

Re: Consumer hanging after a producer fails for being inactive

So I was unable to produce a JUnit test that causes this issue to occur. My first attempt was to use the SocketProxy in the test package of activemq. I had the broker,the consumer, and the producer all running in the same JVM. The consumer was using the VM transport and the producer was connecting

Re: Consumer not able to consumer messages from queue

The producer is not blocked as the msgHeld value keeps increasing, its the consumer that stops consuming messages. >>Also, I was under the impression that it wasn't possible to set message TTL on the broker and that it could only be set by the producer; Yes, sorry about that it can be set by pro

Re: Impact of checkForDuplicates = false

the case where it is necessary is when a client connection drops between sending an ack and the broker receiving the ack. So the broker will redispatch the message when the consumer reconnects (when failover kicks in). If there is no failover the consumer and connection will die. If the ack is in a

Impact of checkForDuplicates = false

Due to https://issues.apache.org/jira/browse/AMQ-5016 our large and stable systems will hit the 2^31 + 1 message limit after a few days. I gather that the "checkForDuplicates" flag will prevent the "Duplicate dispatch on connection" issue. I can set that flag on just our highest volume queues bu

Re: ActiveMQ Stomp producer messages size limitation

Jan 13, 2015 7:08 AM, "khandelwalanuj" wrote: > Hi, > > I am not able to send message more than 100MB to ActiveMQ broker. Producer > throws below exception: > > /[20150113 03:16:59:609 stomp_client.py:80 ERROR] Received an error: > org.apache.activemq.transport.stomp.Protoc

Re: ActiveMQ Stomp producer messages size limitation

On 01/13/2015 09:05 AM, khandelwalanuj wrote: Hi, I am not able to send message more than 100MB to ActiveMQ broker. Producer throws below exception: /[20150113 03:16:59:609 stomp_client.py:80 ERROR] Received an error: org.apache.activemq.transport.stomp.ProtocolException: The maximum data

Re: Consumer not able to consumer messages from queue

I can't speak to the question about closing the session (I use Camel to interact with ActiveMQ, so I don't directly deal with the session), but even if that explains the increasing msgsHeld value, it doesn't explain the producer slowing down and eventually stopping its sends. So there might be mul

ActiveMQ Stomp producer messages size limitation

Hi, I am not able to send message more than 100MB to ActiveMQ broker. Producer throws below exception: /[20150113 03:16:59:609 stomp_client.py:80 ERROR] Received an error: org.apache.activemq.transport.stomp.ProtocolException: The maximum data length was exceeded at

Should I still use idleTimeout=0 which ActiveMQ 5.10.0 after the bug fix in ActiveMQ 5.8.0

There was this bug in ActiveMQ v 5.8.0 ( https://issues.apache.org/jira/browse/AMQ-4366 ) which was worked around by setting idleTimeout to 0 in connection factory. I have upgraded my setup to ActiveMQ 5.10.0. I am wondering whether to keep this se

Re: activemq.xml Embedded Tomee redeliveryDelay

No idea? Does someone use a redelivery policy and can send his configuration? Thanks Clément -- View this message in context: http://activemq.2283324.n4.nabble.com/activemq-xml-Embedded-Tomee-redeliveryDelay-tp4689728p4689836.html Sent from the ActiveMQ - User mailing list archive at Nabble.c

Re: Consumer not able to consumer messages from queue

Thanks for the reply. I have disabled producer flow control on both topics and queues in my broker configuration and I have message TTL specified on broker side. The destination on which heartbeats are sent is a Queue on which 5 concurrent consumers are listening and the reply to destination is a