Gordon Sim wrote
> On 19/10/18 12:13, rk wrote:
>> Using the python client I can send much larger messages than 16k to the
>> same
>> broker so it appears to be an issue with the Go bindings.
>>
>> The issue can be recreated by editing the example send.go file in the
>> electron repo to look like https://play.golang.org/p/2dQ4jdlKHKi
>>
>> I am using version 1.38.0 of qpidd running on Centos 7 and the Go is
>> bring
>> compiled with the latest electron bindings and 0.24.0-1 qpid-proton-c
>> library.
>>
>> My knowledge of AMQP and the qpidd internals isn't great so I'm unsure of
>> why qpidd thinks it hasn't got the delivery so any help much appreciated.
>
>
> If you can get a protocol trace, that would be helpful. --log-enable
> trace+:Protocol as an argument to qpidd should do it.
>
> For additional commands, e-mail:
> users-help@.apache
Protocol output below
2018-10-19 12:27:22 [Protocol] debug qpid.172.18.0.2:5672-172.18.0.4:50426
Sent SASL-MECHANISMS(ANONYMOUS PLAIN) 40
2018-10-19 12:27:22 [Protocol] debug qpid.172.18.0.2:5672-172.18.0.4:50426
writing protocol header: 1-0
2018-10-19 12:27:22 [Protocol] debug qpid.172.18.0.2:5672-172.18.0.4:50426
Received SASL-INIT(ANONYMOUS, anonymous@a9ac779f4434, )
2018-10-19 12:27:22 [Protocol] debug qpid.172.18.0.2:5672-172.18.0.4:50426
Sent SASL-OUTCOME(0) 16
2018-10-19 12:27:22 [Protocol] trace
[qpid.172.18.0.2:5672-172.18.0.4:50426]: -> AMQP
2018-10-19 12:27:22 [Protocol] trace
[qpid.172.18.0.2:5672-172.18.0.4:50426]: <- AMQP
2018-10-19 12:27:22 [Protocol] trace
[qpid.172.18.0.2:5672-172.18.0.4:50426]: 0 <- @open(16)
[container-id="send[1]", channel-max=32767]
2018-10-19 12:27:22 [Protocol] trace
[qpid.172.18.0.2:5672-172.18.0.4:50426]: 0 <- @begin(17)
[next-outgoing-id=0, incoming-window=2147483647, outgoing-window=0]
2018-10-19 12:27:22 [Protocol] trace
[qpid.172.18.0.2:5672-172.18.0.4:50426]: 0 <- @attach(18) [name="send[1]@1",
handle=0, role=false, snd-settle-mode=0, rcv-settle-mode=0,
source=@source(40) [address="", durable=0, expiry-policy=:"link-detach",
timeout=0, dynamic=false], target=@target(41) [address="test_exchange",
durable=0, expiry-policy=:"link-detach", timeout=0, dynamic=false],
initial-delivery-count=0, max-message-size=0]
2018-10-19 12:27:22 [Protocol] debug qpid.172.18.0.2:5672-172.18.0.4:50426
link 0x7f2728001900 attached on 0x7f272801a540
2018-10-19 12:27:22 [Protocol] trace
[qpid.172.18.0.2:5672-172.18.0.4:50426]: 0 -> @open(16)
[container-id="dd6b88fa-8a0e-4437-9aca-22e4626abddc", channel-max=32767,
offered-capabilities=@PN_SYMBOL[:"ANONYMOUS-RELAY"],
properties={:product="qpid-cpp", :version="1.38.0", :platform="Linux",
:host="af00d45580a7"}]
2018-10-19 12:27:22 [Protocol] trace
[qpid.172.18.0.2:5672-172.18.0.4:50426]: 0 -> @begin(17) [remote-channel=0,
next-outgoing-id=0, incoming-window=2147483647, outgoing-window=2147483647]
2018-10-19 12:27:22 [Protocol] trace
[qpid.172.18.0.2:5672-172.18.0.4:50426]: 0 -> @attach(18) [name="send[1]@1",
handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0,
source=@source(40) [durable=0, timeout=0, dynamic=false], target=@target(41)
[address="test_exchange", durable=0, timeout=0, dynamic=false],
initial-delivery-count=0, max-message-size=0]
2018-10-19 12:27:22 [Protocol] trace
[qpid.172.18.0.2:5672-172.18.0.4:50426]: 0 -> @flow(19) [next-incoming-id=0,
incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
handle=0, delivery-count=0, link-credit=500, drain=false]
It does look like the ActiveMQ issue is probably the same thing. The problem
is not always consistent and sometimes the larger messages will get through.
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
