Qpid-Proton 0.10 not working

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Qpid-Proton 0.10 not working

serega
Hello.
I want to upgrade Qpid-Proton from 0.6 to the latest 0.10

Yet when running the send utility from 0.10
./send -a amqp://10.250.0.127:5672/testqueue@router1  Test

I get errors in the error.log, the errors telling that there are some wrong headers received.

2015-09-16 20:12:55.349/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=AMQP, id=0, major=1, minor=0, revision=0], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.349/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=R, id=2, major=0, minor=0, revision=0], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.349/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=S�, id=0, major=0, minor=0, revision=66], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.349/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=
, id=-95, major=36, minor=67, revision=67], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.349/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=37F1, id=53, major=70, minor=45, revision=49], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.350/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=422-, id=52, major=52, minor=53, revision=56], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.350/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=-B88, id=70, major=45, minor=68, revision=66], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.350/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=016A, id=48, major=55, minor=53, revision=54], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.350/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=71�
                                                                                                                                          , id=49, major=48, minor=46, revision=50], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.351/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=50.0, id=46, major=49, minor=50, revision=55], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.351/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=@`�, id=64, major=64, minor=64, revision=64], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.351/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=@@, id=0, major=33, minor=2, revision=0], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.351/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=S, id=17, major=-48, minor=0, revision=0], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.351/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=, id=0, major=4, minor=64, revision=82], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.351/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=p�, id=-1, major=-1, minor=112, revision=127], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.351/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=���, id=0, major=0, minor=125, revision=2], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.352/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=, id=83, major=18, minor=-48, revision=0], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.352/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=m, id=0, major=0, minor=10, revision=-95], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.352/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=
sen, id=100, major=101, minor=114, revision=45], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.352/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=xxxR, id=0, major=66, minor=80, revision=2], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.352/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=PS, id=40, major=-48, minor=0, revision=0], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.352/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=#, id=0, major=11, minor=-95, revision=17], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.352/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=test, id=113, major=117, minor=101, revision=117], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.352/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=e@ro, id=117, major=116, minor=101, revision=114], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.353/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=1R@, id=82, major=0, minor=66, revision=64], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.353/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=@@@@, id=64, major=0, minor=83, revision=41], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.353/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=�, id=31, major=0, minor=0, revision=0], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.353/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=�t, id=101, major=115, minor=116, revision=113], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.353/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=ueue, id=64, major=114, minor=111, revision=117], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.353/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=ter1, id=82, major=0, minor=64, revision=82], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection
2015-09-16 20:12:55.353/sys$amqp/ERROR/VersionedConnection, connection=10.250.0.137:40576/wrong header received: [ProtocolHeader, name=B@@, id=64, major=64, minor=82, revision=0], required: [ProtocolHeader, name=AMQP, id=3, major=1, minor=0, revision=0], closing connection

Reply | Threaded
Open this post in threaded view
|

Re: Qpid-Proton 0.10 not working

IIT Software
Administrator
We haven't changed anything so this is a Qpid issue. Please ask in their mailing list as we don't support their software.

You could enable the "protocol" trace space and rerun the client. Then have a look into protocol.trace to see what is sent/received.
Reply | Threaded
Open this post in threaded view
|

Re: Qpid-Proton 0.10 not working

serega
Another issue that we are experiencing with quid-proton-0.10 is SwiftMQ amqp connector hanging, such that no messages can be sent or received from the existing or new amqp clients. I have a jstack output swiftmq-hang-jstack.txt of the process in that state. I can only recover the server by shutting down the process using kill -9 (regular kill does not work) There can be bugs in the qpid-proton, but the server should not become unavailable because of a client that somehow violates the protocol.
Reply | Threaded
Open this post in threaded view
|

Re: Qpid-Proton 0.10 not working

IIT Software
Administrator
Thanks, we will look into it. If I need any more infos, I'll let you know.
Reply | Threaded
Open this post in threaded view
|

Re: Qpid-Proton 0.10 not working

IIT Software
Administrator
In reply to this post by serega
It seems to be a concurrency problem. Do you close a session/link/connection while you are sending to it?
Reply | Threaded
Open this post in threaded view
|

Re: Qpid-Proton 0.10 not working

serega
quid-proton does have API for sessions/links.

Normally we call pn_messenger_close method
https://qpid.apache.org/releases/qpid-proton-0.10/proton/c/api/group__messenger.html#ga40373fb89d70f6c3b7a4b9a0e9c2d3e4
but here is the catch, C language does not have exceptions and when a C app crashes the opened resources cannot be closed, and that method may not be called. Unfortunately, our legacy C software crashes sometimes, and there is a always a possibility that connection is not closed on the client side.
Yet, shouldn't SwiftMQ recover by itself?  Could you use await methods that take a timestamp?
Reply | Threaded
Open this post in threaded view
|

Re: Qpid-Proton 0.10 not working

IIT Software
Administrator
It seems the amp.connection pool runs out of threads. Per default it is configured with max-threads="5" and I see all of them locked. Increase it to 20 and see if that solves it.
Reply | Threaded
Open this post in threaded view
|

Re: Qpid-Proton 0.10 not working

serega
I increased the number of threads to 20 and haven't had the same situation, but I will keep monitoring.