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=b"\x00", message-format=0] (1592) "..."
was that message seen by the app? Is it one that was already on the queue?
Also there is one difference in the attach that may be relevant, the
distribution-mode. Have you tried your python app with delete=True?
[0x7f8906cedea0]:0 -> @attach(18) [name="xxx", handle=0, role=true,
snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="xxx",
durable=0, timeout=0, dynamic=false, distribution-mode=:copy],
target=@target(41) [durable=0, timeout=0, dynamic=false],
initial-delivery-count=0, max-message-size=0]
v.
[2040136358:1] -> Attach{name='qpid-jms:receiver:xxx', handle=0,
role=RECEIVER, sndSettleMode=UNSETTLED, rcvSettleMode=FIRST,
source=Source{address='xxx', durable=NONE, expiryPolicy=LINK_DETACH,
timeout=0, dynamic=false, dynamicNodeProperties=null,
distributionMode=null, filter=null,
defaultOutcome=Modified{deliveryFailed=true, undeliverableHere=null,
messageAnnotations=null}, outcomes=[amqp:accepted:list, amqp:rejected:list,
amqp:released:list, amqp:modified:list], capabilities=[queue]},
target=Target{address='null', durable=NONE, expiryPolicy=SESSION_END,
timeout=0, dynamic=false, dynamicNodeProperties=null, capabilities=null},
unsettled=null, incompleteUnsettled=false, initialDeliveryCount=null,
maxMessageSize=null, offeredCapabilities=null, desiredCapabilities=null,
properties=null}
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
