You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Maheedhar Gunnam <ma...@netapp.com> on 2020/11/04 18:06:53 UTC
Connection aborted with amqp:connection:framing-error
Hello Team,
I am running into a weird scenario where I have a python client connected as
a receiver, killing this client leads to a framing error as below
2020-11-03 11:25:34.249356 -0500 PROTOCOL (trace) [5]:FRAME: 0 -> @close(24)
[error=@error(29) [condition=:"amqp:connection:framing-error",
description="connection aborted"]] (distro/src/server.c:112)
2020-11-03 11:25:34.252048 -0500 PROTOCOL (trace) [5]:RAW: RAW:
"\x00\x00\x00S\x02\x00\x00\x00\x00S\x18\xd0\x00\x00\x00C\x00\x00\x00\x01\x00S\x1d\xd0\x00\x00\x007\x00\x00\x00\x02\xa3\x1damqp:connection:framing-error\xa1\x12connection
aborted" (distro/src/server.c:112)
Further the control flow fails at the assertion `qd_conn->n_senders >= 0`
but continues with the execution though.
Below is the backtrace on gdb:
#1 0x000000080126b6bf in __assert (func=<optimized out>, file=0x8004eb973
"distro/src/container.c", line=714, failedexpr=0x8004ea63c
"qd_conn->n_senders >= 0") at ../../../../../../src/lib/libc/gen/assert.c:55
#2 0x000000080052f6ea in qd_container_handle_event (container=0x801b19020,
event=0x80559fb10, conn=0x8044dd510, qd_conn=0x8044ee090) at
distro/src/container.c:714
#3 0x000000080059cc28 in handle (qd_server=0x801a66240, e=0x80559fb10,
pn_conn=0x8044dd510, ctx=0x8044ee090) at distro/src/server.c:1041
#4 0x000000080059afbd in thread_run (arg=0x801a66240) at
distro/src/server.c:1066
#5 0x00000008005a210a in _thread_init (arg=0x801b790a0) at
distro/src/posix/threading.c:172
#6 0x0000000800b6a8c5 in thread_start (curthread=0x801a34e00) at
../../../../../../src/lib/libthr/thread/thr_create.c:299
I am not really sure whether this is an indication of an existing problem.
Can someone please shed some light on this?
I am using qpid-c++ broker and python client as the receiver.
Thanks in advance.
-Mahee
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Connection aborted with amqp:connection:framing-error
Posted by Gordon Sim <gs...@redhat.com>.
On 05/11/2020 7:56 pm, Maheedhar Gunnam wrote:
> This behavior is reproducible 100% of the time. Basically, on the disconnect
> of every client(receiver) I see the assertion failure.
>
> *1.13.0* is the ROUTER version.
I can run python examples against a debug build of 1.13.0 and kill or
cleanly disconnect the clients without any assertion. That version has
been quite widely used so I suspect there must be more to whatever issue
you are seeing.
Do you see the assertion when running e.g. the helloworld.py example? or
simple_recv.py which you then kill? Are you running with a particular
router config or do you see the issue even with the default config?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Connection aborted with amqp:connection:framing-error
Posted by Maheedhar Gunnam <ma...@netapp.com>.
This behavior is reproducible 100% of the time. Basically, on the disconnect
of every client(receiver) I see the assertion failure.
*1.13.0* is the ROUTER version.
Thank you,
Mahee
--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Connection aborted with amqp:connection:framing-error
Posted by Ted Ross <tr...@redhat.com>.
On Wed, Nov 4, 2020 at 2:00 PM Gordon Sim <gs...@redhat.com> wrote:
> On 04/11/2020 6:06 pm, Maheedhar Gunnam wrote:
> > Hello Team,
> >
> > I am running into a weird scenario where I have a python client
> connected as
> > a receiver, killing this client leads to a framing error as below
> >
> > 2020-11-03 11:25:34.249356 -0500 PROTOCOL (trace) [5]:FRAME: 0 ->
> @close(24)
> > [error=@error(29) [condition=:"amqp:connection:framing-error",
> > description="connection aborted"]] (distro/src/server.c:112)
> > 2020-11-03 11:25:34.252048 -0500 PROTOCOL (trace) [5]:RAW: RAW:
> >
> "\x00\x00\x00S\x02\x00\x00\x00\x00S\x18\xd0\x00\x00\x00C\x00\x00\x00\x01\x00S\x1d\xd0\x00\x00\x007\x00\x00\x00\x02\xa3\x1damqp:connection:framing-error\xa1\x12connection
> > aborted" (distro/src/server.c:112)
> >
> > Further the control flow fails at the assertion `qd_conn->n_senders >= 0`
> > but continues with the execution though.
> >
> > Below is the backtrace on gdb:
> > #1 0x000000080126b6bf in __assert (func=<optimized out>,
> file=0x8004eb973
> > "distro/src/container.c", line=714, failedexpr=0x8004ea63c
> > "qd_conn->n_senders >= 0") at
> ../../../../../../src/lib/libc/gen/assert.c:55
> > #2 0x000000080052f6ea in qd_container_handle_event
> (container=0x801b19020,
> > event=0x80559fb10, conn=0x8044dd510, qd_conn=0x8044ee090) at
> > distro/src/container.c:714
> > #3 0x000000080059cc28 in handle (qd_server=0x801a66240, e=0x80559fb10,
> > pn_conn=0x8044dd510, ctx=0x8044ee090) at distro/src/server.c:1041
> > #4 0x000000080059afbd in thread_run (arg=0x801a66240) at
> > distro/src/server.c:1066
> > #5 0x00000008005a210a in _thread_init (arg=0x801b790a0) at
> > distro/src/posix/threading.c:172
> > #6 0x0000000800b6a8c5 in thread_start (curthread=0x801a34e00) at
> > ../../../../../../src/lib/libthr/thread/thr_create.c:299
> >
> >
> > I am not really sure whether this is an indication of an existing
> problem.
> > Can someone please shed some light on this?
> >
> > I am using qpid-c++ broker and python client as the receiver.
>
> The trace above is for the router (not the broker). If the assert is
> failing it certainly suggests a bug. Do you have a reproducer?
>
Also, can you tell us which version of the router you are running?
Thanks,
-Ted
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Connection aborted with amqp:connection:framing-error
Posted by Gordon Sim <gs...@redhat.com>.
On 04/11/2020 6:06 pm, Maheedhar Gunnam wrote:
> Hello Team,
>
> I am running into a weird scenario where I have a python client connected as
> a receiver, killing this client leads to a framing error as below
>
> 2020-11-03 11:25:34.249356 -0500 PROTOCOL (trace) [5]:FRAME: 0 -> @close(24)
> [error=@error(29) [condition=:"amqp:connection:framing-error",
> description="connection aborted"]] (distro/src/server.c:112)
> 2020-11-03 11:25:34.252048 -0500 PROTOCOL (trace) [5]:RAW: RAW:
> "\x00\x00\x00S\x02\x00\x00\x00\x00S\x18\xd0\x00\x00\x00C\x00\x00\x00\x01\x00S\x1d\xd0\x00\x00\x007\x00\x00\x00\x02\xa3\x1damqp:connection:framing-error\xa1\x12connection
> aborted" (distro/src/server.c:112)
>
> Further the control flow fails at the assertion `qd_conn->n_senders >= 0`
> but continues with the execution though.
>
> Below is the backtrace on gdb:
> #1 0x000000080126b6bf in __assert (func=<optimized out>, file=0x8004eb973
> "distro/src/container.c", line=714, failedexpr=0x8004ea63c
> "qd_conn->n_senders >= 0") at ../../../../../../src/lib/libc/gen/assert.c:55
> #2 0x000000080052f6ea in qd_container_handle_event (container=0x801b19020,
> event=0x80559fb10, conn=0x8044dd510, qd_conn=0x8044ee090) at
> distro/src/container.c:714
> #3 0x000000080059cc28 in handle (qd_server=0x801a66240, e=0x80559fb10,
> pn_conn=0x8044dd510, ctx=0x8044ee090) at distro/src/server.c:1041
> #4 0x000000080059afbd in thread_run (arg=0x801a66240) at
> distro/src/server.c:1066
> #5 0x00000008005a210a in _thread_init (arg=0x801b790a0) at
> distro/src/posix/threading.c:172
> #6 0x0000000800b6a8c5 in thread_start (curthread=0x801a34e00) at
> ../../../../../../src/lib/libthr/thread/thr_create.c:299
>
>
> I am not really sure whether this is an indication of an existing problem.
> Can someone please shed some light on this?
>
> I am using qpid-c++ broker and python client as the receiver.
The trace above is for the router (not the broker). If the assert is
failing it certainly suggests a bug. Do you have a reproducer?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org