DQL java.lang.Throwable: Duplicate non transacted delivery

Hello What could be the cause of DQL for "Duplicate non transacted delivery" reason ? Thanks -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: VirtualTopic and VirtualTopic Consumer

Tim thanks alot for your answer. Sorry for not checking in earlier, the issue I was having ( with 5.14.5) is that I stumbled upon the following problem. We used selectorAware=true but did not use the virtualSelectorCacheBrokerPlugin ( as in https://github.com/apache/activemq/blob/master/active

VirtualTopic and VirtualTopic Consumer

Hello It look's like that messages sent to VirtualTopic are only forwarded to Consumer when they are actively listening. Is there a way to have this forwarding regardless of the consumer actually listening or not, but just by the fact the the queues exist ? Thanks Alain -- Sent from: http

OOM when pruging as queue from console when store is at 100%

Hello Using AMQ 5.10.0 Once Store is at 100% when purging a queue we get OutOfMemory error. Is there a setting to prevent this ? Thanks Alain -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: cursorMemoryHighWaterMark applies on the broker ? or policyEntry ?

Hello Yes that's the configuration be with 5.10.0 this didn't work. Like explained. What seams to be working is If producerFlowControl is not false the producer is block if above memoryLimit. Message a not "store" only like when highwatermark is reached. Thanks Al

Re: dlqDeliveryFailureCause java.lang.Throwable: duplicate from store for queue

okay thanks ! -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: How can Memory percent used be 100 if cursorMemoryHighWaterMark is 70%

Okay thanks. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

How can Memory percent used be 100 if cursorMemoryHighWaterMark is 70%

Hello, Using activemq 5.10.0 we had a production issue where Memory percent used was 100% I've beeing trying to reproduce but I can't get the memory used % above the default cursorMemoryHighWaterMark of 70 % I've trying "flooding" several queues with huge messages but I can't get passed 74% mem

cursorMemoryHighWaterMark applies on the broker ? or policyEntry ?

Hello I'm very puzzled by the cursorMemoryHighWaterMark after reading http://blog.christianposta.com/activemq/activemq-understanding-memory-usage/ I tested lowering the highwater mark to prevent (or defer ) 100% memory usage. Using 5.10.0, with the setting I was excepting the limit to be pe

Re: dlqDeliveryFailureCause java.lang.Throwable: duplicate from store for queue

Hello Tim, Thanks for your reply. I saw that post but it mentions the following issues that don't apply to our setting: - AMQ-4485 fixed in 5.9 - AMQ-5266 jdbc store which we don't use We're using 5.10.0 : - with no network of brokers. - basic queue's and topics We're planing to use authentica

dlqDeliveryFailureCause java.lang.Throwable: duplicate from store for queue

Hello, Using AMQ 5.10, what would cause a message land in the deadletter queue with the following cause : dlqDeliveryFailureCause java.lang.Throwable: duplicate from store for queue X Thanks Alain -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html