You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by jihong <zu...@hotmail.com> on 2015/07/15 18:11:34 UTC

Failed to send large batch of messages to Event Hub with Qpid Proton-C

Greetings,
  I tried to send messages in batch asynchronously to Azure Event Hub using
Qpid Proton C. It seems that sending will fail when the batch size is
greater than 50. The protocol traces show the handshake will fail when batch
size exceeds 50. Below are protocol traces for failed sending:

[0x7521c0]:  -> SASL
[0x7521c0]:0 -> @sasl-init(65) [mechanism=:PLAIN,
initial-response=b"\x00sendRule\x00Z0ipoEPvXzQVKw++q+5cChHLJhCgjXOtX+QTn0QSo3A="]
[0x7521c0]:0 -> @open(16) [container-id=""]
[0x7521c0]:0 -> @close(24) [error=@error(29)
[condition=:"amqp:connection:framing-error", description="SSL Failure:
error:140780E5:SSL routines:SSL23_READ:ssl handshake failure"]]
[0x7521c0]:  <- EOS
[0x7521c0]:  -> EOS

   By contrast, when message batch size is 50, the handshake can succeed:

[0x1e361c0]:  -> SASL
[0x1e361c0]:0 -> @sasl-init(65) [mechanism=:PLAIN,
initial-response=b"\x00sendRule\x00Z0ipoEPvXzQVKw++q+5cChHLJhCgjXOtX+QTn0QSo3A="]
[0x1e361c0]:0 <- @sasl-mechanisms(64)
[sasl-server-mechanisms=@PN_SYMBOL[:PLAIN, :EXTERNAL]]


[0x1e361c0]:0 <- @sasl-outcome(68) [code=0, additional-data=b"Welcome!"]
[0x1e361c0]:  -> AMQP
[0x1e361c0]:0 -> @open(16)
[container-id="85b207fe-68de-4bf2-a551-fe32dbe12c87",
hostname="bluebeam-ns.servicebus.windows.net"]
[0x1e361c0]:0 -> @begin(17) [next-outgoing-id=0, incoming-window=2147483647,
outgoing-window=50]
[0x1e361c0]:0 -> @attach(18) [name="sender-xxx", handle=0, role=false,
snd-settle-mode=1, rcv-settle-mode=0, source=@source(40)
[address="bluebeam", durable=0, timeout=0, dynamic=false],
target=@target(41) [address="bluebeam", durable=0, timeout=0,
dynamic=false], initial-delivery-count=0]

[0x1e361c0]:0 <- @open(16)
[container-id="e64e1a369a8542c299eb4acd0adea354_G38", max-frame-size=65536,
channel-max=4999, idle-time-out=240000]
[0x1e361c0]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=1,
incoming-window=50, outgoing-window=5000, handle-max=255]
[0x1e361c0]:0 <- @attach(18) [name="sender-xxx", handle=0, role=true,
snd-settle-mode=1, rcv-settle-mode=0, source=@source(40)
[address="bluebeam", durable=0, timeout=0, dynamic=false],
target=@target(41) [address="bluebeam", durable=0, timeout=0,
dynamic=false], max-message-size=262144,
properties={:"com.microsoft:tracking-id"="e64e1a369a8542c299eb4acd0adea354_G38"}]
[0x1e361c0]:0 <- @flow(19) [next-incoming-id=0, incoming-window=50,
next-outgoing-id=1, outgoing-window=5000, handle=0, delivery-count=0,
link-credit=300, available=0, echo=false]
[0x1e361c0]:0 -> @transfer(20) [handle=0, delivery-id=0,
delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0,
settled=false, more=false] (349)
"\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00p\x00\x00\x00\x0d@@\xa13amqps://bluebeam-ns.servicebus.windows.net/bluebeam@@@\xa3\x19application/octect-stream@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Su\xa0\xcd{"version":
"0.1.0", "eventType": "lift-status", "deviceId": "ELEV-2000-MON-2000",
"timestamp": "2015-07-15 15:39:15 UTC", "liftId": "ELEV-2000", "liftStatus":
"ascending", "curFloor": 10, "weight": 268.0}"

   What's the reason behind this? And do I miss some configuration options?
Thanks!



--
View this message in context: http://qpid.2158936.n2.nabble.com/Failed-to-send-large-batch-of-messages-to-Event-Hub-with-Qpid-Proton-C-tp7628207.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org