[jira] [Commented] (PROTON-561) Using the java broker, messenger apparently doesn't propagate error back from broker to messenger
[
https://issues.apache.org/jira/browse/PROTON-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14066894#comment-14066894
]
Keith Wall commented on PROTON-561:
---
Should be fixed in Java Broker 0.30.
Using the java broker, messenger apparently doesn't propagate error back from
broker to messenger
-
Key: PROTON-561
URL: https://issues.apache.org/jira/browse/PROTON-561
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.6, 0.7
Reporter: Justin Ross
(The java broker logging for AMQP 1.0 is minimal; I'll mention that in
another jira.)
The test program below simply hangs. It didn't seem to want to time out,
either.
{noformat}
from proton import Message, Messenger
msgr = Messenger()
msgr.start()
try:
msg = Message()
msg.address = amqp://0.0.0.0:5672/test
msg.body = test
msgr.put(msg)
msgr.send()
finally:
msgr.stop()
{noformat}
By contrast, the same operation rendered in the qpid_messaging API produces
the expected error:
{noformat}
import sys
# You will need to build the swig python binding and point at it
sys.path.append(/home/jross/code/qpid/cpp/build/bindings/qpid/python)
from qpid_messaging import Connection
conn = Connection(0.0.0.0:5672, protocol=amqp1.0)
conn.open()
try:
session = conn.session()
sender = session.sender(test)
message = Message(test)
sender.send(message)
finally:
conn.close()
{noformat}
Error:
{noformat}
Traceback (most recent call last):
File /home/jross/test2.py, line 13, in module
sender = session.sender(test)
File
/home/jross/code/qpid/cpp/build/bindings/qpid/python/qpid_messaging.py,
line 560, in sender
s = self._sender(target)
File
/home/jross/code/qpid/cpp/build/bindings/qpid/python/qpid_messaging.py,
line 532, in _sender
def _sender(self, *args): return _qpid_messaging.Session__sender(self,
*args)
_qpid_messaging.NotFound: No such target : test
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (PROTON-561) Using the java broker, messenger apparently doesn't propagate error back from broker to messenger
[
https://issues.apache.org/jira/browse/PROTON-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966758#comment-13966758
]
Rafael H. Schloming commented on PROTON-561:
Can you try export PN_TRACE_FRM=1 on the client side? That should give us the
log from the clients perspective at least.
Using the java broker, messenger apparently doesn't propagate error back from
broker to messenger
-
Key: PROTON-561
URL: https://issues.apache.org/jira/browse/PROTON-561
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Reporter: Justin Ross
(The java broker logging for AMQP 1.0 is minimal; I'll mention that in
another jira.)
The test program below simply hangs. It didn't seem to want to time out,
either.
{noformat}
from proton import Message, Messenger
msgr = Messenger()
msgr.start()
try:
msg = Message()
msg.address = amqp://0.0.0.0:5672/test
msg.body = test
msgr.put(msg)
msgr.send()
finally:
msgr.stop()
{noformat}
By contrast, the same operation rendered in the qpid_messaging API produces
the expected error:
{noformat}
import sys
# You will need to build the swig python binding and point at it
sys.path.append(/home/jross/code/qpid/cpp/build/bindings/qpid/python)
from qpid_messaging import Connection
conn = Connection(0.0.0.0:5672, protocol=amqp1.0)
conn.open()
try:
session = conn.session()
sender = session.sender(test)
message = Message(test)
sender.send(message)
finally:
conn.close()
{noformat}
Error:
{noformat}
Traceback (most recent call last):
File /home/jross/test2.py, line 13, in module
sender = session.sender(test)
File
/home/jross/code/qpid/cpp/build/bindings/qpid/python/qpid_messaging.py,
line 560, in sender
s = self._sender(target)
File
/home/jross/code/qpid/cpp/build/bindings/qpid/python/qpid_messaging.py,
line 532, in _sender
def _sender(self, *args): return _qpid_messaging.Session__sender(self,
*args)
_qpid_messaging.NotFound: No such target : test
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (PROTON-561) Using the java broker, messenger apparently doesn't propagate error back from broker to messenger
[
https://issues.apache.org/jira/browse/PROTON-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966819#comment-13966819
]
Justin Ross commented on PROTON-561:
I get the same result with trunk.
Using the java broker, messenger apparently doesn't propagate error back from
broker to messenger
-
Key: PROTON-561
URL: https://issues.apache.org/jira/browse/PROTON-561
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.6, 0.7
Reporter: Justin Ross
(The java broker logging for AMQP 1.0 is minimal; I'll mention that in
another jira.)
The test program below simply hangs. It didn't seem to want to time out,
either.
{noformat}
from proton import Message, Messenger
msgr = Messenger()
msgr.start()
try:
msg = Message()
msg.address = amqp://0.0.0.0:5672/test
msg.body = test
msgr.put(msg)
msgr.send()
finally:
msgr.stop()
{noformat}
By contrast, the same operation rendered in the qpid_messaging API produces
the expected error:
{noformat}
import sys
# You will need to build the swig python binding and point at it
sys.path.append(/home/jross/code/qpid/cpp/build/bindings/qpid/python)
from qpid_messaging import Connection
conn = Connection(0.0.0.0:5672, protocol=amqp1.0)
conn.open()
try:
session = conn.session()
sender = session.sender(test)
message = Message(test)
sender.send(message)
finally:
conn.close()
{noformat}
Error:
{noformat}
Traceback (most recent call last):
File /home/jross/test2.py, line 13, in module
sender = session.sender(test)
File
/home/jross/code/qpid/cpp/build/bindings/qpid/python/qpid_messaging.py,
line 560, in sender
s = self._sender(target)
File
/home/jross/code/qpid/cpp/build/bindings/qpid/python/qpid_messaging.py,
line 532, in _sender
def _sender(self, *args): return _qpid_messaging.Session__sender(self,
*args)
_qpid_messaging.NotFound: No such target : test
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (PROTON-561) Using the java broker, messenger apparently doesn't propagate error back from broker to messenger
[
https://issues.apache.org/jira/browse/PROTON-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966882#comment-13966882
]
Justin Ross commented on PROTON-561:
Sure!
{noformat}
jross@localhost bailey$ LD_LIBRARY_PATH=/tmp/tmp.mXaVrrHF8a/lib64
PYTHONPATH=/tmp/tmp.mXaVrrHF8a/lib64/proton/bindings/python/ PN_TRACE_FRM=1
python ~/test.py
[0x221be30]: - SASL
[0x221be30]:0 - @sasl-init(65) [mechanism=:ANONYMOUS, initial-response=b]
[0x221be30]: - SASL
[0x221be30]:0 - @sasl-mechanisms(64)
[sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS, :DIGEST-MD5, :PLAIN]]
[0x221be30]:0 - @sasl-outcome(68) [code=0]
[0x221be30]: - AMQP
[0x221be30]:0 - @open(16)
[container-id=2c45594d-8db2-4e9c-8a46-b45a43858c4a, hostname=0.0.0.0]
[0x221be30]:0 - @begin(17) [next-outgoing-id=0, incoming-window=2147483647,
outgoing-window=1]
[0x221be30]:0 - @attach(18) [name=sender-xxx, handle=0, role=false,
snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address=test,
durable=0, timeout=0, dynamic=false], target=@target(41) [address=test,
durable=0, timeout=0, dynamic=false], initial-delivery-count=0]
[0x221be30]: - AMQP
[0x221be30]:0 - @open(16) [container-id=7425ccf2-d216-40f5-a820-9772c0070ce8]
[0x221be30]:0 - @begin(17) [remote-channel=0, next-outgoing-id=0,
incoming-window=2147483647, outgoing-window=0]
[0x221be30]:0 - @attach(18) [name=sender-xxx, handle=0, role=true,
snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [durable=0, timeout=0,
dynamic=false], initial-delivery-count=0]
[0x221be30]:0 - @detach(22) [handle=0, closed=true, error=@error(29)
[condition=:amqp:not-found, description=Node not found: test]]
LINK ERROR (amqp:not-found) Node not found: test
[0x221be30]:0 - @detach(22) [handle=0, closed=true]
[0x221be30]:0 - @close(24) []
[0x221be30]: - EOS
[0x221be30]: - EOS
[0x221be30]:0 - @close(24) []
[0x221be30]: - EOS
[0x221be30]: - EOS
[0x221be30]: - EOS
[0x221be30]: - EOS
{noformat}
On potentially another topic, is this expected:
https://gist.github.com/ssorj/10488102 . That's what happened when I
accidentally ran the test against qpidd without the 1.0 module. I'm surprised
that it surfaces as a SASL error. Let me know if I should file another jira.
Using the java broker, messenger apparently doesn't propagate error back from
broker to messenger
-
Key: PROTON-561
URL: https://issues.apache.org/jira/browse/PROTON-561
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.6, 0.7
Reporter: Justin Ross
(The java broker logging for AMQP 1.0 is minimal; I'll mention that in
another jira.)
The test program below simply hangs. It didn't seem to want to time out,
either.
{noformat}
from proton import Message, Messenger
msgr = Messenger()
msgr.start()
try:
msg = Message()
msg.address = amqp://0.0.0.0:5672/test
msg.body = test
msgr.put(msg)
msgr.send()
finally:
msgr.stop()
{noformat}
By contrast, the same operation rendered in the qpid_messaging API produces
the expected error:
{noformat}
import sys
# You will need to build the swig python binding and point at it
sys.path.append(/home/jross/code/qpid/cpp/build/bindings/qpid/python)
from qpid_messaging import Connection
conn = Connection(0.0.0.0:5672, protocol=amqp1.0)
conn.open()
try:
session = conn.session()
sender = session.sender(test)
message = Message(test)
sender.send(message)
finally:
conn.close()
{noformat}
Error:
{noformat}
Traceback (most recent call last):
File /home/jross/test2.py, line 13, in module
sender = session.sender(test)
File
/home/jross/code/qpid/cpp/build/bindings/qpid/python/qpid_messaging.py,
line 560, in sender
s = self._sender(target)
File
/home/jross/code/qpid/cpp/build/bindings/qpid/python/qpid_messaging.py,
line 532, in _sender
def _sender(self, *args): return _qpid_messaging.Session__sender(self,
*args)
_qpid_messaging.NotFound: No such target : test
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (PROTON-561) Using the java broker, messenger apparently doesn't propagate error back from broker to messenger
[
https://issues.apache.org/jira/browse/PROTON-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966905#comment-13966905
]
Rafael H. Schloming commented on PROTON-561:
What you're seeing there is expected in that the client is looking for a SASL
header and finding something (in this case the 0-10 header). We could make the
behaviour more friendly in a couple of ways, the simplest would be to just
rephrase the error message so it's more clear that it is a protocol header
missmatch, e.g. something like Protocol header missmatch: expecting SASL
header, found X. To get slightly fancier we could probably have some sort of
lookup for common headers we might run into like the 0-10 headers or TLS
headers. That would allow us to put something human readable in for X instead
of just displaying the raw binary.
On the original topic, I haven't yet verified if this is the issue, but if you
notice, the detach coming from the Java Broker does not specify closed=true,
and the default value would be closed=false. That could be the cause of the
hang and is probably deserving of a separate JIRA for the Java broker. Either
way proton should handle the situation more gracefully than just hanging so I'd
say this JIRA still stands.
Using the java broker, messenger apparently doesn't propagate error back from
broker to messenger
-
Key: PROTON-561
URL: https://issues.apache.org/jira/browse/PROTON-561
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Affects Versions: 0.6, 0.7
Reporter: Justin Ross
(The java broker logging for AMQP 1.0 is minimal; I'll mention that in
another jira.)
The test program below simply hangs. It didn't seem to want to time out,
either.
{noformat}
from proton import Message, Messenger
msgr = Messenger()
msgr.start()
try:
msg = Message()
msg.address = amqp://0.0.0.0:5672/test
msg.body = test
msgr.put(msg)
msgr.send()
finally:
msgr.stop()
{noformat}
By contrast, the same operation rendered in the qpid_messaging API produces
the expected error:
{noformat}
import sys
# You will need to build the swig python binding and point at it
sys.path.append(/home/jross/code/qpid/cpp/build/bindings/qpid/python)
from qpid_messaging import Connection
conn = Connection(0.0.0.0:5672, protocol=amqp1.0)
conn.open()
try:
session = conn.session()
sender = session.sender(test)
message = Message(test)
sender.send(message)
finally:
conn.close()
{noformat}
Error:
{noformat}
Traceback (most recent call last):
File /home/jross/test2.py, line 13, in module
sender = session.sender(test)
File
/home/jross/code/qpid/cpp/build/bindings/qpid/python/qpid_messaging.py,
line 560, in sender
s = self._sender(target)
File
/home/jross/code/qpid/cpp/build/bindings/qpid/python/qpid_messaging.py,
line 532, in _sender
def _sender(self, *args): return _qpid_messaging.Session__sender(self,
*args)
_qpid_messaging.NotFound: No such target : test
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
