JAkub Scholz created QPID-6353:
----------------------------------
Summary: Java broker AMQP 1.0 impl doesn't seem to support
"synchronous get" / respond to drain request
Key: QPID-6353
URL: https://issues.apache.org/jira/browse/QPID-6353
Project: Qpid
Issue Type: Bug
Components: Java Broker
Affects Versions: 0.30
Reporter: JAkub Scholz
While playing with the C++ qpid.messaging client and the Java broker (both from
release 0.30), I noticed that the fetch() command with a timeout never
timeouts. It seems to be reproducible even with the qpid-receive:
qpid-receive -b admin/[email protected]:5672 -a "testQueue; { node: { type:
queue } }" --timeout 10 --connection-options "{protocol: amqp1.0}"
>From the log it looks like the Java broker doesn't properly implement the
>"synchronous get" feature and keeps the client hanging
[vagrant@localhost ~]$ qpid-receive -b admin/[email protected]:5672 -a
"testQueue; { node: { type: queue } }" --timeout 10 --connection-options
"{protocol: amqp1.0}"
2015-02-02 23:21:47 [Protocol] debug tcp:192.168.33.1:5672 writing protocol
header: 1-0
2015-02-02 23:21:47 [Protocol] debug tcp:192.168.33.1:5672 read protocol
header: 1-0
2015-02-02 23:21:47 [Protocol] debug tcp:192.168.33.1:5672 Received
SASL-MECHANISMS(CRAM-MD5 )
2015-02-02 23:21:47 [Protocol] debug tcp:192.168.33.1:5672 Sent
SASL-INIT(CRAM-MD5, null, 192.168.33.1)
2015-02-02 23:21:47 [Protocol] debug tcp:192.168.33.1:5672 Received
SASL-CHALLENGE(46 bytes)
2015-02-02 23:21:47 [Protocol] debug tcp:192.168.33.1:5672 Sent
SASL-RESPONSE(admin d57002773e3649eb2ee1e628f7e67b13)
2015-02-02 23:21:47 [Protocol] debug tcp:192.168.33.1:5672 Received
SASL-OUTCOME(\x00)
2015-02-02 23:21:47 [Protocol] trace [572afd7a-ddad-4d58-8dfe-99f747162284]:
<- AMQP
2015-02-02 23:21:47 [Protocol] trace [572afd7a-ddad-4d58-8dfe-99f747162284]:
-> AMQP
2015-02-02 23:21:47 [Protocol] trace [572afd7a-ddad-4d58-8dfe-99f747162284]: 0
-> @open(16) [container-id="572afd7a-ddad-4d58-8dfe-99f747162284",
properties={:"qpid.client_process"="qpid-receive", :"qpid.client_pid"=15027,
:"qpid.client_ppid"=1938}]
2015-02-02 23:21:47 [Protocol] trace [572afd7a-ddad-4d58-8dfe-99f747162284]: 0
<- @open(16) [container-id="fb3f1523-f85c-4c46-997b-e637c17014a9",
max-frame-size=32768, channel-max=255, properties={:product="qpid",
:version="0.30", :"qpid.build"="Unversioned directory",
:"qpid.instance_name"="Broker"}]
2015-02-02 23:21:47 [Protocol] trace [572afd7a-ddad-4d58-8dfe-99f747162284]: 0
-> @begin(17) [next-outgoing-id=0, incoming-window=2147483647,
outgoing-window=0]
2015-02-02 23:21:47 [Protocol] trace [572afd7a-ddad-4d58-8dfe-99f747162284]: 0
<- @begin(17) [remote-channel=0, next-outgoing-id=0, incoming-window=2048,
outgoing-window=2048]
2015-02-02 23:21:47 [Protocol] trace [572afd7a-ddad-4d58-8dfe-99f747162284]: 0
-> @attach(18) [name="testQueue_46e96608-19ae-49cd-a7d2-ae6e1d6afa3b",
handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
[address="testQueue", durable=0, timeout=0, dynamic=false,
capabilities=:queue], target=@target(41) [address="testQueue", durable=0,
timeout=0, dynamic=false], initial-delivery-count=0]
2015-02-02 23:21:47 [Protocol] trace [572afd7a-ddad-4d58-8dfe-99f747162284]: 0
<- @attach(18) [name="testQueue_46e96608-19ae-49cd-a7d2-ae6e1d6afa3b",
handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
[address="testQueue", durable=0, timeout=0, dynamic=false,
capabilities=@PN_SYMBOL[:queue]], target=@target(41) [address="testQueue",
durable=0, timeout=0, dynamic=false], initial-delivery-count=0]
2015-02-02 23:21:47 [Protocol] trace [572afd7a-ddad-4d58-8dfe-99f747162284]: 0
-> @flow(19) [next-incoming-id=0, incoming-window=2147483647,
next-outgoing-id=0, outgoing-window=0, handle=0, delivery-count=0,
link-credit=1000, drain=false]
2015-02-02 23:21:57 [Protocol] trace [572afd7a-ddad-4d58-8dfe-99f747162284]: 0
-> @flow(19) [next-incoming-id=0, incoming-window=2147483647,
next-outgoing-id=0, outgoing-window=0, handle=0, delivery-count=0,
link-credit=1000, drain=true]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
