[jira] [Created] (DISPATCH-2359) Link route not detached when outbound connection is terminated while attach is being forwarded
Ganesh Murthy created DISPATCH-2359:
---
Summary: Link route not detached when outbound connection is
terminated while attach is being forwarded
Key: DISPATCH-2359
URL: https://issues.apache.org/jira/browse/DISPATCH-2359
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Affects Versions: 1.19.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
Notice in the below trace that the attach that is coming into the router
(test_address) has come in just before the outbound connection is terminated
and the attach does not actually create a link on the outbound side and is
instead stuck in the core thread and is not detached with the core links are
cleaned up
{noformat}
2023-07-21 06:08:49.717257 -0400 PROTOCOL (trace) [7]:FRAME: 11 <- @attach(18)
[name="eb629c56-52b3-4d10-a511-3f2776dce422", handle=0x8, role=false,
snd-settle-mode=0x2, rcv-settle-mode=0x0, source=@source(40) [durable=0x0,
expiry-policy=:session-end, timeout=0x0, dynamic=false], target=@target(41)
[address="test_address", durable=0x0, expiry-policy=:session-end, timeout=0x0,
dynamic=false], initial-delivery-count=0x0, max-message-size=0x0]
2023-07-21 06:08:49.717348 -0400 PROTOCOL (trace) [9]:FRAME: 0 -> @close(24)
[error=@error(29) [condition=:"amqp:connection:framing-error", description="SSL
Failure: Unknown error"]]
2023-07-21 06:08:49.717361 -0400 PROTOCOL (trace) [9]:FRAME: <- EOS
2023-07-21 06:08:49.717372 -0400 SERVER (info) [C9] Connection to
router2.test.com:55671 failed: amqp:connection:framing-error SSL Failure:
Unknown error
2023-07-21 06:08:49.717381 -0400 PROTOCOL (trace) [9]:FRAME: -> EOS
2023-07-21 06:08:49.717414 -0400 CONTAINER (debug) Aborting link
'qdlink.jpruwfMhn+73tJi' due to parent connection end
2023-07-21 06:08:49.717428 -0400 CONTAINER (debug) Aborting link
'qdlink.9Np_9D9Quv_3AmE' due to parent connection end
2023-07-21 06:08:49.717437 -0400 CONTAINER (debug) Aborting link
'qdlink.J_OXudwlskEHGbK' due to parent connection end
2023-07-21 06:08:49.717446 -0400 CONTAINER (debug) Aborting link
'qdlink.YXwnWha98pDiu+N' due to parent connection end
2023-07-21 06:08:49.717456 -0400 CONTAINER (debug) Aborting link
'qdlink.l7GrghPt6FFWly_' due to parent connection end
2023-07-21 06:08:49.717465 -0400 CONTAINER (debug) Aborting link
'qdlink.s6XtscgssYDt5kz' due to parent connection end
2023-07-21 06:08:49.717474 -0400 CONTAINER (debug) Aborting link
'qdlink.9vKbt1iMlCV_PWu' due to parent connection end
2023-07-21 06:08:49.717482 -0400 CONTAINER (debug) Aborting link
'qdlink.Oo0m+dZHLJND_ob' due to parent connection end
2023-07-21 06:08:49.717491 -0400 CONTAINER (debug) Aborting link
'qdlink.zK6UQFdoJrtpZwY' due to parent connection end
2023-07-21 06:08:49.717500 -0400 CONTAINER (debug) Aborting link
'qdlink.sXSSmwI5M4J0_Q2' due to parent connection end
2023-07-21 06:08:49.717509 -0400 CONTAINER (debug) Aborting link
'qdlink.568NGS6FTbIV2+A' due to parent connection end
2023-07-21 06:08:49.717519 -0400 CONTAINER (debug) Aborting link
'qdlink.k3JTGQhDy54V+yN' due to parent connection end
2023-07-21 06:08:49.717528 -0400 CONTAINER (debug) Aborting link
'qdlink.zAIks_C0JWcnD5P' due to parent connection end
2023-07-21 06:08:49.717536 -0400 CONTAINER (debug) Aborting link
'qdlink.bmuoGWU0HrrRcnN' due to parent connection end
2023-07-21 06:08:49.717545 -0400 CONTAINER (debug) Aborting link
'qdlink.yypvX3QD0AXkPya' due to parent connection end
2023-07-21 06:08:49.717553 -0400 CONTAINER (debug) Aborting link
'qdlink.4QkCekKKhlJOPsk' due to parent connection end
2023-07-21 06:08:49.717562 -0400 CONTAINER (debug) Aborting link
'qdlink.QNFFgD2STE_xc77' due to parent connection end
2023-07-21 06:08:49.717571 -0400 CONTAINER (debug) Aborting link
'qdlink.oqTvtBcFpEJ_x7j' due to parent connection end
2023-07-21 06:08:49.717579 -0400 CONTAINER (debug) Aborting link
'qdlink.cPszbgNJE70syUG' due to parent connection end
2023-07-21 06:08:49.717588 -0400 CONTAINER (debug) Aborting link
'qdlink.97d4TtkfxlT2lUk' due to parent connection end
2023-07-21 06:08:49.717616 -0400 CONTAINER (debug) Aborting link
'qdlink.P09pvZXa2_VybKj' due to parent connection end
2023-07-21 06:08:49.717624 -0400 CONTAINER (debug) Aborting link
'qdlink.L+08cuEiuVOrCJI' due to parent connection end
2023-07-21 06:08:49.717632 -0400 CONTAINER (debug) Aborting link
'd2fc6467-2b1f-4b71-ba0b-8aea444d7752' due to parent connection end
2023-07-21 06:08:49.717641 -0400 CONTAINER (debug) Aborting link
'a2867376-a162-46cb-8fad-5f639d1c53a3' due to parent connection end
2023-07-21 06:08:49.717649 -0400 CONTAINER (debug) Aborting link
'd2fc6467-2b1f-4b71-ba0b-8aea444d7752' due to parent connection end
2023-07-21 06:08:49.717662 -0400 CONTAINER (debug) Aborting link
'a2867376-a162-46cb-8fad-5f639d1c53a3' due to parent connection end
2023-07-21 06:08:49.717670 -0400 CONTAINER (debug) Aborting
[jira] [Updated] (DISPATCH-2358) Compilation failure using Proton 0.38.0
[
https://issues.apache.org/jira/browse/DISPATCH-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-2358:
Description:
{{{noformat}}}
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
'qd_message_receive':
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1494:48: error:
'PN_WEAKREF' undeclared (first use in this function)
1494 | pn_record_def(record, PN_DELIVERY_CTX, PN_WEAKREF);
| ^~
{{{noformat}}}
was:
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
'qd_message_receive':
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1494:48: error:
'PN_WEAKREF' undeclared (first use in this function) 1494 |
pn_record_def(record, PN_DELIVERY_CTX, PN_WEAKREF); | ^~
> Compilation failure using Proton 0.38.0
> ---
>
> Key: DISPATCH-2358
> URL: https://issues.apache.org/jira/browse/DISPATCH-2358
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.19.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
>
>
> {{{noformat}}}
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
> 'qd_message_receive':
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1494:48: error:
> 'PN_WEAKREF' undeclared (first use in this function)
> 1494 | pn_record_def(record, PN_DELIVERY_CTX, PN_WEAKREF);
> | ^~
>
> {{{noformat}}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2358) Compilation failure using Proton 0.38.0
Ganesh Murthy created DISPATCH-2358: --- Summary: Compilation failure using Proton 0.38.0 Key: DISPATCH-2358 URL: https://issues.apache.org/jira/browse/DISPATCH-2358 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 1.19.0 Reporter: Ganesh Murthy Assignee: Ganesh Murthy /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function 'qd_message_receive': /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1494:48: error: 'PN_WEAKREF' undeclared (first use in this function) 1494 | pn_record_def(record, PN_DELIVERY_CTX, PN_WEAKREF); | ^~ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2354) Compilation failure on Fedora 38
[
https://issues.apache.org/jira/browse/DISPATCH-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2354.
-
Fix Version/s: 1.20.0
Resolution: Fixed
> Compilation failure on Fedora 38
>
>
> Key: DISPATCH-2354
> URL: https://issues.apache.org/jira/browse/DISPATCH-2354
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.20.0
>
>
> {noformat}
> In file included from
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:27:
> In function 'qd_buffer_list_append_field',
> inlined from 'compose_router_message_annotations' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1821:13,
> inlined from 'qd_message_send' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1905:33:
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/buffer_field_api.h:284:27:
> error: 'in_trace.remaining' may be used uninitialized
> [-Werror=maybe-uninitialized]
> 284 | bfield->remaining -= len;
> | ^~
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
> 'qd_message_send':
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1806:27: note:
> 'in_trace.remaining' was declared here
> 1806 | qd_buffer_field_t in_trace;
> | ^~~~
> In file included from
> /builddir/build/BUILD/qpid-dispatch-1.19.0/include/qpid/dispatch/message.h:22,
> from
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:20:
> In function 'qd_buffer_cursor',
> inlined from 'qd_buffer_list_append_field' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/buffer_field_api.h:280:24,
> inlined from 'compose_router_message_annotations' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1821:13,
> inlined from 'qd_message_send' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1905:33:
> /builddir/build/BUILD/qpid-dispatch-1.19.0/include/qpid/dispatch/buffer.h:83:39:
> error: 'in_trace.buffer' may be used uninitialized
> [-Werror=maybe-uninitialized]
>83 | return ((unsigned char*) [1]) + buf->size;
> |~~~^~~
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
> 'qd_message_send':
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1806:27: note:
> 'in_trace.buffer' was declared here
> 1806 | qd_buffer_field_t in_trace;
> | ^~~~
> In function 'qd_buffer_list_append_field',
> inlined from 'compose_router_message_annotations' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1821:13,
> inlined from 'qd_message_send' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1905:33:
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/buffer_field_api.h:280:57:
> error: 'in_trace.cursor' may be used uninitialized
> [-Werror=maybe-uninitialized]
> 280 | size_t avail = qd_buffer_cursor(bfield->buffer) -
> bfield->cursor;
> |
> ~^~~~
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
> 'qd_message_send':
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1806:27: note:
> 'in_trace.cursor' was declared here
> 1806 | qd_buffer_field_t in_trace;
> | ^~~~
> cc1: all warnings being treated as errors
> make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/build.make:405:
> src/CMakeFiles/qpid-dispatch.dir/message.c.o] Error 1
> make[2]: Leaving directory '/builddir/build/BUILD/qpid-dispatch-1.19.0'
> make[1]: *** [CMakeFiles/Makefile2:1030:
> src/CMakeFiles/qpid-dispatch.dir/all] Error 2
> make[1]: Leaving directory '/builddir/build/BUILD/qpid-dispatch-1.19.0'
> make: *** [Makefile:149: all] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.XW4Weo (%build)
> RPM build warnings:
> RPM build errors:
> line 56: It's not recommended to have unversioned Obsoletes: Obsoletes:
> libqpid-dispatch
> line 57: It's not recommended to have unversioned Obsoletes: Obsoletes:
> libqpid-dispatch-devel
> line 110: It's not recommended to have unversioned Obsoletes: Obsoletes:
> qpid-dispatch-router-docs
> Bad exit status from /var/tmp/rpm-tmp.XW4Weo (%build)
> Child return code was: 1
> EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M
> 59981b45e3a84010bd25b5df4ad8b522 -D
> /var/lib/mock/f39-build-41300068-5058376/root -a -u mockbuild
> --capability=cap_ipc_lock --bind=/tmp/mock-resolv.uytbst9d:/etc/resolv.conf
> --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/loop-control
>
[jira] [Assigned] (DISPATCH-2354) Compilation failure on Fedora 38
[
https://issues.apache.org/jira/browse/DISPATCH-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-2354:
---
Assignee: Ganesh Murthy (was: Ken Giusti)
> Compilation failure on Fedora 38
>
>
> Key: DISPATCH-2354
> URL: https://issues.apache.org/jira/browse/DISPATCH-2354
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
>
> {noformat}
> In file included from
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:27:
> In function 'qd_buffer_list_append_field',
> inlined from 'compose_router_message_annotations' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1821:13,
> inlined from 'qd_message_send' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1905:33:
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/buffer_field_api.h:284:27:
> error: 'in_trace.remaining' may be used uninitialized
> [-Werror=maybe-uninitialized]
> 284 | bfield->remaining -= len;
> | ^~
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
> 'qd_message_send':
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1806:27: note:
> 'in_trace.remaining' was declared here
> 1806 | qd_buffer_field_t in_trace;
> | ^~~~
> In file included from
> /builddir/build/BUILD/qpid-dispatch-1.19.0/include/qpid/dispatch/message.h:22,
> from
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:20:
> In function 'qd_buffer_cursor',
> inlined from 'qd_buffer_list_append_field' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/buffer_field_api.h:280:24,
> inlined from 'compose_router_message_annotations' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1821:13,
> inlined from 'qd_message_send' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1905:33:
> /builddir/build/BUILD/qpid-dispatch-1.19.0/include/qpid/dispatch/buffer.h:83:39:
> error: 'in_trace.buffer' may be used uninitialized
> [-Werror=maybe-uninitialized]
>83 | return ((unsigned char*) [1]) + buf->size;
> |~~~^~~
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
> 'qd_message_send':
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1806:27: note:
> 'in_trace.buffer' was declared here
> 1806 | qd_buffer_field_t in_trace;
> | ^~~~
> In function 'qd_buffer_list_append_field',
> inlined from 'compose_router_message_annotations' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1821:13,
> inlined from 'qd_message_send' at
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1905:33:
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/buffer_field_api.h:280:57:
> error: 'in_trace.cursor' may be used uninitialized
> [-Werror=maybe-uninitialized]
> 280 | size_t avail = qd_buffer_cursor(bfield->buffer) -
> bfield->cursor;
> |
> ~^~~~
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
> 'qd_message_send':
> /builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1806:27: note:
> 'in_trace.cursor' was declared here
> 1806 | qd_buffer_field_t in_trace;
> | ^~~~
> cc1: all warnings being treated as errors
> make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/build.make:405:
> src/CMakeFiles/qpid-dispatch.dir/message.c.o] Error 1
> make[2]: Leaving directory '/builddir/build/BUILD/qpid-dispatch-1.19.0'
> make[1]: *** [CMakeFiles/Makefile2:1030:
> src/CMakeFiles/qpid-dispatch.dir/all] Error 2
> make[1]: Leaving directory '/builddir/build/BUILD/qpid-dispatch-1.19.0'
> make: *** [Makefile:149: all] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.XW4Weo (%build)
> RPM build warnings:
> RPM build errors:
> line 56: It's not recommended to have unversioned Obsoletes: Obsoletes:
> libqpid-dispatch
> line 57: It's not recommended to have unversioned Obsoletes: Obsoletes:
> libqpid-dispatch-devel
> line 110: It's not recommended to have unversioned Obsoletes: Obsoletes:
> qpid-dispatch-router-docs
> Bad exit status from /var/tmp/rpm-tmp.XW4Weo (%build)
> Child return code was: 1
> EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M
> 59981b45e3a84010bd25b5df4ad8b522 -D
> /var/lib/mock/f39-build-41300068-5058376/root -a -u mockbuild
> --capability=cap_ipc_lock --bind=/tmp/mock-resolv.uytbst9d:/etc/resolv.conf
> --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/loop-control
> --bind=/dev/loop0 --bind=/dev/loop1
[jira] [Created] (DISPATCH-2354) Compilation failure on Fedora 38
Ganesh Murthy created DISPATCH-2354:
---
Summary: Compilation failure on Fedora 38
Key: DISPATCH-2354
URL: https://issues.apache.org/jira/browse/DISPATCH-2354
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Reporter: Ganesh Murthy
{noformat}
In file included from
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:27:
In function 'qd_buffer_list_append_field',
inlined from 'compose_router_message_annotations' at
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1821:13,
inlined from 'qd_message_send' at
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1905:33:
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/buffer_field_api.h:284:27:
error: 'in_trace.remaining' may be used uninitialized
[-Werror=maybe-uninitialized]
284 | bfield->remaining -= len;
| ^~
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
'qd_message_send':
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1806:27: note:
'in_trace.remaining' was declared here
1806 | qd_buffer_field_t in_trace;
| ^~~~
In file included from
/builddir/build/BUILD/qpid-dispatch-1.19.0/include/qpid/dispatch/message.h:22,
from
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:20:
In function 'qd_buffer_cursor',
inlined from 'qd_buffer_list_append_field' at
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/buffer_field_api.h:280:24,
inlined from 'compose_router_message_annotations' at
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1821:13,
inlined from 'qd_message_send' at
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1905:33:
/builddir/build/BUILD/qpid-dispatch-1.19.0/include/qpid/dispatch/buffer.h:83:39:
error: 'in_trace.buffer' may be used uninitialized
[-Werror=maybe-uninitialized]
83 | return ((unsigned char*) [1]) + buf->size;
|~~~^~~
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
'qd_message_send':
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1806:27: note:
'in_trace.buffer' was declared here
1806 | qd_buffer_field_t in_trace;
| ^~~~
In function 'qd_buffer_list_append_field',
inlined from 'compose_router_message_annotations' at
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1821:13,
inlined from 'qd_message_send' at
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1905:33:
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/buffer_field_api.h:280:57:
error: 'in_trace.cursor' may be used uninitialized [-Werror=maybe-uninitialized]
280 | size_t avail = qd_buffer_cursor(bfield->buffer) -
bfield->cursor;
|~^~~~
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c: In function
'qd_message_send':
/builddir/build/BUILD/qpid-dispatch-1.19.0/src/message.c:1806:27: note:
'in_trace.cursor' was declared here
1806 | qd_buffer_field_t in_trace;
| ^~~~
cc1: all warnings being treated as errors
make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/build.make:405:
src/CMakeFiles/qpid-dispatch.dir/message.c.o] Error 1
make[2]: Leaving directory '/builddir/build/BUILD/qpid-dispatch-1.19.0'
make[1]: *** [CMakeFiles/Makefile2:1030: src/CMakeFiles/qpid-dispatch.dir/all]
Error 2
make[1]: Leaving directory '/builddir/build/BUILD/qpid-dispatch-1.19.0'
make: *** [Makefile:149: all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.XW4Weo (%build)
RPM build warnings:
RPM build errors:
line 56: It's not recommended to have unversioned Obsoletes: Obsoletes:
libqpid-dispatch
line 57: It's not recommended to have unversioned Obsoletes: Obsoletes:
libqpid-dispatch-devel
line 110: It's not recommended to have unversioned Obsoletes: Obsoletes:
qpid-dispatch-router-docs
Bad exit status from /var/tmp/rpm-tmp.XW4Weo (%build)
Child return code was: 1
EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M
59981b45e3a84010bd25b5df4ad8b522 -D
/var/lib/mock/f39-build-41300068-5058376/root -a -u mockbuild
--capability=cap_ipc_lock --bind=/tmp/mock-resolv.uytbst9d:/etc/resolv.conf
--bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/loop-control
--bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3
--bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7
--bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11
--console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash
--setenv=HOME=/builddir --setenv=HOSTNAME=mock
--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin --setenv=PROMPT_COMMAND=printf
"\\033]0;\\007" --setenv=PS1= \\s-\\v\\$
--setenv=LANG=C.UTF-8
[jira] [Commented] (PROTON-2680) [proton-c] PN_RAW_CONNECTION_DISCONNECTED event does not show up when client is disconnected
[
https://issues.apache.org/jira/browse/PROTON-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683468#comment-17683468
]
Ganesh Murthy commented on PROTON-2680:
---
Comment Clifford Jansen -
This looks to me like 2 bugs. The first might be cascading to the one you are
asking about.
The "other" bug is a PN_RAW_CONNECTION_READ with 0 bytes, which appears to
contradict the docs. It looks like this might result in the raw connection
being in some state that prevents the detected PN_RAW_CONNECTION_CLOSED_READ to
progress towards a disconnect.
It should suffice to raise a single Jira.
> [proton-c] PN_RAW_CONNECTION_DISCONNECTED event does not show up when client
> is disconnected
> -
>
> Key: PROTON-2680
> URL: https://issues.apache.org/jira/browse/PROTON-2680
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Reporter: Ganesh Murthy
>Priority: Major
>
> Steps to reproduce
> Start the skupper-router with the following config -
> {noformat}
> router {
> mode: standalone
> }
> listener {
> host: 0.0.0.0
> port: amqp
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> }
> tcpConnector {
> name: echo-1
> host: 10.108.50.177
> port: 9090
> address: echo
> }
> tcpConnector {
> name: echo-2
> host: 10.108.50.177
> port: 9090
> address: echo
> }
> tcpListener {
> host: 0.0.0.0
> port: 9000
> address: echo
> }
> log {
> module: DEFAULT
> enable: trace+
> outputFile: tcp.log
> } {noformat}
>
> Note that the ip address in the host field of the tcpConnector is bogus.
> Now connect a curl client to the tcpListener port -
> {noformat}
> curl http://localhost:9000/api {noformat}
>
> The curl client will hang. Terminate the curl client and look in the tcp.log
> for logged proton events - the PN_RAW_CONNECTION_DISCONNECTED event will be
> missing on connection C2
> Here is the full log of the relevant client connection
>
> {noformat}
> 2023-02-01 16:51:57.069705 -0500 ROUTER_CORE (info) [C2] Connection Opened:
> dir=in host=127.0.0.1:35348 encrypted=no auth=no user=
> container_id=TcpAdaptor props={:"qd.adaptor"="tcp"}
> 2023-02-01 16:51:57.069793 -0500 ROUTER_CORE (trace) Core action
> 'connection_opened'
> 2023-02-01 16:51:57.069986 -0500 TCP_ADAPTOR (info) [C2]
> PN_RAW_CONNECTION_CONNECTED Listener ingress accepted to 0.0.0.0:9000 from
> 127.0.0.1:35348 (global_id=127.0.0.1:35348)
> 2023-02-01 16:51:57.070015 -0500 ROUTER_CORE (trace) Core action
> 'link_first_attach'
> 2023-02-01 16:51:57.070098 -0500 TCP_ADAPTOR (debug) [C2]
> PN_RAW_CONNECTION_NEED_WRITE_BUFFERS listener
> 2023-02-01 16:51:57.070148 -0500 TCP_ADAPTOR (debug) [C2]
> PN_RAW_CONNECTION_NEED_READ_BUFFERS listener
> 2023-02-01 16:51:57.070171 -0500 ROUTER_CORE (info) [C2][L4] Link attached:
> dir=out source={(dyn) expire:link} target={ expire:link}
> 2023-02-01 16:51:57.070222 -0500 TCP_ADAPTOR (debug) [C2]
> qdr_tcp_activate_CT: call pn_raw_connection_wake()
> 2023-02-01 16:51:57.070246 -0500 ROUTER_CORE (trace) Core action
> 'link_first_attach'
> 2023-02-01 16:51:57.070273 -0500 TCP_ADAPTOR (debug) [C2][L4] (listener
> outgoing) qdr_tcp_second_attach
> 2023-02-01 16:51:57.070347 -0500 DEFAULT (trace) Parse tree search for 'echo'
> 2023-02-01 16:51:57.070376 -0500 TCP_ADAPTOR (trace) [C2][L5] handle_incoming
> qdr_tcp_second_attach for listener connection. read_closed:F, flow_enabled:F
> 2023-02-01 16:51:57.070404 -0500 DEFAULT (trace) Parse tree match not found
> 2023-02-01 16:51:57.070425 -0500 TCP_ADAPTOR (debug) [C2][L5] Waiting for
> credit before initiating listener ingress stream message, returning
> 2023-02-01 16:51:57.070456 -0500 TCP_ADAPTOR (debug) [C2][L4]
> qdr_tcp_get_credit: NOOP
> 2023-02-01 16:51:57.070517 -0500 TCP_ADAPTOR (trace) Listener
> tcpListener/0.0.0.0:9000 (0.0.0.0:9000) service address echo consumer count
> updates: local=1 in-process=0 remote=0
> 2023-02-01 16:51:57.070553 -0500 ROUTER_CORE (info) [C2][L5] Link attached:
> dir=in source={ expire:link} target={echo expire:link}
> 2023-02-01 16:51:57.070583 -0500 ROUTER_CORE (trace) Core action
> 'add_tcp_connection'
> 2023-02-01 16:51:57.070606 -0500 TCP_ADAPTOR (debug) [C2]
> PN_RAW_CONNECTION_WAKE listener
> 2023-02-01 16:51:57.070646 -0500 TCP_ADAPTOR (debug) [C2]
> qdr_add_tcp_connection_CT 0.0.0.0:9000 (1)
> 2023-02-01 16:51:57.070673 -0500 TCP_ADAPTOR (debug) [C2][L4] qdr_tcp_flow:
> Flow enabled, credit=250
> 2023-02-01 16:51:57.070722 -0500 TCP_ADAPTOR (debug) [C2]
> qdr_tcp_activate_CT: call pn_raw_connection_wake()
> 2023-02-01 16:51:57.070774 -0500 ROUTER_CORE (trace) Core action 'link_flow'
> 2023-02-01 16:51:57.070800 -0500 TCP_ADAPTOR (trace) [C2][L5] handle_incoming
> qdr_tcp_flow
[jira] [Created] (PROTON-2680) [proton-c] PN_RAW_CONNECTION_DISCONNECTED event does not show up when client is disconnected
Ganesh Murthy created PROTON-2680:
-
Summary: [proton-c] PN_RAW_CONNECTION_DISCONNECTED event does not
show up when client is disconnected
Key: PROTON-2680
URL: https://issues.apache.org/jira/browse/PROTON-2680
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Reporter: Ganesh Murthy
Steps to reproduce
Start the skupper-router with the following config -
{noformat}
router {
mode: standalone
}
listener {
host: 0.0.0.0
port: amqp
authenticatePeer: no
saslMechanisms: ANONYMOUS
}
tcpConnector {
name: echo-1
host: 10.108.50.177
port: 9090
address: echo
}
tcpConnector {
name: echo-2
host: 10.108.50.177
port: 9090
address: echo
}
tcpListener {
host: 0.0.0.0
port: 9000
address: echo
}
log {
module: DEFAULT
enable: trace+
outputFile: tcp.log
} {noformat}
Note that the ip address in the host field of the tcpConnector is bogus.
Now connect a curl client to the tcpListener port -
{noformat}
curl http://localhost:9000/api {noformat}
The curl client will hang. Terminate the curl client and look in the tcp.log
for logged proton events - the PN_RAW_CONNECTION_DISCONNECTED event will be
missing on connection C2
Here is the full log of the relevant client connection
{noformat}
2023-02-01 16:51:57.069705 -0500 ROUTER_CORE (info) [C2] Connection Opened:
dir=in host=127.0.0.1:35348 encrypted=no auth=no user= container_id=TcpAdaptor
props={:"qd.adaptor"="tcp"}
2023-02-01 16:51:57.069793 -0500 ROUTER_CORE (trace) Core action
'connection_opened'
2023-02-01 16:51:57.069986 -0500 TCP_ADAPTOR (info) [C2]
PN_RAW_CONNECTION_CONNECTED Listener ingress accepted to 0.0.0.0:9000 from
127.0.0.1:35348 (global_id=127.0.0.1:35348)
2023-02-01 16:51:57.070015 -0500 ROUTER_CORE (trace) Core action
'link_first_attach'
2023-02-01 16:51:57.070098 -0500 TCP_ADAPTOR (debug) [C2]
PN_RAW_CONNECTION_NEED_WRITE_BUFFERS listener
2023-02-01 16:51:57.070148 -0500 TCP_ADAPTOR (debug) [C2]
PN_RAW_CONNECTION_NEED_READ_BUFFERS listener
2023-02-01 16:51:57.070171 -0500 ROUTER_CORE (info) [C2][L4] Link attached:
dir=out source={(dyn) expire:link} target={ expire:link}
2023-02-01 16:51:57.070222 -0500 TCP_ADAPTOR (debug) [C2] qdr_tcp_activate_CT:
call pn_raw_connection_wake()
2023-02-01 16:51:57.070246 -0500 ROUTER_CORE (trace) Core action
'link_first_attach'
2023-02-01 16:51:57.070273 -0500 TCP_ADAPTOR (debug) [C2][L4] (listener
outgoing) qdr_tcp_second_attach
2023-02-01 16:51:57.070347 -0500 DEFAULT (trace) Parse tree search for 'echo'
2023-02-01 16:51:57.070376 -0500 TCP_ADAPTOR (trace) [C2][L5] handle_incoming
qdr_tcp_second_attach for listener connection. read_closed:F, flow_enabled:F
2023-02-01 16:51:57.070404 -0500 DEFAULT (trace) Parse tree match not found
2023-02-01 16:51:57.070425 -0500 TCP_ADAPTOR (debug) [C2][L5] Waiting for
credit before initiating listener ingress stream message, returning
2023-02-01 16:51:57.070456 -0500 TCP_ADAPTOR (debug) [C2][L4]
qdr_tcp_get_credit: NOOP
2023-02-01 16:51:57.070517 -0500 TCP_ADAPTOR (trace) Listener
tcpListener/0.0.0.0:9000 (0.0.0.0:9000) service address echo consumer count
updates: local=1 in-process=0 remote=0
2023-02-01 16:51:57.070553 -0500 ROUTER_CORE (info) [C2][L5] Link attached:
dir=in source={ expire:link} target={echo expire:link}
2023-02-01 16:51:57.070583 -0500 ROUTER_CORE (trace) Core action
'add_tcp_connection'
2023-02-01 16:51:57.070606 -0500 TCP_ADAPTOR (debug) [C2]
PN_RAW_CONNECTION_WAKE listener
2023-02-01 16:51:57.070646 -0500 TCP_ADAPTOR (debug) [C2]
qdr_add_tcp_connection_CT 0.0.0.0:9000 (1)
2023-02-01 16:51:57.070673 -0500 TCP_ADAPTOR (debug) [C2][L4] qdr_tcp_flow:
Flow enabled, credit=250
2023-02-01 16:51:57.070722 -0500 TCP_ADAPTOR (debug) [C2] qdr_tcp_activate_CT:
call pn_raw_connection_wake()
2023-02-01 16:51:57.070774 -0500 ROUTER_CORE (trace) Core action 'link_flow'
2023-02-01 16:51:57.070800 -0500 TCP_ADAPTOR (trace) [C2][L5] handle_incoming
qdr_tcp_flow for listener connection. read_closed:F, flow_enabled:T
2023-02-01 16:51:57.070831 -0500 TCP_ADAPTOR (debug) [C2]
handle_incoming_raw_read() returning with result=0
2023-02-01 16:51:57.071258 -0500 TCP_ADAPTOR (debug) [C2][L5] Initiating
listener (ingress) stream incoming link for listener connection to: echo reply:
amqp:/_topo/0/QDR.A/temp.rr__pKcuMowq3o4
2023-02-01 16:51:57.071468 -0500 ROUTER_CORE (debug) [C2][L5][D1] Delivery
created qdr_link_deliver
2023-02-01 16:51:57.071513 -0500 ROUTER_CORE (debug) [C2][L5][D1] Delivery
incref: rc:1 qdr_link_deliver - newly created delivery, add to action list
2023-02-01 16:51:57.071535 -0500 ROUTER_CORE (debug) [C2][L5][D1] Delivery
incref: rc:2 qdr_link_deliver - protect returned value
2023-02-01 16:51:57.071559 -0500 TCP_ADAPTOR (debug) [C2][L5][D1] Initiating
listener side empty incoming stream message
2023-02-01
[jira] [Resolved] (DISPATCH-2347) Console tests failing with 'Update your lock file with 'npm install' message
[
https://issues.apache.org/jira/browse/DISPATCH-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2347.
-
Fix Version/s: 1.20.0
Resolution: Fixed
> Console tests failing with 'Update your lock file with 'npm install' message
>
>
> Key: DISPATCH-2347
> URL: https://issues.apache.org/jira/browse/DISPATCH-2347
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Console
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.20.0
>
>
> {noformat}
> npm ERR! code EUSAGE
> npm ERR!
> npm ERR! `npm ci` can only install packages when your package.json and
> package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock
> file with `npm install` before continuing.
> npm ERR!
> npm ERR! Invalid: lock file's type-fest@0.21.3 does not satisfy
> type-fest@0.13.1
> npm ERR! Missing: type-fest@0.21.3 from lock file
> npm ERR!
> npm ERR! Clean install a project
> npm ERR!
> npm ERR! Usage:
> npm ERR! npm ci
> npm ERR!
> npm ERR! Options:
> npm ERR! [--no-audit] [--foreground-scripts] [--ignore-scripts]
> npm ERR! [--script-shell ]
> npm ERR!
> npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
> npm ERR!
> npm ERR! Run "npm help ci" for more info
> npm ERR! A complete log of this run can be found in:
> npm ERR! /home/runner/.npm/_logs/2022-06-09T21_11_13_314Z-debug-0.log
> Error: Process completed with exit code 1. {noformat}
>
> https://github.com/apache/qpid-dispatch/runs/6821003726?check_suite_focus=true#step:3:7
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2347) Console tests failing with 'Update your lock file with 'npm install' message
Ganesh Murthy created DISPATCH-2347:
---
Summary: Console tests failing with 'Update your lock file with
'npm install' message
Key: DISPATCH-2347
URL: https://issues.apache.org/jira/browse/DISPATCH-2347
Project: Qpid Dispatch
Issue Type: Bug
Components: Console
Reporter: Ganesh Murthy
{noformat}
npm ERR! code EUSAGE
npm ERR!
npm ERR! `npm ci` can only install packages when your package.json and
package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock
file with `npm install` before continuing.
npm ERR!
npm ERR! Invalid: lock file's type-fest@0.21.3 does not satisfy type-fest@0.13.1
npm ERR! Missing: type-fest@0.21.3 from lock file
npm ERR!
npm ERR! Clean install a project
npm ERR!
npm ERR! Usage:
npm ERR! npm ci
npm ERR!
npm ERR! Options:
npm ERR! [--no-audit] [--foreground-scripts] [--ignore-scripts]
npm ERR! [--script-shell ]
npm ERR!
npm ERR! aliases: clean-install, ic, install-clean, isntall-clean
npm ERR!
npm ERR! Run "npm help ci" for more info
npm ERR! A complete log of this run can be found in:
npm ERR! /home/runner/.npm/_logs/2022-06-09T21_11_13_314Z-debug-0.log
Error: Process completed with exit code 1. {noformat}
https://github.com/apache/qpid-dispatch/runs/6821003726?check_suite_focus=true#step:3:7
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2345) Compilation failure against main branch of qpid-proton
[
https://issues.apache.org/jira/browse/DISPATCH-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2345.
-
Fix Version/s: 1.20.0
Assignee: Ganesh Murthy
Resolution: Fixed
> Compilation failure against main branch of qpid-proton
> --
>
> Key: DISPATCH-2345
> URL: https://issues.apache.org/jira/browse/DISPATCH-2345
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.20.0
>
>
> {noformat}
> ../src/remote_sasl.c:162:1: error: return type defaults to ‘int’
> [-Wimplicit-int]
> 162 | PN_HANDLE(REMOTE_SASL_CTXT)
> | ^
> ../src/remote_sasl.c: In function ‘PN_HANDLE’:
> ../src/remote_sasl.c:165:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 165 | {
> | ^
> ../src/remote_sasl.c:175:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 175 | {
> | ^
> ../src/remote_sasl.c:189:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 189 | {
> | ^
> ../src/remote_sasl.c:196:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 196 | {
> | ^
> ../src/remote_sasl.c:231:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 231 | {
> | ^
> ../src/remote_sasl.c:247:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 247 | {
> | ^
> ../src/remote_sasl.c:257:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 257 | {
> | ^
> ../src/remote_sasl.c:268:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 268 | {
> | ^
> ../src/remote_sasl.c:279:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 279 | {
> | ^
> ../src/remote_sasl.c:289:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 289 | {
> | ^
> ../src/remote_sasl.c:299:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 299 | {
> | ^
> ../src/remote_sasl.c:308:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 308 | {
> | ^
> ../src/remote_sasl.c:316:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 316 | {
> | ^
> ../src/remote_sasl.c:334:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 334 | {
> | ^
> ../src/remote_sasl.c:375:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 375 | {
> | ^
> ../src/remote_sasl.c:392:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 392 | {
> | ^
> ../src/remote_sasl.c:404:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 404 | {
> | ^
> ../src/remote_sasl.c:423:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 423 | {
> | ^
> ../src/remote_sasl.c:434:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 434 | {
> | ^
> ../src/remote_sasl.c:447:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 447 | {
> | ^
> ../src/remote_sasl.c:458:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 458 | {
> | ^
> ../src/remote_sasl.c:463:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 463 | {
> | ^
> ../src/remote_sasl.c:467:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 467 | {
> | ^
> ../src/remote_sasl.c:471:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 471 | {
> | ^
> ../src/remote_sasl.c:476:38: error: storage class specified for parameter
> ‘remote_sasl_impl’
> 476 | static const pnx_sasl_implementation remote_sasl_impl = {
> | ^~~~
> ../src/remote_sasl.c:476:1: error: parameter ‘remote_sasl_impl’ is initialized
> 476 | static const pnx_sasl_implementation remote_sasl_impl = {
> | ^~
> ../src/remote_sasl.c:477:5: error: ‘remote_sasl_free’ undeclared (first use
> in this function); did you mean ‘remote_sasl_impl’?
> 477 | remote_sasl_free,
> | ^~~~
> | remote_sasl_impl
> ../src/remote_sasl.c:477:5: note: each undeclared identifier is reported only
> once for each function it appears in
> ../src/remote_sasl.c:478:5: error: ‘remote_sasl_list_mechs’ undeclared (first
> use in this function); did you mean ‘remote_sasl_impl’?
> 478 | remote_sasl_list_mechs,
> |
[jira] [Commented] (DISPATCH-2345) Compilation failure against main branch of qpid-proton
[
https://issues.apache.org/jira/browse/DISPATCH-2345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17552414#comment-17552414
]
Ganesh Murthy commented on DISPATCH-2345:
-
https://github.com/apache/qpid-dispatch/runs/6813201782?check_suite_focus=true#step:16:58
> Compilation failure against main branch of qpid-proton
> --
>
> Key: DISPATCH-2345
> URL: https://issues.apache.org/jira/browse/DISPATCH-2345
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ganesh Murthy
>Priority: Major
>
> {noformat}
> ../src/remote_sasl.c:162:1: error: return type defaults to ‘int’
> [-Wimplicit-int]
> 162 | PN_HANDLE(REMOTE_SASL_CTXT)
> | ^
> ../src/remote_sasl.c: In function ‘PN_HANDLE’:
> ../src/remote_sasl.c:165:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 165 | {
> | ^
> ../src/remote_sasl.c:175:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 175 | {
> | ^
> ../src/remote_sasl.c:189:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 189 | {
> | ^
> ../src/remote_sasl.c:196:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 196 | {
> | ^
> ../src/remote_sasl.c:231:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 231 | {
> | ^
> ../src/remote_sasl.c:247:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 247 | {
> | ^
> ../src/remote_sasl.c:257:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 257 | {
> | ^
> ../src/remote_sasl.c:268:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 268 | {
> | ^
> ../src/remote_sasl.c:279:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 279 | {
> | ^
> ../src/remote_sasl.c:289:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 289 | {
> | ^
> ../src/remote_sasl.c:299:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 299 | {
> | ^
> ../src/remote_sasl.c:308:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 308 | {
> | ^
> ../src/remote_sasl.c:316:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 316 | {
> | ^
> ../src/remote_sasl.c:334:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 334 | {
> | ^
> ../src/remote_sasl.c:375:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 375 | {
> | ^
> ../src/remote_sasl.c:392:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 392 | {
> | ^
> ../src/remote_sasl.c:404:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 404 | {
> | ^
> ../src/remote_sasl.c:423:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 423 | {
> | ^
> ../src/remote_sasl.c:434:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 434 | {
> | ^
> ../src/remote_sasl.c:447:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 447 | {
> | ^
> ../src/remote_sasl.c:458:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 458 | {
> | ^
> ../src/remote_sasl.c:463:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 463 | {
> | ^
> ../src/remote_sasl.c:467:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 467 | {
> | ^
> ../src/remote_sasl.c:471:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
> ‘__attribute__’ before ‘{’ token
> 471 | {
> | ^
> ../src/remote_sasl.c:476:38: error: storage class specified for parameter
> ‘remote_sasl_impl’
> 476 | static const pnx_sasl_implementation remote_sasl_impl = {
> | ^~~~
> ../src/remote_sasl.c:476:1: error: parameter ‘remote_sasl_impl’ is initialized
> 476 | static const pnx_sasl_implementation remote_sasl_impl = {
> | ^~
> ../src/remote_sasl.c:477:5: error: ‘remote_sasl_free’ undeclared (first use
> in this function); did you mean ‘remote_sasl_impl’?
> 477 | remote_sasl_free,
> | ^~~~
> | remote_sasl_impl
> ../src/remote_sasl.c:477:5: note: each undeclared identifier is reported only
> once for each function it appears in
> ../src/remote_sasl.c:478:5: error: ‘remote_sasl_list_mechs’ undeclared (first
> use in this function); did you mean ‘remote_sasl_impl’?
> 478 | remote_sasl_list_mechs,
> | ^~
> |
[jira] [Created] (DISPATCH-2345) Compilation failure against main branch of qpid-proton
Ganesh Murthy created DISPATCH-2345:
---
Summary: Compilation failure against main branch of qpid-proton
Key: DISPATCH-2345
URL: https://issues.apache.org/jira/browse/DISPATCH-2345
Project: Qpid Dispatch
Issue Type: Bug
Reporter: Ganesh Murthy
{noformat}
../src/remote_sasl.c:162:1: error: return type defaults to ‘int’
[-Wimplicit-int]
162 | PN_HANDLE(REMOTE_SASL_CTXT)
| ^
../src/remote_sasl.c: In function ‘PN_HANDLE’:
../src/remote_sasl.c:165:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
165 | {
| ^
../src/remote_sasl.c:175:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
175 | {
| ^
../src/remote_sasl.c:189:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
189 | {
| ^
../src/remote_sasl.c:196:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
196 | {
| ^
../src/remote_sasl.c:231:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
231 | {
| ^
../src/remote_sasl.c:247:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
247 | {
| ^
../src/remote_sasl.c:257:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
257 | {
| ^
../src/remote_sasl.c:268:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
268 | {
| ^
../src/remote_sasl.c:279:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
279 | {
| ^
../src/remote_sasl.c:289:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
289 | {
| ^
../src/remote_sasl.c:299:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
299 | {
| ^
../src/remote_sasl.c:308:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
308 | {
| ^
../src/remote_sasl.c:316:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
316 | {
| ^
../src/remote_sasl.c:334:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
334 | {
| ^
../src/remote_sasl.c:375:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
375 | {
| ^
../src/remote_sasl.c:392:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
392 | {
| ^
../src/remote_sasl.c:404:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
404 | {
| ^
../src/remote_sasl.c:423:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
423 | {
| ^
../src/remote_sasl.c:434:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
434 | {
| ^
../src/remote_sasl.c:447:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
447 | {
| ^
../src/remote_sasl.c:458:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
458 | {
| ^
../src/remote_sasl.c:463:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
463 | {
| ^
../src/remote_sasl.c:467:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
467 | {
| ^
../src/remote_sasl.c:471:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘{’ token
471 | {
| ^
../src/remote_sasl.c:476:38: error: storage class specified for parameter
‘remote_sasl_impl’
476 | static const pnx_sasl_implementation remote_sasl_impl = {
| ^~~~
../src/remote_sasl.c:476:1: error: parameter ‘remote_sasl_impl’ is initialized
476 | static const pnx_sasl_implementation remote_sasl_impl = {
| ^~
../src/remote_sasl.c:477:5: error: ‘remote_sasl_free’ undeclared (first use in
this function); did you mean ‘remote_sasl_impl’?
477 | remote_sasl_free,
| ^~~~
| remote_sasl_impl
../src/remote_sasl.c:477:5: note: each undeclared identifier is reported only
once for each function it appears in
../src/remote_sasl.c:478:5: error: ‘remote_sasl_list_mechs’ undeclared (first
use in this function); did you mean ‘remote_sasl_impl’?
478 | remote_sasl_list_mechs,
| ^~
| remote_sasl_impl
../src/remote_sasl.c:479:5: error: ‘remote_sasl_init_server’ undeclared (first
use in this function)
479 | remote_sasl_init_server,
| ^~~
../src/remote_sasl.c:480:5: error: ‘remote_sasl_init_client’ undeclared (first
use in this function)
480 | remote_sasl_init_client,
| ^~~
../src/remote_sasl.c:481:5: error: ‘remote_sasl_prepare’ undeclared (first use
in this function); did you mean ‘remote_sasl_impl’?
481 | remote_sasl_prepare,
| ^~~
|
[jira] [Comment Edited] (DISPATCH-2276) The latest release of proton (pre-0.37.0) breaks scraper
[
https://issues.apache.org/jira/browse/DISPATCH-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17497589#comment-17497589
]
Ganesh Murthy edited comment on DISPATCH-2276 at 2/24/22, 5:36 PM:
---
{noformat}
/test_04_scraper_tool/python3.6-1.cmd
test_04_scraper_tool
(system_tests_topology_disposition.TopologyDispositionTests) ... FAIL
==
FAIL: test_04_scraper_tool
(system_tests_topology_disposition.TopologyDispositionTests)
--
Traceback (most recent call last):
File
"/home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/system_tests_topology_disposition.py",
line 432, in test_04_scraper_tool
self.assertEqual(str(None), error)
AssertionError: 'None' != 'Process 4868 error: exit code 1, expected[1097
chars]'{noformat}
This is happening only on rhel 7
Unfortunately full traceback not available.
was (Author: ganeshmurthy):
{noformat}
/test_04_scraper_tool/python3.6-1.cmd
test_04_scraper_tool
(system_tests_topology_disposition.TopologyDispositionTests) ... FAIL
==
FAIL: test_04_scraper_tool
(system_tests_topology_disposition.TopologyDispositionTests)
--
Traceback (most recent call last):
File
"/home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/system_tests_topology_disposition.py",
line 432, in test_04_scraper_tool
self.assertEqual(str(None), error)
AssertionError: 'None' != 'Process 4868 error: exit code 1, expected[1097
chars]'{noformat}
Unfortunately full traceback not available.
> The latest release of proton (pre-0.37.0) breaks scraper
>
>
> Key: DISPATCH-2276
> URL: https://issues.apache.org/jira/browse/DISPATCH-2276
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ken Giusti
>Assignee: Charles E. Rolke
>Priority: Major
>
> The next version of proton changes the format of the message tracing log
> messages.
> Scraper needs to be updated to work with these new log formats.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2276) The latest release of proton (pre-0.37.0) breaks scraper
[
https://issues.apache.org/jira/browse/DISPATCH-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17497589#comment-17497589
]
Ganesh Murthy commented on DISPATCH-2276:
-
{noformat}
/test_04_scraper_tool/python3.6-1.cmd
test_04_scraper_tool
(system_tests_topology_disposition.TopologyDispositionTests) ... FAIL
==
FAIL: test_04_scraper_tool
(system_tests_topology_disposition.TopologyDispositionTests)
--
Traceback (most recent call last):
File
"/home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/system_tests_topology_disposition.py",
line 432, in test_04_scraper_tool
self.assertEqual(str(None), error)
AssertionError: 'None' != 'Process 4868 error: exit code 1, expected[1097
chars]'{noformat}
Unfortunately full traceback not available.
> The latest release of proton (pre-0.37.0) breaks scraper
>
>
> Key: DISPATCH-2276
> URL: https://issues.apache.org/jira/browse/DISPATCH-2276
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ken Giusti
>Assignee: Charles E. Rolke
>Priority: Major
>
> The next version of proton changes the format of the message tracing log
> messages.
> Scraper needs to be updated to work with these new log formats.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2334) test_01_verify_attach failing in system_tests_one_router.py
[
https://issues.apache.org/jira/browse/DISPATCH-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2334.
-
Fix Version/s: 1.19.0
Resolution: Fixed
This proton commit fixed the issue - 91b480e0639a36fe0a47a638f521f92597de5a8d
> test_01_verify_attach failing in system_tests_one_router.py
> ---
>
> Key: DISPATCH-2334
> URL: https://issues.apache.org/jira/browse/DISPATCH-2334
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.19.0
>
>
> {noformat}
> 21:
> 21: ==
> 21: FAIL: test_01_verify_attach
> (system_tests_one_router.OneRouterTransactionalAttachTest)
> 21: Verify the transaction link attach is correctly forwarded to the broker
> 21: --
> 21: Traceback (most recent call last):
> 21: File
> "/home/jenkins/workspace/dispatch/dispatch-rawhide-main/source/dispatch/tests/system_tests_one_router.py",
> line 3898, in test_01_verify_attach
> 21: self.assertEqual(symbol('amqp:declare:list'),
> 21: ^
> 21: AssertionError: symbol('amqp:declare:list') != ulong(119) {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2334) test_01_verify_attach failing in system_tests_one_router.py
Ganesh Murthy created DISPATCH-2334:
---
Summary: test_01_verify_attach failing in
system_tests_one_router.py
Key: DISPATCH-2334
URL: https://issues.apache.org/jira/browse/DISPATCH-2334
Project: Qpid Dispatch
Issue Type: Test
Components: Tests
Reporter: Ganesh Murthy
{noformat}
21:
21: ==
21: FAIL: test_01_verify_attach
(system_tests_one_router.OneRouterTransactionalAttachTest)
21: Verify the transaction link attach is correctly forwarded to the broker
21: --
21: Traceback (most recent call last):
21: File
"/home/jenkins/workspace/dispatch/dispatch-rawhide-main/source/dispatch/tests/system_tests_one_router.py",
line 3898, in test_01_verify_attach
21: self.assertEqual(symbol('amqp:declare:list'),
21: ^
21: AssertionError: symbol('amqp:declare:list') != ulong(119) {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2276) The latest release of proton (pre-0.37.0) breaks scraper
[ https://issues.apache.org/jira/browse/DISPATCH-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17494163#comment-17494163 ] Ganesh Murthy commented on DISPATCH-2276: - Looks like [~chug] is BCK !! > The latest release of proton (pre-0.37.0) breaks scraper > > > Key: DISPATCH-2276 > URL: https://issues.apache.org/jira/browse/DISPATCH-2276 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Ken Giusti >Assignee: Charles E. Rolke >Priority: Major > > The next version of proton changes the format of the message tracing log > messages. > Scraper needs to be updated to work with these new log formats. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2314) TSAN data race when setting the presettled flag
[
https://issues.apache.org/jira/browse/DISPATCH-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2314.
-
Fix Version/s: 1.19.0
Assignee: Ganesh Murthy
Resolution: Fixed
> TSAN data race when setting the presettled flag
> ---
>
> Key: DISPATCH-2314
> URL: https://issues.apache.org/jira/browse/DISPATCH-2314
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Labels: race-condition, tsan
> Fix For: 1.19.0
>
>
> {noformat}
> 21: E Process 2380 error: exit code 66, expected 0
> 21: E qdrouterd -c test-router.conf -I
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/python
> 21: E
> /__w/qpid-dispatch/qpid-dispatch/qpid-dispatch/build/tests/system_test.dir/system_tests_one_router/OneRouterTest/setUpClass/test-router-9.cmd
> 21: E
> 21: E ==
> 21: E WARNING: ThreadSanitizer: data race (pid=2380)
> 21: E Write of size 1 at 0x7b440003d355 by thread T4:
> 21: E #0 qdr_delivery_set_presettled
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/delivery.c:136
> (qdrouterd+0x49d8c5)
> 21: E #1 AMQP_rx_handler
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_node.c:538
> (qdrouterd+0x4d2ff5)
> 21: E #2 deferred_AMQP_rx_handler
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_node.c:922
> (qdrouterd+0x4d37b2)
> 21: E #3 invoke_deferred_calls
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:801
> (qdrouterd+0x4d584b)
> 21: E #4 invoke_deferred_calls
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:790
> (qdrouterd+0x4d8b16)
> 21: E #5 handle
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1058
> (qdrouterd+0x4d8b16)
> 21: E #6 thread_run
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1133
> (qdrouterd+0x4dae84)
> 21: E #7 _thread_init
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:172
> (qdrouterd+0x48160d)
> 21: E
> 21: E Previous read of size 1 at 0x7b440003d355 by thread T1:
> 21: E #0 qdr_delivery_continue_CT
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/delivery.c:1108
> (qdrouterd+0x49f9e2)
> 21: E #1 router_core_thread
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/router_core_thread.c:236
> (qdrouterd+0x4b572a)
> 21: E #2 _thread_init
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:172
> (qdrouterd+0x48160d)
> 21: E
> 21: E Location is heap block of size 320 at 0x7b440003d2c0
> allocated by thread T3:
> 21: E #0 posix_memalign (libtsan.so.0+0x32a23)
> 21: E #1 qd_alloc
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/alloc_pool.c:391
> (qdrouterd+0x44ad29)
> 21: E #2 new_qdr_delivery_t
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/delivery.c:24
> (qdrouterd+0x49d33c)
> 21: E #3 qdr_link_deliver
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/transfer.c:64
> (qdrouterd+0x4bb125)
> 21: E #4 AMQP_rx_handler
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_node.c:877
> (qdrouterd+0x4d3106)
> 21: E #5 do_receive
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/container.c:219
> (qdrouterd+0x45f234)
> 21: E #6 qd_container_handle_event
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/container.c:734
> (qdrouterd+0x45f234)
> 21: E #7 handle
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1108
> (qdrouterd+0x4d8b41)
> 21: E #8 thread_run
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1133
> (qdrouterd+0x4dae84)
> 21: E #9 _thread_init
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:172
> (qdrouterd+0x48160d)
> 21: E
> 21: E Thread T4 (tid=2385, running) created by main thread at:
> 21: E #0 pthread_create (libtsan.so.0+0x5bef5)
> 21: E #1 sys_thread
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:181
> (qdrouterd+0x481a9c)
> 21: E #2
[jira] [Resolved] (DISPATCH-2326) Remove HTTP1/HTTP2/TCP Adaptors from the source code.
[ https://issues.apache.org/jira/browse/DISPATCH-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-2326. - Fix Version/s: 1.19.0 Resolution: Fixed > Remove HTTP1/HTTP2/TCP Adaptors from the source code. > -- > > Key: DISPATCH-2326 > URL: https://issues.apache.org/jira/browse/DISPATCH-2326 > Project: Qpid Dispatch > Issue Type: Task >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.19.0 > > > Remove all adaptor code and all supporting adaptor tests. Do not remove the > adaptor code API. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2330) system_tests_one_router fails in test_30_presettled_overflow test
[
https://issues.apache.org/jira/browse/DISPATCH-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2330.
-
Fix Version/s: 1.19.0
Resolution: Fixed
> system_tests_one_router fails in test_30_presettled_overflow test
> -
>
> Key: DISPATCH-2330
> URL: https://issues.apache.org/jira/browse/DISPATCH-2330
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.19.0
>
>
> {noformat}
> self = testMethod=test_30_presettled_overflow>
> def test_30_presettled_overflow(self):
> test = PresettledOverflowTest(self.address)
> test.run()
> > self.assertIsNone(test.error)
>AssertionError: 'No deliveries were dropped' is not None {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2330) system_tests_one_router fails in test_30_presettled_overflow test
Ganesh Murthy created DISPATCH-2330:
---
Summary: system_tests_one_router fails in
test_30_presettled_overflow test
Key: DISPATCH-2330
URL: https://issues.apache.org/jira/browse/DISPATCH-2330
Project: Qpid Dispatch
Issue Type: Test
Components: Tests
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
{noformat}
self =
def test_30_presettled_overflow(self):
test = PresettledOverflowTest(self.address)
test.run()
> self.assertIsNone(test.error)
AssertionError: 'No deliveries were dropped' is not None {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2329) system_tests_delivery_count failing on test_06_large_message_released
[
https://issues.apache.org/jira/browse/DISPATCH-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2329.
-
Fix Version/s: 1.19.0
Resolution: Fixed
> system_tests_delivery_count failing on test_06_large_message_released
> -
>
> Key: DISPATCH-2329
> URL: https://issues.apache.org/jira/browse/DISPATCH-2329
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.19.0
>
>
> {noformat}
> 44: === FAILURES
> ===
> 44: __ OneRouterLinkCountersTest.test_06_large_message_released
> ___
> 44: 44: self = testMethod=test_06_large_message_released>
> 44:
> 44: def test_06_large_message_released(self):
> 44: > self.verify_released(True)
> 44: 44:
> /home/runner/work/skupper-router/skupper-router/skupper-router/tests/system_tests_delivery_counts.py:1198:
>
> 44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _ _ _
> 44:
> /home/runner/work/skupper-router/skupper-router/skupper-router/tests/system_tests_delivery_counts.py:1059:
> in verify_released
> 44: self.assertEqual(test.receiver_stats['releasedCount'], self.COUNT)
> 44: E AssertionError: 29 != 40
> 44: - generated xml file:
> /__w/skupper-router/skupper-router/skupper-router/build/tests/junitxmls/system_tests_delivery_counts.xml
> -
> 44: === short test summary info
>
> 44: FAILED ::OneRouterLinkCountersTest::test_06_large_message_released -
> Assertio...
> 44: 1 failed, 26 passed in 59.43s
> =
> 23/33 Test #44: system_tests_delivery_counts ...***Failed
> 59.76 sec
> = test session starts
> == {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2329) system_tests_delivery_count failing on test_06_large_message_released
Ganesh Murthy created DISPATCH-2329:
---
Summary: system_tests_delivery_count failing on
test_06_large_message_released
Key: DISPATCH-2329
URL: https://issues.apache.org/jira/browse/DISPATCH-2329
Project: Qpid Dispatch
Issue Type: Test
Components: Tests
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
{noformat}
44: === FAILURES
===
44: __ OneRouterLinkCountersTest.test_06_large_message_released
___
44: 44: self =
44:
44: def test_06_large_message_released(self):
44: > self.verify_released(True)
44: 44:
/home/runner/work/skupper-router/skupper-router/skupper-router/tests/system_tests_delivery_counts.py:1198:
44: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _
44:
/home/runner/work/skupper-router/skupper-router/skupper-router/tests/system_tests_delivery_counts.py:1059:
in verify_released
44: self.assertEqual(test.receiver_stats['releasedCount'], self.COUNT)
44: E AssertionError: 29 != 40
44: - generated xml file:
/__w/skupper-router/skupper-router/skupper-router/build/tests/junitxmls/system_tests_delivery_counts.xml
-
44: === short test summary info
44: FAILED ::OneRouterLinkCountersTest::test_06_large_message_released -
Assertio...
44: 1 failed, 26 passed in 59.43s
=
23/33 Test #44: system_tests_delivery_counts ...***Failed
59.76 sec
= test session starts
== {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2328) c_unittests failing on RHEL 7
[
https://issues.apache.org/jira/browse/DISPATCH-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490476#comment-17490476
]
Ganesh Murthy commented on DISPATCH-2328:
-
Could be caused because of the command line option
-D_FORTIFY_SOURCE
> c_unittests failing on RHEL 7
> -
>
> Key: DISPATCH-2328
> URL: https://issues.apache.org/jira/browse/DISPATCH-2328
> Project: Qpid Dispatch
> Issue Type: Task
> Components: Tests
>Reporter: Ganesh Murthy
>Assignee: Jiri Daněk
>Priority: Major
>
> {noformat}
> /home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/c_unittests/test_terminus.cpp:42:
> TEST CASE: test_safe_snprintf
> vsnprintf failure (_STUB_)
> /home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/c_unittests/test_terminus.cpp:94:
> ERROR: CHECK( 0 == len ) is NOT correct!
> values: CHECK( 0 == 9 )
> /home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/c_unittests/test_terminus.cpp:95:
> ERROR: CHECK( '\0' == output[0] ) is NOT correct!
> values: CHECK( 0 == 115 ) {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-2328) c_unittests failing on RHEL 7
[
https://issues.apache.org/jira/browse/DISPATCH-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-2328:
---
Assignee: Jiri Daněk
> c_unittests failing on RHEL 7
> -
>
> Key: DISPATCH-2328
> URL: https://issues.apache.org/jira/browse/DISPATCH-2328
> Project: Qpid Dispatch
> Issue Type: Task
> Components: Tests
>Reporter: Ganesh Murthy
>Assignee: Jiri Daněk
>Priority: Major
>
> {noformat}
> /home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/c_unittests/test_terminus.cpp:42:
> TEST CASE: test_safe_snprintf
> vsnprintf failure (_STUB_)
> /home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/c_unittests/test_terminus.cpp:94:
> ERROR: CHECK( 0 == len ) is NOT correct!
> values: CHECK( 0 == 9 )
> /home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/c_unittests/test_terminus.cpp:95:
> ERROR: CHECK( '\0' == output[0] ) is NOT correct!
> values: CHECK( 0 == 115 ) {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2328) c_unittests failing on RHEL 7
Ganesh Murthy created DISPATCH-2328:
---
Summary: c_unittests failing on RHEL 7
Key: DISPATCH-2328
URL: https://issues.apache.org/jira/browse/DISPATCH-2328
Project: Qpid Dispatch
Issue Type: Task
Components: Tests
Reporter: Ganesh Murthy
{noformat}
/home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/c_unittests/test_terminus.cpp:42:
TEST CASE: test_safe_snprintf
vsnprintf failure (_STUB_)
/home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/c_unittests/test_terminus.cpp:94:
ERROR: CHECK( 0 == len ) is NOT correct!
values: CHECK( 0 == 9 )
/home/jenkins/workspace/rh-qpid-dispatch-dist-el7-main/build/BUILD/qpid-dispatch-1.19.0/tests/c_unittests/test_terminus.cpp:95:
ERROR: CHECK( '\0' == output[0] ) is NOT correct!
values: CHECK( 0 == 115 ) {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2326) Remove HTTP1/HTTP2/TCP Adaptors from the source code.
Ganesh Murthy created DISPATCH-2326: --- Summary: Remove HTTP1/HTTP2/TCP Adaptors from the source code. Key: DISPATCH-2326 URL: https://issues.apache.org/jira/browse/DISPATCH-2326 Project: Qpid Dispatch Issue Type: Task Reporter: Ganesh Murthy Remove all adaptor code and all supporting adaptor tests. Do not remove the adaptor code API. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-2326) Remove HTTP1/HTTP2/TCP Adaptors from the source code.
[ https://issues.apache.org/jira/browse/DISPATCH-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-2326: --- Assignee: Ganesh Murthy > Remove HTTP1/HTTP2/TCP Adaptors from the source code. > -- > > Key: DISPATCH-2326 > URL: https://issues.apache.org/jira/browse/DISPATCH-2326 > Project: Qpid Dispatch > Issue Type: Task >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > > Remove all adaptor code and all supporting adaptor tests. Do not remove the > adaptor code API. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2325) system_tests_routing_protocol hangs and times out
Ganesh Murthy created DISPATCH-2325:
---
Summary: system_tests_routing_protocol hangs and times out
Key: DISPATCH-2325
URL: https://issues.apache.org/jira/browse/DISPATCH-2325
Project: Qpid Dispatch
Issue Type: Test
Components: Tests
Reporter: Ganesh Murthy
{noformat}
test 68
Start 68: system_tests_routing_protocol68: Test command: /usr/bin/python3
"/__w/qpid-dispatch/qpid-dispatch/qpid-dispatch/build/tests/run.py" "-m"
"pytest" "-vs" "--junit-prefix=pytest.system_tests_routing_protocol"
"--junit-xml=junitxmls/system_tests_routing_protocol.xml" "--pyargs"
"system_tests_routing_protocol"
37/37 Test #68: system_tests_routing_protocol .***Timeout
1200.04 sec {noformat}
https://github.com/apache/qpid-dispatch/runs/5041374330?check_suite_focus=true
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2319) system_tests_one_router.test_43_dropped_presettled_receiver_stops fails
[
https://issues.apache.org/jira/browse/DISPATCH-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2319.
-
Fix Version/s: 1.19.0
Resolution: Fixed
> system_tests_one_router.test_43_dropped_presettled_receiver_stops fails
> ---
>
> Key: DISPATCH-2319
> URL: https://issues.apache.org/jira/browse/DISPATCH-2319
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.19.0
>
>
> {noformat}
> 21: ___ OneRouterTest.test_43_dropped_presettled_receiver_stops
>
> 21:
> 21: self = testMethod=test_43_dropped_presettled_receiver_stops>
> 21:
> 21: def test_43_dropped_presettled_receiver_stops(self):
> 21: local_node = Node.connect(self.address, timeout=TIMEOUT)
> 21: res = local_node.query('org.apache.qpid.dispatch.router')
> 21: deliveries_ingress =
> res.attribute_names.index('deliveriesIngress')
> 21: presettled_dropped_count =
> res.attribute_names.index('droppedPresettledDeliveries')
> 21: ingress_delivery_count = res.results[0][deliveries_ingress]
> 21: test = DroppedPresettledTest(self.address, 200,
> ingress_delivery_count, presettled_dropped_count)
> 21: test.run()
> 21: > self.assertIsNone(test.error)
> 21: E AssertionError: 'Messages sent to the router is 200, Messages
> processed by the router is 107' is not None
> 21:
> 21:
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/system_tests_one_router.py:666:
> AssertionError
> 21: - generated xml file:
> /__w/qpid-dispatch/qpid-dispatch/qpid-dispatch/build/tests/junitxmls/system_tests_one_router.xml
> -
> 21: === short test summary info
>
> 21: FAILED ::OneRouterTest::test_43_dropped_presettled_receiver_stops -
> Assertion...
> 21: === 1 failed, 55 passed in 77.73s (0:01:17)
>
> 10/38 Test #21: system_tests_one_router .***Failed 78.00
> sec {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2295) system_tests_multicast failure with timeout
[
https://issues.apache.org/jira/browse/DISPATCH-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2295.
-
Fix Version/s: 1.19.0
Resolution: Cannot Reproduce
This has not been seen in a long time. Will reopen if this shows up again.
> system_tests_multicast failure with timeout
> ---
>
> Key: DISPATCH-2295
> URL: https://issues.apache.org/jira/browse/DISPATCH-2295
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Affects Versions: 1.18.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.19.0
>
>
> {noformat}
> 63: ::MulticastLinearTest::test_50_presettled FAILED
> 63: ::MulticastLinearTest::test_51_presettled_mixed_large_msg FAILED
> 38/38 Test #63: system_tests_multicast ..***Timeout 1200.11
> sec {noformat}
>
> https://github.com/apache/qpid-dispatch/runs/4461632262?check_suite_focus=true#step:27:5372
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2316) Py_True/Py_False is not increfed, causing crash in policy tests with libpythond (debug python library)
[
https://issues.apache.org/jira/browse/DISPATCH-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2316.
-
Assignee: Jiri Daněk
Resolution: Fixed
> Py_True/Py_False is not increfed, causing crash in policy tests with
> libpythond (debug python library)
> --
>
> Key: DISPATCH-2316
> URL: https://issues.apache.org/jira/browse/DISPATCH-2316
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Policy Engine
>Affects Versions: 1.18.0
>Reporter: Jiri Daněk
>Assignee: Jiri Daněk
>Priority: Major
> Fix For: 1.19.0
>
>
> {noformat}
> Debug memory block at address p=0x8a6e80: API ''
> 0 bytes originally requested
> The 7 pad bytes at p-7 are not all FORBIDDENBYTE (0xfd):
> at p-7: 0x00 *** OUCH
> at p-6: 0x00 *** OUCH
> at p-5: 0x00 *** OUCH
> at p-4: 0x00 *** OUCH
> at p-3: 0x00 *** OUCH
> at p-2: 0x00 *** OUCH
> at p-1: 0x00 *** OUCH
> Because memory is corrupted at the start, the count of bytes requested
>may be bogus, and checking the trailing pad bytes may segfault.
> The 8 pad bytes at tail=0x8a6e80 are not all FORBIDDENBYTE (0xfd):
> at tail+0: 0x00 *** OUCH
> at tail+1: 0x00 *** OUCH
> at tail+2: 0x00 *** OUCH
> at tail+3: 0x00 *** OUCH
> at tail+4: 0x00 *** OUCH
> at tail+5: 0x00 *** OUCH
> at tail+6: 0x00 *** OUCH
> at tail+7: 0x00 *** OUCH
> Enable tracemalloc to get the memory block allocation traceback
> Fatal Python error: _PyMem_DebugRawFree: bad ID: Allocated using API '',
> verified using API 'o'
> Python runtime state: finalizing (tstate=0x01f43c50)
> Current thread 0x7f3f562fa740 (most recent call first):
> Garbage-collecting
>
> Abandon (core dumped)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2319) system_tests_one_router.test_43_dropped_presettled_receiver_stops fails
Ganesh Murthy created DISPATCH-2319:
---
Summary:
system_tests_one_router.test_43_dropped_presettled_receiver_stops fails
Key: DISPATCH-2319
URL: https://issues.apache.org/jira/browse/DISPATCH-2319
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
{noformat}
21: ___ OneRouterTest.test_43_dropped_presettled_receiver_stops
21:
21: self =
21:
21: def test_43_dropped_presettled_receiver_stops(self):
21: local_node = Node.connect(self.address, timeout=TIMEOUT)
21: res = local_node.query('org.apache.qpid.dispatch.router')
21: deliveries_ingress = res.attribute_names.index('deliveriesIngress')
21: presettled_dropped_count =
res.attribute_names.index('droppedPresettledDeliveries')
21: ingress_delivery_count = res.results[0][deliveries_ingress]
21: test = DroppedPresettledTest(self.address, 200,
ingress_delivery_count, presettled_dropped_count)
21: test.run()
21: > self.assertIsNone(test.error)
21: E AssertionError: 'Messages sent to the router is 200, Messages
processed by the router is 107' is not None
21:
21:
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/system_tests_one_router.py:666:
AssertionError
21: - generated xml file:
/__w/qpid-dispatch/qpid-dispatch/qpid-dispatch/build/tests/junitxmls/system_tests_one_router.xml
-
21: === short test summary info
21: FAILED ::OneRouterTest::test_43_dropped_presettled_receiver_stops -
Assertion...
21: === 1 failed, 55 passed in 77.73s (0:01:17)
10/38 Test #21: system_tests_one_router .***Failed 78.00 sec
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2314) TSAN data race when setting the presettled flag
[
https://issues.apache.org/jira/browse/DISPATCH-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479704#comment-17479704
]
Ganesh Murthy commented on DISPATCH-2314:
-
https://github.com/apache/qpid-dispatch/runs/4842943732?check_suite_focus=true#step:27:1274
> TSAN data race when setting the presettled flag
> ---
>
> Key: DISPATCH-2314
> URL: https://issues.apache.org/jira/browse/DISPATCH-2314
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Priority: Major
>
> {noformat}
> 21: E Process 2380 error: exit code 66, expected 0
> 21: E qdrouterd -c test-router.conf -I
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/python
> 21: E
> /__w/qpid-dispatch/qpid-dispatch/qpid-dispatch/build/tests/system_test.dir/system_tests_one_router/OneRouterTest/setUpClass/test-router-9.cmd
> 21: E
> 21: E ==
> 21: E WARNING: ThreadSanitizer: data race (pid=2380)
> 21: E Write of size 1 at 0x7b440003d355 by thread T4:
> 21: E #0 qdr_delivery_set_presettled
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/delivery.c:136
> (qdrouterd+0x49d8c5)
> 21: E #1 AMQP_rx_handler
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_node.c:538
> (qdrouterd+0x4d2ff5)
> 21: E #2 deferred_AMQP_rx_handler
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_node.c:922
> (qdrouterd+0x4d37b2)
> 21: E #3 invoke_deferred_calls
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:801
> (qdrouterd+0x4d584b)
> 21: E #4 invoke_deferred_calls
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:790
> (qdrouterd+0x4d8b16)
> 21: E #5 handle
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1058
> (qdrouterd+0x4d8b16)
> 21: E #6 thread_run
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1133
> (qdrouterd+0x4dae84)
> 21: E #7 _thread_init
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:172
> (qdrouterd+0x48160d)
> 21: E
> 21: E Previous read of size 1 at 0x7b440003d355 by thread T1:
> 21: E #0 qdr_delivery_continue_CT
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/delivery.c:1108
> (qdrouterd+0x49f9e2)
> 21: E #1 router_core_thread
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/router_core_thread.c:236
> (qdrouterd+0x4b572a)
> 21: E #2 _thread_init
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:172
> (qdrouterd+0x48160d)
> 21: E
> 21: E Location is heap block of size 320 at 0x7b440003d2c0
> allocated by thread T3:
> 21: E #0 posix_memalign (libtsan.so.0+0x32a23)
> 21: E #1 qd_alloc
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/alloc_pool.c:391
> (qdrouterd+0x44ad29)
> 21: E #2 new_qdr_delivery_t
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/delivery.c:24
> (qdrouterd+0x49d33c)
> 21: E #3 qdr_link_deliver
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/transfer.c:64
> (qdrouterd+0x4bb125)
> 21: E #4 AMQP_rx_handler
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_node.c:877
> (qdrouterd+0x4d3106)
> 21: E #5 do_receive
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/container.c:219
> (qdrouterd+0x45f234)
> 21: E #6 qd_container_handle_event
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/container.c:734
> (qdrouterd+0x45f234)
> 21: E #7 handle
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1108
> (qdrouterd+0x4d8b41)
> 21: E #8 thread_run
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1133
> (qdrouterd+0x4dae84)
> 21: E #9 _thread_init
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:172
> (qdrouterd+0x48160d)
> 21: E
> 21: E Thread T4 (tid=2385, running) created by main thread at:
> 21: E #0 pthread_create (libtsan.so.0+0x5bef5)
> 21: E #1 sys_thread
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:181
> (qdrouterd+0x481a9c)
> 21: E #2 qd_server_run
>
[jira] [Commented] (DISPATCH-2315) TSAN data race in qdr_connection_process
[
https://issues.apache.org/jira/browse/DISPATCH-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479703#comment-17479703
]
Ganesh Murthy commented on DISPATCH-2315:
-
https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/555878288#L6850
> TSAN data race in qdr_connection_process
>
>
> Key: DISPATCH-2315
> URL: https://issues.apache.org/jira/browse/DISPATCH-2315
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ganesh Murthy
>Priority: Major
>
> {noformat}
> 62: ERROR
> 62:
> 62: ==
> 62: ERROR: tearDownClass (system_tests_multicast.MulticastLinearTest)
> 62: --
> 62: Traceback (most recent call last):
> 62: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py",
> line 836, in tearDownClass
> 62: cls.tester.teardown()
> 62: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py",
> line 779, in teardown
> 62: raise RuntimeError("Errors during teardown: \n\n%s" %
> "\n\n".join([str(e) for e in errors]))
> 62: RuntimeError: Errors during teardown:
> 62:
> 62: Process 16478 error: exit code 66, expected 0
> 62: qdrouterd -c INT.B.conf -I /home/travis/build/apache/qpid-dispatch/python
> 62:
> /home/travis/build/apache/qpid-dispatch/build/tests/system_test.dir/system_tests_multicast/MulticastLinearTest/setUpClass/INT.B-2.cmd
> 62:
> 62: ==
> 62: WARNING: ThreadSanitizer: data race (pid=16478)
> 62: Read of size 1 at 0x7b44000213d4 by thread T2:
> 62: #0 qdr_connection_process
> /home/travis/build/apache/qpid-dispatch/src/router_core/connections.c:405
> (qdrouterd+0x9d9c6)
> 62: #1 AMQP_writable_conn_handler
> /home/travis/build/apache/qpid-dispatch/src/router_node.c:299
> (qdrouterd+0xdbb81)
> 62: #2 writable_handler
> /home/travis/build/apache/qpid-dispatch/src/container.c:388
> (qdrouterd+0x662eb)
> 62: #3 qd_conn_event_batch_complete
> /home/travis/build/apache/qpid-dispatch/src/container.c:478
> (qdrouterd+0x6769b)
> 62: #4 thread_run
> /home/travis/build/apache/qpid-dispatch/src/server.c:1149 (qdrouterd+0xe733e)
> 62: #5 _thread_init
> /home/travis/build/apache/qpid-dispatch/src/posix/threading.c:172
> (qdrouterd+0x8c441)
> 62:
> 62: Previous write of size 1 at 0x7b44000213d4 by thread T1:
> 62: #0 qdr_delivery_mcast_outbound_settled_CT
> /home/travis/build/apache/qpid-dispatch/src/router_core/delivery.c:889
> (qdrouterd+0xab913)
> 62: #1 qdr_delivery_mcast_outbound_update_CT
> /home/travis/build/apache/qpid-dispatch/src/router_core/delivery.c:1020
> (qdrouterd+0xab913)
> 62: #2 qdr_update_delivery_CT
> /home/travis/build/apache/qpid-dispatch/src/router_core/delivery.c:680
> (qdrouterd+0xac615)
> 62: #3 router_core_thread
> /home/travis/build/apache/qpid-dispatch/src/router_core/router_core_thread.c:236
> (qdrouterd+0xc0fe0)
> 62: #4 _thread_init
> /home/travis/build/apache/qpid-dispatch/src/posix/threading.c:172
> (qdrouterd+0x8c441)
> 62:
> 62: Location is heap block of size 320 at 0x7b4400021340 allocated by main
> thread:
> 62: #0 posix_memalign
> ../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:835
> (libtsan.so.0+0x3046d)
> 62: #1 qd_alloc
> /home/travis/build/apache/qpid-dispatch/src/alloc_pool.c:391
> (qdrouterd+0x54d24)
> 62: #2 new_qdr_delivery_t
> /home/travis/build/apache/qpid-dispatch/src/router_core/delivery.c:24
> (qdrouterd+0xa8442)
> 62: #3 qdr_link_deliver_to
> /home/travis/build/apache/qpid-dispatch/src/router_core/transfer.c:99
> (qdrouterd+0xc6ecd)
> 62: #4 AMQP_rx_handler
> /home/travis/build/apache/qpid-dispatch/src/router_node.c:827
> (qdrouterd+0xdf0cf)
> 62: #5 do_receive
> /home/travis/build/apache/qpid-dispatch/src/container.c:219
> (qdrouterd+0x69b54)
> 62: #6 qd_container_handle_event
> /home/travis/build/apache/qpid-dispatch/src/container.c:734
> (qdrouterd+0x69b54)
> 62: #7 handle /home/travis/build/apache/qpid-dispatch/src/server.c:1108
> (qdrouterd+0xe57a9)
> 62: #8 thread_run
> /home/travis/build/apache/qpid-dispatch/src/server.c:1133 (qdrouterd+0xe726c)
> 62: #9 qd_server_run
> /home/travis/build/apache/qpid-dispatch/src/server.c:1527 (qdrouterd+0xe7e6f)
> 62: #10 main_process
> /home/travis/build/apache/qpid-dispatch/router/src/main.c:115
> (qdrouterd+0x2dda7)
> 62: #11 main
> /home/travis/build/apache/qpid-dispatch/router/src/main.c:369
> (qdrouterd+0x2d092)
> 62:
> 62: Thread T2 (tid=16481, running) created by main thread at:
> 62: #0 pthread_create
> ../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:962
> (libtsan.so.0+0x5ea79)
> 62: #1 sys_thread
>
[jira] [Created] (DISPATCH-2315) TSAN data race in qdr_connection_process
Ganesh Murthy created DISPATCH-2315:
---
Summary: TSAN data race in qdr_connection_process
Key: DISPATCH-2315
URL: https://issues.apache.org/jira/browse/DISPATCH-2315
Project: Qpid Dispatch
Issue Type: Bug
Reporter: Ganesh Murthy
{noformat}
62: ERROR
62:
62: ==
62: ERROR: tearDownClass (system_tests_multicast.MulticastLinearTest)
62: --
62: Traceback (most recent call last):
62: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py", line
836, in tearDownClass
62: cls.tester.teardown()
62: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py", line
779, in teardown
62: raise RuntimeError("Errors during teardown: \n\n%s" %
"\n\n".join([str(e) for e in errors]))
62: RuntimeError: Errors during teardown:
62:
62: Process 16478 error: exit code 66, expected 0
62: qdrouterd -c INT.B.conf -I /home/travis/build/apache/qpid-dispatch/python
62:
/home/travis/build/apache/qpid-dispatch/build/tests/system_test.dir/system_tests_multicast/MulticastLinearTest/setUpClass/INT.B-2.cmd
62:
62: ==
62: WARNING: ThreadSanitizer: data race (pid=16478)
62: Read of size 1 at 0x7b44000213d4 by thread T2:
62: #0 qdr_connection_process
/home/travis/build/apache/qpid-dispatch/src/router_core/connections.c:405
(qdrouterd+0x9d9c6)
62: #1 AMQP_writable_conn_handler
/home/travis/build/apache/qpid-dispatch/src/router_node.c:299
(qdrouterd+0xdbb81)
62: #2 writable_handler
/home/travis/build/apache/qpid-dispatch/src/container.c:388 (qdrouterd+0x662eb)
62: #3 qd_conn_event_batch_complete
/home/travis/build/apache/qpid-dispatch/src/container.c:478 (qdrouterd+0x6769b)
62: #4 thread_run /home/travis/build/apache/qpid-dispatch/src/server.c:1149
(qdrouterd+0xe733e)
62: #5 _thread_init
/home/travis/build/apache/qpid-dispatch/src/posix/threading.c:172
(qdrouterd+0x8c441)
62:
62: Previous write of size 1 at 0x7b44000213d4 by thread T1:
62: #0 qdr_delivery_mcast_outbound_settled_CT
/home/travis/build/apache/qpid-dispatch/src/router_core/delivery.c:889
(qdrouterd+0xab913)
62: #1 qdr_delivery_mcast_outbound_update_CT
/home/travis/build/apache/qpid-dispatch/src/router_core/delivery.c:1020
(qdrouterd+0xab913)
62: #2 qdr_update_delivery_CT
/home/travis/build/apache/qpid-dispatch/src/router_core/delivery.c:680
(qdrouterd+0xac615)
62: #3 router_core_thread
/home/travis/build/apache/qpid-dispatch/src/router_core/router_core_thread.c:236
(qdrouterd+0xc0fe0)
62: #4 _thread_init
/home/travis/build/apache/qpid-dispatch/src/posix/threading.c:172
(qdrouterd+0x8c441)
62:
62: Location is heap block of size 320 at 0x7b4400021340 allocated by main
thread:
62: #0 posix_memalign
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:835
(libtsan.so.0+0x3046d)
62: #1 qd_alloc
/home/travis/build/apache/qpid-dispatch/src/alloc_pool.c:391 (qdrouterd+0x54d24)
62: #2 new_qdr_delivery_t
/home/travis/build/apache/qpid-dispatch/src/router_core/delivery.c:24
(qdrouterd+0xa8442)
62: #3 qdr_link_deliver_to
/home/travis/build/apache/qpid-dispatch/src/router_core/transfer.c:99
(qdrouterd+0xc6ecd)
62: #4 AMQP_rx_handler
/home/travis/build/apache/qpid-dispatch/src/router_node.c:827
(qdrouterd+0xdf0cf)
62: #5 do_receive
/home/travis/build/apache/qpid-dispatch/src/container.c:219 (qdrouterd+0x69b54)
62: #6 qd_container_handle_event
/home/travis/build/apache/qpid-dispatch/src/container.c:734 (qdrouterd+0x69b54)
62: #7 handle /home/travis/build/apache/qpid-dispatch/src/server.c:1108
(qdrouterd+0xe57a9)
62: #8 thread_run /home/travis/build/apache/qpid-dispatch/src/server.c:1133
(qdrouterd+0xe726c)
62: #9 qd_server_run
/home/travis/build/apache/qpid-dispatch/src/server.c:1527 (qdrouterd+0xe7e6f)
62: #10 main_process
/home/travis/build/apache/qpid-dispatch/router/src/main.c:115
(qdrouterd+0x2dda7)
62: #11 main /home/travis/build/apache/qpid-dispatch/router/src/main.c:369
(qdrouterd+0x2d092)
62:
62: Thread T2 (tid=16481, running) created by main thread at:
62: #0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:962
(libtsan.so.0+0x5ea79)
62: #1 sys_thread
/home/travis/build/apache/qpid-dispatch/src/posix/threading.c:181
(qdrouterd+0x8ca02)
62: #2 qd_server_run
/home/travis/build/apache/qpid-dispatch/src/server.c:1525 (qdrouterd+0xe7e4a)
62: #3 main_process
/home/travis/build/apache/qpid-dispatch/router/src/main.c:115
(qdrouterd+0x2dda7)
62: #4 main /home/travis/build/apache/qpid-dispatch/router/src/main.c:369
(qdrouterd+0x2d092)
62:
62: Thread T1 (tid=16480, running) created by main thread at:
62: #0 pthread_create
[jira] [Created] (DISPATCH-2314) TSAN data race when setting the presettled flag
Ganesh Murthy created DISPATCH-2314:
---
Summary: TSAN data race when setting the presettled flag
Key: DISPATCH-2314
URL: https://issues.apache.org/jira/browse/DISPATCH-2314
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Reporter: Ganesh Murthy
{noformat}
21: E Process 2380 error: exit code 66, expected 0
21: E qdrouterd -c test-router.conf -I
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/python
21: E
/__w/qpid-dispatch/qpid-dispatch/qpid-dispatch/build/tests/system_test.dir/system_tests_one_router/OneRouterTest/setUpClass/test-router-9.cmd
21: E
21: E ==
21: E WARNING: ThreadSanitizer: data race (pid=2380)
21: E Write of size 1 at 0x7b440003d355 by thread T4:
21: E #0 qdr_delivery_set_presettled
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/delivery.c:136
(qdrouterd+0x49d8c5)
21: E #1 AMQP_rx_handler
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_node.c:538
(qdrouterd+0x4d2ff5)
21: E #2 deferred_AMQP_rx_handler
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_node.c:922
(qdrouterd+0x4d37b2)
21: E #3 invoke_deferred_calls
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:801
(qdrouterd+0x4d584b)
21: E #4 invoke_deferred_calls
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:790
(qdrouterd+0x4d8b16)
21: E #5 handle
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1058
(qdrouterd+0x4d8b16)
21: E #6 thread_run
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1133
(qdrouterd+0x4dae84)
21: E #7 _thread_init
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:172
(qdrouterd+0x48160d)
21: E
21: E Previous read of size 1 at 0x7b440003d355 by thread T1:
21: E #0 qdr_delivery_continue_CT
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/delivery.c:1108
(qdrouterd+0x49f9e2)
21: E #1 router_core_thread
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/router_core_thread.c:236
(qdrouterd+0x4b572a)
21: E #2 _thread_init
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:172
(qdrouterd+0x48160d)
21: E
21: E Location is heap block of size 320 at 0x7b440003d2c0
allocated by thread T3:
21: E #0 posix_memalign (libtsan.so.0+0x32a23)
21: E #1 qd_alloc
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/alloc_pool.c:391
(qdrouterd+0x44ad29)
21: E #2 new_qdr_delivery_t
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/delivery.c:24
(qdrouterd+0x49d33c)
21: E #3 qdr_link_deliver
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_core/transfer.c:64
(qdrouterd+0x4bb125)
21: E #4 AMQP_rx_handler
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/router_node.c:877
(qdrouterd+0x4d3106)
21: E #5 do_receive
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/container.c:219
(qdrouterd+0x45f234)
21: E #6 qd_container_handle_event
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/container.c:734
(qdrouterd+0x45f234)
21: E #7 handle
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1108
(qdrouterd+0x4d8b41)
21: E #8 thread_run
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1133
(qdrouterd+0x4dae84)
21: E #9 _thread_init
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:172
(qdrouterd+0x48160d)
21: E
21: E Thread T4 (tid=2385, running) created by main thread at:
21: E #0 pthread_create (libtsan.so.0+0x5bef5)
21: E #1 sys_thread
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/posix/threading.c:181
(qdrouterd+0x481a9c)
21: E #2 qd_server_run
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1525
(qdrouterd+0x4dba3c)
21: E #3 main_process
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/router/src/main.c:115
(qdrouterd+0x426e5c)
21: E #4 main
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/router/src/main.c:369
(qdrouterd+0x42626c)
21: E
21: E Thread T1 (tid=2382, running) created by main thread at:
21: E #0 pthread_create (libtsan.so.0+0x5bef5)
21: E
[jira] [Commented] (DISPATCH-2313) TSAN data race in remote_sasl.c
[
https://issues.apache.org/jira/browse/DISPATCH-2313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17479694#comment-17479694
]
Ganesh Murthy commented on DISPATCH-2313:
-
https://github.com/apache/qpid-dispatch/runs/4842943732?check_suite_focus=true#step:27:2938
> TSAN data race in remote_sasl.c
> ---
>
> Key: DISPATCH-2313
> URL: https://issues.apache.org/jira/browse/DISPATCH-2313
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Ganesh Murthy
>Priority: Major
>
> {noformat}
> 43: E SUMMARY: ThreadSanitizer: data race
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/remote_sasl.c:425
> in remote_sasl_list_mechs
> 43: E ==
> 43: E ==
> 43: E WARNING: ThreadSanitizer: data race (pid=3109)
> 43: E Read of size 1 at 0x7b041900 by main thread:
> 43: E #0 strlen (libtsan.so.0+0x5c2eb)
> 43: E #1 pn_strdup
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/util.c:122
> (libqpid-proton-core.so.10+0x3e2c2)
> 43: E #2 pni_post_sasl_frame
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/sasl/sasl.c:495
> (libqpid-proton-core.so.10+0x3e2c2)
> 43: E #3 pn_output_write_sasl
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/sasl/sasl.c:693
> (libqpid-proton-core.so.10+0x3e819)
> 43: E #4 transport_produce
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/transport.c:2820
> (libqpid-proton-core.so.10+0x2f7a4)
> 43: E #5 pn_transport_pending
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/transport.c:3110
> (libqpid-proton-core.so.10+0x2f7a4)
> 43: E #6 pn_connection_driver_write_buffer
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/connection_driver.c:112
> (libqpid-proton-core.so.10+0x24d5d)
> 43: E #7 ensure_wbuf
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:827
> (libqpid-proton-proactor.so.1+0x8ece)
> 43: E #8 write_flush
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:1074
> (libqpid-proton-proactor.so.1+0x8ece)
> 43: E #9 pconnection_process
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:1243
> (libqpid-proton-proactor.so.1+0xaa8c)
> 43: E #10 process
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:2209
> (libqpid-proton-proactor.so.1+0x106a6)
> 43: E #11 next_event_batch
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:2419
> (libqpid-proton-proactor.so.1+0x106a6)
> 43: E #12 pn_proactor_wait
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:2650
> (libqpid-proton-proactor.so.1+0x145b2)
> 43: E #13 thread_run
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1118
> (qdrouterd+0x4dadb9)
> 43: E #14 qd_server_run
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1527
> (qdrouterd+0x4dba5c)
> 43: E #15 main_process
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/router/src/main.c:115
> (qdrouterd+0x426e5c)
> 43: E #16 main
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/router/src/main.c:369
> (qdrouterd+0x42626c)
> 43: E
> 43: E Previous write of size 8 at 0x7b041900 by thread T2:
> 43: E #0 malloc (libtsan.so.0+0x32919)
> 43: E #1 strdup (libc.so.6+0x9ffbe)
> 43: E #2 qd_strdup
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/include/qpid/dispatch/ctools.h:266
> (qdrouterd+0x480647)
> 43: E #3 remote_sasl_process_mechanisms
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/remote_sasl.c:378
> (qdrouterd+0x480647)
> 43: E #4 pni_sasl_impl_process_mechanisms
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/sasl/sasl.c:239
> (libqpid-proton-core.so.10+0x402eb)
> 43: E #5 pn_do_mechanisms
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/sasl/sasl.c:956
> (libqpid-proton-core.so.10+0x402eb)
> 43: E #6 pni_dispatch_action
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/dispatcher.c:75
> (libqpid-proton-core.so.10+0x221f8)
> 43: E #7 pni_dispatch_frame
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/dispatcher.c:116
> (libqpid-proton-core.so.10+0x221f8)
> 43: E #8
[jira] [Created] (DISPATCH-2313) TSAN data race in remote_sasl.c
Ganesh Murthy created DISPATCH-2313:
---
Summary: TSAN data race in remote_sasl.c
Key: DISPATCH-2313
URL: https://issues.apache.org/jira/browse/DISPATCH-2313
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Reporter: Ganesh Murthy
{noformat}
43: E SUMMARY: ThreadSanitizer: data race
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/remote_sasl.c:425
in remote_sasl_list_mechs
43: E ==
43: E ==
43: E WARNING: ThreadSanitizer: data race (pid=3109)
43: E Read of size 1 at 0x7b041900 by main thread:
43: E #0 strlen (libtsan.so.0+0x5c2eb)
43: E #1 pn_strdup
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/util.c:122
(libqpid-proton-core.so.10+0x3e2c2)
43: E #2 pni_post_sasl_frame
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/sasl/sasl.c:495
(libqpid-proton-core.so.10+0x3e2c2)
43: E #3 pn_output_write_sasl
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/sasl/sasl.c:693
(libqpid-proton-core.so.10+0x3e819)
43: E #4 transport_produce
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/transport.c:2820
(libqpid-proton-core.so.10+0x2f7a4)
43: E #5 pn_transport_pending
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/transport.c:3110
(libqpid-proton-core.so.10+0x2f7a4)
43: E #6 pn_connection_driver_write_buffer
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/connection_driver.c:112
(libqpid-proton-core.so.10+0x24d5d)
43: E #7 ensure_wbuf
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:827
(libqpid-proton-proactor.so.1+0x8ece)
43: E #8 write_flush
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:1074
(libqpid-proton-proactor.so.1+0x8ece)
43: E #9 pconnection_process
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:1243
(libqpid-proton-proactor.so.1+0xaa8c)
43: E #10 process
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:2209
(libqpid-proton-proactor.so.1+0x106a6)
43: E #11 next_event_batch
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:2419
(libqpid-proton-proactor.so.1+0x106a6)
43: E #12 pn_proactor_wait
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/proactor/epoll.c:2650
(libqpid-proton-proactor.so.1+0x145b2)
43: E #13 thread_run
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1118
(qdrouterd+0x4dadb9)
43: E #14 qd_server_run
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/server.c:1527
(qdrouterd+0x4dba5c)
43: E #15 main_process
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/router/src/main.c:115
(qdrouterd+0x426e5c)
43: E #16 main
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/router/src/main.c:369
(qdrouterd+0x42626c)
43: E
43: E Previous write of size 8 at 0x7b041900 by thread T2:
43: E #0 malloc (libtsan.so.0+0x32919)
43: E #1 strdup (libc.so.6+0x9ffbe)
43: E #2 qd_strdup
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/include/qpid/dispatch/ctools.h:266
(qdrouterd+0x480647)
43: E #3 remote_sasl_process_mechanisms
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/src/remote_sasl.c:378
(qdrouterd+0x480647)
43: E #4 pni_sasl_impl_process_mechanisms
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/sasl/sasl.c:239
(libqpid-proton-core.so.10+0x402eb)
43: E #5 pn_do_mechanisms
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/sasl/sasl.c:956
(libqpid-proton-core.so.10+0x402eb)
43: E #6 pni_dispatch_action
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/dispatcher.c:75
(libqpid-proton-core.so.10+0x221f8)
43: E #7 pni_dispatch_frame
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/dispatcher.c:116
(libqpid-proton-core.so.10+0x221f8)
43: E #8 pn_dispatcher_input
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/dispatcher.c:135
(libqpid-proton-core.so.10+0x221f8)
43: E #9 pn_input_read_sasl
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/sasl/sasl.c:620
(libqpid-proton-core.so.10+0x3d64f)
43: E #10 transport_consume
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-proton/c/src/core/transport.c:1931
(libqpid-proton-core.so.10+0x2da2d)
[jira] [Updated] (DISPATCH-2311) Investigate python library leak reported by ASAN
[ https://issues.apache.org/jira/browse/DISPATCH-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2311: Fix Version/s: Backlog (was: 1.19.0) > Investigate python library leak reported by ASAN > > > Key: DISPATCH-2311 > URL: https://issues.apache.org/jira/browse/DISPATCH-2311 > Project: Qpid Dispatch > Issue Type: Task > Components: Router Node >Reporter: Ken Giusti >Priority: Major > Fix For: Backlog > > > CI tests build with ASAN are consistently reporting that the internal python > code has over 1/2 MB of leaked memory. > Before releasing 1.19.0 we need to rule out the possibility that these leaks > are caused by a leak in the router's python codebase. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2000) Consider increasing default internal buffer size
[ https://issues.apache.org/jira/browse/DISPATCH-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2000: Fix Version/s: Backlog (was: 1.19.0) > Consider increasing default internal buffer size > > > Key: DISPATCH-2000 > URL: https://issues.apache.org/jira/browse/DISPATCH-2000 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Affects Versions: 1.15.0 >Reporter: Charles E. Rolke >Assignee: Ganesh Murthy >Priority: Major > Fix For: Backlog > > > Tests with the TCP adaptor and a 4k-byte buffer size show _significant > throughput increases_ with _otherwise minimal code changes_. For this > discussion, assume that the new buffer size will be 4k bytes. > Note: This discussion nearly parallels the discussion of increasing hard > drive sector size to 4K. See [Transition to Advanced Format 4K Sector Hard > Drives > |[https://www.seagate.com/tech-insights/advanced-format-4k-sector-hard-drives-master-ti/].] > The pros and cons of increasing the size for disk drives and for > qpid-dispatch are pretty much the same. > Dispatch has never had anything but 512-byte internal buffers. This lends a > lot of weight for keeping the current setting. However, from day one the self > tests exercise various buffer sizes from 1-byte to 1-bytes and the tests > have worked fine. This is a positive indication that physically the buffer > functions and buffer management proper would work with any buffer size. > Logically there are some other issues. These must be understood and > considered before moving forward with any change. > * Expect total memory usage to go up due to unused buffer space with small > messages > * Expect total memory usage to go down due to more efficient buffer use with > large messages > * Policy implements Q2 throttling with a buffer count limit. If that limit > is not adjusted then flow control will not take effect until 8x as much AMQP > session data has been buffered. > Adjusting the buffer size from 512 to 4096 must happen either at compile time > or at run time very early, before qd_router_setup_late() is called, when > buffers start being created and buffer size cannot be changed any more. A > pull request is in the works that adds a --4k-buffer switch to the command > line to simplify testing with the larger buffer size. > I expect that going to 4K buffers will have a performance improvement > certainly for the TCP adaptor but also for the other protocol adaptors and > for AMQP as well. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2007) Need better allocation of sessions across inter-router links
[ https://issues.apache.org/jira/browse/DISPATCH-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2007: Fix Version/s: Backlog (was: 1.19.0) > Need better allocation of sessions across inter-router links > > > Key: DISPATCH-2007 > URL: https://issues.apache.org/jira/browse/DISPATCH-2007 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Router Node >Affects Versions: 1.15.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: Backlog > > > Inter-router connections establish several links for passing traffic between > routers. Session allocation across the links is currently: > * one session dedicated to both router control links > * one session for EACH priority link pair (in/out) - 10 sessions total > * one session used by all link route links > * one session used by all streaming link > There is an issue with sharing the session in the case of streaming & link > routes. Due to the way session flow control works all links on the session > share bandwidth. This means one slow link can force flow control on all of > its peer links on the session. > Proton allows for at most 32K sessions per connection. We should make an > attempt to use dedicated sessions for link route and streaming links, sharing > only when the number of link route + streaming links exceeds the proton > limit. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2129) shutdown race accessing core->running flag
[
https://issues.apache.org/jira/browse/DISPATCH-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-2129:
Fix Version/s: Backlog
(was: 1.19.0)
> shutdown race accessing core->running flag
> --
>
> Key: DISPATCH-2129
> URL: https://issues.apache.org/jira/browse/DISPATCH-2129
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 1.16.0
>Reporter: Ken Giusti
>Assignee: Michael Goulish
>Priority: Minor
> Labels: race-condition, tsan
> Fix For: Backlog
>
>
> Low priority, but nice to clean up so we can remove the suppression for
> qdr_core_free.
> The core->running flag is set false by the main thread during shutdown. The
> flag is checked by the core thread as an indication that the core thread
> should exit its main loop.
> A non-racy approach would be to instead have the main thread queue an action
> to the core thread to cause it to exit the main loop (by setting the
> core->running flag to false).
> {noformat}
> 65: WARNING: ThreadSanitizer: data race (pid=613021)
> 65: Write of size 1 at 0x7b6400035220 by main thread:
> 65: #0 qdr_core_free
> /home/kgiusti/work/dispatch/qpid-dispatch/src/router_core/router_core.c:140
> (libqpid-dispatch.so+0xf0484)
> 65: #1 qd_router_free
> /home/kgiusti/work/dispatch/qpid-dispatch/src/router_node.c:2160
> (libqpid-dispatch.so+0x12870e)
> 65: #2 qd_dispatch_free
> /home/kgiusti/work/dispatch/qpid-dispatch/src/dispatch.c:375
> (libqpid-dispatch.so+0x81dfd)
> 65: #3 main_process
> /home/kgiusti/work/dispatch/qpid-dispatch/router/src/main.c:119
> (qdrouterd+0x402750)
> 65: #4 main /home/kgiusti/work/dispatch/qpid-dispatch/router/src/main.c:369
> (qdrouterd+0x403557)
> 65:
> 65: Previous read of size 1 at 0x7b6400035220 by thread T1:
> 65: #0 router_core_thread
> /home/kgiusti/work/dispatch/qpid-dispatch/src/router_core/router_core_thread.c:210
> (libqpid-dispatch.so+0xfb416)
> 65: #1 _thread_init
> /home/kgiusti/work/dispatch/qpid-dispatch/src/posix/threading.c:172
> (libqpid-dispatch.so+0xad37a)
> 65: #2 (libtsan.so.0+0x2d33f)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2133) qd_log_enabled() race
[ https://issues.apache.org/jira/browse/DISPATCH-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2133: Fix Version/s: Backlog (was: 1.19.0) > qd_log_enabled() race > - > > Key: DISPATCH-2133 > URL: https://issues.apache.org/jira/browse/DISPATCH-2133 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.16.0 >Reporter: Ken Giusti >Assignee: Michael Goulish >Priority: Minor > Labels: race-condition, tsan > Fix For: Backlog > > > TSAN flags qd_log_enabled() as a race since it reads the source mask without > holding the source lock. > Mostly harmless - adding synchronizing overhead not likely worth it. > Masking qd_log_enabled() for now. > > 20: WARNING: ThreadSanitizer: data race (pid=637946) > 20: Write of size 4 at 0x7b1c0018 by main thread (mutexes: write M13, > write M11): > 20: #0 qd_log_entity /home/kgiusti/work/dispatch/qpid-dispatch/src/log.c:634 > (libqpid-dispatch.so+0x8dbe0) > 20: #1 ffi_call_unix64 (libffi.so.6+0x6aef) > 20: #2 qdr_forward_on_message > /home/kgiusti/work/dispatch/qpid-dispatch/src/router_core/forwarder.c:336 > (libqpid-dispatch.so+0xe4ff5) > 20: #3 qdr_general_handler > /home/kgiusti/work/dispatch/qpid-dispatch/src/router_core/router_core.c:929 > (libqpid-dispatch.so+0xf83f6) > 20: #4 qd_timer_visit > /home/kgiusti/work/dispatch/qpid-dispatch/src/timer.c:317 > (libqpid-dispatch.so+0x135b52) > 20: #5 handle /home/kgiusti/work/dispatch/qpid-dispatch/src/server.c:1006 > (libqpid-dispatch.so+0x12fc8d) > 20: #6 thread_run /home/kgiusti/work/dispatch/qpid-dispatch/src/server.c:1121 > (libqpid-dispatch.so+0x13063a) > 20: #7 qd_server_run > /home/kgiusti/work/dispatch/qpid-dispatch/src/server.c:1501 > (libqpid-dispatch.so+0x1328de) > 20: #8 main_process > /home/kgiusti/work/dispatch/qpid-dispatch/router/src/main.c:115 > (qdrouterd+0x40271a) > 20: #9 main /home/kgiusti/work/dispatch/qpid-dispatch/router/src/main.c:369 > (qdrouterd+0x403557) > 20: > 20: Previous read of size 4 at 0x7b1c0018 by thread T2: > 20: #0 qd_log_enabled /home/kgiusti/work/dispatch/qpid-dispatch/src/log.c:404 > (libqpid-dispatch.so+0x8cb49) > 20: #1 transport_tracer > /home/kgiusti/work/dispatch/qpid-dispatch/src/server.c:111 > (libqpid-dispatch.so+0x12ac43) > 20: #2 pni_tracer_to_log_sink > /home/kgiusti/work/proton/qpid-proton/c/src/core/transport.c:2874 > (libqpid-proton-core.so.10+0x22185) > 20: #3 _thread_init > /home/kgiusti/work/dispatch/qpid-dispatch/src/posix/threading.c:172 > (libqpid-dispatch.so+0xad37a) > 20: #4 (libtsan.so.0+0x2d33f) -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2294) Enable TCP listeners and connectors to use TLS
[ https://issues.apache.org/jira/browse/DISPATCH-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2294: Fix Version/s: Backlog (was: 1.19.0) > Enable TCP listeners and connectors to use TLS > -- > > Key: DISPATCH-2294 > URL: https://issues.apache.org/jira/browse/DISPATCH-2294 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Protocol Adaptors >Reporter: Ganesh Murthy >Priority: Major > Fix For: Backlog > > > Qpid-Proton is developing a TLS library that works with raw connections. > Enable TCP adaptor's listeners and connectors to be configured with an > SSLProfile which will use proton's new raw connection TLS library to provide > encryption/decryption capabilities. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2302) Segfault in core_client_api.c on shutdown
[ https://issues.apache.org/jira/browse/DISPATCH-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2302: Fix Version/s: Backlog (was: 1.19.0) > Segfault in core_client_api.c on shutdown > - > > Key: DISPATCH-2302 > URL: https://issues.apache.org/jira/browse/DISPATCH-2302 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.18.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: Backlog > > Attachments: NEW_BUG.txt > > > Hard to reproduce - I hit this only due to a buggy patch I was working on but > seems legit: > During shutdown qdr_core_free() cleans up any outstanding endpoint clients. > This results in any outstanding core client RPC calls to be cancelled by > invoking the "free request" logic which invokes the "request done" client > handler with the error parameter set to "link detach". > In the case of the edge router client address lookup module, the error is > ignored and the client assumes the request was successful. At this point it > attempts to process the request which results in a segfault. > We need to audit all the core client "request done" callbacks to make sure > the error flag is being checked and properly handled. > See backtrace in attachment > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2255) Investigate enable_mask for removal of malloc
[ https://issues.apache.org/jira/browse/DISPATCH-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2255: Fix Version/s: Backlog > Investigate enable_mask for removal of malloc > - > > Key: DISPATCH-2255 > URL: https://issues.apache.org/jira/browse/DISPATCH-2255 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: michael goulish >Assignee: michael goulish >Priority: Major > Fix For: Backlog > > > Find out how often enable_mask() is called in log.c > See if it would be practical to remove the malloc() and free() in it. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2256) edge router fallback links and addresses incorrect on interior failover
[ https://issues.apache.org/jira/browse/DISPATCH-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2256: Fix Version/s: Backlog (was: 1.19.0) > edge router fallback links and addresses incorrect on interior failover > --- > > Key: DISPATCH-2256 > URL: https://issues.apache.org/jira/browse/DISPATCH-2256 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.17.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: Backlog > > > Scenario: > Configure an edge router with two separate interior connectors - one for > router A and a standby for router B. > Configure a route-container listener for a broker on the edge router. Assign > two fallback destination autolinks (1 in, 1 out) to the route container for > address "foo". > Start just the edge router: > * no links are active (expected). > * mgmt query for addresses show two "foo" addresses present: > ** MFfoo - the fallback address (no subscribers) > ** M0foo - the primary address (no subscribers) > Now startup the broker and after the connection to the broker: > * On the edge router: > ** links: > *** id 5, out link to broker, owning address MFfoo > *** id 6, in link from broker, owning address M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > Now start router A. Router A has been configured with an edge listener > connection. There is no inter-router connection configured for router B! > Once the connection is established: > * On the edge router: > ** links: > *** the two broker links (see above) > *** id 10, in link from router A, owning address MFfoo > *** id 11, out link to router A for M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > * On Router A: > ** links: > *** id 6, out link to edge, owning address MFfoo > *** id 7, in link from edge, owning address M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > Now start router B, wait for the edge to establish a connection to it. Since > B is a standby interior for the edge there are no 'foo' related links or > addresses on B as expected. Remember router A and B are not directly > connected. > > Fail router A. Wait for the edge to re-establish its proxy links to router > B. The following links/addresses related to foo are now: > * On the edge router: > ** links: > *** the two broker links > *** id 20, in link from router B, owning address MFfoo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > * On Router B: > ** links: > *** id 6, out link to edge, owning address MFfoo > ** addresses: > *** MFfoo - one local subscriber > From the above we can see that after the failover to router B the edge router > does not re-establish an outgoing link (subscription) for M0foo as it did > when connected to router A. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2292) [http2] system_tests_grpc failed with qd_http2_buffer_t leak
[
https://issues.apache.org/jira/browse/DISPATCH-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2292.
-
Fix Version/s: 1.19.0
Resolution: Cannot Reproduce
> [http2] system_tests_grpc failed with qd_http2_buffer_t leak
>
>
> Key: DISPATCH-2292
> URL: https://issues.apache.org/jira/browse/DISPATCH-2292
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.19.0
>Reporter: Jiri Daněk
>Priority: Major
> Fix For: 1.19.0
>
>
> https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/549003884#L10696
> {noformat}
> 70: ERROR: Aborted due to unexpected alloc pool leak of type
> 'qd_http2_buffer_t'
> {noformat}
> {noformat}
> 70: alloc.c: Items of type 'qd_http2_buffer_t' remain allocated at shutdown: 1
> 70: Leak: 2021-11-20 21:14:56.179730 + type: qd_http2_buffer_t address:
> 0x629000163290
> 70: qdrouterd(backtrace+0x5b) [0x47884b]
> 70: qdrouterd(qd_alloc+0x918) [0x572738]
> 70: qdrouterd(qd_http2_buffer+0x24) [0x786874]
> 70: qdrouterd(qd_http2_buffer_list_append+0x81) [0x786a71]
> 70: qdrouterd() [0x7b9b21]
> 70: /lib/x86_64-linux-gnu/libnghttp2.so.14(nghttp2_session_send+0x49)
> [0x7f5f3a894c89]
> 70: qdrouterd() [0x7aa9f0]
> 70: qdrouterd() [0x791536]
> 70: qdrouterd() [0x777830]
> 70: qdrouterd() [0x771dd0]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2293) Review use of qd_parse()
[ https://issues.apache.org/jira/browse/DISPATCH-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2293: Fix Version/s: Backlog (was: 1.19.0) > Review use of qd_parse() > > > Key: DISPATCH-2293 > URL: https://issues.apache.org/jira/browse/DISPATCH-2293 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.18.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: Backlog > > > Review the use of qd_parse() to ensure callers _always_ verify the return > value before using it. > qd_parse() is used to parse amqp messages. Since these messages are coming > from an external entity all callers must check that there were no parse > errors. > > Use qd_parse_ok(return_value) to verify the return value. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2303) system_tests_http1_over_tcp Http1OverTcpEdge2EdgeTest::test_05_large_streaming_msg failure: invalid literal for int() with base 16: b''
[
https://issues.apache.org/jira/browse/DISPATCH-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2303.
-
Fix Version/s: 1.19.0
Resolution: Cannot Reproduce
> system_tests_http1_over_tcp
> Http1OverTcpEdge2EdgeTest::test_05_large_streaming_msg failure: invalid
> literal for int() with base 16: b''
> ---
>
> Key: DISPATCH-2303
> URL: https://issues.apache.org/jira/browse/DISPATCH-2303
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Affects Versions: 1.19.0
>Reporter: Jiri Daněk
>Assignee: Ken Giusti
>Priority: Minor
> Fix For: 1.19.0
>
>
> https://github.com/apache/qpid-dispatch/runs/4703076932?check_suite_focus=true#step:27:5543
> {noformat}
> 71: ::Http1OverTcpEdge2EdgeTest::test_05_large_streaming_msg Exception in
> thread Thread-26 (_run):
> 71: Traceback (most recent call last):
> 71: File "/usr/lib64/python3.10/threading.py", line 1009, in
> _bootstrap_inner
> 71: self.run()
> 71: File "/usr/lib64/python3.10/threading.py", line 946, in run
> 71: self._target(*self._args, **self._kwargs)
> 71: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/http1_tests.py",
> line 184, in _run
> 71: rsp = client.getresponse()
> 71: File "/usr/lib64/python3.10/http/client.py", line 1374, in getresponse
> 71: response.begin()
> 71: File "/usr/lib64/python3.10/http/client.py", line 318, in begin
> 71: version, status, reason = self._read_status()
> 71: File "/usr/lib64/python3.10/http/client.py", line 279, in _read_status
> 71: line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
> 71: File "/usr/lib64/python3.10/socket.py", line 705, in readinto
> 71: return self._sock.recv_into(b)
> 71: TimeoutError: timed out
> 71: FAILED
> 71: Exception occurred during processing of request from ('127.0.0.1', 34566)
> 71: Traceback (most recent call last):
> 71: File "/usr/lib64/python3.10/socketserver.py", line 316, in
> _handle_request_noblock
> 71: self.process_request(request, client_address)
> 71: File "/usr/lib64/python3.10/socketserver.py", line 347, in
> process_request
> 71: self.finish_request(request, client_address)
> 71: File "/usr/lib64/python3.10/socketserver.py", line 360, in
> finish_request
> 71: self.RequestHandlerClass(request, client_address, self)
> 71: File "/usr/lib64/python3.10/socketserver.py", line 747, in __init__
> 71: self.handle()
> 71: File "/usr/lib64/python3.10/http/server.py", line 429, in handle
> 71: self.handle_one_request()
> 71: File "/usr/lib64/python3.10/http/server.py", line 415, in
> handle_one_request
> 71: method()
> 71: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/http1_tests.py",
> line 86, in do_PUT
> 71: self._execute_request(self.server.system_tests["PUT"])
> 71: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/http1_tests.py",
> line 58, in _execute_request
> 71: self._consume_body()
> 71: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/http1_tests.py",
> line 113, in _consume_body
> 71: hlen = int(header, base=16)
> 71: ValueError: invalid literal for int() with base 16: b''
> 71:
> {noformat}
> {noformat}
> 71: === FAILURES
> ===
> 71: Http1OverTcpEdge2EdgeTest.test_05_large_streaming_msg
> _
> 71:
> 71: self = testMethod=test_05_large_streaming_msg>
> 71:
> 71: def test_05_large_streaming_msg(self):
> 71: """
> 71: Verify large streaming message transfer
> 71: """
> 71: TESTS_11 = {
> 71: "PUT": [
> 71: (RequestMsg("PUT", "/PUT/streaming_test_11",
> 71: headers={
> 71: "Transfer-encoding": "chunked",
> 71: "Content-Type": "text/plain;charset=utf-8"
> 71: },
> 71: # 4 chunks each ~= 600K
> 71: body=b'927C1\r\n' + b'0' * 0x927C0 + b'X\r\n'
> 71: + b'927C0\r\n' + b'1' * 0x927C0 + b'\r\n'
> 71: + b'927C1\r\n' + b'2' * 0x927C0 + b'X\r\n'
> 71: + b'927C0\r\n' + b'3' * 0x927C0 + b'\r\n'
> 71: + b'0\r\n\r\n'),
> 71:
> 71: ResponseMsg(201, reason="Created",
> 71: headers={"Response-Header": "data",
> 71:
[jira] [Commented] (DISPATCH-2280) Use setuptools instead of deprecated distutils
[
https://issues.apache.org/jira/browse/DISPATCH-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472182#comment-17472182
]
Ganesh Murthy commented on DISPATCH-2280:
-
https://www.python.org/dev/peps/pep-0632/
> Use setuptools instead of deprecated distutils
> --
>
> Key: DISPATCH-2280
> URL: https://issues.apache.org/jira/browse/DISPATCH-2280
> Project: Qpid Dispatch
> Issue Type: Sub-task
>Affects Versions: 1.17.0
>Reporter: Jiri Daněk
>Priority: Major
>
> {noformat}
> C:\Users\Vitorio\CLionProjects\qpid-dispatch\cmake-build-release-visual-studio-clang\python\setup.py:21:
> DeprecationWarning: The distutils package is deprecated and slated for
> removal in Python 3.12. Use setuptools or check PEP 632 for potential
> alternatives
> from distutils.core import setup
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2266) system_tests_edge_router stalls on Travis CI
[
https://issues.apache.org/jira/browse/DISPATCH-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2266.
-
Fix Version/s: 1.19.0
Resolution: Cannot Reproduce
> system_tests_edge_router stalls on Travis CI
>
>
> Key: DISPATCH-2266
> URL: https://issues.apache.org/jira/browse/DISPATCH-2266
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Affects Versions: 1.17.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.19.0
>
>
> The system_tests_edge_router stalls on Travis CI intermittently
> {noformat}
> 55: test_50_link_topology (system_tests_edge_router.LinkRouteProxyTest) ... ok
> No output has been received in the last 10m0s, this potentially indicates a
> stalled build or something wrong with the build itself.
> Check the details on how to adjust your build configuration on:
> https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
> The build has been terminated
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2266) system_tests_edge_router stalls on Travis CI
[
https://issues.apache.org/jira/browse/DISPATCH-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17472141#comment-17472141
]
Ganesh Murthy commented on DISPATCH-2266:
-
I have not seen this issue show up after we added a bunch of debug statements
to further understand the cause of the test stall. I am going to mark this as
Cannot Reproduce. We will reopen this if necessary.
> system_tests_edge_router stalls on Travis CI
>
>
> Key: DISPATCH-2266
> URL: https://issues.apache.org/jira/browse/DISPATCH-2266
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Affects Versions: 1.17.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
>
> The system_tests_edge_router stalls on Travis CI intermittently
> {noformat}
> 55: test_50_link_topology (system_tests_edge_router.LinkRouteProxyTest) ... ok
> No output has been received in the last 10m0s, this potentially indicates a
> stalled build or something wrong with the build itself.
> Check the details on how to adjust your build configuration on:
> https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
> The build has been terminated
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2094) System tests can freeze, observed especially on AArch64 or s390x
[
https://issues.apache.org/jira/browse/DISPATCH-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2094.
-
Resolution: Cannot Reproduce
> System tests can freeze, observed especially on AArch64 or s390x
>
>
> Key: DISPATCH-2094
> URL: https://issues.apache.org/jira/browse/DISPATCH-2094
> Project: Qpid Dispatch
> Issue Type: Test
>Affects Versions: 1.16.0
>Reporter: Jiri Daněk
>Priority: Minor
> Fix For: 1.19.0
>
>
> Sometimes the system tests freeze. This is especially frequent on AArch64. It
> is possible this is caused by architecture-specific behavior regarding
> threading. AMD64 is strongly memory consistent, while AArch64 is not. Maybe
> some undefined behavior on AArch64 causes the races to be more serious than
> elsewhere.
> https://travis-ci.com/github/apache/qpid-dispatch/jobs/502066462#L9193
> {noformat}
> 64: test_05_no_settlement_same_interior
> (system_tests_stuck_deliveries.RouterTest) ... ok
> {noformat}
> https://travis-ci.com/github/apache/qpid-dispatch/jobs/502066461#L7611
> {noformat}
> 70: test_01_concurrent_requests
> (system_tests_http1_adaptor.Http1AdaptorEdge2EdgeTest)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-2303) system_tests_http1_over_tcp Http1OverTcpEdge2EdgeTest::test_05_large_streaming_msg failure: invalid literal for int() with base 16: b''
[
https://issues.apache.org/jira/browse/DISPATCH-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-2303:
---
Assignee: Ken Giusti
> system_tests_http1_over_tcp
> Http1OverTcpEdge2EdgeTest::test_05_large_streaming_msg failure: invalid
> literal for int() with base 16: b''
> ---
>
> Key: DISPATCH-2303
> URL: https://issues.apache.org/jira/browse/DISPATCH-2303
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Affects Versions: 1.19.0
>Reporter: Jiri Daněk
>Assignee: Ken Giusti
>Priority: Major
>
> https://github.com/apache/qpid-dispatch/runs/4703076932?check_suite_focus=true#step:27:5543
> {noformat}
> 71: ::Http1OverTcpEdge2EdgeTest::test_05_large_streaming_msg Exception in
> thread Thread-26 (_run):
> 71: Traceback (most recent call last):
> 71: File "/usr/lib64/python3.10/threading.py", line 1009, in
> _bootstrap_inner
> 71: self.run()
> 71: File "/usr/lib64/python3.10/threading.py", line 946, in run
> 71: self._target(*self._args, **self._kwargs)
> 71: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/http1_tests.py",
> line 184, in _run
> 71: rsp = client.getresponse()
> 71: File "/usr/lib64/python3.10/http/client.py", line 1374, in getresponse
> 71: response.begin()
> 71: File "/usr/lib64/python3.10/http/client.py", line 318, in begin
> 71: version, status, reason = self._read_status()
> 71: File "/usr/lib64/python3.10/http/client.py", line 279, in _read_status
> 71: line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
> 71: File "/usr/lib64/python3.10/socket.py", line 705, in readinto
> 71: return self._sock.recv_into(b)
> 71: TimeoutError: timed out
> 71: FAILED
> 71: Exception occurred during processing of request from ('127.0.0.1', 34566)
> 71: Traceback (most recent call last):
> 71: File "/usr/lib64/python3.10/socketserver.py", line 316, in
> _handle_request_noblock
> 71: self.process_request(request, client_address)
> 71: File "/usr/lib64/python3.10/socketserver.py", line 347, in
> process_request
> 71: self.finish_request(request, client_address)
> 71: File "/usr/lib64/python3.10/socketserver.py", line 360, in
> finish_request
> 71: self.RequestHandlerClass(request, client_address, self)
> 71: File "/usr/lib64/python3.10/socketserver.py", line 747, in __init__
> 71: self.handle()
> 71: File "/usr/lib64/python3.10/http/server.py", line 429, in handle
> 71: self.handle_one_request()
> 71: File "/usr/lib64/python3.10/http/server.py", line 415, in
> handle_one_request
> 71: method()
> 71: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/http1_tests.py",
> line 86, in do_PUT
> 71: self._execute_request(self.server.system_tests["PUT"])
> 71: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/http1_tests.py",
> line 58, in _execute_request
> 71: self._consume_body()
> 71: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/http1_tests.py",
> line 113, in _consume_body
> 71: hlen = int(header, base=16)
> 71: ValueError: invalid literal for int() with base 16: b''
> 71:
> {noformat}
> {noformat}
> 71: === FAILURES
> ===
> 71: Http1OverTcpEdge2EdgeTest.test_05_large_streaming_msg
> _
> 71:
> 71: self = testMethod=test_05_large_streaming_msg>
> 71:
> 71: def test_05_large_streaming_msg(self):
> 71: """
> 71: Verify large streaming message transfer
> 71: """
> 71: TESTS_11 = {
> 71: "PUT": [
> 71: (RequestMsg("PUT", "/PUT/streaming_test_11",
> 71: headers={
> 71: "Transfer-encoding": "chunked",
> 71: "Content-Type": "text/plain;charset=utf-8"
> 71: },
> 71: # 4 chunks each ~= 600K
> 71: body=b'927C1\r\n' + b'0' * 0x927C0 + b'X\r\n'
> 71: + b'927C0\r\n' + b'1' * 0x927C0 + b'\r\n'
> 71: + b'927C1\r\n' + b'2' * 0x927C0 + b'X\r\n'
> 71: + b'927C0\r\n' + b'3' * 0x927C0 + b'\r\n'
> 71: + b'0\r\n\r\n'),
> 71:
> 71: ResponseMsg(201, reason="Created",
> 71: headers={"Response-Header": "data",
> 71: "Content-Length": "0"}),
> 71:
[jira] [Resolved] (DISPATCH-2300) system_tests_log_level_update failing when run against latest proton master
[
https://issues.apache.org/jira/browse/DISPATCH-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2300.
-
Fix Version/s: 1.19.0
Resolution: Fixed
> system_tests_log_level_update failing when run against latest proton master
> ---
>
> Key: DISPATCH-2300
> URL: https://issues.apache.org/jira/browse/DISPATCH-2300
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.19.0
>
>
> {noformat}
> 67: # Give some time for the MAU to go over the inter-router link
> 67: time.sleep(2)
> 67: logs = qd_manager.get_log()
> 67: mau_found = False
> 67: for log in logs:
> 67: if 'PROTOCOL' in log[0]:
> 67: if "@transfer" in log[2] and TEST_ADDR_1 in log[2] and
> "MAU" in log[2]:
> 67: mau_found = True
> 67: break
> 67:
> 67: > self.assertTrue(mau_found)
> 67: E AssertionError: False is not true
> 67:
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/system_tests_log_level_update.py:288:
> AssertionError
> 67: - generated xml file:
> /__w/qpid-dispatch/qpid-dispatch/qpid-dispatch/build/tests/junitxmls/system_tests_log_level_update.xml
> -
> 67: === short test summary info
>
> 67: FAILED
> ::EnableConnectionLevelInterRouterTraceTest::test_inter_router_protocol_trace
> 67: = 1 failed, 7 passed in 12.90s
> =
> 33/38 Test #67: system_tests_log_level_update ...***Failed 13.18
> sec {noformat}
>
> https://github.com/ganeshmurthy/qpid-dispatch/runs/4526076646?check_suite_focus=true#step:27:4255
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2284) Container run exception: 'NoneType' object has no attribute 'properties'
[
https://issues.apache.org/jira/browse/DISPATCH-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460870#comment-17460870
]
Ganesh Murthy commented on DISPATCH-2284:
-
https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/551423517#L7911
> Container run exception: 'NoneType' object has no attribute 'properties'
>
>
> Key: DISPATCH-2284
> URL: https://issues.apache.org/jira/browse/DISPATCH-2284
> Project: Qpid Dispatch
> Issue Type: Test
>Affects Versions: 1.18.0
>Reporter: Jiri Daněk
>Priority: Major
>
> https://github.com/jiridanek/qpid-dispatch/runs/4140877738?check_suite_focus=true#step:9:336
> {noformat}
> 27: 2021-11-09 13:00:36.803865 Waiting for router network to stabilize
> 27: 2021-11-09 13:00:36.806855 Container run exception: 'NoneType' object has
> no attribute 'properties'
> {noformat}
> {noformat}
> 27: > self.assertTrue(test.error is None)
> 27: E AssertionError: False is not true
> 27:
> 27:
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/system_tests_policy_oversize_compound.py:1041:
> AssertionError
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2300) system_tests_log_level_update failing when run against latest proton master
[
https://issues.apache.org/jira/browse/DISPATCH-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460803#comment-17460803
]
Ganesh Murthy commented on DISPATCH-2300:
-
The test relies on the content of the transfer frames which it should not. The
test needs to be fixed.
> system_tests_log_level_update failing when run against latest proton master
> ---
>
> Key: DISPATCH-2300
> URL: https://issues.apache.org/jira/browse/DISPATCH-2300
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
>
> {noformat}
> 67: # Give some time for the MAU to go over the inter-router link
> 67: time.sleep(2)
> 67: logs = qd_manager.get_log()
> 67: mau_found = False
> 67: for log in logs:
> 67: if 'PROTOCOL' in log[0]:
> 67: if "@transfer" in log[2] and TEST_ADDR_1 in log[2] and
> "MAU" in log[2]:
> 67: mau_found = True
> 67: break
> 67:
> 67: > self.assertTrue(mau_found)
> 67: E AssertionError: False is not true
> 67:
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/system_tests_log_level_update.py:288:
> AssertionError
> 67: - generated xml file:
> /__w/qpid-dispatch/qpid-dispatch/qpid-dispatch/build/tests/junitxmls/system_tests_log_level_update.xml
> -
> 67: === short test summary info
>
> 67: FAILED
> ::EnableConnectionLevelInterRouterTraceTest::test_inter_router_protocol_trace
> 67: = 1 failed, 7 passed in 12.90s
> =
> 33/38 Test #67: system_tests_log_level_update ...***Failed 13.18
> sec {noformat}
>
> https://github.com/ganeshmurthy/qpid-dispatch/runs/4526076646?check_suite_focus=true#step:27:4255
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2300) system_tests_log_level_update failing when run against latest proton master
Ganesh Murthy created DISPATCH-2300:
---
Summary: system_tests_log_level_update failing when run against
latest proton master
Key: DISPATCH-2300
URL: https://issues.apache.org/jira/browse/DISPATCH-2300
Project: Qpid Dispatch
Issue Type: Test
Components: Tests
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
{noformat}
67: # Give some time for the MAU to go over the inter-router link
67: time.sleep(2)
67: logs = qd_manager.get_log()
67: mau_found = False
67: for log in logs:
67: if 'PROTOCOL' in log[0]:
67: if "@transfer" in log[2] and TEST_ADDR_1 in log[2] and
"MAU" in log[2]:
67: mau_found = True
67: break
67:
67: > self.assertTrue(mau_found)
67: E AssertionError: False is not true
67:
/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/system_tests_log_level_update.py:288:
AssertionError
67: - generated xml file:
/__w/qpid-dispatch/qpid-dispatch/qpid-dispatch/build/tests/junitxmls/system_tests_log_level_update.xml
-
67: === short test summary info
67: FAILED
::EnableConnectionLevelInterRouterTraceTest::test_inter_router_protocol_trace
67: = 1 failed, 7 passed in 12.90s
=
33/38 Test #67: system_tests_log_level_update ...***Failed 13.18 sec
{noformat}
https://github.com/ganeshmurthy/qpid-dispatch/runs/4526076646?check_suite_focus=true#step:27:4255
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2477) ASAN use-after-free of proactor pconnection
[
https://issues.apache.org/jira/browse/PROTON-2477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated PROTON-2477:
--
Description:
qpid-dispatch github actions CI has hit this ASAN issue a couple of times since
enabling use of latest proton-c/main in our CI tests (see attached).
Appears to show a pconnection being freed at the end of batch processing, then
accessing that freed pconnection while waiting for the next event.
[https://github.com/apache/qpid-dispatch/runs/4513058827?check_suite_focus=true#step:9:7347]
{noformat}
==4956==ERROR: AddressSanitizer: heap-use-after-free on address 0x616000171412
at pc 0x7f7144626f6d bp 0x7ffe23b9a600 sp 0x7ffe23b9a5f0
63: E READ of size 1 at 0x616000171412 thread T0
63: E #0 0x7f7144626f6c in next_runnable
../c/src/proactor/epoll.c:2403
63: E #1 0x7f7144627e53 in next_event_batch
../c/src/proactor/epoll.c:2456
63: E #2 0x7f714462d11a in pn_proactor_wait
../c/src/proactor/epoll.c:2715
63: E #3 0x556f559f860e in thread_run ../src/server.c:1118
63: E #4 0x556f55a001cf in qd_server_run ../src/server.c:1527
63: E #5 0x556f55a5b7ea in main_process ../router/src/main.c:115
63: E #6 0x556f55a5d7ee in main ../router/src/main.c:369
63: E #7 0x7f714327e0b2 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x270b2)
63: E #8 0x556f5571574d in _start
(/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/build/router/qdrouterd+0x56874d)
63: E
63: E 0x616000171412 is located 146 bytes inside of 576-byte region
[0x616000171380,0x6160001715c0)
63: E freed by thread T0 here:
63: E #0 0x7f71447f07cf in __interceptor_free
(/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)
63: E #1 0x7f714460d565 in pconnection_final_free
../c/src/proactor/epoll.c:832
63: E #2 0x7f714460d8bc in pconnection_cleanup
../c/src/proactor/epoll.c:848
63: E #3 0x7f71446104ab in pconnection_done
../c/src/proactor/epoll.c:1048
63: E #4 0x7f714462d20e in pn_proactor_done
../c/src/proactor/epoll.c:2725
63: E #5 0x556f559f88b5 in thread_run ../src/server.c:1151
63: E #6 0x556f55a001cf in qd_server_run ../src/server.c:1527
63: E #7 0x556f55a5b7ea in main_process ../router/src/main.c:115
63: E #8 0x556f55a5d7ee in main ../router/src/main.c:369
63: E #9 0x7f714327e0b2 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x270b2)
63: E
63: E previously allocated by thread T2 here:
63: E #0 0x7f71447f0bc8 in malloc
(/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)
63: E #1 0x7f714461dbda in pn_listener_accept2
../c/src/proactor/epoll.c:1883
63: E #2 0x7f7144638bd3 in pn_listener_accept
../c/src/proactor/proactor-internal.c:94
63: E #3 0x556f559efbe1 in on_accept ../src/server.c:622
63: E #4 0x556f559f44fc in handle_listener ../src/server.c:865
63: E #5 0x556f559f3d83 in handle_event_with_context
../src/server.c:814
63: E #6 0x556f559f3e0a in do_handle_listener ../src/server.c:825
63: E #7 0x556f559f6a2f in handle ../src/server.c:1024
63: E #8 0x556f559f86b1 in thread_run ../src/server.c:1133
63: E #9 0x556f55871fbb in _thread_init
../src/posix/threading.c:172
63: E #10 0x7f7144183608 in start_thread
(/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
63: E
63: E Thread T2 created by T0 here:
63: E #0 0x7f714471d805 in pthread_create
(/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)
63: E #1 0x556f5587212a in sys_thread ../src/posix/threading.c:181
63: E #2 0x556f55a00137 in qd_server_run ../src/server.c:1525
63: E #3 0x556f55a5b7ea in main_process ../router/src/main.c:115
63: E #4 0x556f55a5d7ee in main ../router/src/main.c:369
63: E #5 0x7f714327e0b2 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x270b2)
63: E
63: E SUMMARY: AddressSanitizer: heap-use-after-free
../c/src/proactor/epoll.c:2403 in next_runnable
63: E Shadow bytes around the buggy address:
63: E 0x0c2c80026230: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
fd
63: E 0x0c2c80026240: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
fd
63: E 0x0c2c80026250: fd fd fd fd fd fd fd fd fa fa fa fa fa fa fa
fa
63: E 0x0c2c80026260: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
fa
63: E 0x0c2c80026270: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
fd
63: E =>0x0c2c80026280: fd fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd
fd
63: E 0x0c2c80026290: fd fd fd fd fd fd fd
[jira] [Created] (PROTON-2476) [proton-c] Trace level logging prints large transfer messages
Ganesh Murthy created PROTON-2476:
-
Summary: [proton-c] Trace level logging prints large transfer
messages
Key: PROTON-2476
URL: https://issues.apache.org/jira/browse/PROTON-2476
Project: Qpid Proton
Issue Type: Test
Components: proton-c
Reporter: Ganesh Murthy
The transfer frames printed by proton trace level logging are very large. This
leads the Dispatch Travis CI to terminate the test run with the following
message
{noformat}
The job exceeded the maximum log length, and has been terminated. {noformat}
[https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/551423517#L7947]
The large transfer frames can be seen here -
[https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/551423517#L7945]
The transfer frames must be truncated.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2297) OneRouter Q2 test failing in system_tests_http2 on rhel 9
Ganesh Murthy created DISPATCH-2297:
---
Summary: OneRouter Q2 test failing in system_tests_http2 on rhel 9
Key: DISPATCH-2297
URL: https://issues.apache.org/jira/browse/DISPATCH-2297
Project: Qpid Dispatch
Issue Type: Test
Components: Tests
Affects Versions: 1.18.0
Reporter: Ganesh Murthy
{noformat}
71: Test command: /usr/bin/python3.9
"/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/build/tests/run.py"
"-m" "unittest" "-v" "system_tests_http2"
71: Test timeout computed to be: 600
71: test_q2_block_unblock (system_tests_http2.Http2Q2OneRouterTest) ... ERROR
71:
71: Router QDR output file:
71:
71:
71:
71:
71: Router QDR command file:
71:
71: qdrouterd -c http2-test-router.conf -I
/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/python
71: pid=7610
71:
71:
71:
71: Router QDR log file tail:
71:
71: 2021-12-08 20:08:23.643322 + ROUTER_CORE (debug) [C3][L2][D1] Delivery
decref_CT: rc:1 qdr_delivery_unlink_peers_CT - unlinked from peer (delivery)
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/delivery.c:640)
71: 2021-12-08 20:08:23.643338 + ROUTER_CORE (debug) [C1][L4][D2] Delivery
decref_CT: rc:2 qdr_delivery_unlink_peers_CT - unlinked from delivery (peer)
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/delivery.c:640)
71: 2021-12-08 20:08:23.643361 + ROUTER_CORE (debug) [C3][L2][D1] Delivery
outcome : is unknown (0x0)
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/delivery.c:392)
71: 2021-12-08 20:08:23.643373 + ROUTER_CORE (debug) [C3][L2][D1] Delivery
decref_CT: rc:0 qdr_link_cleanup_deliveries_CT - remove from unsettled list
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/delivery.c:640)
71: 2021-12-08 20:08:23.643472 + ROUTER_CORE (trace) Core action
'link_detach'
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/router_core_thread.c:235)
71: 2021-12-08 20:08:23.643493 + ROUTER_CORE (trace) Core action
'connection_closed'
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/router_core_thread.c:235)
71: 2021-12-08 20:08:23.643514 + ROUTER_CORE (info) [C3][L2] Link closed
due to connection loss: del=1 presett=0 psdrop=0 acc=0 rej=0 rel=0 mod=0
delay1=0 delay10=1 blocked=no
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/connections.c:1109)
71: 2021-12-08 20:08:23.643546 + ROUTER_CORE (info) [C3][L3] Link closed
due to connection loss: del=0 presett=0 psdrop=0 acc=0 rej=0 rel=0 mod=0
delay1=0 delay10=0 blocked=no
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/connections.c:1109)
71: 2021-12-08 20:08:23.643559 + ROUTER_CORE (info) [C3] Connection Closed
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/connections.c:1604)
71: 2021-12-08 20:08:23.643613 + ROUTER_CORE (trace) Core action
'delete_http2_connection'
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/router_core_thread.c:235)
71: 2021-12-08 20:08:23.643631 + HTTP_ADAPTOR (trace) [C3] Freeing http2
connection in free_qdr_http2_connection
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/adaptors/http2/http2_adaptor.c:459)
71: 2021-12-08 20:08:23.643654 + HTTP_ADAPTOR (trace) [C1] Activation
triggered, calling pn_raw_connection_wake()
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/adaptors/http2/http2_adaptor.c:1704)
71: 2021-12-08 20:08:23.643765 + HTTP_ADAPTOR (trace) [C1]
PN_RAW_CONNECTION_WAKE Wake-up
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/adaptors/http2/http2_adaptor.c:2539)
71: 2021-12-08 20:08:23.643791 + ROUTER_CORE (debug) [C1][L4][D2] Delivery
incref:rc:3 qdr_link_process_deliveries - holding the undelivered delivery
locally
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/router_core/delivery.c:115)
71: 2021-12-08 20:08:23.643825 + HTTP_ADAPTOR (debug) [C1][S1]
qdr_http_deliver - call handle_outgoing_http
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/adaptors/http2/http2_adaptor.c:2076)
71: 2021-12-08 20:08:23.643838 + PROTOCOL (trace) [C1] Starting to
handle_outgoing_http
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/adaptors/http2/http2_adaptor.c:1744)
71: 2021-12-08 20:08:23.643853 + PROTOCOL (trace) [C1][S1] Headers already
submitted, Proceeding with the body
(/home/jenkins/workspace/dispatch/dispatch-rhel9-main/source/dispatch/src/adaptors/http2/http2_adaptor.c:1864)
71: 2021-12-08
[jira] [Updated] (DISPATCH-2296) Some streaming message tests failing on system_tests_edge_router
[
https://issues.apache.org/jira/browse/DISPATCH-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-2296:
Description:
{noformat}
54: === short test summary info
54: FAILED ::StreamingMessageTest::test_11_streaming_closest_parallel -
proton._u...
54: FAILED ::StreamingMessageTest::test_12_streaming_multicast_parallel -
proton
54: FAILED ::StreamingMessageTest::test_13_streaming_balanced_parallel -
Attribut...
54: ERROR ::StreamingMessageTest::test_12_streaming_multicast_parallel -
RuntimeE...
54: ERROR ::StreamingMessageTest::test_13_streaming_balanced_parallel -
RuntimeEr...
54: == 3 failed, 86 passed, 2 errors in 623.32s (0:10:23)
==
36/37 Test #54: system_tests_edge_router ..***Failed
623.61 sec
{noformat}
[https://github.com/apache/qpid-dispatch/runs/4461632417?check_suite_focus=true#step:27:2894]
[https://github.com/apache/qpid-dispatch/runs/4461657326?check_suite_focus=true#step:9:4289]
[https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/551423517#L7834]
was:
{noformat}
54: === short test summary info
54: FAILED ::StreamingMessageTest::test_11_streaming_closest_parallel -
proton._u...
54: FAILED ::StreamingMessageTest::test_12_streaming_multicast_parallel -
proton
54: FAILED ::StreamingMessageTest::test_13_streaming_balanced_parallel -
Attribut...
54: ERROR ::StreamingMessageTest::test_12_streaming_multicast_parallel -
RuntimeE...
54: ERROR ::StreamingMessageTest::test_13_streaming_balanced_parallel -
RuntimeEr...
54: == 3 failed, 86 passed, 2 errors in 623.32s (0:10:23)
==
36/37 Test #54: system_tests_edge_router ..***Failed
623.61 sec
{noformat}
[https://github.com/apache/qpid-dispatch/runs/4461632417?check_suite_focus=true#step:27:2894]
[https://github.com/apache/qpid-dispatch/runs/4461657326?check_suite_focus=true#step:9:4289]
> Some streaming message tests failing on system_tests_edge_router
>
>
> Key: DISPATCH-2296
> URL: https://issues.apache.org/jira/browse/DISPATCH-2296
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Reporter: Ganesh Murthy
>Priority: Major
>
> {noformat}
> 54: === short test summary info
>
> 54: FAILED ::StreamingMessageTest::test_11_streaming_closest_parallel -
> proton._u...
> 54: FAILED ::StreamingMessageTest::test_12_streaming_multicast_parallel -
> proton
> 54: FAILED ::StreamingMessageTest::test_13_streaming_balanced_parallel -
> Attribut...
> 54: ERROR ::StreamingMessageTest::test_12_streaming_multicast_parallel -
> RuntimeE...
> 54: ERROR ::StreamingMessageTest::test_13_streaming_balanced_parallel -
> RuntimeEr...
> 54: == 3 failed, 86 passed, 2 errors in 623.32s (0:10:23)
> ==
> 36/37 Test #54: system_tests_edge_router ..***Failed
> 623.61 sec
> {noformat}
>
> [https://github.com/apache/qpid-dispatch/runs/4461632417?check_suite_focus=true#step:27:2894]
>
> [https://github.com/apache/qpid-dispatch/runs/4461657326?check_suite_focus=true#step:9:4289]
>
> [https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/551423517#L7834]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2296) Some streaming message tests failing on system_tests_edge_router
[
https://issues.apache.org/jira/browse/DISPATCH-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-2296:
Description:
{noformat}
54: === short test summary info
54: FAILED ::StreamingMessageTest::test_11_streaming_closest_parallel -
proton._u...
54: FAILED ::StreamingMessageTest::test_12_streaming_multicast_parallel -
proton
54: FAILED ::StreamingMessageTest::test_13_streaming_balanced_parallel -
Attribut...
54: ERROR ::StreamingMessageTest::test_12_streaming_multicast_parallel -
RuntimeE...
54: ERROR ::StreamingMessageTest::test_13_streaming_balanced_parallel -
RuntimeEr...
54: == 3 failed, 86 passed, 2 errors in 623.32s (0:10:23)
==
36/37 Test #54: system_tests_edge_router ..***Failed
623.61 sec
{noformat}
[https://github.com/apache/qpid-dispatch/runs/4461632417?check_suite_focus=true#step:27:2894]
[https://github.com/apache/qpid-dispatch/runs/4461657326?check_suite_focus=true#step:9:4289]
was:
{noformat}
54: === short test summary info
54: FAILED ::StreamingMessageTest::test_11_streaming_closest_parallel -
proton._u...
54: FAILED ::StreamingMessageTest::test_12_streaming_multicast_parallel -
proton
54: FAILED ::StreamingMessageTest::test_13_streaming_balanced_parallel -
Attribut...
54: ERROR ::StreamingMessageTest::test_12_streaming_multicast_parallel -
RuntimeE...
54: ERROR ::StreamingMessageTest::test_13_streaming_balanced_parallel -
RuntimeEr...
54: == 3 failed, 86 passed, 2 errors in 623.32s (0:10:23)
==
36/37 Test #54: system_tests_edge_router ..***Failed
623.61 sec
{noformat}
https://github.com/apache/qpid-dispatch/runs/4461632417?check_suite_focus=true#step:27:2894
> Some streaming message tests failing on system_tests_edge_router
>
>
> Key: DISPATCH-2296
> URL: https://issues.apache.org/jira/browse/DISPATCH-2296
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Reporter: Ganesh Murthy
>Priority: Major
>
> {noformat}
> 54: === short test summary info
>
> 54: FAILED ::StreamingMessageTest::test_11_streaming_closest_parallel -
> proton._u...
> 54: FAILED ::StreamingMessageTest::test_12_streaming_multicast_parallel -
> proton
> 54: FAILED ::StreamingMessageTest::test_13_streaming_balanced_parallel -
> Attribut...
> 54: ERROR ::StreamingMessageTest::test_12_streaming_multicast_parallel -
> RuntimeE...
> 54: ERROR ::StreamingMessageTest::test_13_streaming_balanced_parallel -
> RuntimeEr...
> 54: == 3 failed, 86 passed, 2 errors in 623.32s (0:10:23)
> ==
> 36/37 Test #54: system_tests_edge_router ..***Failed
> 623.61 sec
> {noformat}
>
> [https://github.com/apache/qpid-dispatch/runs/4461632417?check_suite_focus=true#step:27:2894]
>
> [https://github.com/apache/qpid-dispatch/runs/4461657326?check_suite_focus=true#step:9:4289]
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2296) Some streaming message tests failing on system_tests_edge_router
Ganesh Murthy created DISPATCH-2296:
---
Summary: Some streaming message tests failing on
system_tests_edge_router
Key: DISPATCH-2296
URL: https://issues.apache.org/jira/browse/DISPATCH-2296
Project: Qpid Dispatch
Issue Type: Test
Components: Tests
Reporter: Ganesh Murthy
{noformat}
54: === short test summary info
54: FAILED ::StreamingMessageTest::test_11_streaming_closest_parallel -
proton._u...
54: FAILED ::StreamingMessageTest::test_12_streaming_multicast_parallel -
proton
54: FAILED ::StreamingMessageTest::test_13_streaming_balanced_parallel -
Attribut...
54: ERROR ::StreamingMessageTest::test_12_streaming_multicast_parallel -
RuntimeE...
54: ERROR ::StreamingMessageTest::test_13_streaming_balanced_parallel -
RuntimeEr...
54: == 3 failed, 86 passed, 2 errors in 623.32s (0:10:23)
==
36/37 Test #54: system_tests_edge_router ..***Failed
623.61 sec
{noformat}
https://github.com/apache/qpid-dispatch/runs/4461632417?check_suite_focus=true#step:27:2894
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2295) system_tests_multicast failure with timeout
Ganesh Murthy created DISPATCH-2295:
---
Summary: system_tests_multicast failure with timeout
Key: DISPATCH-2295
URL: https://issues.apache.org/jira/browse/DISPATCH-2295
Project: Qpid Dispatch
Issue Type: Test
Components: Tests
Affects Versions: 1.18.0
Reporter: Ganesh Murthy
{noformat}
63: ::MulticastLinearTest::test_50_presettled FAILED
63: ::MulticastLinearTest::test_51_presettled_mixed_large_msg FAILED
38/38 Test #63: system_tests_multicast ..***Timeout 1200.11 sec
{noformat}
https://github.com/apache/qpid-dispatch/runs/4461632262?check_suite_focus=true#step:27:5372
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2294) Enable TCP listeners and connectors to use TLS
[ https://issues.apache.org/jira/browse/DISPATCH-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2294: Component/s: Protocol Adaptors > Enable TCP listeners and connectors to use TLS > -- > > Key: DISPATCH-2294 > URL: https://issues.apache.org/jira/browse/DISPATCH-2294 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Protocol Adaptors >Reporter: Ganesh Murthy >Priority: Major > > Qpid-Proton is developing a TLS library that works with raw connections. > Enable TCP adaptor's listeners and connectors to be configured with an > SSLProfile which will use proton's new raw connection TLS library to provide > encryption/decryption capabilities. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2294) Enable TCP listeners and connectors to use TLS
[ https://issues.apache.org/jira/browse/DISPATCH-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2294: Fix Version/s: 1.19.0 > Enable TCP listeners and connectors to use TLS > -- > > Key: DISPATCH-2294 > URL: https://issues.apache.org/jira/browse/DISPATCH-2294 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Protocol Adaptors >Reporter: Ganesh Murthy >Priority: Major > Fix For: 1.19.0 > > > Qpid-Proton is developing a TLS library that works with raw connections. > Enable TCP adaptor's listeners and connectors to be configured with an > SSLProfile which will use proton's new raw connection TLS library to provide > encryption/decryption capabilities. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2294) Enable TCP listeners and connectors to use TLS
Ganesh Murthy created DISPATCH-2294: --- Summary: Enable TCP listeners and connectors to use TLS Key: DISPATCH-2294 URL: https://issues.apache.org/jira/browse/DISPATCH-2294 Project: Qpid Dispatch Issue Type: New Feature Reporter: Ganesh Murthy Qpid-Proton is developing a TLS library that works with raw connections. Enable TCP adaptor's listeners and connectors to be configured with an SSLProfile which will use proton's new raw connection TLS library to provide encryption/decryption capabilities. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2275) Dispatch test failures with the latest from proton main branch
[
https://issues.apache.org/jira/browse/DISPATCH-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2275.
-
Fix Version/s: 1.19.0
Resolution: Fixed
> Dispatch test failures with the latest from proton main branch
> --
>
> Key: DISPATCH-2275
> URL: https://issues.apache.org/jira/browse/DISPATCH-2275
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Affects Versions: 1.17.1
>Reporter: Ganesh Murthy
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.19.0
>
>
> There are 3 test errors
> {noformat}
> 47: Error text: Process 2801860 error: exit code 1, expected 0
> 47: /usr/bin/python3.9
> /home/gmurthy/opensource/qpid-dispatch/build/tests/scraper/scraper.py -f
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/A.log
>
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/B.log
>
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/C.log
>
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/D.log
> 47:
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/test_04_scraper_tool/python3.9-1.cmd
> 47:
> 47:
> 47: FAIL
> 75: 2021-11-05 10:49:25.394391 TCP_TEST test_01_tcp_EB1_EA1 Client
> test_01_tcp_EB1_EA1_0_1_1 exited normally
> 75: 2021-11-05 10:49:25.394507 TCP_TEST test_01_tcp_EB1_EA1 SUCCESS
> 75: 2021-11-05 10:49:25.394626 TCP_TEST test_01_tcp_basic_connectivity Stop
> test_01_tcp_EB1_EA1 SUCCESS
> 75: 2021-11-05 10:49:25.394673 TCP_TEST test_01_tcp_basic_connectivity Start
> test_01_tcp_EB1_EA2
> 75: 2021-11-05 10:49:25.394726 TCP_TEST test_01_tcp_EB1_EA2 Start
> do_tcp_echo_n_routers
> 75: 2021-11-05 10:49:25.394774 TCP_TEST test_01_tcp_EB1_EA2 Running pair 0
> EB1->EA2 size=1 count=1
> 47:
> 47: ==
> 47: FAIL: test_04_scraper_tool
> (system_tests_topology_disposition.TopologyDispositionTests)
> 47: --
> 47: Traceback (most recent call last):
> 47: File
> "/home/gmurthy/opensource/qpid-dispatch/tests/system_tests_topology_disposition.py",
> line 432, in test_04_scraper_tool
> 47: self.assertEqual(str(None), error)
> 47: AssertionError: 'None' != 'Process 2801860 error: exit code 1, expec[842
> chars]'
> 47: - None
> 47: + Process 2801860 error: exit code 1, expected 0
> 47: /usr/bin/python3.9
> /home/gmurthy/opensource/qpid-dispatch/build/tests/scraper/scraper.py -f
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/A.log
>
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/B.log
>
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/C.log
>
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/D.log
> 47:
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/test_04_scraper_tool/python3.9-1.cmd
> 47:
> 47: {noformat}
>
> {noformat}
> 29: test_max_sessions_zero
> (system_tests_protocol_settings.MaxSessionsZeroTest) ... FAIL
> 29:
> 29: ==
> 29: FAIL: test_connector_default
> (system_tests_protocol_settings.ConnectorSettingsDefaultTest)
> 29: --
> 29: Traceback (most recent call last):
> 29: File
> "/home/gmurthy/opensource/qpid-dispatch/tests/system_tests_protocol_settings.py",
> line 322, in test_connector_default
> 29: self.assertIn(' max-frame-size=16384,', open_lines[0])
> 29: AssertionError: ' max-frame-size=16384,' not found in '2021-11-05
> 10:50:24.161355 -0400 PROTOCOL (trace) [C3]:FRAME: 0 <- @open(16)
> [container-id="QDR.B", hostname="127.0.0.1", max-frame-size=0x4000,
> channel-max=0x7fff, idle-time-out=0xea60, outgoing-locales=null,
> incoming-locales=null, offered-capabilities=@[:ANONYMOUS-RELAY,
> :"qd.streaming-links"], desired-capabilities=@[:ANONYMOUS-RELAY,
> :"qd.streaming-links"],
[jira] [Commented] (DISPATCH-2292) [http2] system_tests_grpc failed with qd_http2_buffer_t leak
[
https://issues.apache.org/jira/browse/DISPATCH-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17447419#comment-17447419
]
Ganesh Murthy commented on DISPATCH-2292:
-
This is the first time I am seeing this leak in this test. Let's keep this Jira
around to see if this happens again.
> [http2] system_tests_grpc failed with qd_http2_buffer_t leak
>
>
> Key: DISPATCH-2292
> URL: https://issues.apache.org/jira/browse/DISPATCH-2292
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.19.0
>Reporter: Jiri Daněk
>Priority: Major
>
> https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/549003884#L10696
> {noformat}
> 70: ERROR: Aborted due to unexpected alloc pool leak of type
> 'qd_http2_buffer_t'
> {noformat}
> {noformat}
> 70: alloc.c: Items of type 'qd_http2_buffer_t' remain allocated at shutdown: 1
> 70: Leak: 2021-11-20 21:14:56.179730 + type: qd_http2_buffer_t address:
> 0x629000163290
> 70: qdrouterd(backtrace+0x5b) [0x47884b]
> 70: qdrouterd(qd_alloc+0x918) [0x572738]
> 70: qdrouterd(qd_http2_buffer+0x24) [0x786874]
> 70: qdrouterd(qd_http2_buffer_list_append+0x81) [0x786a71]
> 70: qdrouterd() [0x7b9b21]
> 70: /lib/x86_64-linux-gnu/libnghttp2.so.14(nghttp2_session_send+0x49)
> [0x7f5f3a894c89]
> 70: qdrouterd() [0x7aa9f0]
> 70: qdrouterd() [0x791536]
> 70: qdrouterd() [0x777830]
> 70: qdrouterd() [0x771dd0]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2291) system_tests_qdstat and system_tests_qdmanage take a long time to execute
[ https://issues.apache.org/jira/browse/DISPATCH-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2291: Summary: system_tests_qdstat and system_tests_qdmanage take a long time to execute (was: system_tests_qdstat take a long time to execute) > system_tests_qdstat and system_tests_qdmanage take a long time to execute > - > > Key: DISPATCH-2291 > URL: https://issues.apache.org/jira/browse/DISPATCH-2291 > Project: Qpid Dispatch > Issue Type: Test > Components: Tests >Affects Versions: 1.17.1 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.19.0 > > > Investigate why system_tests_qdstat takes a long time to execute and fix it. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2065) AttributeError: 'DeleteConnectionWithReceiver' object has no attribute 'n_sent'
[
https://issues.apache.org/jira/browse/DISPATCH-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2065.
-
Assignee: Ganesh Murthy
Resolution: Fixed
> AttributeError: 'DeleteConnectionWithReceiver' object has no attribute
> 'n_sent'
> ---
>
> Key: DISPATCH-2065
> URL: https://issues.apache.org/jira/browse/DISPATCH-2065
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Affects Versions: 1.15.0
>Reporter: Jiri Daněk
>Assignee: Ganesh Murthy
>Priority: Minor
> Fix For: 1.19.0
>
>
> https://github.com/apache/qpid-dispatch/pull/1052/checks?check_run_id=2394806073#step:9:2728
> The stacktrace below is caused by a copy-paste error. The test object does
> not have the attributes that are accessed.
> Furthermore, the test output does not provide any useful diagnostics in its
> output to investigate why the timeout happened.
> {noformat}
> 34: ==
> 34: ERROR: test_21_delete_connection_with_receiver
> (system_tests_two_routers.TwoRouterTest)
> 34: --
> 34: Traceback (most recent call last):
> 34: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/system_tests_two_routers.py",
> line 377, in test_21_delete_connection_with_receiver
> 34: test.run()
> 34: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/system_tests_two_routers.py",
> line 496, in run
> 34: Container(self).run()
> 34: File
> "/opt/hostedtoolcache/Python/3.7.10/x64/lib/python3.7/site-packages/proton/_reactor.py",
> line 182, in run
> 34: while self.process():
> 34: File
> "/opt/hostedtoolcache/Python/3.7.10/x64/lib/python3.7/site-packages/proton/_reactor.py",
> line 240, in process
> 34: event.dispatch(handler)
> 34: File
> "/opt/hostedtoolcache/Python/3.7.10/x64/lib/python3.7/site-packages/proton/_events.py",
> line 162, in dispatch
> 34: _dispatch(handler, type.method, self)
> 34: File
> "/opt/hostedtoolcache/Python/3.7.10/x64/lib/python3.7/site-packages/proton/_events.py",
> line 123, in _dispatch
> 34: m(*args)
> 34: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/system_test.py",
> line 1327, in on_timer_task
> 34: self.parent.timeout()
> 34: File
> "/home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/tests/system_tests_two_routers.py",
> line 432, in timeout
> 34: self.error = "Timeout Expired: sent=%d, received=%d" % (self.n_sent,
> self.n_received)
> 34: AttributeError: 'DeleteConnectionWithReceiver' object has no attribute
> 'n_sent'
> 34:
> 34: --
> 34: Ran 32 tests in 124.158s
> 34:
> 34: FAILED (errors=1)
> 34:
> 18/37 Test #34: system_tests_two_routers ..***Failed
> 124.31 sec
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2291) system_tests_qdstat take a long time to execute
[ https://issues.apache.org/jira/browse/DISPATCH-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-2291. - Resolution: Fixed > system_tests_qdstat take a long time to execute > --- > > Key: DISPATCH-2291 > URL: https://issues.apache.org/jira/browse/DISPATCH-2291 > Project: Qpid Dispatch > Issue Type: Test > Components: Tests >Affects Versions: 1.17.1 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.19.0 > > > Investigate why system_tests_qdstat takes a long time to execute and fix it. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2291) system_tests_qdstat take a long time to execute
Ganesh Murthy created DISPATCH-2291: --- Summary: system_tests_qdstat take a long time to execute Key: DISPATCH-2291 URL: https://issues.apache.org/jira/browse/DISPATCH-2291 Project: Qpid Dispatch Issue Type: Test Components: Tests Affects Versions: 1.17.1 Reporter: Ganesh Murthy Assignee: Ganesh Murthy Fix For: 1.19.0 Investigate why system_tests_qdstat takes a long time to execute and fix it. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-2258) test_25_parallel_waypoint_test failing in system_tests_distribution
[
https://issues.apache.org/jira/browse/DISPATCH-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-2258:
---
Assignee: Ken Giusti (was: Ganesh Murthy)
> test_25_parallel_waypoint_test failing in system_tests_distribution
> ---
>
> Key: DISPATCH-2258
> URL: https://issues.apache.org/jira/browse/DISPATCH-2258
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Reporter: Ganesh Murthy
>Assignee: Ken Giusti
>Priority: Major
>
> {noformat}
> 37: ==
> 37: FAIL: test_25_parallel_waypoint_test
> (system_tests_distribution.DistributionTests)
> 37: --
> 37: Traceback (most recent call last):
> 37: File
> "/home/travis/build/apache/qpid-dispatch/tests/system_tests_distribution.py",
> line 1641, in test_25_parallel_waypoint_test
> 37: self.assertIsNone(test.error)
> 37: AssertionError: 'Timeout Expired: n_sent=200 n_rcvd=194 n_thru=198' is
> not None
> 37:
> 37: --
> 37: Ran 25 tests in 344.700s
> 37:
> 37: FAILED (failures=1, skipped=7)
> 37/73 Test #37: system_tests_distribution .***Failed
> 344.85 sec {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-2287) Comment out switchover tests in system_tests_fallback_dest in GitHub Actions
[ https://issues.apache.org/jira/browse/DISPATCH-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-2287. - Resolution: Fixed > Comment out switchover tests in system_tests_fallback_dest in GitHub Actions > > > Key: DISPATCH-2287 > URL: https://issues.apache.org/jira/browse/DISPATCH-2287 > Project: Qpid Dispatch > Issue Type: Test > Components: Tests >Affects Versions: 1.17.1 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.19.0 > > > The switchover tests fail intermittently in GitHub Actions > [https://github.com/apache/qpid-dispatch/runs/4203396003?check_suite_focus=true#step:9:5125] > > We will comment the switchover tests until we fix DISPATCH-2256 > > These tests have already been commented out in Travis -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2283) heap-use-after-free in system_tests_policy_oversize_compound during qdrc_endpoint_delivery_CT
[
https://issues.apache.org/jira/browse/DISPATCH-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443955#comment-17443955
]
Ganesh Murthy commented on DISPATCH-2283:
-
Fixed by commit -
[https://github.com/apache/qpid-dispatch/commit/6769203991b20ecf0fdeb28bb8d84962b73c22fd]
as part of fix to https://issues.apache.org/jira/browse/DISPATCH-2262
> heap-use-after-free in system_tests_policy_oversize_compound during
> qdrc_endpoint_delivery_CT
> -
>
> Key: DISPATCH-2283
> URL: https://issues.apache.org/jira/browse/DISPATCH-2283
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.18.0
>Reporter: Jiri Daněk
>Assignee: Ted Ross
>Priority: Major
> Fix For: 1.18.0
>
>
> https://github.com/jiridanek/qpid-dispatch/runs/4140877666?check_suite_focus=true#step:9:35786
> This comes from the "set memory pool max size to 0" memory poisoning
> investigation. I haven't seen this fail with unmodified main branch (yet ;)
> The only somewhat similar stacktrace I could find in Jira is for this leak
> DISPATCH-1699.
> {noformat}
> 27: ==12548==ERROR: AddressSanitizer: heap-use-after-free on address
> 0x611136e0 at pc 0x55f47830adb9 bp 0x7f1063183140 sp 0x7f1063183130
> 27: READ of size 8 at 0x611136e0 thread T1
> 27: #0 0x55f47830adb8 in qdrc_endpoint_delivery_CT
> ../src/router_core/core_link_endpoint.c:136
> 27: #1 0x55f4783eea3b in on_timer
> ../src/router_core/modules/heartbeat_edge/heartbeat_edge.c:157
> 27: #2 0x55f4783c0613 in qdr_process_tick_CT
> ../src/router_core/core_timer.c:123
> 27: #3 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #4 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #5 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27: #6 0x7f106864e292 in __clone
> (/lib/x86_64-linux-gnu/libc.so.6+0x122292)
> 27:
> 27: 0x611136e0 is located 160 bytes inside of 192-byte region
> [0x61113640,0x61113700)
> 27: freed by thread T1 here:
> 27: #0 0x7f1069a167cf in __interceptor_free
> (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)
> 27: #1 0x55f4781e3b84 in qd_dealloc ../src/alloc_pool.c:497
> 27: #2 0x55f478308e1d in free_qdrc_endpoint_t
> ../src/router_core/core_link_endpoint.c:35
> 27: #3 0x55f47830d34f in qdrc_endpoint_do_cleanup_CT
> ../src/router_core/core_link_endpoint.c:245
> 27: #4 0x55f47830cb0f in qdrc_endpoint_do_detach_CT
> ../src/router_core/core_link_endpoint.c:220
> 27: #5 0x55f478301824 in qdr_link_inbound_detach_CT
> ../src/router_core/connections.c:2033
> 27: #6 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #7 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #8 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27:
> 27: previously allocated by thread T1 here:
> 27: #0 0x7f1069a17aa5 in posix_memalign
> (/lib/x86_64-linux-gnu/libasan.so.5+0x10eaa5)
> 27: #1 0x55f4781df9cd in qd_alloc ../src/alloc_pool.c:393
> 27: #2 0x55f478308de5 in new_qdrc_endpoint_t
> ../src/router_core/core_link_endpoint.c:35
> 27: #3 0x55f478309d28 in qdrc_endpoint_create_link_CT
> ../src/router_core/core_link_endpoint.c:74
> 27: #4 0x55f4783eed7d in on_conn_event
> ../src/router_core/modules/heartbeat_edge/heartbeat_edge.c:178
> 27: #5 0x55f47830823d in qdrc_event_conn_raise
> ../src/router_core/core_events.c:101
> 27: #6 0x55f4783c5a14 in on_conn_event
> ../src/router_core/modules/edge_router/connection_manager.c:59
> 27: #7 0x55f47830823d in qdrc_event_conn_raise
> ../src/router_core/core_events.c:101
> 27: #8 0x55f4782f5fdc in qdr_connection_opened_CT
> ../src/router_core/connections.c:1479
> 27: #9 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #10 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #11 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27:
> 27: Thread T1 created by T0 here:
> 27: #0 0x7f1069943805 in pthread_create
> (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)
> 27: #1 0x55f4782a2ad3 in sys_thread ../src/posix/threading.c:181
> 27: #2 0x55f47836b817 in qdr_core ../src/router_core/router_core.c:124
> 27: #3 0x55f478411c5c in qd_router_setup_late ../src/router_node.c:2127
> 27: #4 0x7f1064308ff4 (/lib/x86_64-linux-gnu/libffi.so.7+0x6ff4)
> 27: #5 0x7ffdaab8945f ([stack]+0x2145f)
> 27:
> 27: SUMMARY: AddressSanitizer: heap-use-after-free
> ../src/router_core/core_link_endpoint.c:136 in qdrc_endpoint_delivery_CT
> 27: Shadow bytes around the buggy address:
> 27:
[jira] [Resolved] (DISPATCH-2283) heap-use-after-free in system_tests_policy_oversize_compound during qdrc_endpoint_delivery_CT
[
https://issues.apache.org/jira/browse/DISPATCH-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2283.
-
Resolution: Fixed
> heap-use-after-free in system_tests_policy_oversize_compound during
> qdrc_endpoint_delivery_CT
> -
>
> Key: DISPATCH-2283
> URL: https://issues.apache.org/jira/browse/DISPATCH-2283
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.18.0
>Reporter: Jiri Daněk
>Assignee: Ted Ross
>Priority: Major
> Fix For: 1.18.0
>
>
> https://github.com/jiridanek/qpid-dispatch/runs/4140877666?check_suite_focus=true#step:9:35786
> This comes from the "set memory pool max size to 0" memory poisoning
> investigation. I haven't seen this fail with unmodified main branch (yet ;)
> The only somewhat similar stacktrace I could find in Jira is for this leak
> DISPATCH-1699.
> {noformat}
> 27: ==12548==ERROR: AddressSanitizer: heap-use-after-free on address
> 0x611136e0 at pc 0x55f47830adb9 bp 0x7f1063183140 sp 0x7f1063183130
> 27: READ of size 8 at 0x611136e0 thread T1
> 27: #0 0x55f47830adb8 in qdrc_endpoint_delivery_CT
> ../src/router_core/core_link_endpoint.c:136
> 27: #1 0x55f4783eea3b in on_timer
> ../src/router_core/modules/heartbeat_edge/heartbeat_edge.c:157
> 27: #2 0x55f4783c0613 in qdr_process_tick_CT
> ../src/router_core/core_timer.c:123
> 27: #3 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #4 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #5 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27: #6 0x7f106864e292 in __clone
> (/lib/x86_64-linux-gnu/libc.so.6+0x122292)
> 27:
> 27: 0x611136e0 is located 160 bytes inside of 192-byte region
> [0x61113640,0x61113700)
> 27: freed by thread T1 here:
> 27: #0 0x7f1069a167cf in __interceptor_free
> (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)
> 27: #1 0x55f4781e3b84 in qd_dealloc ../src/alloc_pool.c:497
> 27: #2 0x55f478308e1d in free_qdrc_endpoint_t
> ../src/router_core/core_link_endpoint.c:35
> 27: #3 0x55f47830d34f in qdrc_endpoint_do_cleanup_CT
> ../src/router_core/core_link_endpoint.c:245
> 27: #4 0x55f47830cb0f in qdrc_endpoint_do_detach_CT
> ../src/router_core/core_link_endpoint.c:220
> 27: #5 0x55f478301824 in qdr_link_inbound_detach_CT
> ../src/router_core/connections.c:2033
> 27: #6 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #7 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #8 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27:
> 27: previously allocated by thread T1 here:
> 27: #0 0x7f1069a17aa5 in posix_memalign
> (/lib/x86_64-linux-gnu/libasan.so.5+0x10eaa5)
> 27: #1 0x55f4781df9cd in qd_alloc ../src/alloc_pool.c:393
> 27: #2 0x55f478308de5 in new_qdrc_endpoint_t
> ../src/router_core/core_link_endpoint.c:35
> 27: #3 0x55f478309d28 in qdrc_endpoint_create_link_CT
> ../src/router_core/core_link_endpoint.c:74
> 27: #4 0x55f4783eed7d in on_conn_event
> ../src/router_core/modules/heartbeat_edge/heartbeat_edge.c:178
> 27: #5 0x55f47830823d in qdrc_event_conn_raise
> ../src/router_core/core_events.c:101
> 27: #6 0x55f4783c5a14 in on_conn_event
> ../src/router_core/modules/edge_router/connection_manager.c:59
> 27: #7 0x55f47830823d in qdrc_event_conn_raise
> ../src/router_core/core_events.c:101
> 27: #8 0x55f4782f5fdc in qdr_connection_opened_CT
> ../src/router_core/connections.c:1479
> 27: #9 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #10 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #11 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27:
> 27: Thread T1 created by T0 here:
> 27: #0 0x7f1069943805 in pthread_create
> (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)
> 27: #1 0x55f4782a2ad3 in sys_thread ../src/posix/threading.c:181
> 27: #2 0x55f47836b817 in qdr_core ../src/router_core/router_core.c:124
> 27: #3 0x55f478411c5c in qd_router_setup_late ../src/router_node.c:2127
> 27: #4 0x7f1064308ff4 (/lib/x86_64-linux-gnu/libffi.so.7+0x6ff4)
> 27: #5 0x7ffdaab8945f ([stack]+0x2145f)
> 27:
> 27: SUMMARY: AddressSanitizer: heap-use-after-free
> ../src/router_core/core_link_endpoint.c:136 in qdrc_endpoint_delivery_CT
> 27: Shadow bytes around the buggy address:
> 27: 0x0c227fffa680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 27: 0x0c227fffa690: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> 27: 0x0c227fffa6a0: fd fd fd fd fd fd fd fd fd fd fd fd fd
[jira] [Updated] (DISPATCH-2256) edge router fallback links and addresses incorrect on interior failover
[ https://issues.apache.org/jira/browse/DISPATCH-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2256: Fix Version/s: 1.19.0 (was: 1.18.0) > edge router fallback links and addresses incorrect on interior failover > --- > > Key: DISPATCH-2256 > URL: https://issues.apache.org/jira/browse/DISPATCH-2256 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.17.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.19.0 > > > Scenario: > Configure an edge router with two separate interior connectors - one for > router A and a standby for router B. > Configure a route-container listener for a broker on the edge router. Assign > two fallback destination autolinks (1 in, 1 out) to the route container for > address "foo". > Start just the edge router: > * no links are active (expected). > * mgmt query for addresses show two "foo" addresses present: > ** MFfoo - the fallback address (no subscribers) > ** M0foo - the primary address (no subscribers) > Now startup the broker and after the connection to the broker: > * On the edge router: > ** links: > *** id 5, out link to broker, owning address MFfoo > *** id 6, in link from broker, owning address M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > Now start router A. Router A has been configured with an edge listener > connection. There is no inter-router connection configured for router B! > Once the connection is established: > * On the edge router: > ** links: > *** the two broker links (see above) > *** id 10, in link from router A, owning address MFfoo > *** id 11, out link to router A for M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > * On Router A: > ** links: > *** id 6, out link to edge, owning address MFfoo > *** id 7, in link from edge, owning address M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > Now start router B, wait for the edge to establish a connection to it. Since > B is a standby interior for the edge there are no 'foo' related links or > addresses on B as expected. Remember router A and B are not directly > connected. > > Fail router A. Wait for the edge to re-establish its proxy links to router > B. The following links/addresses related to foo are now: > * On the edge router: > ** links: > *** the two broker links > *** id 20, in link from router B, owning address MFfoo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > * On Router B: > ** links: > *** id 6, out link to edge, owning address MFfoo > ** addresses: > *** MFfoo - one local subscriber > From the above we can see that after the failover to router B the edge router > does not re-establish an outgoing link (subscription) for M0foo as it did > when connected to router A. > -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2266) system_tests_edge_router stalls on Travis CI
[
https://issues.apache.org/jira/browse/DISPATCH-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17443914#comment-17443914
]
Ganesh Murthy commented on DISPATCH-2266:
-
Test failure log -
https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/547809231
{noformat}
test_51_link_route_proxy_configured
(system_tests_edge_router.LinkRouteProxyTest) ...
2021-11-11 23:12:28.696004 test_51_link_route_proxy_configured Created
FakeService
2021-11-11 23:12:28.723208 test_51_link_route_proxy_configured Wait done on
CfgLinkRoute1
2021-11-11 23:12:28.723277 _test_traffic begin
2021-11-11 23:12:28.724614 Starting reactor
2021-11-11 23:12:28.731841 Connection opened
2021-11-11 23:12:28.746942 link opened
2021-11-11 23:12:28.748881 _test_traffic AsyncTestReceiver created
2021-11-11 23:12:28.752892 reactor thread done
2021-11-11 23:12:28.753839 _test_traffic AsyncTestSender created
2021-11-11 23:12:28.753882 AsyncTestSender wait: about to join thread
2021-11-11 23:12:28.754024 Starting reactor
2021-11-11 23:12:28.761420 Connection opened
2021-11-11 23:12:28.774905 message 1 sent
2021-11-11 23:12:28.775375 message 2 sent
2021-11-11 23:12:28.775861 message 3 sent
2021-11-11 23:12:28.776305 message 4 sent
2021-11-11 23:12:28.776805 message 5 sent
2021-11-11 23:12:28.809712 message 1 accepted
2021-11-11 23:12:28.817583 message 2 accepted
2021-11-11 23:12:28.835311 message 3 accepted
2021-11-11 23:12:28.835522 message 4 accepted
2021-11-11 23:12:28.837575 message 5 accepted
2021-11-11 23:12:29.006677 Connection closed
2021-11-11 23:12:29.011393 reactor thread done
2021-11-11 23:12:29.011573 AsyncTestSender wait: thread done
2021-11-11 23:12:29.013014 AsyncTestSender wait: no errors in wait
2021-11-11 23:12:29.013070 _test_traffic sender wait done {noformat}
> system_tests_edge_router stalls on Travis CI
>
>
> Key: DISPATCH-2266
> URL: https://issues.apache.org/jira/browse/DISPATCH-2266
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Affects Versions: 1.17.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
>
> The system_tests_edge_router stalls on Travis CI intermittently
> {noformat}
> 55: test_50_link_topology (system_tests_edge_router.LinkRouteProxyTest) ... ok
> No output has been received in the last 10m0s, this potentially indicates a
> stalled build or something wrong with the build itself.
> Check the details on how to adjust your build configuration on:
> https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
> The build has been terminated
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-2287) Comment out switchover tests in system_tests_fallback_dest in GitHub Actions
Ganesh Murthy created DISPATCH-2287: --- Summary: Comment out switchover tests in system_tests_fallback_dest in GitHub Actions Key: DISPATCH-2287 URL: https://issues.apache.org/jira/browse/DISPATCH-2287 Project: Qpid Dispatch Issue Type: Test Components: Tests Affects Versions: 1.17.1 Reporter: Ganesh Murthy Assignee: Ganesh Murthy Fix For: 1.19.0 The switchover tests fail intermittently in GitHub Actions [https://github.com/apache/qpid-dispatch/runs/4203396003?check_suite_focus=true#step:9:5125] We will comment the switchover tests until we fix DISPATCH-2256 These tests have already been commented out in Travis -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2085) system_tests_fallback_dest failure - addr_proxy.c:323: on_conn_event: Assertion `addr->edge_outlink == 0' failed
[
https://issues.apache.org/jira/browse/DISPATCH-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-2085:
Fix Version/s: 1.19.0
(was: 1.18.0)
> system_tests_fallback_dest failure - addr_proxy.c:323: on_conn_event:
> Assertion `addr->edge_outlink == 0' failed
>
>
> Key: DISPATCH-2085
> URL: https://issues.apache.org/jira/browse/DISPATCH-2085
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.16.0, 1.17.0
>Reporter: Jiri Daněk
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.19.0
>
>
> First spotted on s390x,
> https://travis-ci.com/github/apache/qpid-dispatch/jobs/501153572#L6607
> {noformat}
> 62: Router EA2 output file:
> 62:
> 62: 2021-04-26 16:56:05.615255 + AGENT (warning) Attribute 'dir' of
> entity 'autoLink' has been deprecated. Use 'direction' instead
> 62: 2021-04-26 16:56:05.615411 + AGENT (warning) Attribute 'dir' of
> entity 'autoLink' has been deprecated. Use 'direction' instead
> 62: qdrouterd:
> /home/travis/build/apache/qpid-dispatch/src/router_core/modules/edge_router/addr_proxy.c:323:
> on_conn_event: Assertion `addr->edge_outlink == 0' failed.
> 62:
> 62:
> 62:
> 62: Router EA2 command file:
> 62:
> 62: qdrouterd -c EA2.conf -I /home/travis/build/apache/qpid-dispatch/python
> 62: pid=14036
> 62:
> 62:
> 62:
> 62: Router EA2 log file tail:
> 62:
> 62: 2021-04-26 16:58:05.686184 + ROUTER_CORE (trace) Core action
> 'link_detach'
> (/home/travis/build/apache/qpid-dispatch/src/router_core/router_core_thread.c:238)
> 62: 2021-04-26 16:58:05.686235 + ROUTER_CORE (info) [C4][L12] Link lost:
> del=1 presett=1 psdrop=0 acc=0 rej=0 rel=0 mod=0 delay1=0 delay10=0
> blocked=no
> (/home/travis/build/apache/qpid-dispatch/src/router_core/connections.c:1074)
> 62: 2021-04-26 16:58:05.686281 + ROUTER_CORE (trace) Core action
> 'connection_closed'
> (/home/travis/build/apache/qpid-dispatch/src/router_core/router_core_thread.c:238)
> 62: 2021-04-26 16:58:05.686346 + ROUTER_CORE (info) [C4] Connection
> Closed
> (/home/travis/build/apache/qpid-dispatch/src/router_core/connections.c:1557)
> 62: 2021-04-26 16:58:05.705484 + SERVER (trace) Accepting connection on
> 0.0.0.0:23020 (/home/travis/build/apache/qpid-dispatch/src/server.c:852)
> 62: 2021-04-26 16:58:05.705577 + SERVER (trace) [C5]: Accepting incoming
> connection to '0.0.0.0:23020'
> (/home/travis/build/apache/qpid-dispatch/src/server.c:606)
> 62: 2021-04-26 16:58:05.705691 + POLICY (trace) ALLOW Connection
> '127.0.0.1' based on global connection count. nConnections= 1
> (/home/travis/build/apache/qpid-dispatch/src/policy.c:271)
> 62: 2021-04-26 16:58:05.705782 + SERVER (info) [C5] Accepted connection
> to 0.0.0.0:23020 from 127.0.0.1:37922
> (/home/travis/build/apache/qpid-dispatch/src/server.c:750)
> 62: 2021-04-26 16:58:05.706152 + PROTOCOL (trace) [C5]:FRAME: <- SASL
> (/home/travis/build/apache/qpid-dispatch/src/server.c:111)
> 62: 2021-04-26 16:58:05.706180 + PROTOCOL (trace) [C5]:FRAME: -> SASL
> (/home/travis/build/apache/qpid-dispatch/src/server.c:111)
> 62: 2021-04-26 16:58:05.706590 + PROTOCOL (trace) [C5]:FRAME: 0 ->
> @sasl-mechanisms(64) [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> (/home/travis/build/apache/qpid-dispatch/src/server.c:111)
> 62: 2021-04-26 16:58:05.706949 + PROTOCOL (trace) [C5]:FRAME: 0 <-
> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"anonymous@travis-job-apache-qpid-dispatch-501153572"]
> (/home/travis/build/apache/qpid-dispatch/src/server.c:111)
> 62: 2021-04-26 16:58:05.707025 + PROTOCOL (trace) [C5]:FRAME: 0 ->
> @sasl-outcome(68) [code=0]
> (/home/travis/build/apache/qpid-dispatch/src/server.c:111)
> 62: 2021-04-26 16:58:05.707319 + PROTOCOL (trace) [C5]:FRAME: <- AMQP
> (/home/travis/build/apache/qpid-dispatch/src/server.c:111)
> 62: 2021-04-26 16:58:05.707363 + PROTOCOL (trace) [C5]:FRAME: 0 <-
> @open(16) [container-id="ac3fab39-661e-44f4-8361-5866a600788d",
> hostname="0.0.0.0", channel-max=32767]
> (/home/travis/build/apache/qpid-dispatch/src/server.c:111)
> 62: 2021-04-26 16:58:05.707432 + PROTOCOL (trace) [C5]:FRAME: 0 <-
> @begin(17) [next-outgoing-id=0, incoming-window=2147483647,
> outgoing-window=2147483647]
> (/home/travis/build/apache/qpid-dispatch/src/server.c:111)
> 62: 2021-04-26 16:58:05.707500 + PROTOCOL (trace) [C5]:FRAME: 0 <-
> @attach(18) [name="dest.32_primary_receiver", handle=0, role=true,
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="dest.32",
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0,
> timeout=0,
[jira] [Assigned] (DISPATCH-2283) heap-use-after-free in system_tests_policy_oversize_compound during qdrc_endpoint_delivery_CT
[
https://issues.apache.org/jira/browse/DISPATCH-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-2283:
---
Assignee: Ted Ross
> heap-use-after-free in system_tests_policy_oversize_compound during
> qdrc_endpoint_delivery_CT
> -
>
> Key: DISPATCH-2283
> URL: https://issues.apache.org/jira/browse/DISPATCH-2283
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.18.0
>Reporter: Jiri Daněk
>Assignee: Ted Ross
>Priority: Major
> Fix For: 1.18.0
>
>
> https://github.com/jiridanek/qpid-dispatch/runs/4140877666?check_suite_focus=true#step:9:35786
> This comes from the "set memory pool max size to 0" memory poisoning
> investigation. I haven't seen this fail with unmodified main branch (yet ;)
> The only somewhat similar stacktrace I could find in Jira is for this leak
> DISPATCH-1699.
> {noformat}
> 27: ==12548==ERROR: AddressSanitizer: heap-use-after-free on address
> 0x611136e0 at pc 0x55f47830adb9 bp 0x7f1063183140 sp 0x7f1063183130
> 27: READ of size 8 at 0x611136e0 thread T1
> 27: #0 0x55f47830adb8 in qdrc_endpoint_delivery_CT
> ../src/router_core/core_link_endpoint.c:136
> 27: #1 0x55f4783eea3b in on_timer
> ../src/router_core/modules/heartbeat_edge/heartbeat_edge.c:157
> 27: #2 0x55f4783c0613 in qdr_process_tick_CT
> ../src/router_core/core_timer.c:123
> 27: #3 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #4 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #5 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27: #6 0x7f106864e292 in __clone
> (/lib/x86_64-linux-gnu/libc.so.6+0x122292)
> 27:
> 27: 0x611136e0 is located 160 bytes inside of 192-byte region
> [0x61113640,0x61113700)
> 27: freed by thread T1 here:
> 27: #0 0x7f1069a167cf in __interceptor_free
> (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)
> 27: #1 0x55f4781e3b84 in qd_dealloc ../src/alloc_pool.c:497
> 27: #2 0x55f478308e1d in free_qdrc_endpoint_t
> ../src/router_core/core_link_endpoint.c:35
> 27: #3 0x55f47830d34f in qdrc_endpoint_do_cleanup_CT
> ../src/router_core/core_link_endpoint.c:245
> 27: #4 0x55f47830cb0f in qdrc_endpoint_do_detach_CT
> ../src/router_core/core_link_endpoint.c:220
> 27: #5 0x55f478301824 in qdr_link_inbound_detach_CT
> ../src/router_core/connections.c:2033
> 27: #6 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #7 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #8 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27:
> 27: previously allocated by thread T1 here:
> 27: #0 0x7f1069a17aa5 in posix_memalign
> (/lib/x86_64-linux-gnu/libasan.so.5+0x10eaa5)
> 27: #1 0x55f4781df9cd in qd_alloc ../src/alloc_pool.c:393
> 27: #2 0x55f478308de5 in new_qdrc_endpoint_t
> ../src/router_core/core_link_endpoint.c:35
> 27: #3 0x55f478309d28 in qdrc_endpoint_create_link_CT
> ../src/router_core/core_link_endpoint.c:74
> 27: #4 0x55f4783eed7d in on_conn_event
> ../src/router_core/modules/heartbeat_edge/heartbeat_edge.c:178
> 27: #5 0x55f47830823d in qdrc_event_conn_raise
> ../src/router_core/core_events.c:101
> 27: #6 0x55f4783c5a14 in on_conn_event
> ../src/router_core/modules/edge_router/connection_manager.c:59
> 27: #7 0x55f47830823d in qdrc_event_conn_raise
> ../src/router_core/core_events.c:101
> 27: #8 0x55f4782f5fdc in qdr_connection_opened_CT
> ../src/router_core/connections.c:1479
> 27: #9 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #10 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #11 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27:
> 27: Thread T1 created by T0 here:
> 27: #0 0x7f1069943805 in pthread_create
> (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)
> 27: #1 0x55f4782a2ad3 in sys_thread ../src/posix/threading.c:181
> 27: #2 0x55f47836b817 in qdr_core ../src/router_core/router_core.c:124
> 27: #3 0x55f478411c5c in qd_router_setup_late ../src/router_node.c:2127
> 27: #4 0x7f1064308ff4 (/lib/x86_64-linux-gnu/libffi.so.7+0x6ff4)
> 27: #5 0x7ffdaab8945f ([stack]+0x2145f)
> 27:
> 27: SUMMARY: AddressSanitizer: heap-use-after-free
> ../src/router_core/core_link_endpoint.c:136 in qdrc_endpoint_delivery_CT
> 27: Shadow bytes around the buggy address:
> 27: 0x0c227fffa680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 27: 0x0c227fffa690: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> 27: 0x0c227fffa6a0: fd fd fd fd fd fd fd fd fd fd fd
[jira] [Updated] (DISPATCH-2283) heap-use-after-free in system_tests_policy_oversize_compound during qdrc_endpoint_delivery_CT
[
https://issues.apache.org/jira/browse/DISPATCH-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-2283:
Fix Version/s: 1.18.0
> heap-use-after-free in system_tests_policy_oversize_compound during
> qdrc_endpoint_delivery_CT
> -
>
> Key: DISPATCH-2283
> URL: https://issues.apache.org/jira/browse/DISPATCH-2283
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.18.0
>Reporter: Jiri Daněk
>Priority: Major
> Fix For: 1.18.0
>
>
> https://github.com/jiridanek/qpid-dispatch/runs/4140877666?check_suite_focus=true#step:9:35786
> This comes from the "set memory pool max size to 0" memory poisoning
> investigation. I haven't seen this fail with unmodified main branch (yet ;)
> The only somewhat similar stacktrace I could find in Jira is for this leak
> DISPATCH-1699.
> {noformat}
> 27: ==12548==ERROR: AddressSanitizer: heap-use-after-free on address
> 0x611136e0 at pc 0x55f47830adb9 bp 0x7f1063183140 sp 0x7f1063183130
> 27: READ of size 8 at 0x611136e0 thread T1
> 27: #0 0x55f47830adb8 in qdrc_endpoint_delivery_CT
> ../src/router_core/core_link_endpoint.c:136
> 27: #1 0x55f4783eea3b in on_timer
> ../src/router_core/modules/heartbeat_edge/heartbeat_edge.c:157
> 27: #2 0x55f4783c0613 in qdr_process_tick_CT
> ../src/router_core/core_timer.c:123
> 27: #3 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #4 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #5 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27: #6 0x7f106864e292 in __clone
> (/lib/x86_64-linux-gnu/libc.so.6+0x122292)
> 27:
> 27: 0x611136e0 is located 160 bytes inside of 192-byte region
> [0x61113640,0x61113700)
> 27: freed by thread T1 here:
> 27: #0 0x7f1069a167cf in __interceptor_free
> (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)
> 27: #1 0x55f4781e3b84 in qd_dealloc ../src/alloc_pool.c:497
> 27: #2 0x55f478308e1d in free_qdrc_endpoint_t
> ../src/router_core/core_link_endpoint.c:35
> 27: #3 0x55f47830d34f in qdrc_endpoint_do_cleanup_CT
> ../src/router_core/core_link_endpoint.c:245
> 27: #4 0x55f47830cb0f in qdrc_endpoint_do_detach_CT
> ../src/router_core/core_link_endpoint.c:220
> 27: #5 0x55f478301824 in qdr_link_inbound_detach_CT
> ../src/router_core/connections.c:2033
> 27: #6 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #7 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #8 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27:
> 27: previously allocated by thread T1 here:
> 27: #0 0x7f1069a17aa5 in posix_memalign
> (/lib/x86_64-linux-gnu/libasan.so.5+0x10eaa5)
> 27: #1 0x55f4781df9cd in qd_alloc ../src/alloc_pool.c:393
> 27: #2 0x55f478308de5 in new_qdrc_endpoint_t
> ../src/router_core/core_link_endpoint.c:35
> 27: #3 0x55f478309d28 in qdrc_endpoint_create_link_CT
> ../src/router_core/core_link_endpoint.c:74
> 27: #4 0x55f4783eed7d in on_conn_event
> ../src/router_core/modules/heartbeat_edge/heartbeat_edge.c:178
> 27: #5 0x55f47830823d in qdrc_event_conn_raise
> ../src/router_core/core_events.c:101
> 27: #6 0x55f4783c5a14 in on_conn_event
> ../src/router_core/modules/edge_router/connection_manager.c:59
> 27: #7 0x55f47830823d in qdrc_event_conn_raise
> ../src/router_core/core_events.c:101
> 27: #8 0x55f4782f5fdc in qdr_connection_opened_CT
> ../src/router_core/connections.c:1479
> 27: #9 0x55f47838fec7 in router_core_thread
> ../src/router_core/router_core_thread.c:236
> 27: #10 0x55f4782a2964 in _thread_init ../src/posix/threading.c:172
> 27: #11 0x7f1069458608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> 27:
> 27: Thread T1 created by T0 here:
> 27: #0 0x7f1069943805 in pthread_create
> (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)
> 27: #1 0x55f4782a2ad3 in sys_thread ../src/posix/threading.c:181
> 27: #2 0x55f47836b817 in qdr_core ../src/router_core/router_core.c:124
> 27: #3 0x55f478411c5c in qd_router_setup_late ../src/router_node.c:2127
> 27: #4 0x7f1064308ff4 (/lib/x86_64-linux-gnu/libffi.so.7+0x6ff4)
> 27: #5 0x7ffdaab8945f ([stack]+0x2145f)
> 27:
> 27: SUMMARY: AddressSanitizer: heap-use-after-free
> ../src/router_core/core_link_endpoint.c:136 in qdrc_endpoint_delivery_CT
> 27: Shadow bytes around the buggy address:
> 27: 0x0c227fffa680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 27: 0x0c227fffa690: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> 27: 0x0c227fffa6a0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd
> 27:
[jira] [Updated] (DISPATCH-2094) System tests can freeze, observed especially on AArch64 or s390x
[
https://issues.apache.org/jira/browse/DISPATCH-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-2094:
Fix Version/s: 1.19.0
(was: 1.18.0)
> System tests can freeze, observed especially on AArch64 or s390x
>
>
> Key: DISPATCH-2094
> URL: https://issues.apache.org/jira/browse/DISPATCH-2094
> Project: Qpid Dispatch
> Issue Type: Test
>Affects Versions: 1.16.0
>Reporter: Jiri Daněk
>Priority: Minor
> Fix For: 1.19.0
>
>
> Sometimes the system tests freeze. This is especially frequent on AArch64. It
> is possible this is caused by architecture-specific behavior regarding
> threading. AMD64 is strongly memory consistent, while AArch64 is not. Maybe
> some undefined behavior on AArch64 causes the races to be more serious than
> elsewhere.
> https://travis-ci.com/github/apache/qpid-dispatch/jobs/502066462#L9193
> {noformat}
> 64: test_05_no_settlement_same_interior
> (system_tests_stuck_deliveries.RouterTest) ... ok
> {noformat}
> https://travis-ci.com/github/apache/qpid-dispatch/jobs/502066461#L7611
> {noformat}
> 70: test_01_concurrent_requests
> (system_tests_http1_adaptor.Http1AdaptorEdge2EdgeTest)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-2206) ASAN use-after-free of qdr_link_t by I/O thread
[
https://issues.apache.org/jira/browse/DISPATCH-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440530#comment-17440530
]
Ganesh Murthy commented on DISPATCH-2206:
-
[~jdanek] can you please get a backtrace of where the qdr_link_t object was
freed? Thanks
> ASAN use-after-free of qdr_link_t by I/O thread
> ---
>
> Key: DISPATCH-2206
> URL: https://issues.apache.org/jira/browse/DISPATCH-2206
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 1.16.1
>Reporter: Ken Giusti
>Priority: Major
> Labels: asan
> Fix For: 1.19.0
>
>
> [https://github.com/apache/qpid-dispatch/blob/main/src/router_core/connections.c#L1344]
>
> {{27: ==3859==ERROR: AddressSanitizer: use-after-poison on address
> 0x61700017e030 at pc 0x56212343cdac bp 0x7f9d33c40c90 sp 0x7f9d33c40c80 }}
> {{ }}{{}}
> 27: READ of size 8 at 0x61700017e030 thread T2
> {{}}{{}}{{}}{{}}{{}}{{}}{{}}{{}}{{}}{{}}{{}}{{}}{{ }}{{}}
> 27: #0 0x56212343cdab in qdr_link_get_context
> ../src/router_core/connections.c:498
> {{}}{{ }}{{}}
> 27: #1 0x56212352ec25 in CORE_link_second_attach ../src/router_node.c:1729
> {{}}{{ }}{{}}
> 27: #2 0x5621234388df in qdr_connection_process
> ../src/router_core/connections.c:355
> {{}}{{ }}{{}}
> 27: #3 0x56212338eccf in writable_handler ../src/container.c:396
> {{}}{{ }}{{}}
> 27: #4 0x56212338eccf in qd_container_handle_event ../src/container.c:748
> {{}}{{ }}{{}}
> 27: #5 0x562123547289 in handle ../src/server.c:1108
> {{}}{{ }}{{}}
> 27: #6 0x562123554c9f in thread_run ../src/server.c:1133
> {{}}{{ }}{{}}
> 27: #7 0x7f9d3ba6c608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> {{}}{{ }}{{}}
> 27: #8 0x7f9d3ac33292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)
> {{}}{{ }}{{}}
> 27:
> {{}}{{ }}{{}}
> 27: 0x61700017e030 is located 176 bytes inside of 704-byte region
> [0x61700017df80,0x61700017e240)
> {{}}{{ }}{{}}
> 27: allocated by thread T2 here:
> {{}}{{ }}{{}}
> 27: #0 0x7f9d3bfd9aa5 in posix_memalign
> (/lib/x86_64-linux-gnu/libasan.so.5+0x10eaa5)
> {{}}{{ }}{{}}
> 27: #1 0x5621233247b0 in qd_alloc ../src/alloc_pool.c:396
> {{}}{{ }}{{}}
> 27: #2 0x56212343d4c9 in qdr_link_first_attach
> ../src/router_core/connections.c:592
> {{}}{{ }}{{}}
> 27: #3 0x56212352dde9 in AMQP_outgoing_link_handler
> ../src/router_node.c:1018
> {{}}{{ }}{{}}
> 27: #4 0x562123547289 in handle ../src/server.c:1108
> {{}}{{ }}{{}}
> 27: #5 0x562123554c9f in thread_run ../src/server.c:1133
> {{}}{{ }}{{}}
> 27: #6 0x7f9d3ba6c608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> {{}}{{ }}{{}}
> 27:
> {{}}{{ }}{{}}
> 27: Thread T2 created by T0 here:
> {{}}{{ }}{{}}
> 27: #0 0x7f9d3bf05805 in pthread_create
> (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)
> {{}}{{ }}{{}}
> 27: #1 0x562123403bcf in sys_thread ../src/posix/threading.c:181
> {{}}{{ }}{{}}
> 27: #2 0x56212355541e in qd_server_run ../src/server.c:1522
> {{}}{{ }}{{}}
> 27: #3 0x56212359f46c in main_process ../router/src/main.c:115
> {{}}{{ }}{{}}
> 27: #4 0x56212329bc50 in main ../router/src/main.c:369
> {{}}{{ }}{{}}
> 27: #5 0x7f9d3ab380b2 in __libc_start_main
> (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)
> {{}}{{ }}{{}}
> 27:
> {{}}{{ }}{{}}
> 27: SUMMARY: AddressSanitizer: use-after-poison
> ../src/router_core/connections.c:498 in qdr_link_get_context
> {{}}{{ }}{{}}
> 27: Shadow bytes around the buggy address:
> {{}}{{ }}{{}}
> 27: 0x0c2e80027bb0: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027bc0: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027bd0: f7 f7 f7 f7 f7 f7 f7 00 fa fa fa fa fa fa fa fa
> {{}}{{ }}{{}}
> 27: 0x0c2e80027be0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> {{}}{{ }}{{}}
> 27: 0x0c2e80027bf0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> {{}}{{ }}{{}}
> 27: =>0x0c2e80027c00: 00 00 f7 f7 f7 f7[f7]f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027c10: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027c20: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027c30: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027c40: f7 f7 f7 f7 f7 f7 f7 00 fa fa fa fa fa fa fa fa
> {{}}{{ }}{{}}
> 27: 0x0c2e80027c50: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> {{}}{{ }}{{}}
> 27: Shadow byte legend (one shadow byte represents 8 application bytes):
> {{}}{{ }}{{}}
> 27: Addressable: 00
> {{}}{{ }}{{}}
> 27: Partially addressable: 01 02 03 04 05 06 07
> {{}}{{ }}{{}}
> 27: Heap left redzone: fa
> {{}}{{ }}{{}}
> 27: Freed heap region: fd
> {{}}{{ }}{{}}
> 27: Stack left redzone: f1
> {{}}{{
[jira] [Comment Edited] (DISPATCH-1786) system_tests_fallback_dest failing in test_31_switchover_local_interior_alt_remote_interior
[
https://issues.apache.org/jira/browse/DISPATCH-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440480#comment-17440480
]
Ganesh Murthy edited comment on DISPATCH-1786 at 11/8/21, 2:25 PM:
---
This test and other switchover tests have been commented out. [~kgiusti] is
working on a fix to uncomment those tests.
was (Author: ganeshmurthy):
This test and other switchover tests have been commented out. [~kgiusti] is
working on a fix to uncomment those t
> system_tests_fallback_dest failing in
> test_31_switchover_local_interior_alt_remote_interior
> ---
>
> Key: DISPATCH-1786
> URL: https://issues.apache.org/jira/browse/DISPATCH-1786
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Affects Versions: 1.14.0
>Reporter: Ganesh Murthy
>Assignee: Charles E. Rolke
>Priority: Major
> Fix For: 1.18.0
>
> Attachments: DISPATCH-1786-fallback-test-fail-analysis.txt
>
>
> {noformat}
> 63: Test command: /usr/bin/python "/foo/qpid-dispatch/build/tests/run.py"
> "-m" "unittest" "-v" "system_tests_fallback_dest"
> 63: Test timeout computed to be: 600
> 63: test_01_sender_first_primary_same_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_02_sender_first_fallback_same_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_03_sender_first_primary_same_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_04_sender_first_fallback_same_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_05_sender_first_primary_interior_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_06_sender_first_fallback_interior_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_07_sender_first_primary_edge_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_08_sender_first_fallback_edge_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_09_sender_first_primary_interior_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_10_sender_first_fallback_interior_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_11_sender_first_primary_edge_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_12_sender_first_fallback_edge_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_13_receiver_first_primary_same_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_14_receiver_first_fallback_same_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_15_receiver_first_primary_same_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_16_receiver_first_fallback_same_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_17_receiver_first_primary_interior_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_18_receiver_first_fallback_interior_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_19_receiver_first_primary_edge_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_20_receiver_first_fallback_edge_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_21_receiver_first_primary_interior_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_22_receiver_first_fallback_interior_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_23_receiver_first_primary_edge_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_24_receiver_first_fallback_edge_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_25_switchover_same_edge (system_tests_fallback_dest.RouterTest) ...
> ok
> 63: test_26_switchover_same_interior (system_tests_fallback_dest.RouterTest)
> ... ok
> 63: test_27_switchover_local_edge_alt_remote_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_28_switchover_local_edge_alt_remote_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_29_switchover_local_edge_pri_remote_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_30_switchover_local_interior_pri_remote_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_31_switchover_local_interior_alt_remote_interior
> (system_tests_fallback_dest.RouterTest) ... FAIL
> 63: test_32_switchover_local_interior_alt_remote_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_33_switchover_local_interior_pri_remote_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_34_switchover_local_interior_pri_remote_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_35_switchover_mix_1 (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_36_switchover_mix_2 (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_37_switchover_mix_3
[jira] [Commented] (DISPATCH-2206) ASAN use-after-free of qdr_link_t by I/O thread
[
https://issues.apache.org/jira/browse/DISPATCH-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17440500#comment-17440500
]
Ganesh Murthy commented on DISPATCH-2206:
-
DISPATCH-2274 is attempting to fix the use after free on qd_link_t object. This
one is use after free of the qdr_link_t object.
> ASAN use-after-free of qdr_link_t by I/O thread
> ---
>
> Key: DISPATCH-2206
> URL: https://issues.apache.org/jira/browse/DISPATCH-2206
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
>Affects Versions: 1.16.1
>Reporter: Ken Giusti
>Priority: Major
> Labels: asan
> Fix For: 1.19.0
>
>
> [https://github.com/apache/qpid-dispatch/blob/main/src/router_core/connections.c#L1344]
>
> {{27: ==3859==ERROR: AddressSanitizer: use-after-poison on address
> 0x61700017e030 at pc 0x56212343cdac bp 0x7f9d33c40c90 sp 0x7f9d33c40c80 }}
> {{ }}{{}}
> 27: READ of size 8 at 0x61700017e030 thread T2
> {{}}{{}}{{}}{{}}{{}}{{}}{{}}{{}}{{}}{{}}{{}}{{}}{{ }}{{}}
> 27: #0 0x56212343cdab in qdr_link_get_context
> ../src/router_core/connections.c:498
> {{}}{{ }}{{}}
> 27: #1 0x56212352ec25 in CORE_link_second_attach ../src/router_node.c:1729
> {{}}{{ }}{{}}
> 27: #2 0x5621234388df in qdr_connection_process
> ../src/router_core/connections.c:355
> {{}}{{ }}{{}}
> 27: #3 0x56212338eccf in writable_handler ../src/container.c:396
> {{}}{{ }}{{}}
> 27: #4 0x56212338eccf in qd_container_handle_event ../src/container.c:748
> {{}}{{ }}{{}}
> 27: #5 0x562123547289 in handle ../src/server.c:1108
> {{}}{{ }}{{}}
> 27: #6 0x562123554c9f in thread_run ../src/server.c:1133
> {{}}{{ }}{{}}
> 27: #7 0x7f9d3ba6c608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> {{}}{{ }}{{}}
> 27: #8 0x7f9d3ac33292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)
> {{}}{{ }}{{}}
> 27:
> {{}}{{ }}{{}}
> 27: 0x61700017e030 is located 176 bytes inside of 704-byte region
> [0x61700017df80,0x61700017e240)
> {{}}{{ }}{{}}
> 27: allocated by thread T2 here:
> {{}}{{ }}{{}}
> 27: #0 0x7f9d3bfd9aa5 in posix_memalign
> (/lib/x86_64-linux-gnu/libasan.so.5+0x10eaa5)
> {{}}{{ }}{{}}
> 27: #1 0x5621233247b0 in qd_alloc ../src/alloc_pool.c:396
> {{}}{{ }}{{}}
> 27: #2 0x56212343d4c9 in qdr_link_first_attach
> ../src/router_core/connections.c:592
> {{}}{{ }}{{}}
> 27: #3 0x56212352dde9 in AMQP_outgoing_link_handler
> ../src/router_node.c:1018
> {{}}{{ }}{{}}
> 27: #4 0x562123547289 in handle ../src/server.c:1108
> {{}}{{ }}{{}}
> 27: #5 0x562123554c9f in thread_run ../src/server.c:1133
> {{}}{{ }}{{}}
> 27: #6 0x7f9d3ba6c608 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x9608)
> {{}}{{ }}{{}}
> 27:
> {{}}{{ }}{{}}
> 27: Thread T2 created by T0 here:
> {{}}{{ }}{{}}
> 27: #0 0x7f9d3bf05805 in pthread_create
> (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)
> {{}}{{ }}{{}}
> 27: #1 0x562123403bcf in sys_thread ../src/posix/threading.c:181
> {{}}{{ }}{{}}
> 27: #2 0x56212355541e in qd_server_run ../src/server.c:1522
> {{}}{{ }}{{}}
> 27: #3 0x56212359f46c in main_process ../router/src/main.c:115
> {{}}{{ }}{{}}
> 27: #4 0x56212329bc50 in main ../router/src/main.c:369
> {{}}{{ }}{{}}
> 27: #5 0x7f9d3ab380b2 in __libc_start_main
> (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)
> {{}}{{ }}{{}}
> 27:
> {{}}{{ }}{{}}
> 27: SUMMARY: AddressSanitizer: use-after-poison
> ../src/router_core/connections.c:498 in qdr_link_get_context
> {{}}{{ }}{{}}
> 27: Shadow bytes around the buggy address:
> {{}}{{ }}{{}}
> 27: 0x0c2e80027bb0: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027bc0: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027bd0: f7 f7 f7 f7 f7 f7 f7 00 fa fa fa fa fa fa fa fa
> {{}}{{ }}{{}}
> 27: 0x0c2e80027be0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> {{}}{{ }}{{}}
> 27: 0x0c2e80027bf0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> {{}}{{ }}{{}}
> 27: =>0x0c2e80027c00: 00 00 f7 f7 f7 f7[f7]f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027c10: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027c20: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027c30: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> {{}}{{ }}{{}}
> 27: 0x0c2e80027c40: f7 f7 f7 f7 f7 f7 f7 00 fa fa fa fa fa fa fa fa
> {{}}{{ }}{{}}
> 27: 0x0c2e80027c50: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> {{}}{{ }}{{}}
> 27: Shadow byte legend (one shadow byte represents 8 application bytes):
> {{}}{{ }}{{}}
> 27: Addressable: 00
> {{}}{{ }}{{}}
> 27: Partially addressable: 01 02 03 04 05 06 07
> {{}}{{ }}{{}}
> 27: Heap left redzone: fa
> {{}}{{ }}{{}}
> 27: Freed heap region: fd
> {{}}{{ }}{{}}
> 27:
[jira] [Resolved] (DISPATCH-1786) system_tests_fallback_dest failing in test_31_switchover_local_interior_alt_remote_interior
[
https://issues.apache.org/jira/browse/DISPATCH-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1786.
-
Fix Version/s: 1.18.0
(was: 1.15.0)
Resolution: Fixed
This test and other switchover tests have been commented out. [~kgiusti] is
working on a fix to uncomment those t
> system_tests_fallback_dest failing in
> test_31_switchover_local_interior_alt_remote_interior
> ---
>
> Key: DISPATCH-1786
> URL: https://issues.apache.org/jira/browse/DISPATCH-1786
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Affects Versions: 1.14.0
>Reporter: Ganesh Murthy
>Assignee: Charles E. Rolke
>Priority: Major
> Fix For: 1.18.0
>
> Attachments: DISPATCH-1786-fallback-test-fail-analysis.txt
>
>
> {noformat}
> 63: Test command: /usr/bin/python "/foo/qpid-dispatch/build/tests/run.py"
> "-m" "unittest" "-v" "system_tests_fallback_dest"
> 63: Test timeout computed to be: 600
> 63: test_01_sender_first_primary_same_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_02_sender_first_fallback_same_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_03_sender_first_primary_same_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_04_sender_first_fallback_same_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_05_sender_first_primary_interior_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_06_sender_first_fallback_interior_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_07_sender_first_primary_edge_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_08_sender_first_fallback_edge_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_09_sender_first_primary_interior_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_10_sender_first_fallback_interior_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_11_sender_first_primary_edge_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_12_sender_first_fallback_edge_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_13_receiver_first_primary_same_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_14_receiver_first_fallback_same_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_15_receiver_first_primary_same_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_16_receiver_first_fallback_same_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_17_receiver_first_primary_interior_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_18_receiver_first_fallback_interior_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_19_receiver_first_primary_edge_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_20_receiver_first_fallback_edge_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_21_receiver_first_primary_interior_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_22_receiver_first_fallback_interior_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_23_receiver_first_primary_edge_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_24_receiver_first_fallback_edge_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_25_switchover_same_edge (system_tests_fallback_dest.RouterTest) ...
> ok
> 63: test_26_switchover_same_interior (system_tests_fallback_dest.RouterTest)
> ... ok
> 63: test_27_switchover_local_edge_alt_remote_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_28_switchover_local_edge_alt_remote_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_29_switchover_local_edge_pri_remote_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_30_switchover_local_interior_pri_remote_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_31_switchover_local_interior_alt_remote_interior
> (system_tests_fallback_dest.RouterTest) ... FAIL
> 63: test_32_switchover_local_interior_alt_remote_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_33_switchover_local_interior_pri_remote_interior
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_34_switchover_local_interior_pri_remote_edge
> (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_35_switchover_mix_1 (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_36_switchover_mix_2 (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_37_switchover_mix_3 (system_tests_fallback_dest.RouterTest) ... ok
> 63: test_38_switchover_mix_4 (system_tests_fallback_dest.RouterTest) ... ok
> 63:
[jira] [Resolved] (DISPATCH-2274) system_tests_router_mesh: ERROR: AddressSanitizer: use-after-poison in qd_link_pn container.c:1029
[
https://issues.apache.org/jira/browse/DISPATCH-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-2274.
-
Assignee: Ganesh Murthy (was: Ken Giusti)
Resolution: Fixed
> system_tests_router_mesh: ERROR: AddressSanitizer: use-after-poison in
> qd_link_pn container.c:1029
> --
>
> Key: DISPATCH-2274
> URL: https://issues.apache.org/jira/browse/DISPATCH-2274
> Project: Qpid Dispatch
> Issue Type: Bug
>Affects Versions: 1.18.0
> Environment: Aarch64 Linux, amd64 macOS
>Reporter: Jiri Daněk
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.18.0
>
>
> https://app.travis-ci.com/github/apache/qpid-dispatch/jobs/545969177
> {noformat}
> 66: Create 10 senders each with a different priority. ... ERROR
> 66: ERROR
> 66:
> 66: Router RouterC output file:
> 66:
> 66: =
> 66: ==21601==ERROR: AddressSanitizer: use-after-poison on address
> 0x6137d828 at pc 0x0001064a6469 bp 0x7843bca0 sp 0x7843bc98
> 66: READ of size 8 at 0x6137d828 thread T4
> 66: #0 0x1064a6468 in qd_link_pn container.c:1029
> 66: #1 0x1066d0e37 in CORE_link_push router_node.c:1920
> 66: #2 0x106576df6 in qdr_connection_process connections.c:414
> 66: #3 0x1064956ce in writable_handler container.c:396
> 66: #4 0x1066edb36 in thread_run server.c:1149
> 66: #5 0x7fff5fa152ea in _pthread_body
> (libsystem_pthread.dylib:x86_64+0x32ea)
> 66: #6 0x7fff5fa18248 in _pthread_start
> (libsystem_pthread.dylib:x86_64+0x6248)
> 66: #7 0x7fff5fa1440c in thread_start
> (libsystem_pthread.dylib:x86_64+0x240c)
> 66:
> 66: 0x6137d828 is located 168 bytes inside of 320-byte region
> [0x6137d780,0x6137d8c0)
> 66: allocated by thread T4 here:
> 66: #0 0x106f823a7 in wrap_posix_memalign
> (libclang_rt.asan_osx_dynamic.dylib:x86_64+0x5f3a7)
> 66: #1 0x1064555df in qd_alloc alloc_pool.c:396
> 66: #2 0x10649691a in qd_container_handle_event container.c:75
> 66: #3 0x1066f4366 in handle server.c:1108
> 66: #4 0x1066eda23 in thread_run server.c:1133
> 66: #5 0x7fff5fa152ea in _pthread_body
> (libsystem_pthread.dylib:x86_64+0x32ea)
> 66: #6 0x7fff5fa18248 in _pthread_start
> (libsystem_pthread.dylib:x86_64+0x6248)
> 66: #7 0x7fff5fa1440c in thread_start
> (libsystem_pthread.dylib:x86_64+0x240c)
> 66:
> 66: Thread T4 created by T0 here:
> 66: #0 0x106f79add in wrap_pthread_create
> (libclang_rt.asan_osx_dynamic.dylib:x86_64+0x56add)
> 66: #1 0x106535a6d in sys_thread threading.c:181
> 66: #2 0x1066ed1af in qd_server_run server.c:1525
> 66: #3 0x1063b081e in main_process main.c:115
> 66: #4 0x1063af12b in main main.c:369
> 66: #5 0x7fff5f8213d4 in start (libdyld.dylib:x86_64+0x163d4)
> 66:
> 66: SUMMARY: AddressSanitizer: use-after-poison container.c:1029 in qd_link_pn
> 66: Shadow bytes around the buggy address:
> 66: 0x1c26fab0: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00
> 66: 0x1c26fac0: 00 00 00 00 00 00 00 00 00 00 f7 f7 f7 f7 f7 f7
> 66: 0x1c26fad0: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 00 00 00 00
> 66: 0x1c26fae0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> 66: 0x1c26faf0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 66: =>0x1c26fb00: 00 00 f7 f7 f7[f7]f7 f7 f7 f7 f7 f7 f7 f7 f7 f7
> 66: 0x1c26fb10: f7 f7 f7 f7 00 00 00 00 fa fa fa fa fa fa fa fa
> 66: 0x1c26fb20: fa fa fa fa fa fa fa fa 00 00 00 00 00 00 00 00
> 66: 0x1c26fb30: 00 00 00 00 00 00 00 00 00 00 f7 f7 f7 f7 f7 f7
> 66: 0x1c26fb40: f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 f7 00 00 00 00
> 66: 0x1c26fb50: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> 66: Shadow byte legend (one shadow byte represents 8 application bytes):
> 66: Addressable: 00
> 66: Partially addressable: 01 02 03 04 05 06 07
> 66: Heap left redzone: fa
> 66: Freed heap region: fd
> 66: Stack left redzone: f1
> 66: Stack mid redzone: f2
> 66: Stack right redzone: f3
> 66: Stack after return: f5
> 66: Stack use after scope: f8
> 66: Global redzone: f9
> 66: Global init order: f6
> 66: Poisoned by user:f7
> 66: Container overflow: fc
> 66: Array cookie:ac
> 66: Intra object redzone:bb
> 66: ASan internal: fe
> 66: Left alloca redzone: ca
> 66: Right alloca redzone:cb
> 66: Shadow gap: cc
> 66: ==21601==ABORTING
> {noformat}
> essentially the same stacktrace in the same job
> {noformat}
> 27: ERROR
> 27: test_90_block_link_route_EB1_INTB
>
[jira] [Created] (DISPATCH-2275) Dispatch test failures with the latest from proton main branch
Ganesh Murthy created DISPATCH-2275:
---
Summary: Dispatch test failures with the latest from proton main
branch
Key: DISPATCH-2275
URL: https://issues.apache.org/jira/browse/DISPATCH-2275
Project: Qpid Dispatch
Issue Type: Test
Components: Tests
Affects Versions: 1.17.1
Reporter: Ganesh Murthy
Assignee: Ken Giusti
There are 3 test errors
{noformat}
47: Error text: Process 2801860 error: exit code 1, expected 0
47: /usr/bin/python3.9
/home/gmurthy/opensource/qpid-dispatch/build/tests/scraper/scraper.py -f
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/A.log
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/B.log
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/C.log
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/D.log
47:
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/test_04_scraper_tool/python3.9-1.cmd
47:
47:
47: FAIL
75: 2021-11-05 10:49:25.394391 TCP_TEST test_01_tcp_EB1_EA1 Client
test_01_tcp_EB1_EA1_0_1_1 exited normally
75: 2021-11-05 10:49:25.394507 TCP_TEST test_01_tcp_EB1_EA1 SUCCESS
75: 2021-11-05 10:49:25.394626 TCP_TEST test_01_tcp_basic_connectivity Stop
test_01_tcp_EB1_EA1 SUCCESS
75: 2021-11-05 10:49:25.394673 TCP_TEST test_01_tcp_basic_connectivity Start
test_01_tcp_EB1_EA2
75: 2021-11-05 10:49:25.394726 TCP_TEST test_01_tcp_EB1_EA2 Start
do_tcp_echo_n_routers
75: 2021-11-05 10:49:25.394774 TCP_TEST test_01_tcp_EB1_EA2 Running pair 0
EB1->EA2 size=1 count=1
47:
47: ==
47: FAIL: test_04_scraper_tool
(system_tests_topology_disposition.TopologyDispositionTests)
47: --
47: Traceback (most recent call last):
47: File
"/home/gmurthy/opensource/qpid-dispatch/tests/system_tests_topology_disposition.py",
line 432, in test_04_scraper_tool
47: self.assertEqual(str(None), error)
47: AssertionError: 'None' != 'Process 2801860 error: exit code 1, expec[842
chars]'
47: - None
47: + Process 2801860 error: exit code 1, expected 0
47: /usr/bin/python3.9
/home/gmurthy/opensource/qpid-dispatch/build/tests/scraper/scraper.py -f
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/A.log
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/B.log
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/C.log
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/setUpClass/D.log
47:
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_topology_disposition/TopologyDispositionTests/test_04_scraper_tool/python3.9-1.cmd
47:
47: {noformat}
{noformat}
29: test_max_sessions_zero (system_tests_protocol_settings.MaxSessionsZeroTest)
... FAIL
29:
29: ==
29: FAIL: test_connector_default
(system_tests_protocol_settings.ConnectorSettingsDefaultTest)
29: --
29: Traceback (most recent call last):
29: File
"/home/gmurthy/opensource/qpid-dispatch/tests/system_tests_protocol_settings.py",
line 322, in test_connector_default
29: self.assertIn(' max-frame-size=16384,', open_lines[0])
29: AssertionError: ' max-frame-size=16384,' not found in '2021-11-05
10:50:24.161355 -0400 PROTOCOL (trace) [C3]:FRAME: 0 <- @open(16)
[container-id="QDR.B", hostname="127.0.0.1", max-frame-size=0x4000,
channel-max=0x7fff, idle-time-out=0xea60, outgoing-locales=null,
incoming-locales=null, offered-capabilities=@[:ANONYMOUS-RELAY,
:"qd.streaming-links"], desired-capabilities=@[:ANONYMOUS-RELAY,
:"qd.streaming-links"], properties={:product="qpid-dispatch-router",
:version="1.19.0-SNAPSHOT", :"qd.conn-id"=1}]
(/home/gmurthy/opensource/qpid-dispatch/src/server.c:111)'
29:
29: ==
29: FAIL: test_connector_default
(system_tests_protocol_settings.ConnectorSettingsNondefaultTest)
29: --
29: Traceback (most recent call last):
29: File
[jira] [Updated] (DISPATCH-2256) edge router fallback links and addresses incorrect on interior failover
[ https://issues.apache.org/jira/browse/DISPATCH-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2256: Fix Version/s: (was: 1.18.0) 1.19.0 > edge router fallback links and addresses incorrect on interior failover > --- > > Key: DISPATCH-2256 > URL: https://issues.apache.org/jira/browse/DISPATCH-2256 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.17.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.19.0 > > > Scenario: > Configure an edge router with two separate interior connectors - one for > router A and a standby for router B. > Configure a route-container listener for a broker on the edge router. Assign > two fallback destination autolinks (1 in, 1 out) to the route container for > address "foo". > Start just the edge router: > * no links are active (expected). > * mgmt query for addresses show two "foo" addresses present: > ** MFfoo - the fallback address (no subscribers) > ** M0foo - the primary address (no subscribers) > Now startup the broker and after the connection to the broker: > * On the edge router: > ** links: > *** id 5, out link to broker, owning address MFfoo > *** id 6, in link from broker, owning address M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > Now start router A. Router A has been configured with an edge listener > connection. There is no inter-router connection configured for router B! > Once the connection is established: > * On the edge router: > ** links: > *** the two broker links (see above) > *** id 10, in link from router A, owning address MFfoo > *** id 11, out link to router A for M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > * On Router A: > ** links: > *** id 6, out link to edge, owning address MFfoo > *** id 7, in link from edge, owning address M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > Now start router B, wait for the edge to establish a connection to it. Since > B is a standby interior for the edge there are no 'foo' related links or > addresses on B as expected. Remember router A and B are not directly > connected. > > Fail router A. Wait for the edge to re-establish its proxy links to router > B. The following links/addresses related to foo are now: > * On the edge router: > ** links: > *** the two broker links > *** id 20, in link from router B, owning address MFfoo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > * On Router B: > ** links: > *** id 6, out link to edge, owning address MFfoo > ** addresses: > *** MFfoo - one local subscriber > From the above we can see that after the failover to router B the edge router > does not re-establish an outgoing link (subscription) for M0foo as it did > when connected to router A. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2256) edge router fallback links and addresses incorrect on interior failover
[ https://issues.apache.org/jira/browse/DISPATCH-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2256: Fix Version/s: (was: 1.19.0) 1.18.0 > edge router fallback links and addresses incorrect on interior failover > --- > > Key: DISPATCH-2256 > URL: https://issues.apache.org/jira/browse/DISPATCH-2256 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.17.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.18.0 > > > Scenario: > Configure an edge router with two separate interior connectors - one for > router A and a standby for router B. > Configure a route-container listener for a broker on the edge router. Assign > two fallback destination autolinks (1 in, 1 out) to the route container for > address "foo". > Start just the edge router: > * no links are active (expected). > * mgmt query for addresses show two "foo" addresses present: > ** MFfoo - the fallback address (no subscribers) > ** M0foo - the primary address (no subscribers) > Now startup the broker and after the connection to the broker: > * On the edge router: > ** links: > *** id 5, out link to broker, owning address MFfoo > *** id 6, in link from broker, owning address M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > Now start router A. Router A has been configured with an edge listener > connection. There is no inter-router connection configured for router B! > Once the connection is established: > * On the edge router: > ** links: > *** the two broker links (see above) > *** id 10, in link from router A, owning address MFfoo > *** id 11, out link to router A for M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > * On Router A: > ** links: > *** id 6, out link to edge, owning address MFfoo > *** id 7, in link from edge, owning address M0foo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > Now start router B, wait for the edge to establish a connection to it. Since > B is a standby interior for the edge there are no 'foo' related links or > addresses on B as expected. Remember router A and B are not directly > connected. > > Fail router A. Wait for the edge to re-establish its proxy links to router > B. The following links/addresses related to foo are now: > * On the edge router: > ** links: > *** the two broker links > *** id 20, in link from router B, owning address MFfoo > ** addresses: > *** MFfoo - one local subscriber > *** M0foo - no subscribers > * On Router B: > ** links: > *** id 6, out link to edge, owning address MFfoo > ** addresses: > *** MFfoo - one local subscriber > From the above we can see that after the failover to router B the edge router > does not re-establish an outgoing link (subscription) for M0foo as it did > when connected to router A. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (DISPATCH-1931) HTTP client not seeing a reply when sending a request through the TCP adaptor
[
https://issues.apache.org/jira/browse/DISPATCH-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reopened DISPATCH-1931:
-
> HTTP client not seeing a reply when sending a request through the TCP adaptor
> -
>
> Key: DISPATCH-1931
> URL: https://issues.apache.org/jira/browse/DISPATCH-1931
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Protocol Adaptors
>Reporter: Fernando Giorgetti
>Assignee: Michael Goulish
>Priority: Major
> Fix For: 1.18.0
>
> Attachments: private-router.log, public-router.log, routerLinks.out,
> successful-client-sample.log, tcpConnectors.out, tcpListeners.out
>
>
> In a two router topology (using Skupper on Kubernetes), an HTTP client (curl)
> was not
> seeing any response from the routers for requests going through a TCP
> adaptor.
> The request was reaching the router that has the TCP connector to the HTTP
> Server,
> but the request was not reaching the HTTP server and the HTTP client is
> being disconnected
> with no reply from the router.
> I have also executed the HTTP client (curl) from inside the router container,
> to avoid issues
> with the Kubernetes service and observed the same outcome.
> The TCP Listener that was causing issues was: nginx-2-svc-exp-notarget port
> 1026 (from router named private-annotated-1-skupper-router-746455769d-jcmmh).
>
> {noformat}
> [root@skupper-service-controller-78747bf9b6-xwclq app]# curl --trace
> /tmp/curl.error nginx-2-svc-exp-notarget:8080
> curl: (52) Empty reply from server
> [root@skupper-service-controller-78747bf9b6-xwclq app]# cat /tmp/curl.error
> == Info: Rebuilt URL to: nginx-2-svc-exp-notarget:8080/
> == Info: Trying 10.111.1.35...
> == Info: TCP_NODELAY set
> == Info: Connected to nginx-2-svc-exp-notarget (10.111.1.35) port 8080 (#0)
> => Send header, 93 bytes (0x5d)
> : 47 45 54 20 2f 20 48 54 54 50 2f 31 2e 31 0d 0a GET / HTTP/1.1..
> 0010: 48 6f 73 74 3a 20 6e 67 69 6e 78 2d 32 2d 73 76 Host: nginx-2-sv
> 0020: 63 2d 65 78 70 2d 6e 6f 74 61 72 67 65 74 3a 38 c-exp-notarget:8
> 0030: 30 38 30 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a 080..User-Agent:
> 0040: 20 63 75 72 6c 2f 37 2e 36 31 2e 31 0d 0a 41 63 curl/7.61.1..Ac
> 0050: 63 65 70 74 3a 20 2a 2f 2a 0d 0a 0d 0a cept: */*
> == Info: Empty reply from server
> == Info: Connection #0 to host nginx-2-svc-exp-notarget left intact{noformat}
>
> Or when executed directly from the router pod:
> {noformat}
> [root@skupper-router-746455769d-jcmmh bin]# curl --trace - 0.0.0.0:1026
> == Info: Trying 0.0.0.0:1026...
> == Info: TCP_NODELAY set
> == Info: Connected to 0.0.0.0 (127.0.0.1) port 1026 (#0)
> => Send header, 76 bytes (0x4c)
> : 47 45 54 20 2f 20 48 54 54 50 2f 31 2e 31 0d 0a GET / HTTP/1.1..
> 0010: 48 6f 73 74 3a 20 30 2e 30 2e 30 2e 30 3a 31 30 Host: 0.0.0.0:10
> 0020: 32 36 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a 20 26..User-Agent:
> 0030: 63 75 72 6c 2f 37 2e 36 35 2e 33 0d 0a 41 63 63 curl/7.65.3..Acc
> 0040: 65 70 74 3a 20 2a 2f 2a 0d 0a 0d 0a ept: */*
> == Info: Recv failure: Connection reset by peer
> == Info: Closing connection 0
> curl: (56) Recv failure: Connection reset by peer{noformat}
> I am attaching some other logs from both routers to help with the
> investigation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1931) HTTP client not seeing a reply when sending a request through the TCP adaptor
[
https://issues.apache.org/jira/browse/DISPATCH-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1931.
-
Resolution: Cannot Reproduce
> HTTP client not seeing a reply when sending a request through the TCP adaptor
> -
>
> Key: DISPATCH-1931
> URL: https://issues.apache.org/jira/browse/DISPATCH-1931
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Protocol Adaptors
>Reporter: Fernando Giorgetti
>Assignee: Michael Goulish
>Priority: Major
> Fix For: 1.18.0
>
> Attachments: private-router.log, public-router.log, routerLinks.out,
> successful-client-sample.log, tcpConnectors.out, tcpListeners.out
>
>
> In a two router topology (using Skupper on Kubernetes), an HTTP client (curl)
> was not
> seeing any response from the routers for requests going through a TCP
> adaptor.
> The request was reaching the router that has the TCP connector to the HTTP
> Server,
> but the request was not reaching the HTTP server and the HTTP client is
> being disconnected
> with no reply from the router.
> I have also executed the HTTP client (curl) from inside the router container,
> to avoid issues
> with the Kubernetes service and observed the same outcome.
> The TCP Listener that was causing issues was: nginx-2-svc-exp-notarget port
> 1026 (from router named private-annotated-1-skupper-router-746455769d-jcmmh).
>
> {noformat}
> [root@skupper-service-controller-78747bf9b6-xwclq app]# curl --trace
> /tmp/curl.error nginx-2-svc-exp-notarget:8080
> curl: (52) Empty reply from server
> [root@skupper-service-controller-78747bf9b6-xwclq app]# cat /tmp/curl.error
> == Info: Rebuilt URL to: nginx-2-svc-exp-notarget:8080/
> == Info: Trying 10.111.1.35...
> == Info: TCP_NODELAY set
> == Info: Connected to nginx-2-svc-exp-notarget (10.111.1.35) port 8080 (#0)
> => Send header, 93 bytes (0x5d)
> : 47 45 54 20 2f 20 48 54 54 50 2f 31 2e 31 0d 0a GET / HTTP/1.1..
> 0010: 48 6f 73 74 3a 20 6e 67 69 6e 78 2d 32 2d 73 76 Host: nginx-2-sv
> 0020: 63 2d 65 78 70 2d 6e 6f 74 61 72 67 65 74 3a 38 c-exp-notarget:8
> 0030: 30 38 30 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a 080..User-Agent:
> 0040: 20 63 75 72 6c 2f 37 2e 36 31 2e 31 0d 0a 41 63 curl/7.61.1..Ac
> 0050: 63 65 70 74 3a 20 2a 2f 2a 0d 0a 0d 0a cept: */*
> == Info: Empty reply from server
> == Info: Connection #0 to host nginx-2-svc-exp-notarget left intact{noformat}
>
> Or when executed directly from the router pod:
> {noformat}
> [root@skupper-router-746455769d-jcmmh bin]# curl --trace - 0.0.0.0:1026
> == Info: Trying 0.0.0.0:1026...
> == Info: TCP_NODELAY set
> == Info: Connected to 0.0.0.0 (127.0.0.1) port 1026 (#0)
> => Send header, 76 bytes (0x4c)
> : 47 45 54 20 2f 20 48 54 54 50 2f 31 2e 31 0d 0a GET / HTTP/1.1..
> 0010: 48 6f 73 74 3a 20 30 2e 30 2e 30 2e 30 3a 31 30 Host: 0.0.0.0:10
> 0020: 32 36 0d 0a 55 73 65 72 2d 41 67 65 6e 74 3a 20 26..User-Agent:
> 0030: 63 75 72 6c 2f 37 2e 36 35 2e 33 0d 0a 41 63 63 curl/7.65.3..Acc
> 0040: 65 70 74 3a 20 2a 2f 2a 0d 0a 0d 0a ept: */*
> == Info: Recv failure: Connection reset by peer
> == Info: Closing connection 0
> curl: (56) Recv failure: Connection reset by peer{noformat}
> I am attaching some other logs from both routers to help with the
> investigation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`
[
https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1958.
-
Resolution: Fixed
> Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`
>
>
> Key: DISPATCH-1958
> URL: https://issues.apache.org/jira/browse/DISPATCH-1958
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tools
>Affects Versions: 1.15.0
>Reporter: Jiri Daněk
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.18.0
>
>
> From the README
> {noformat}
> -DQD_MEMORY_STATS=
> --
> Dispatch will track memory pool usage statistics if this is enabled.
> {noformat}
> So the statistics may not be always available, depending on the way
> Dispatch is compiled.
> Allocator metrics get reported as 0. I see that {{qdmanage}} works just fine,
> but {{qdstat}} is throwing an error in such case:
> {noformat}
> $ qdstat -m
> 2021-02-04 15:08:19.288818 UTC
> Standalone_v++jCPCjYiQcGo3
> TypeError: unsupported operand type(s) for *: 'int32' and 'NoneType'
> {noformat}
> Found during PR review by [~fgiorget].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-2144) Fatal Python error: _PyMem_DebugMalloc: Python memory allocator called without holding the GIL
[
https://issues.apache.org/jira/browse/DISPATCH-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-2144:
Fix Version/s: (was: 1.18.0)
1.19.0
> Fatal Python error: _PyMem_DebugMalloc: Python memory allocator called
> without holding the GIL
> --
>
> Key: DISPATCH-2144
> URL: https://issues.apache.org/jira/browse/DISPATCH-2144
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Policy Engine
>Affects Versions: 1.16.0
>Reporter: Jiri Daněk
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.19.0
>
>
> To reproduce, install python3-debug on Fedora, then use it to build and run
> Dispatch
> https://github.com/jiridanek/qpid-dispatch/runs/2629007367?check_suite_focus=true#step:25:7044
> {noformat}
> 25: Router QDR.Policy output file:
> 25:
> 25:
> /home/runner/work/qpid-dispatch/qpid-dispatch/qpid-dispatch/python/qpid_dispatch_internal/policy/policy_util.py:65:
> ResourceWarning: unclosed family=AddressFamily.AF_INET6, type=SocketKind.SOCK_STREAM, proto=0,
> laddr=('::', 0, 0, 0)>
> 25: if is_ipv6_enabled():
> 25: ResourceWarning: Enable tracemalloc to get the object allocation traceback
> 25: Fatal Python error: _PyMem_DebugMalloc: Python memory allocator called
> without holding the GIL
> 25: Python runtime state: initialized
> 25:
> 25: Thread 0x7f0e8fffcec0 (most recent call first):
> 25:
> {noformat}
> Unrelated error in the same log that I noticed at random
> {noformat}
> 23: E /builddir/build/BUILD/Python-3.9.5/Modules/gcmodule.c:114:
> gc_decref: Assertion "gc_get_refs(g) > 0" failed: refcount is too small
> 23: E Enable tracemalloc to get the memory block allocation
> traceback
> 23: E
> 23: E object address : 0x7fd3e1b90cd0
> 23: E object refcount : 117
> 23: E object type : 0x7b695c30
> 23: E object type name: Agent
> 23: E object repr :
>
> 23: E
> 23: E Fatal Python error: _PyObject_AssertFailed:
> _PyObject_AssertFailed
> 23: E Python runtime state: initialized
> 23: E
> 23: E Current thread 0x7fd3e39e3ec0 (most recent call first):
> 23: E
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
