Re: Stopping JMS Connection with unprocessed prefetched messages results in message moved to DLQ

2018-02-14 Thread Keith W
On 14 February 2018 at 09:59, Keith W wrote: > Hi Bryan > > >> So that brings me to the potential bug. I found that when using the JMS >> QueueBrowser it actually increments the Delivery Count for a message >> everytime it is browsed. That is why most of my source messages

Travel Assistance applications open.

2018-02-14 Thread Gordon Sim
FYI: message from Travel Assistance Committee below: — The Travel Assistance Committee (TAC) are pleased to announce that travel assistance applications for ApacheCon NA 2018 are now open! We will be supporting ApacheCon NA Montreal, Canada on 24th - 29th September 2018 TAC exists to help

Re: Stopping JMS Connection with unprocessed prefetched messages results in message moved to DLQ

2018-02-14 Thread Keith W
Hi Bryan Yes, that's a defect. Thanks for reporting. From my initial > So that brings me to the potential bug. I found that when using the JMS > QueueBrowser it actually increments the Delivery Count for a message > everytime it is browsed. That is why most of my source messages had a >

Not sure how to use failover_exchange

2018-02-14 Thread bryand
I'm using qpid-broker-j-7.0.1, qpid-jms-amqp-0-x-6.3.0 and JDK 1.8. I have HA setup for broker-j and have been using failover of roundrobin for my client connections and that's been working fine. I was wanting to see the difference when using failover_exchange though. When I try that I get

Re: Not sure how to use failover_exchange

2018-02-14 Thread Rob Godfrey
Hi Bryan, Qpid Broker-J does not currently implement the failover exchange, the only way to achieve failover reconnection to a different broker is by configuring the clients -- Rob On 14 February 2018 at 21:22, bryand wrote: > I'm using qpid-broker-j-7.0.1,