Re: [Artemis 2.6.2] Resolving Split-Brain

For clarity's sake a JIRA has been opened for this here [1]. Justin [1] https://issues.apache.org/jira/browse/ARTEMIS-2077 On Wed, Sep 5, 2018 at 1:35 AM Ilkka Virolainen wrote: > Hello, > > We had a case where the slave node of a replicating master/slave pair > failed over due to either netw

Re: STOMP anycastPrefix difference between 2.4.0 and 2.5.0 above

The behavior in 2.4.0 was a bug which was fixed via this JIRA [1]. However, the documentation still indicates that anycast will be used by default. I'll fix that ASAP. Justin [1] https://issues.apache.org/jira/browse/ARTEMIS-1596 On Thu, Aug 23, 2018 at 3:17 PM BS wrote: > On my tests with S

Re: Artemis - Starting Replicating Slave as Live

No, there is currently no way to force a replicating slave to start as live if it cannot connect to the live server other than changing the configuration manually. The risk in this use-case is if the live broker is actually up but the network connection between the live and backup cannot be establ

Stale connection hanging at broker during consumer crash

Stale connection hanging at broker during consumer crash : Step1 : When a consumer is getting attached with ActiveMQ broker, the consumer count is getting increased with one , which is verified through “dstat” command . Also the “netstat” from client machine shows one connection establishment with

Re: NullPointerException when trying to browse queue using web console

The configuration block and exception text seem to have been dropped from your message. Can you please re-send them? Also, what version of ActiveMQ are you using? Tim On Thu, Sep 20, 2018, 7:22 AM krezemin2 wrote: > I'm getting a NullPointerException when trying to browse a queue in the web >

Re: dlqDeliveryFailureCause Message Expired and deadLetterStrategy

Please submit this as a bug in JIRA, and provide the link here. My first guess would be that the message is dispatched to the consumer before it expires, but expires before the consumer pulls it from the dispatch queue (so this is consumer-side expiration rather than broker-side expiration), and t

Re: Discarded messages and Expired messages.

The bit is not meant to be used literally; it means "whatever you had already chosen to use here." Try replacing it with sharedDeadLetterStrategy. However, that setting is for controlling the expiration of the message off the DLQ, not for controlling the expiration of the message off the orig

dlqDeliveryFailureCause Message Expired and deadLetterStrategy

Hey all! We're running 5.15.3 and we're using for monitoring (SSL'ed) OpenWire. Healthchecks fail and to not get our aliveness-check queue filled with old messages we added TTL via

Re: Discarded messages and Expired messages.

Hi sry to interrupt, is this the correct way to put expirration messages in dlq ? Because once implement even broker is fail to run < expiration="30"/> -- Sent from: http://activemq.2283324.n4.nabble.co