[Broker-J] REST-API: getMessageInfo does not list message groupIds

Hi, we’re using Qpid’s message grouping feature and are sending messages through Qpid java client with the JMSXGroupID property. This is working great. We noticed that when using the getMessageInfo REST API there is no way to retrieve the groupId for enqueued messages. There is no field in the

Re: [python] Receiver find current queued messages, but no new ones

Well, that's actually good news, in that I now know where the problem lies. Thank you so much for your help! - Mike On Mon, Nov 18, 2019 at 3:59 PM Gordon Sim wrote: > On 18/11/2019 7:52 pm, Mike Longfritz wrote: > > I doubt it's very recent. I suspect it's 5.15.2, from here: > > > > [0x7fddfd

Re: [python] Receiver find current queued messages, but no new ones

On 18/11/2019 7:52 pm, Mike Longfritz wrote: I doubt it's very recent. I suspect it's 5.15.2, from here: [0x7fddfdd4e800]:0 <- @open(16) [container-id="localhost", max-frame-size=4294967295, channel-max=32767, idle-time-out=15000, offered-capabilities=@PN_SYMBOL[:"ANONYMOUS-RELAY", :"DELAYED_DEL

Windows Project

Hello. I would like some help importing the QPID C ++ libraries into Visual Studio project. What is the best practice? Regards Gustavo Magni Bueno Arquiteto de Soluções gustavo.bu...@service.com.br +55 41 3155-8500 +55 41 99245-6

Re: [python] Receiver find current queued messages, but no new ones

I doubt it's very recent. I suspect it's 5.15.2, from here: [0x7fddfdd4e800]:0 <- @open(16) [container-id="localhost", max-frame-size=4294967295, channel-max=32767, idle-time-out=15000, offered-capabilities=@PN_SYMBOL[:"ANONYMOUS-RELAY", :"DELAYED_DELIVERY"], properties={:product="ActiveMQ", :"top

Re: [python] Receiver find current queued messages, but no new ones

On 18/11/2019 6:45 pm, Mike Longfritz wrote: Any idea what's causing the problem with copy() mode? No. What version of the java broker are you using? I tried with 7.1.4 (also latest c++ broker) and did not see the issue you are reporting when using the copy mode. --

Re: [python] Receiver find current queued messages, but no new ones

Comparing the traces for the working and not-working runs, there's one different line of note: Working (mode=delete) [id]:0 <- @attach(18) [name="xxx", handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="xxx"], target=@target(41) [], incomplete-unsettled=false,

Re: [python] Receiver find current queued messages, but no new ones

I'll be darned, it does receive new messages. That's helpful, but not quite sufficient - I have a significant use case for reading in browse mode. Any idea what's causing the problem with copy() mode? On Mon, Nov 18, 2019 at 1:03 PM Gordon Sim wrote: > On 18/11/2019 1:59 pm, Mike Longfritz wrote

Re: [python] Receiver find current queued messages, but no new ones

On 18/11/2019 1:59 pm, Mike Longfritz wrote: On Mon, Nov 18, 2019 at 8:22 AM Gordon Sim wrote: Also there is one difference in the attach that may be relevant, the distribution-mode. Have you tried your python app with delete=True? I have, and it does delete from the queue when run that way.

Re: Qpid as a RabbitMQ broker for Java app integration tests - exchange declare arguments

Rob, I do not have any tentative date for the release yet. Potentially, the changes can be ported into 7.1.6 and released as part of 7.1.x line. I have a couple of defects to fix there (I am in process of raising corresponding JIRAs). The defects are straight-forward to fix. Potentially, the ver

Re: [python] Receiver find current queued messages, but no new ones

Sorry, meant to also say that there are several messages in the queue, I just sent the trace up until the first transfer. I can send more if that might help. On Mon, Nov 18, 2019 at 8:59 AM Mike Longfritz wrote: > > On Mon, Nov 18, 2019 at 8:22 AM Gordon Sim wrote: > >> On 18/11/2019 1:01 pm, M

Re: [python] Receiver find current queued messages, but no new ones

On Mon, Nov 18, 2019 at 8:22 AM Gordon Sim wrote: > On 18/11/2019 1:01 pm, Mike Longfritz wrote: > > I do not see any transfers to the python client - or, really, anything at > > all other than the occasional empty frame. > > The trace you included does have one incoming transfer: > > > [0x7f8906

Re: Qpid as a RabbitMQ broker for Java app integration tests - exchange declare arguments

On Mon, 18 Nov 2019 at 13:42, Lukasz Guzik wrote: > Hi Rob, > > Yes, this is a perfect solution for me, thank you! :) > Could you please let me know when it will be released? > > Alex - do we have a plan for the next release yet? -- Rob > niedz., 17 lis 2019 o 23:30 Rob Godfrey > napisał(a):

Re: [python] Receiver find current queued messages, but no new ones

On 18/11/2019 1:01 pm, Mike Longfritz wrote: I do not see any transfers to the python client - or, really, anything at all other than the occasional empty frame. The trace you included does have one incoming transfer: [0x7f8906cedea0]:0 <- @transfer(20) [handle=0, delivery-id=0, delivery-tag=

Re: Dispatch-Router statistics and CPU consumption

On Mon, Nov 18, 2019 at 3:51 AM VERMEULEN Olivier < olivier.vermeu...@murex.com> wrote: > Hello, > > We're using the Dispatch-Router 1.9.0. > Is there a way, using the AMQP management of the Dispatch-Router, to > retrieve statistics like the CPU consumption? > There are no plans to do this at the

Re: [python] Receiver find current queued messages, but no new ones

I do not see any transfers to the python client - or, really, anything at all other than the occasional empty frame. Sorry for the dump here, I hope this is helpful: PYTHON STARTUP [0x7f8906cedea0]: -> SASL [0x7f8906cedea0]: <- SASL [0x7f8906cedea0]:0 <- @sasl-mechanisms(64) [sasl-server-mecha

Re: Qpid as a RabbitMQ broker for Java app integration tests - exchange declare arguments

Hi Rob, Yes, this is a perfect solution for me, thank you! :) Could you please let me know when it will be released? niedz., 17 lis 2019 o 23:30 Rob Godfrey napisał(a): > Hi Łukasz, > > I have made an enhancement to the Broker as QPID-8377 > alo

Re: [python] Receiver find current queued messages, but no new ones

On 18/11/2019 12:07 pm, Mike Longfritz wrote: It's the latter, unfortunately. I set self.expected to zero and self.timeout to something big so that poll_for_messages() runs basically indefinitely - and new messages are not seen. With PN_TRACE_FRM set to true, I see empty frames being sent one wa

Re: [python] Receiver find current queued messages, but no new ones

It's the latter, unfortunately. I set self.expected to zero and self.timeout to something big so that poll_for_messages() runs basically indefinitely - and new messages are not seen. With PN_TRACE_FRM set to true, I see empty frames being sent one way every ~15 seconds, but not the other way: [0

Re: [python] Receiver find current queued messages, but no new ones

On 16/11/2019 11:34 pm, Mike Longfritz wrote: I have a receiver that is connecting to an apache qpid queue (java-based, I believe, though that's probably not relevant). The issue I'm finding is that the receiver gets messages that are currently in the queue when it connects (there are often many)

Dispatch-Router statistics and CPU consumption

Hello, We're using the Dispatch-Router 1.9.0. Is there a way, using the AMQP management of the Dispatch-Router, to retrieve statistics like the CPU consumption? Thanks, Olivier *** This e-mail contains information for the intended recipient only. It may contain propr