[jira] [Created] (DISPATCH-1733) system_tests_open_properties failure due to qdr_connection_t leak
Ganesh Murthy created DISPATCH-1733:
---
Summary: system_tests_open_properties failure due to
qdr_connection_t leak
Key: DISPATCH-1733
URL: https://issues.apache.org/jira/browse/DISPATCH-1733
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Reporter: Ganesh Murthy
{noformat}
67: ==
67: ERROR: test_01_verify_listener_properties
(system_tests_open_properties.OpenPropertiesConfigTest)
67: --
67: Traceback (most recent call last):
67: File
"/home/travis/build/apache/qpid-dispatch/tests/system_tests_open_properties.py",
line 197, in test_01_verify_listener_properties
67: self._valid_properties_check(OpenPropertiesClient)
67: File
"/home/travis/build/apache/qpid-dispatch/tests/system_tests_open_properties.py",
line 194, in _valid_properties_check
67: router.teardown()
67: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py", line
538, in teardown
67: raise teardown_exc
67: RuntimeError: Process 14125 error: exit code -6, expected 0
67: qdrouterd -c Router2.conf -I /home/travis/build/apache/qpid-dispatch/python
67:
/home/travis/build/apache/qpid-dispatch/build/tests/system_test.dir/system_tests_open_properties/OpenPropertiesConfigTest/test_01_verify_listener_properties/Router2-15.cmd
67:
67: ERROR: Aborted due to unexpected alloc pool leak of type 'qdr_connection_t'
67: {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
[jira] [Assigned] (DISPATCH-1722) system_tests_qdstat fails when checking for presence Worker Threads
[
https://issues.apache.org/jira/browse/DISPATCH-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1722:
---
Assignee: Ganesh Murthy
> system_tests_qdstat fails when checking for presence Worker Threads
> ---
>
> Key: DISPATCH-1722
> URL: https://issues.apache.org/jira/browse/DISPATCH-1722
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> 30: ==
> 30: FAIL: test_general (system_tests_qdstat.QdstatTest)
> 30: --
> 30: Traceback (most recent call last):
> 30: File
> "/home/travis/build/apache/qpid-dispatch/tests/system_tests_qdstat.py", line
> 73, in test_general
> 30: self.assertTrue("Worker Threads 1" in out)
> 30: AssertionError: False is not true {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
[jira] [Resolved] (DISPATCH-1722) system_tests_qdstat fails when checking for presence Worker Threads
[
https://issues.apache.org/jira/browse/DISPATCH-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1722.
-
Fix Version/s: 1.13.0
Resolution: Fixed
> system_tests_qdstat fails when checking for presence Worker Threads
> ---
>
> Key: DISPATCH-1722
> URL: https://issues.apache.org/jira/browse/DISPATCH-1722
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> 30: ==
> 30: FAIL: test_general (system_tests_qdstat.QdstatTest)
> 30: --
> 30: Traceback (most recent call last):
> 30: File
> "/home/travis/build/apache/qpid-dispatch/tests/system_tests_qdstat.py", line
> 73, in test_general
> 30: self.assertTrue("Worker Threads 1" in out)
> 30: AssertionError: False is not true {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
[jira] [Updated] (DISPATCH-1719) Add note about vhost
[ https://issues.apache.org/jira/browse/DISPATCH-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1719: Fix Version/s: 1.13.0 > Add note about vhost > > > Key: DISPATCH-1719 > URL: https://issues.apache.org/jira/browse/DISPATCH-1719 > Project: Qpid Dispatch > Issue Type: Task > Components: Documentation >Reporter: Paul Wright >Assignee: Paul Wright >Priority: Major > Fix For: 1.13.0 > > > PR at [https://github.com/apache/qpid-dispatch/pull/764/files] -- 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] [Created] (DISPATCH-1722) system_tests_qdstat fails when checking for presence Worker Threads
Ganesh Murthy created DISPATCH-1722:
---
Summary: system_tests_qdstat fails when checking for presence
Worker Threads
Key: DISPATCH-1722
URL: https://issues.apache.org/jira/browse/DISPATCH-1722
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
30: ==
30: FAIL: test_general (system_tests_qdstat.QdstatTest)
30: --
30: Traceback (most recent call last):
30: File
"/home/travis/build/apache/qpid-dispatch/tests/system_tests_qdstat.py", line
73, in test_general
30: self.assertTrue("Worker Threads 1" in out)
30: AssertionError: False is not true {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
[jira] [Resolved] (DISPATCH-1686) system_tests_policy_oversize_compound fails with new ASAN leak
[
https://issues.apache.org/jira/browse/DISPATCH-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1686.
-
Resolution: Cannot Reproduce
> system_tests_policy_oversize_compound fails with new ASAN leak
> --
>
> Key: DISPATCH-1686
> URL: https://issues.apache.org/jira/browse/DISPATCH-1686
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Priority: Major
>
> {noformat}
> 26: ==
> 26: ERROR: tearDownClass
> (system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize)
> 26: --
> 26: Traceback (most recent call last):
> 26: File
> "/home/travis/build/ganeshmurthy/qpid-dispatch/tests/system_test.py", line
> 723, in tearDownClass
> 26: cls.tester.teardown()
> 26: File
> "/home/travis/build/ganeshmurthy/qpid-dispatch/tests/system_test.py", line
> 669, in teardown
> 26: raise RuntimeError("Errors during teardown: \n\n%s" %
> "\n\n".join([str(e) for e in errors]))
> 26: RuntimeError: Errors during teardown:
> 26:
> 26: Process 12895 error: exit code 23, expected 0
> 26: qdrouterd -c INT.B.conf -I
> /home/travis/build/ganeshmurthy/qpid-dispatch/python
> 26:
> /home/travis/build/ganeshmurthy/qpid-dispatch/build/tests/system_test.dir/system_tests_policy_oversize_compound/MaxMessageSizeBlockOversize/setUpClass/INT.B-2.cmd
> 26:
> 26:
> 26: =
> 26: ==12895==ERROR: LeakSanitizer: detected memory leaks
> 26:
> 26: Indirect leak of 64 byte(s) in 1 object(s) allocated from:
> 26: #0 0x7fc2f1e2f076 in __interceptor_posix_memalign
> (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x99076)
> 26: #1 0x7fc2f1703128 in qd_alloc
> /home/travis/build/ganeshmurthy/qpid-dispatch/src/alloc_pool.c:347
> 26: #2 0x7fc2f17fe877 in qdr_forward_deliver_CT
> /home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/forwarder.c:276
> 26: #3 0x7fc2f17db699 in qdrc_event_link_raise
> /home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/core_events.c:113
> 26: #4 0x7fc2f185fb7c in qcm_addr_lookup_CT
> /home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/modules/address_lookup_client/lookup_client.c:570
> 26: #5 0x7fc2f17ce7d9 in qdr_link_inbound_first_attach_CT
> /home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/connections.c:1671
> 26: #6 0x7fc2f1826b6b in router_core_thread
> /home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/router_core_thread.c:193
> 26: #7 0x7fc2f128c6b9 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9)
> 26: -
> 26: Suppressions used:
> 26: count bytes template
> 26: 1 64 qd_message_receive
> 26: 2384 qdr_connection_opened
> 26: 13 4368 qdr_core_subscribe
> 26: 1192 qdr_forward_closest_CT
> 26: 2 1472 qdr_link_deliver
> 26: 1 64 qdr_node_connect_deliveries
> 26: 1192 qd_container_register_node_type
> 26: 28 70 __strdup
> 26: 1128 qd_parse_internal
> 26:46433425516 *libpython*
> 26: 37120 *python2*
> 26: -
> 26:
> 26: SUMMARY: AddressSanitizer: 64 byte(s) leaked in 1 allocation(s).
> {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
[jira] [Resolved] (DISPATCH-1663) system_tests_edge_router fails with ASAN leak
[
https://issues.apache.org/jira/browse/DISPATCH-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1663.
-
Fix Version/s: 1.13.0
Resolution: Duplicate
> system_tests_edge_router fails with ASAN leak
> -
>
> Key: DISPATCH-1663
> URL: https://issues.apache.org/jira/browse/DISPATCH-1663
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> 53: ==
> 53: ERROR: test_03_interior_conn_lost
> (system_tests_edge_router.LinkRouteProxyTest)
> 53: --
> 53: Traceback (most recent call last):
> 53: File
> "/home/gmurthy/opensource/qpid-dispatch/tests/system_tests_edge_router.py",
> line 1859, in test_03_interior_conn_lost
> 53: er.teardown()
> 53: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py",
> line 442, in teardown
> 53: super(Qdrouterd, self).teardown()
> 53: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py",
> line 295, in teardown
> 53: error("exit code %s, expected %s" % (status, self.expect))
> 53: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py",
> line 285, in error
> 53: self.outfile + '.cmd', f.read()));
> 53: RuntimeError: Process 16556 error: exit code 1, expected 0
> 53: qdrouterd -c Edge1.conf -I /home/gmurthy/opensource/qpid-dispatch/python
> 53:
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/test_03_interior_conn_lost/Edge1-9.cmd
> 53:
> 53:
> 53: =
> 53: ==16556==ERROR: LeakSanitizer: detected memory leaks
> 53:
> 53: Indirect leak of 704 byte(s) in 1 object(s) allocated from:
> 53: #0 0x7f60c03a3bf5 in __interceptor_posix_memalign
> (/lib64/libasan.so.5+0x10ebf5)
> 53: #1 0x7f60bfb5ace3 in qd_alloc
> /home/gmurthy/opensource/qpid-dispatch/src/alloc_pool.c:347
> 53: #2 0x7f60bfb63e62 in new_qd_buffer_t
> /home/gmurthy/opensource/qpid-dispatch/src/buffer.c:31
> 53: #3 0x7f60bfb641a8 in qd_buffer
> /home/gmurthy/opensource/qpid-dispatch/src/buffer.c:44
> 53: #4 0x7f60bfb64628 in qd_buffer_list_clone
> /home/gmurthy/opensource/qpid-dispatch/src/buffer.c:71
> 53: #5 0x7f60bfbc4d98 in qd_message_copy
> /home/gmurthy/opensource/qpid-dispatch/src/message.c:1030
> 53: #6 0x7f60bfcf9bc9 in qdr_send_to2
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/transfer.c:293
> 53: #7 0x7f60bfcf064f in qdr_management_agent_on_message
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/management_agent.c:534
> 53: #8 0x7f60bfc9f707 in qdr_forward_on_message
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/forwarder.c:310
> 53: #9 0x7f60bfcd7e3c in qdr_general_handler
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:808
> 53: #10 0x7f60bfd7a303 in qd_timer_visit
> /home/gmurthy/opensource/qpid-dispatch/src/timer.c:201
> 53: #11 0x7f60bfd694f5 in handle
> /home/gmurthy/opensource/qpid-dispatch/src/server.c:937
> 53: #12 0x7f60bfd6b153 in thread_run
> /home/gmurthy/opensource/qpid-dispatch/src/server.c:1040
> 53: #13 0x7f60bf7334bf in start_thread (/lib64/libpthread.so.0+0x84bf)
> 53:
> 53: -
> 53: Suppressions used:
> 53: count bytes template
> 53: 5 3008 qd_message_receive
> 53: 2640 qdr_action
> 53: 2760 qdr_core_subscribe
> 53: 1320 qdr_forward_closest_CT
> 53: 2896 qdr_link_deliver
> 53: 1256 qdr_link_issue_credit_CT
> 53: 1192 qdr_delivery_push_CT
> 53:45453371352 *libpython*
> 53: 50788 *python2*
> 53: -
> 53:
> 53: SUMMARY: AddressSanitizer: 704 byte(s) leaked in 1 allocation(s).
> 53:
> 53:
> 53: --
> 53: Ran 90 tests in 240.786s
> 53:
> 53: FAILED (errors=1)
> 1/1 Test #53: system_tests_edge_router .***Failed 240.99 sec
> {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
[jira] [Resolved] (DISPATCH-1661) system_tests_edge_router fails with ASAN leak
[
https://issues.apache.org/jira/browse/DISPATCH-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1661.
-
Fix Version/s: 1.13.0
Resolution: Fixed
> system_tests_edge_router fails with ASAN leak
> -
>
> Key: DISPATCH-1661
> URL: https://issues.apache.org/jira/browse/DISPATCH-1661
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> 53: Router EB1 debug dump file:
> 53: alloc.c: Items of type 'qd_timer_t' remain allocated at shutdown: 2
> 53: alloc.c: Items of type 'qd_connector_t' remain allocated at shutdown: 2
> 53: ERROR
> 53:
> 53: ==
> 53: ERROR: tearDownClass (system_tests_edge_router.StreamingMessageTest)
> 53: --
> 53: Traceback (most recent call last):
> 53: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py",
> line 691, in tearDownClass
> 53: cls.tester.teardown()
> 53: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py",
> line 637, in teardown
> 53: raise RuntimeError("Errors during teardown: \n\n%s" %
> "\n\n".join([str(e) for e in errors]))
> 53: RuntimeError: Errors during teardown:
> 53:
> 53: Process 14572 error: exit code 23, expected 0
> 53: qdrouterd -c EA1.conf -I /home/travis/build/apache/qpid-dispatch/python
> 53:
> /home/travis/build/apache/qpid-dispatch/build/tests/system_test.dir/system_tests_edge_router/StreamingMessageTest/setUpClass/EA1-18.cmd
> 53:
> 53:
> 53: =
> 53: ==14572==ERROR: LeakSanitizer: detected memory leaks
> 53:
> 53: Indirect leak of 7488 byte(s) in 13 object(s) allocated from:
> 53: #0 0x7fdea74bb076 in __interceptor_posix_memalign
> (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x99076)
> 53: #1 0x7fdea6d95d28 in qd_alloc
> /home/travis/build/apache/qpid-dispatch/src/alloc_pool.c:347
> 53: #2 0x7fdea6d9fddd in qd_buffer
> /home/travis/build/apache/qpid-dispatch/src/buffer.c:44
> 53: #3 0x7fdea6ea7b8a in qdr_field
> /home/travis/build/apache/qpid-dispatch/src/router_core/router_core.c:255
> 53: #4 0x7fdea6ec331f in qdr_terminus
> /home/travis/build/apache/qpid-dispatch/src/router_core/terminus.c:47
> 53: #5 0x7fdea6efd6dd in AMQP_link_attach_handler
> /home/travis/build/apache/qpid-dispatch/src/router_node.c:866
> 53: #6 0x7fdea6f13674 in handle
> /home/travis/build/apache/qpid-dispatch/src/server.c:1015
> 53: #7 0x7fdea6f1919f in thread_run
> /home/travis/build/apache/qpid-dispatch/src/server.c:1040
> 53: #8 0x7fdea69236b9 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9)
> 53:
> 53: -
> 53: Suppressions used:
> 53: count bytes template
> 53: 18 10944 qd_core_agent_query_handler
> 53: 73 41536 qd_message_receive
> 53: 13 7488 qdr_connection_opened
> 53: 15 8120 qdr_core_subscribe
> 53: 1192 qdr_link_deliver
> 53:3311244 *libpython*
> 53: 37120 *python2*
> 53: -
> 53:
> 53: SUMMARY: AddressSanitizer: 7488 byte(s) leaked in 13 allocation(s).
> 53:
> 53:
> 53: --
> 53: Ran 90 tests in 241.217s
> 53:
> 53: FAILED (errors=1)53/66 Test #53: system_tests_edge_router
> ..***Failed 241.32 sec {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
[jira] [Resolved] (DISPATCH-1662) system_tests_policy_oversize_compound fails with ASAN leak
[
https://issues.apache.org/jira/browse/DISPATCH-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1662.
-
Fix Version/s: 1.13.0
Resolution: Fixed
> system_tests_policy_oversize_compound fails with ASAN leak
> --
>
> Key: DISPATCH-1662
> URL: https://issues.apache.org/jira/browse/DISPATCH-1662
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> 26: Test command: /usr/bin/python
> "/home/travis/build/apache/qpid-dispatch/build/tests/run.py" "-m" "unittest"
> "-v" "system_tests_policy_oversize_compound"
> 26: Test timeout computed to be: 600
> 26: test_60_block_oversize_EB1_INTB_at_INTB
> (system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
> 26: test_61_block_oversize_EB1_EA1_at_INTB
> (system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
> 26: test_70_block_oversize_EB1_INTB_at_both
> (system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
> 26: test_80_block_multicast_EB1_INTB_at_INTB
> (system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
> 26: test_81_block_multicast_EA1
> (system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
> 26: test_82_block_multicast_INTA
> (system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
> 26:
> 26: Router EA1 debug dump file:
> 26: alloc.c: Items of type 'qd_iterator_t' remain allocated at shutdown: 12
> 26: alloc.c: Items of type 'qd_buffer_t' remain allocated at shutdown: 3
> 26: alloc.c: Items of type 'qd_parsed_field_t' remain allocated at shutdown: 5
> 26: alloc.c: Items of type 'qd_message_t' remain allocated at shutdown: 1
> 26: alloc.c: Items of type 'qd_message_content_t' remain allocated at
> shutdown: 1
> 26: alloc.c: Items of type 'qdr_delivery_t' remain allocated at shutdown: 1
> 26: alloc.c: Items of type 'qd_link_ref_t' remain allocated at shutdown: 1
> 26: ERROR
> 26: test_90_block_link_route_EB1_INTB
> (system_tests_policy_oversize_compound.MaxMessageSizeLinkRouteOversize) ... ok
> 26:
> 26: Router INT.B debug dump file:
> 26: alloc.c: Items of type 'qd_timer_t' remain allocated at shutdown: 2
> 26: alloc.c: Items of type 'qd_connector_t' remain allocated at shutdown: 2
> 26:
> 26: ==
> 26: ERROR: tearDownClass
> (system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize)
> 26: --
> 26: Traceback (most recent call last):
> 26: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py",
> line 691, in tearDownClass
> 26: cls.tester.teardown()
> 26: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py",
> line 637, in teardown
> 26: raise RuntimeError("Errors during teardown: \n\n%s" %
> "\n\n".join([str(e) for e in errors]))
> 26: RuntimeError: Errors during teardown:
> 26:
> 26: Process 12913 error: exit code 23, expected 0
> 26: qdrouterd -c INT.B.conf -I /home/travis/build/apache/qpid-dispatch/python
> 26:
> /home/travis/build/apache/qpid-dispatch/build/tests/system_test.dir/system_tests_policy_oversize_compound/MaxMessageSizeBlockOversize/setUpClass/INT.B-2.cmd
> 26:
> 26:
> 26: =
> 26: ==12913==ERROR: LeakSanitizer: detected memory leaks
> 26:
> 26: Indirect leak of 576 byte(s) in 3 object(s) allocated from:
> 26: #0 0x7fd7c490a076 in __interceptor_posix_memalign
> (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x99076)
> 26: #1 0x7fd7c41e4d28 in qd_alloc
> /home/travis/build/apache/qpid-dispatch/src/alloc_pool.c:347
> 26: #2 0x7fd7c4240c41 in qd_iterator_buffer
> /home/travis/build/apache/qpid-dispatch/src/iterator.c:597
> 26: #3 0x7fd7c42f6d2d in qdr_field
> /home/travis/build/apache/qpid-dispatch/src/router_core/router_core.c:265
> 26: #4 0x7fd7c431231f in qdr_terminus
> /home/travis/build/apache/qpid-dispatch/src/router_core/terminus.c:47
> 26: #5 0x7fd7c434ca3b in AMQP_incoming_link_handler
> /home/travis/build/apache/qpid-dispatch/src/router_node.c:817
> 26: #6 0x7fd7c4362674 in handle
> /home/travis/build/apache/qpid-dispatch/src/server.c:1015
> 26: #7 0x7fd7c436819f in thread_run
> /home/travis/build/apache/qpid-dispatch/src/server.c:1040
> 26: #8 0x7fd7c3d726b9 in start_thread
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9)
> 26:
> 26: -26: Suppressions
> used:
> 26: count bytes template
> 26: 2 1216 qd_message_receive
> 26: 13
[jira] [Assigned] (DISPATCH-1676) system_tests_policy failure on router shutdown
[
https://issues.apache.org/jira/browse/DISPATCH-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1676:
---
Assignee: Charles E. Rolke
> system_tests_policy failure on router shutdown
> --
>
> Key: DISPATCH-1676
> URL: https://issues.apache.org/jira/browse/DISPATCH-1676
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Charles E. Rolke
>Priority: Major
>
> {noformat}
> "24: Test command: /usr/bin/python
> \"/opt/qpid-dispatch-src/build/tests/run.py\" \"-m\" \"unittest\" \"-v\"
> \"system_tests_policy\"",
> "24: Test timeout computed to be: 600",
> "24: test_verify_maximum_connections
> (system_tests_policy.AbsoluteConnectionCountLimit) ... ok",
> "24: test_30_connector_policy_misconfigured
> (system_tests_policy.ConnectorPolicyMisconfigured) ... ok",
> "24: ",
> "24: Router QDR.Policy debug dump file:",
> "24: alloc.c: Items of type 'qd_timer_t' remain allocated at
> shutdown: 1",
> "24:
> Leak,/opt/qpid-dispatch-src/build/tests/system_test.dir/system_tests_policy/ConnectorPolicyMisconfigured/setUpClass/connectorPolicyMisconfigured-qddebug.txt,2020-05-28
> 08:09:47.923751 -0400,qd_timer_t,0x153e990",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_alloc+0x20c)
> [0x7f4b7caaec75]",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(new_qd_timer_t+0x26)
> [0x7f4b7cb1f5bd]",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_timer+0x19)
> [0x7f4b7cb1f9a7]",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_server_connector+0x12b)
> [0x7f4b7cb1f049]",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_dispatch_configure_connector+0x2c)
> [0x7f4b7cab6407]",
> "24: /lib64/libffi.so.6(ffi_call_unix64+0x4c) [0x7f4b6b95a04e]",
> "24: /lib64/libffi.so.6(ffi_call+0x35f) [0x7f4b6b959a0f]",
> "24:
> /usr/lib64/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so(_ctypes_callproc+0x6df)
> [0x7f4b6bb79b4f]",
> "24:
> /usr/lib64/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so(+0xfb17)
> [0x7f4b6bb75b17]",
> "24: /lib64/libpython3.6m.so.1.0(_PyObject_FastCallDict+0x36c)
> [0x7f4b7bbd4bfc]",
> "24: ",
> "24: alloc.c: Items of type 'qd_connector_t' remain allocated at
> shutdown: 1",
> "24:
> Leak,/opt/qpid-dispatch-src/build/tests/system_test.dir/system_tests_policy/ConnectorPolicyMisconfigured/setUpClass/connectorPolicyMisconfigured-qddebug.txt,2020-05-28
> 08:09:47.923745 -0400,qd_connector_t,0x15cf6d0",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_alloc+0x5cf)
> [0x7f4b7caaf038]",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(new_qd_connector_t+0x26)
> [0x7f4b7cb19b35]",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_server_connector+0x11)
> [0x7f4b7cb1ef2f]",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_dispatch_configure_connector+0x2c)
> [0x7f4b7cab6407]",
> "24: /lib64/libffi.so.6(ffi_call_unix64+0x4c) [0x7f4b6b95a04e]",
> "24: /lib64/libffi.so.6(ffi_call+0x35f) [0x7f4b6b959a0f]",
> "24:
> /usr/lib64/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so(_ctypes_callproc+0x6df)
> [0x7f4b6bb79b4f]",
> "24:
> /usr/lib64/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so(+0xfb17)
> [0x7f4b6bb75b17]",
> "24: /lib64/libpython3.6m.so.1.0(_PyObject_FastCallDict+0x36c)
> [0x7f4b7bbd4bfc]",
> "24: /lib64/libpython3.6m.so.1.0(+0x167bc8) [0x7f4b7bc26bc8]",
> "24: ",
> "24: test_32_connector_policy_max_sndr_rcvr
> (system_tests_policy.ConnectorPolicyNSndrRcvr) ... ok",
> "24: test_31_connector_policy
> (system_tests_policy.ConnectorPolicySrcTgt) ... ok",
> "24: ",
> "24: Router B debug dump file:",
> "24: alloc.c: Items of type 'qd_timer_t' remain allocated at
> shutdown: 1",
> "24:
> Leak,/opt/qpid-dispatch-src/build/tests/system_test.dir/system_tests_policy/InterrouterLinksAllowed/setUpClass/B-qddebug.txt,2020-05-28
> 08:10:20.261254 -0400,qd_timer_t,0x1e69910",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_alloc+0x20c)
> [0x7fcd57f19c75]",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(new_qd_timer_t+0x26)
> [0x7fcd57f8a5bd]",
> "24:
> /opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_timer+0x19)
> [0x7fcd57f8a9a7]",
> "24:
>
[jira] [Resolved] (DISPATCH-1675) system_tests_stuck_deliveries failure with AttributeError: 'DelayedSettlementTest' object has no attribute 'proxy'",
[
https://issues.apache.org/jira/browse/DISPATCH-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1675.
-
Fix Version/s: 1.13.0
Resolution: Fixed
> system_tests_stuck_deliveries failure with AttributeError:
> 'DelayedSettlementTest' object has no attribute 'proxy'",
> -
>
> Key: DISPATCH-1675
> URL: https://issues.apache.org/jira/browse/DISPATCH-1675
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> "64: Test command: /usr/bin/python
> \"/opt/qpid-dispatch-src/build/tests/run.py\" \"-m\" \"unittest\" \"-v\"
> \"system_tests_stuck_deliveries\"",
> "64: Test timeout computed to be: 600",
> "64: test_01_delayed_settlement_same_interior
> (system_tests_stuck_deliveries.RouterTest) ... ERROR",
> "64: test_02_delayed_settlement_different_edges_check_sender
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_03_delayed_settlement_different_edges_check_receiver
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_04_delayed_settlement_different_edges_check_interior
> (system_tests_stuck_deliveries.RouterTest) ... FAIL",
> "64: test_05_no_settlement_same_interior
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_06_no_settlement_different_edges_check_sender
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_07_no_settlement_different_edges_check_receiver
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_08_no_settlement_different_edges_check_interior
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_09_receiver_link_credit_test
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_10_sender_link_credit_test
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: ",
> "64:
> ==",
> "64: ERROR: test_01_delayed_settlement_same_interior
> (system_tests_stuck_deliveries.RouterTest)",
> "64:
> --",
> "64: Traceback (most recent call last):",
> "64: File
> \"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 97,
> in test_01_delayed_settlement_same_interior",
> "64: test.run()",
> "64: File
> \"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 264,
> in run",
> "64: Container(self).run()",
> "64: File
> \"/usr/lib64/python2.7/site-packages/proton/_reactor.py\", line 180, in run",
> "64: while self.process(): pass",
> "64: File
> \"/usr/lib64/python2.7/site-packages/proton/_reactor.py\", line 237, in
> process",
> "64: event.dispatch(handler)",
> "64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
> line 165, in dispatch",
> "64: self.dispatch(h, type)",
> "64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
> line 165, in dispatch",
> "64: self.dispatch(h, type)",
> "64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
> line 162, in dispatch",
> "64: _dispatch(handler, type.method, self)",
> "64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
> line 123, in _dispatch",
> "64: m(*args)",
> "64: File
> \"/usr/lib64/python2.7/site-packages/proton/_handlers.py\", line 260, in
> on_delivery",
> "64: self.on_message(event)",
> "64: File
> \"/usr/lib64/python2.7/site-packages/proton/_handlers.py\", line 286, in
> on_message",
> "64: _dispatch(self.delegate, 'on_message', event)",
> "64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
> line 123, in _dispatch",
> "64: m(*args)",
> "64: File
> \"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 236,
> in on_message",
> "64: self.query_stats(len(self.stuck_list) * 2)",
> "64: File
> \"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 257,
> in query_stats",
> "64: msg = self.proxy.query_router()",
> "64: AttributeError: 'DelayedSettlementTest' object has no attribute
> 'proxy'",
> "64: ",
> "64:
> ==",
> "64:
[jira] [Resolved] (DISPATCH-1677) test_48_connection_uptime_last_dlv failing in system_tests_one_router
[
https://issues.apache.org/jira/browse/DISPATCH-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1677.
-
Fix Version/s: 1.13.0
Resolution: Fixed
> test_48_connection_uptime_last_dlv failing in system_tests_one_router
> --
>
> Key: DISPATCH-1677
> URL: https://issues.apache.org/jira/browse/DISPATCH-1677
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> test_52_add_interrouter_connector_to_edge_router
> (system_tests_one_router.EdgeRouterQdManageTest) ... ok
> test_53_add_edge_listener_to_edge_router
> (system_tests_one_router.EdgeRouterQdManageTest) ... ok
> test_54_add_interrouter_listener_to_edge_router
> (system_tests_one_router.EdgeRouterQdManageTest) ... ok
> test_01_listen_error (system_tests_one_router.OneRouterTest) ... ok
> test_02_pre_settled (system_tests_one_router.OneRouterTest) ... ok
> test_03_multicast_unsettled (system_tests_one_router.OneRouterTest) ... ok
> test_04_disposition_returns_to_closed_connection
> (system_tests_one_router.OneRouterTest) ... ok
> test_05_sender_settles_first (system_tests_one_router.OneRouterTest) ... ok
> test_06_propagated_disposition (system_tests_one_router.OneRouterTest) ... ok
> test_07_unsettled_undeliverable (system_tests_one_router.OneRouterTest) ... ok
> test_08_three_ack (system_tests_one_router.OneRouterTest) ... ok
> test_09_message_annotations (system_tests_one_router.OneRouterTest) ... ok
> test_10_strip_message_annotations_custom
> (system_tests_one_router.OneRouterTest) ... ok
> test_11_test_strip_message_annotations_no
> (system_tests_one_router.OneRouterTest) ... ok
> test_12_test_strip_message_annotations_no_add_trace
> (system_tests_one_router.OneRouterTest) ... ok
> test_13_test_strip_message_annotations_both
> (system_tests_one_router.OneRouterTest) ... ok
> test_14_test_strip_message_annotations_out
> (system_tests_one_router.OneRouterTest) ... ok
> test_15_test_strip_message_annotations_in
> (system_tests_one_router.OneRouterTest) ... ok
> test_16_management (system_tests_one_router.OneRouterTest) ... ok
> test_17_management_get_operations (system_tests_one_router.OneRouterTest) ...
> ok
> test_17_multiframe_presettled (system_tests_one_router.OneRouterTest) ... ok
> test_18_management_not_implemented (system_tests_one_router.OneRouterTest)
> ... ok
> test_19_semantics_multicast (system_tests_one_router.OneRouterTest) ... ok
> test_20_semantics_closest (system_tests_one_router.OneRouterTest) ... ok
> test_21_semantics_balanced (system_tests_one_router.OneRouterTest) ... ok
> test_22_to_override (system_tests_one_router.OneRouterTest) ... ok
> test_23_send_settle_mode_settled (system_tests_one_router.OneRouterTest) ...
> ok
> test_24_excess_deliveries_released (system_tests_one_router.OneRouterTest)
> ... ok
> test_25_multicast_unsettled (system_tests_one_router.OneRouterTest) ... ok
> test_27_released_vs_modified (system_tests_one_router.OneRouterTest) ... ok
> test_28_appearance_of_balance (system_tests_one_router.OneRouterTest) ... ok
> test_29_batched_settlement (system_tests_one_router.OneRouterTest) ... ok
> test_30_presettled_overflow (system_tests_one_router.OneRouterTest) ... ok
> test_31_create_unavailable_sender (system_tests_one_router.OneRouterTest) ...
> ok
> test_32_create_unavailable_receiver (system_tests_one_router.OneRouterTest)
> ... ok
> test_33_large_streaming_test (system_tests_one_router.OneRouterTest) ... ok
> test_34_reject_coordinator (system_tests_one_router.OneRouterTest) ... ok
> test_35_reject_disposition (system_tests_one_router.OneRouterTest) ... ok
> test_37_connection_properties_unicode_string
> (system_tests_one_router.OneRouterTest) ... ok
> test_38_connection_properties_symbols (system_tests_one_router.OneRouterTest)
> ... ok
> test_40_anonymous_sender_no_receiver (system_tests_one_router.OneRouterTest)
> ... ok
> test_41_large_streaming_close_conn_test
> (system_tests_one_router.OneRouterTest) ... ok
> test_42_unsettled_large_message_test (system_tests_one_router.OneRouterTest)
> ... ok
> test_43_dropped_presettled_receiver_stops
> (system_tests_one_router.OneRouterTest) ... ok
> test_44_delete_connection_fail (system_tests_one_router.OneRouterTest) ... ok
> test_45_q2_holdoff_drop_stalled_rx (system_tests_one_router.OneRouterTest)
> ... ok
> test_48_connection_uptime_last_dlv (system_tests_one_router.OneRouterTest)
> ... FAIL
> test_49_unexpected_release_test (system_tests_one_router.OneRouterTest) ... ok
> test_01_verify_attach
> (system_tests_one_router.OneRouterTransactionalAttachTest) ... ok
>
[jira] [Updated] (DISPATCH-1686) system_tests_policy_oversize_compound fails with new ASAN leak
[
https://issues.apache.org/jira/browse/DISPATCH-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1686:
Description:
{noformat}
26: ==
26: ERROR: tearDownClass
(system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize)
26: --
26: Traceback (most recent call last):
26: File
"/home/travis/build/ganeshmurthy/qpid-dispatch/tests/system_test.py", line 723,
in tearDownClass
26: cls.tester.teardown()
26: File
"/home/travis/build/ganeshmurthy/qpid-dispatch/tests/system_test.py", line 669,
in teardown
26: raise RuntimeError("Errors during teardown: \n\n%s" %
"\n\n".join([str(e) for e in errors]))
26: RuntimeError: Errors during teardown:
26:
26: Process 12895 error: exit code 23, expected 0
26: qdrouterd -c INT.B.conf -I
/home/travis/build/ganeshmurthy/qpid-dispatch/python
26:
/home/travis/build/ganeshmurthy/qpid-dispatch/build/tests/system_test.dir/system_tests_policy_oversize_compound/MaxMessageSizeBlockOversize/setUpClass/INT.B-2.cmd
26:
26:
26: =
26: ==12895==ERROR: LeakSanitizer: detected memory leaks
26:
26: Indirect leak of 64 byte(s) in 1 object(s) allocated from:
26: #0 0x7fc2f1e2f076 in __interceptor_posix_memalign
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x99076)
26: #1 0x7fc2f1703128 in qd_alloc
/home/travis/build/ganeshmurthy/qpid-dispatch/src/alloc_pool.c:347
26: #2 0x7fc2f17fe877 in qdr_forward_deliver_CT
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/forwarder.c:276
26: #3 0x7fc2f17db699 in qdrc_event_link_raise
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/core_events.c:113
26: #4 0x7fc2f185fb7c in qcm_addr_lookup_CT
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/modules/address_lookup_client/lookup_client.c:570
26: #5 0x7fc2f17ce7d9 in qdr_link_inbound_first_attach_CT
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/connections.c:1671
26: #6 0x7fc2f1826b6b in router_core_thread
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/router_core_thread.c:193
26: #7 0x7fc2f128c6b9 in start_thread
(/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9)
26: -
26: Suppressions used:
26: count bytes template
26: 1 64 qd_message_receive
26: 2384 qdr_connection_opened
26: 13 4368 qdr_core_subscribe
26: 1192 qdr_forward_closest_CT
26: 2 1472 qdr_link_deliver
26: 1 64 qdr_node_connect_deliveries
26: 1192 qd_container_register_node_type
26: 28 70 __strdup
26: 1128 qd_parse_internal
26:46433425516 *libpython*
26: 37120 *python2*
26: -
26:
26: SUMMARY: AddressSanitizer: 64 byte(s) leaked in 1 allocation(s). {noformat}
was:
{noformat}
26: ==26:
ERROR: tearDownClass
(system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize)26:
--26:
Traceback (most recent call last):26: File
"/home/travis/build/ganeshmurthy/qpid-dispatch/tests/system_test.py", line 723,
in tearDownClass26: cls.tester.teardown()26: File
"/home/travis/build/ganeshmurthy/qpid-dispatch/tests/system_test.py", line 669,
in teardown26: raise RuntimeError("Errors during teardown: \n\n%s" %
"\n\n".join([str(e) for e in errors]))26: RuntimeError: Errors during teardown:
26: 26: Process 12895 error: exit code 23, expected 026: qdrouterd -c
INT.B.conf -I /home/travis/build/ganeshmurthy/qpid-dispatch/python26:
/home/travis/build/ganeshmurthy/qpid-dispatch/build/tests/system_test.dir/system_tests_policy_oversize_compound/MaxMessageSizeBlockOversize/setUpClass/INT.B-2.cmd26:
26: 26:
=26:
==12895==ERROR: LeakSanitizer: detected memory leaks26: 26: Indirect leak of 64
byte(s) in 1 object(s) allocated from:26: #0 0x7fc2f1e2f076 in
__interceptor_posix_memalign
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x99076)26: #1 0x7fc2f1703128 in
qd_alloc /home/travis/build/ganeshmurthy/qpid-dispatch/src/alloc_pool.c:34726:
#2 0x7fc2f17fe877 in qdr_forward_deliver_CT
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/forwarder.c:27626:
#3 0x7fc2f17db699 in qdrc_event_link_raise
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/core_events.c:11326:
#4 0x7fc2f185fb7c in qcm_addr_lookup_CT
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/modules/address_lookup_client/lookup_client.c:57026:
#5
[jira] [Created] (DISPATCH-1686) system_tests_policy_oversize_compound fails with new ASAN leak
Ganesh Murthy created DISPATCH-1686:
---
Summary: system_tests_policy_oversize_compound fails with new ASAN
leak
Key: DISPATCH-1686
URL: https://issues.apache.org/jira/browse/DISPATCH-1686
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
26: ==26:
ERROR: tearDownClass
(system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize)26:
--26:
Traceback (most recent call last):26: File
"/home/travis/build/ganeshmurthy/qpid-dispatch/tests/system_test.py", line 723,
in tearDownClass26: cls.tester.teardown()26: File
"/home/travis/build/ganeshmurthy/qpid-dispatch/tests/system_test.py", line 669,
in teardown26: raise RuntimeError("Errors during teardown: \n\n%s" %
"\n\n".join([str(e) for e in errors]))26: RuntimeError: Errors during teardown:
26: 26: Process 12895 error: exit code 23, expected 026: qdrouterd -c
INT.B.conf -I /home/travis/build/ganeshmurthy/qpid-dispatch/python26:
/home/travis/build/ganeshmurthy/qpid-dispatch/build/tests/system_test.dir/system_tests_policy_oversize_compound/MaxMessageSizeBlockOversize/setUpClass/INT.B-2.cmd26:
26: 26:
=26:
==12895==ERROR: LeakSanitizer: detected memory leaks26: 26: Indirect leak of 64
byte(s) in 1 object(s) allocated from:26: #0 0x7fc2f1e2f076 in
__interceptor_posix_memalign
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x99076)26: #1 0x7fc2f1703128 in
qd_alloc /home/travis/build/ganeshmurthy/qpid-dispatch/src/alloc_pool.c:34726:
#2 0x7fc2f17fe877 in qdr_forward_deliver_CT
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/forwarder.c:27626:
#3 0x7fc2f17db699 in qdrc_event_link_raise
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/core_events.c:11326:
#4 0x7fc2f185fb7c in qcm_addr_lookup_CT
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/modules/address_lookup_client/lookup_client.c:57026:
#5 0x7fc2f17ce7d9 in qdr_link_inbound_first_attach_CT
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/connections.c:167126:
#6 0x7fc2f1826b6b in router_core_thread
/home/travis/build/ganeshmurthy/qpid-dispatch/src/router_core/router_core_thread.c:19326:
#7 0x7fc2f128c6b9 in start_thread
(/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9) {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
[jira] [Assigned] (DISPATCH-1677) test_48_connection_uptime_last_dlv failing in system_tests_one_router
[
https://issues.apache.org/jira/browse/DISPATCH-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1677:
---
Assignee: Ganesh Murthy
> test_48_connection_uptime_last_dlv failing in system_tests_one_router
> --
>
> Key: DISPATCH-1677
> URL: https://issues.apache.org/jira/browse/DISPATCH-1677
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
>
> {noformat}
> test_52_add_interrouter_connector_to_edge_router
> (system_tests_one_router.EdgeRouterQdManageTest) ... ok
> test_53_add_edge_listener_to_edge_router
> (system_tests_one_router.EdgeRouterQdManageTest) ... ok
> test_54_add_interrouter_listener_to_edge_router
> (system_tests_one_router.EdgeRouterQdManageTest) ... ok
> test_01_listen_error (system_tests_one_router.OneRouterTest) ... ok
> test_02_pre_settled (system_tests_one_router.OneRouterTest) ... ok
> test_03_multicast_unsettled (system_tests_one_router.OneRouterTest) ... ok
> test_04_disposition_returns_to_closed_connection
> (system_tests_one_router.OneRouterTest) ... ok
> test_05_sender_settles_first (system_tests_one_router.OneRouterTest) ... ok
> test_06_propagated_disposition (system_tests_one_router.OneRouterTest) ... ok
> test_07_unsettled_undeliverable (system_tests_one_router.OneRouterTest) ... ok
> test_08_three_ack (system_tests_one_router.OneRouterTest) ... ok
> test_09_message_annotations (system_tests_one_router.OneRouterTest) ... ok
> test_10_strip_message_annotations_custom
> (system_tests_one_router.OneRouterTest) ... ok
> test_11_test_strip_message_annotations_no
> (system_tests_one_router.OneRouterTest) ... ok
> test_12_test_strip_message_annotations_no_add_trace
> (system_tests_one_router.OneRouterTest) ... ok
> test_13_test_strip_message_annotations_both
> (system_tests_one_router.OneRouterTest) ... ok
> test_14_test_strip_message_annotations_out
> (system_tests_one_router.OneRouterTest) ... ok
> test_15_test_strip_message_annotations_in
> (system_tests_one_router.OneRouterTest) ... ok
> test_16_management (system_tests_one_router.OneRouterTest) ... ok
> test_17_management_get_operations (system_tests_one_router.OneRouterTest) ...
> ok
> test_17_multiframe_presettled (system_tests_one_router.OneRouterTest) ... ok
> test_18_management_not_implemented (system_tests_one_router.OneRouterTest)
> ... ok
> test_19_semantics_multicast (system_tests_one_router.OneRouterTest) ... ok
> test_20_semantics_closest (system_tests_one_router.OneRouterTest) ... ok
> test_21_semantics_balanced (system_tests_one_router.OneRouterTest) ... ok
> test_22_to_override (system_tests_one_router.OneRouterTest) ... ok
> test_23_send_settle_mode_settled (system_tests_one_router.OneRouterTest) ...
> ok
> test_24_excess_deliveries_released (system_tests_one_router.OneRouterTest)
> ... ok
> test_25_multicast_unsettled (system_tests_one_router.OneRouterTest) ... ok
> test_27_released_vs_modified (system_tests_one_router.OneRouterTest) ... ok
> test_28_appearance_of_balance (system_tests_one_router.OneRouterTest) ... ok
> test_29_batched_settlement (system_tests_one_router.OneRouterTest) ... ok
> test_30_presettled_overflow (system_tests_one_router.OneRouterTest) ... ok
> test_31_create_unavailable_sender (system_tests_one_router.OneRouterTest) ...
> ok
> test_32_create_unavailable_receiver (system_tests_one_router.OneRouterTest)
> ... ok
> test_33_large_streaming_test (system_tests_one_router.OneRouterTest) ... ok
> test_34_reject_coordinator (system_tests_one_router.OneRouterTest) ... ok
> test_35_reject_disposition (system_tests_one_router.OneRouterTest) ... ok
> test_37_connection_properties_unicode_string
> (system_tests_one_router.OneRouterTest) ... ok
> test_38_connection_properties_symbols (system_tests_one_router.OneRouterTest)
> ... ok
> test_40_anonymous_sender_no_receiver (system_tests_one_router.OneRouterTest)
> ... ok
> test_41_large_streaming_close_conn_test
> (system_tests_one_router.OneRouterTest) ... ok
> test_42_unsettled_large_message_test (system_tests_one_router.OneRouterTest)
> ... ok
> test_43_dropped_presettled_receiver_stops
> (system_tests_one_router.OneRouterTest) ... ok
> test_44_delete_connection_fail (system_tests_one_router.OneRouterTest) ... ok
> test_45_q2_holdoff_drop_stalled_rx (system_tests_one_router.OneRouterTest)
> ... ok
> test_48_connection_uptime_last_dlv (system_tests_one_router.OneRouterTest)
> ... FAIL
> test_49_unexpected_release_test (system_tests_one_router.OneRouterTest) ... ok
> test_01_verify_attach
> (system_tests_one_router.OneRouterTransactionalAttachTest) ... ok
> test_46_coordinator_linkroute_unavailable_DISPATCH_1453
>
[jira] [Assigned] (DISPATCH-1683) test_06_dynamic_reply_to_DC in system_tests_distribution is failing
[
https://issues.apache.org/jira/browse/DISPATCH-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1683:
---
Assignee: Ganesh Murthy
> test_06_dynamic_reply_to_DC in system_tests_distribution is failing
> ---
>
> Key: DISPATCH-1683
> URL: https://issues.apache.org/jira/browse/DISPATCH-1683
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> 36: ==
> 36: FAIL: test_06_dynamic_reply_to_DC
> (system_tests_distribution.DistributionTests)
> 36: --
> 36: Traceback (most recent call last):
> 36: File "/foo/qpid-dispatch/tests/system_test.py", line 820, in wrap
> 36: return f(*args, **kwargs)
> 36: File "/foo/qpid-dispatch/tests/system_tests_distribution.py", line 564,
> in test_06_dynamic_reply_to_DC
> 36: self.assertEqual ( None, test.error )
> 36: AssertionError: None != u'Timeout Expired: n_sent=0 received_by_server=0
> received_by_client=0'
> 36:
> 36: --
> 36: Ran 25 tests in 92.816s
> 36:
> 36: FAILED (failures=1, skipped=7)
> 36/67 Test #36: system_tests_distribution .***Failed
> 93.00 sec {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
[jira] [Resolved] (DISPATCH-1683) test_06_dynamic_reply_to_DC in system_tests_distribution is failing
[
https://issues.apache.org/jira/browse/DISPATCH-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1683.
-
Fix Version/s: 1.13.0
Resolution: Fixed
> test_06_dynamic_reply_to_DC in system_tests_distribution is failing
> ---
>
> Key: DISPATCH-1683
> URL: https://issues.apache.org/jira/browse/DISPATCH-1683
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> 36: ==
> 36: FAIL: test_06_dynamic_reply_to_DC
> (system_tests_distribution.DistributionTests)
> 36: --
> 36: Traceback (most recent call last):
> 36: File "/foo/qpid-dispatch/tests/system_test.py", line 820, in wrap
> 36: return f(*args, **kwargs)
> 36: File "/foo/qpid-dispatch/tests/system_tests_distribution.py", line 564,
> in test_06_dynamic_reply_to_DC
> 36: self.assertEqual ( None, test.error )
> 36: AssertionError: None != u'Timeout Expired: n_sent=0 received_by_server=0
> received_by_client=0'
> 36:
> 36: --
> 36: Ran 25 tests in 92.816s
> 36:
> 36: FAILED (failures=1, skipped=7)
> 36/67 Test #36: system_tests_distribution .***Failed
> 93.00 sec {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
[jira] [Created] (PROTON-2234) [proton-c] Need ability to add an authorization id in the SASL exchange
Ganesh Murthy created PROTON-2234: - Summary: [proton-c] Need ability to add an authorization id in the SASL exchange Key: PROTON-2234 URL: https://issues.apache.org/jira/browse/PROTON-2234 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: proton-c-0.31.0 Reporter: Ganesh Murthy The Qpid Dispatch router is capable of delegating SASL authentication to an external auth service. We need a way (1) for a server to get the authzid for a sasl external request - The "server" in this case the router, needs a way to obtain the authzid if the client has specified one during the SASL exchange (2) for a client to specify the authzid to send with an external request - the "client" in this case the router acts as a client to the auth service and it needs a way to specify/send the authzid to the auth service as part of the SASL exchange. [https://tools.ietf.org/html/rfc4422#page-29] (section A.2) -- 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] [Comment Edited] (DISPATCH-1634) Expose client X509 certificate identity (TLS client auth) to the auth service delegate
[
https://issues.apache.org/jira/browse/DISPATCH-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123845#comment-17123845
]
Ganesh Murthy edited comment on DISPATCH-1634 at 6/2/20, 2:51 PM:
--
The Dispatch Router provides fields in the sslProfile entity, namely, uidFormat
and uidNameMappingFile.
The uidFormat allows you to specify a format which will be used to generate an
identity from the TLS client certificate.
Allowed values in uidFormat can be any combination of
{noformat}
'c'( ISO3166 two character country code),
's'(state or province),
'l'(Locality; generally - city),
'o'(Organization - Company Name),
'u'(Organization Unit - typically certificate type or brand),
'n'(CommonName - typically a user name for client certificates) and
'1'(sha1 certificate fingerprint, as displayed in the fingerprints section when
looking at a certificate with say a web browser is the hash of the entire
certificate)
'2'(sha256 certificate fingerprint)
'5' (sha512 certificate fingerprint).
The user identifier (uid) that is generated based on the uidFormat is a string
which has a semi-colon as a separator between the components{noformat}
For example the uidFormat can be
{noformat}
('sslProfile', {'name': 'sslProfile',
'caCertFile': 'ca-certificate.pem',
'certFile': 'server-certificate.pem',
'privateKeyFile': 'server-private-key.pem',
'uidFormat': 'nsuco',
'uidNameMappingFile': /path/to/ssl_profile.json,
'password': 'server-password'}) {noformat}
{noformat}
'nsuco' for uidFormat indicates that the unique certificate identity be
constructed using CommonName, State, Organization Unit, Country Code and
Company Name{noformat}
The uidNameMappingFile is the absolute path to the file containing the unique
id to display name mapping.
For example, the contents of ssl_profile.json file could be
{noformat}
{
"Danny DeVito;MA;Dev;US;Acme Inc": "ddevito",
"Jane Doe;MA;Dev;US;Acme Inc": "janedoe",
"John Doe;MA;Dev;US;Acme Inc": "johndoe",
}
{noformat}
The file is simply a JSON which maps the identity string generated by the
uidFormat to a user name.
The user name can be empty in which case the router will just return the
identity string
Now that we have explained how the uidFormat and uidNameMappingFile work, there
are two parts to this Jira
# If the certificate identity (string generated using uidFormat) does not
exist in the uidNameMappingFile, the router does not currently close the
connection which it will have to do.
# The router's authplugin SASL relay should be able to prepare to rewrite the
authorization identity within response of the SASL-INIT (or SASL-RESPONSE) and
insert the identity from the client cert. To do this we need a way from
proton-c to
## for a server to get the authzid for a sasl external request
## for a client to specify the authzid to send with an external request
was (Author: ganeshmurthy):
The Dispatch Router provides a fields in the sslProfile entity, namely,
uidFormat and uidNameMappingFile.
The uidFormat allows you to specify a format which will be used to generate an
identity from the TLS client certificate.
Allowed values in uidFormat can be any combination of
{noformat}
'c'( ISO3166 two character country code),
's'(state or province),
'l'(Locality; generally - city),
'o'(Organization - Company Name),
'u'(Organization Unit - typically certificate type or brand),
'n'(CommonName - typically a user name for client certificates) and
'1'(sha1 certificate fingerprint, as displayed in the fingerprints section when
looking at a certificate with say a web browser is the hash of the entire
certificate)
'2'(sha256 certificate fingerprint)
'5' (sha512 certificate fingerprint).
The user identifier (uid) that is generated based on the uidFormat is a string
which has a semi-colon as a separator between the components{noformat}
For example the uidFormat can be
{noformat}
('sslProfile', {'name': 'sslProfile',
'caCertFile': 'ca-certificate.pem',
'certFile': 'server-certificate.pem',
'privateKeyFile': 'server-private-key.pem',
'uidFormat': 'nsuco',
'uidNameMappingFile': /path/to/ssl_profile.json,
'password': 'server-password'}) {noformat}
{noformat}
'nsuco' for uidFormat indicates that the unique certificate identity be
constructed using CommonName, State, Organization Unit, Country Code and
Company Name{noformat}
The uidNameMappingFile is the absolute path to the file containing the unique
id to display name mapping.
For example, the contents of ssl_profile.json file could be
{noformat}
{
"Danny DeVito;MA;Dev;US;Acme Inc": "ddevito",
"Jane Doe;MA;Dev;US;Acme Inc": "janedoe",
"John Doe;MA;Dev;US;Acme Inc": "johndoe",
}
{noformat}
The file is simply a JSON which maps the identity string
[jira] [Commented] (DISPATCH-1634) Expose client X509 certificate identity (TLS client auth) to the auth service delegate
[
https://issues.apache.org/jira/browse/DISPATCH-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123845#comment-17123845
]
Ganesh Murthy commented on DISPATCH-1634:
-
The Dispatch Router provides a fields in the sslProfile entity, namely,
uidFormat and uidNameMappingFile.
The uidFormat allows you to specify a format which will be used to generate an
identity from the TLS client certificate.
Allowed values in uidFormat can be any combination of
{noformat}
'c'( ISO3166 two character country code),
's'(state or province),
'l'(Locality; generally - city),
'o'(Organization - Company Name),
'u'(Organization Unit - typically certificate type or brand),
'n'(CommonName - typically a user name for client certificates) and
'1'(sha1 certificate fingerprint, as displayed in the fingerprints section when
looking at a certificate with say a web browser is the hash of the entire
certificate)
'2'(sha256 certificate fingerprint)
'5' (sha512 certificate fingerprint).
The user identifier (uid) that is generated based on the uidFormat is a string
which has a semi-colon as a separator between the components{noformat}
For example the uidFormat can be
{noformat}
('sslProfile', {'name': 'sslProfile',
'caCertFile': 'ca-certificate.pem',
'certFile': 'server-certificate.pem',
'privateKeyFile': 'server-private-key.pem',
'uidFormat': 'nsuco',
'uidNameMappingFile': /path/to/ssl_profile.json,
'password': 'server-password'}) {noformat}
{noformat}
'nsuco' for uidFormat indicates that the unique certificate identity be
constructed using CommonName, State, Organization Unit, Country Code and
Company Name{noformat}
The uidNameMappingFile is the absolute path to the file containing the unique
id to display name mapping.
For example, the contents of ssl_profile.json file could be
{noformat}
{
"Danny DeVito;MA;Dev;US;Acme Inc": "ddevito",
"Jane Doe;MA;Dev;US;Acme Inc": "janedoe",
"John Doe;MA;Dev;US;Acme Inc": "johndoe",
}
{noformat}
The file is simply a JSON which maps the identity string generated by the
uidFormat to a user name.
The user name can be empty in which case the router will just return the
identity string
Now that we have explained how the uidFormat and uidNameMappingFile work, there
are two parts to this Jira
# If the certificate identity (string generated using uidFormat) does not
exist in the uidNameMappingFile, the router does not currently close the
connection which it will have to do.
# The router's authplugin SASL relay should be able to prepare to rewrite the
authorization identity within response of the SASL-INIT (or SASL-RESPONSE) and
insert the identity from the client cert. To do this we need a way from
proton-c to
## for a server to get the authzid for a sasl external request
## for a client to specify the authzid to send with an external request
> Expose client X509 certificate identity (TLS client auth) to the auth service
> delegate
> --
>
> Key: DISPATCH-1634
> URL: https://issues.apache.org/jira/browse/DISPATCH-1634
> Project: Qpid Dispatch
> Issue Type: Improvement
>Reporter: Keith Wall
>Priority: Major
>
> For the use-case where Dispatch Router is configured to require the client
> use TLS client auth (authenticatePeer: yes) and the authServicePlugin is in
> use, there needs to be a mechanism to expose the X509 certificate identity of
> the client to the auth service so it can be used to control the`address-authz
> response.
--
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] [Created] (DISPATCH-1683) test_06_dynamic_reply_to_DC in system_tests_distribution is failing
Ganesh Murthy created DISPATCH-1683:
---
Summary: test_06_dynamic_reply_to_DC in system_tests_distribution
is failing
Key: DISPATCH-1683
URL: https://issues.apache.org/jira/browse/DISPATCH-1683
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
36: ==
36: FAIL: test_06_dynamic_reply_to_DC
(system_tests_distribution.DistributionTests)
36: --
36: Traceback (most recent call last):
36: File "/foo/qpid-dispatch/tests/system_test.py", line 820, in wrap
36: return f(*args, **kwargs)
36: File "/foo/qpid-dispatch/tests/system_tests_distribution.py", line 564,
in test_06_dynamic_reply_to_DC
36: self.assertEqual ( None, test.error )
36: AssertionError: None != u'Timeout Expired: n_sent=0 received_by_server=0
received_by_client=0'
36:
36: --
36: Ran 25 tests in 92.816s
36:
36: FAILED (failures=1, skipped=7)
36/67 Test #36: system_tests_distribution .***Failed
93.00 sec {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
[jira] [Created] (DISPATCH-1677) test_48_connection_uptime_last_dlv failing in system_tests_one_router
Ganesh Murthy created DISPATCH-1677:
---
Summary: test_48_connection_uptime_last_dlv failing in
system_tests_one_router
Key: DISPATCH-1677
URL: https://issues.apache.org/jira/browse/DISPATCH-1677
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
test_52_add_interrouter_connector_to_edge_router
(system_tests_one_router.EdgeRouterQdManageTest) ... ok
test_53_add_edge_listener_to_edge_router
(system_tests_one_router.EdgeRouterQdManageTest) ... ok
test_54_add_interrouter_listener_to_edge_router
(system_tests_one_router.EdgeRouterQdManageTest) ... ok
test_01_listen_error (system_tests_one_router.OneRouterTest) ... ok
test_02_pre_settled (system_tests_one_router.OneRouterTest) ... ok
test_03_multicast_unsettled (system_tests_one_router.OneRouterTest) ... ok
test_04_disposition_returns_to_closed_connection
(system_tests_one_router.OneRouterTest) ... ok
test_05_sender_settles_first (system_tests_one_router.OneRouterTest) ... ok
test_06_propagated_disposition (system_tests_one_router.OneRouterTest) ... ok
test_07_unsettled_undeliverable (system_tests_one_router.OneRouterTest) ... ok
test_08_three_ack (system_tests_one_router.OneRouterTest) ... ok
test_09_message_annotations (system_tests_one_router.OneRouterTest) ... ok
test_10_strip_message_annotations_custom
(system_tests_one_router.OneRouterTest) ... ok
test_11_test_strip_message_annotations_no
(system_tests_one_router.OneRouterTest) ... ok
test_12_test_strip_message_annotations_no_add_trace
(system_tests_one_router.OneRouterTest) ... ok
test_13_test_strip_message_annotations_both
(system_tests_one_router.OneRouterTest) ... ok
test_14_test_strip_message_annotations_out
(system_tests_one_router.OneRouterTest) ... ok
test_15_test_strip_message_annotations_in
(system_tests_one_router.OneRouterTest) ... ok
test_16_management (system_tests_one_router.OneRouterTest) ... ok
test_17_management_get_operations (system_tests_one_router.OneRouterTest) ... ok
test_17_multiframe_presettled (system_tests_one_router.OneRouterTest) ... ok
test_18_management_not_implemented (system_tests_one_router.OneRouterTest) ...
ok
test_19_semantics_multicast (system_tests_one_router.OneRouterTest) ... ok
test_20_semantics_closest (system_tests_one_router.OneRouterTest) ... ok
test_21_semantics_balanced (system_tests_one_router.OneRouterTest) ... ok
test_22_to_override (system_tests_one_router.OneRouterTest) ... ok
test_23_send_settle_mode_settled (system_tests_one_router.OneRouterTest) ... ok
test_24_excess_deliveries_released (system_tests_one_router.OneRouterTest) ...
ok
test_25_multicast_unsettled (system_tests_one_router.OneRouterTest) ... ok
test_27_released_vs_modified (system_tests_one_router.OneRouterTest) ... ok
test_28_appearance_of_balance (system_tests_one_router.OneRouterTest) ... ok
test_29_batched_settlement (system_tests_one_router.OneRouterTest) ... ok
test_30_presettled_overflow (system_tests_one_router.OneRouterTest) ... ok
test_31_create_unavailable_sender (system_tests_one_router.OneRouterTest) ... ok
test_32_create_unavailable_receiver (system_tests_one_router.OneRouterTest) ...
ok
test_33_large_streaming_test (system_tests_one_router.OneRouterTest) ... ok
test_34_reject_coordinator (system_tests_one_router.OneRouterTest) ... ok
test_35_reject_disposition (system_tests_one_router.OneRouterTest) ... ok
test_37_connection_properties_unicode_string
(system_tests_one_router.OneRouterTest) ... ok
test_38_connection_properties_symbols (system_tests_one_router.OneRouterTest)
... ok
test_40_anonymous_sender_no_receiver (system_tests_one_router.OneRouterTest)
... ok
test_41_large_streaming_close_conn_test (system_tests_one_router.OneRouterTest)
... ok
test_42_unsettled_large_message_test (system_tests_one_router.OneRouterTest)
... ok
test_43_dropped_presettled_receiver_stops
(system_tests_one_router.OneRouterTest) ... ok
test_44_delete_connection_fail (system_tests_one_router.OneRouterTest) ... ok
test_45_q2_holdoff_drop_stalled_rx (system_tests_one_router.OneRouterTest) ...
ok
test_48_connection_uptime_last_dlv (system_tests_one_router.OneRouterTest) ...
FAIL
test_49_unexpected_release_test (system_tests_one_router.OneRouterTest) ... ok
test_01_verify_attach
(system_tests_one_router.OneRouterTransactionalAttachTest) ... ok
test_46_coordinator_linkroute_unavailable_DISPATCH_1453
(system_tests_one_router.OneRouterUnavailableCoordinatorTest) ... ok
test_47_coordinator_linkroute_available_DISPATCH_1453
(system_tests_one_router.OneRouterUnavailableCoordinatorTest) ... ok
test_48_router_in_error
(system_tests_one_router.StandaloneEdgeRouterConfigTest) ... ok
test_49_add_interrouter_connector_to_standalone_router
(system_tests_one_router.StandaloneRouterQdManageTest) ... ok
test_50_add_edge_listener_to_standalone_router
[jira] [Updated] (DISPATCH-1670) system_tests_edge_router.LinkRouteProxyTest.test_50_link_topology reports many objects that remain allocated after test finishes
[
https://issues.apache.org/jira/browse/DISPATCH-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1670:
Issue Type: Bug (was: Improvement)
> system_tests_edge_router.LinkRouteProxyTest.test_50_link_topology reports
> many objects that remain allocated after test finishes
>
>
> Key: DISPATCH-1670
> URL: https://issues.apache.org/jira/browse/DISPATCH-1670
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> [gmurthy@localhost build]$ /usr/bin/python
> "/home/gmurthy/opensource/qpid-dispatch/build/tests/run.py" "-m" "unittest"
> "-v" "system_tests_edge_router.LinkRouteProxyTest.test_50_link_topology"
> test_50_link_topology (system_tests_edge_router.LinkRouteProxyTest) ...
> okRouter EB1 debug dump file:
> alloc.c: Items of type 'qd_buffer_t' remain allocated at shutdown: 1
> Leak,/home/gmurthy/opensource/qpid-dispatch/build/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/setUpClass/EB1-qddebug.txt,2020-05-26
> 14:15:50.146413 -0400,qd_buffer_t,0x61700028f010
> /lib64/libasan.so.5(+0x6ce80) [0x7f8fc94eae80]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_alloc+0xf5d)
> [0x7f8fc8d4172e]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(new_qd_buffer_t+0x26)
> [0x7f8fc8d4be83]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_buffer+0x17)
> [0x7f8fc8d4c1c9]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message_receive+0x15b4)
> [0x7f8fc8db1909]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5b56f9)
> [0x7f8fc8f326f9]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x3f26ca)
> [0x7f8fc8d6f6ca]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_container_handle_event+0x2e06)
> [0x7f8fc8d75d37]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6063)
> [0x7f8fc8f53063]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6259)
> [0x7f8fc8f53259]alloc.c: Items of type 'qd_message_t' remain allocated at
> shutdown: 2
> Leak,/home/gmurthy/opensource/qpid-dispatch/build/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/setUpClass/EB1-qddebug.txt,2020-05-26
> 14:15:50.146401 -0400,qd_message_t,0x61396c50
> /lib64/libasan.so.5(+0x6ce80) [0x7f8fc94eae80]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_alloc+0xf5d)
> [0x7f8fc8d4172e]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(new_qd_message_t+0x26)
> [0x7f8fc8da4ff0]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message+0x10)
> [0x7f8fc8dab492]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message_receive+0x69)
> [0x7f8fc8db03be]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5b56f9)
> [0x7f8fc8f326f9]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x3f26ca)
> [0x7f8fc8d6f6ca]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_container_handle_event+0x2e06)
> [0x7f8fc8d75d37]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6063)
> [0x7f8fc8f53063]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6259)
>
> [0x7f8fc8f53259]Leak,/home/gmurthy/opensource/qpid-dispatch/build/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/setUpClass/EB1-qddebug.txt,2020-05-26
> 14:15:50.146606 -0400,qd_message_t,0x61376810
> /lib64/libasan.so.5(+0x6ce80) [0x7f8fc94eae80]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_alloc+0xf5d)
> [0x7f8fc8d4172e]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(new_qd_message_t+0x26)
> [0x7f8fc8da4ff0]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message_copy+0x91)
> [0x7f8fc8dacde2]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qdr_forward_new_delivery_CT+0x2e4)
> [0x7f8fc8e833e4]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x56b76a)
> [0x7f8fc8ee876a]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(router_core_thread+0x1009)
> [0x7f8fc8ec6c08]
> /lib64/libpthread.so.0(+0x84c0) [0x7f8fc891b4c0]
> /lib64/libc.so.6(clone+0x43) [0x7f8fc7c11133]alloc.c: Items of type
> 'qd_message_content_t' remain allocated at shutdown: 1
>
[jira] [Created] (DISPATCH-1676) system_tests_policy failure on router shutdown
Ganesh Murthy created DISPATCH-1676:
---
Summary: system_tests_policy failure on router shutdown
Key: DISPATCH-1676
URL: https://issues.apache.org/jira/browse/DISPATCH-1676
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
"24: Test command: /usr/bin/python
\"/opt/qpid-dispatch-src/build/tests/run.py\" \"-m\" \"unittest\" \"-v\"
\"system_tests_policy\"",
"24: Test timeout computed to be: 600",
"24: test_verify_maximum_connections
(system_tests_policy.AbsoluteConnectionCountLimit) ... ok",
"24: test_30_connector_policy_misconfigured
(system_tests_policy.ConnectorPolicyMisconfigured) ... ok",
"24: ",
"24: Router QDR.Policy debug dump file:",
"24: alloc.c: Items of type 'qd_timer_t' remain allocated at shutdown:
1",
"24:
Leak,/opt/qpid-dispatch-src/build/tests/system_test.dir/system_tests_policy/ConnectorPolicyMisconfigured/setUpClass/connectorPolicyMisconfigured-qddebug.txt,2020-05-28
08:09:47.923751 -0400,qd_timer_t,0x153e990",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_alloc+0x20c)
[0x7f4b7caaec75]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(new_qd_timer_t+0x26)
[0x7f4b7cb1f5bd]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_timer+0x19)
[0x7f4b7cb1f9a7]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_server_connector+0x12b)
[0x7f4b7cb1f049]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_dispatch_configure_connector+0x2c)
[0x7f4b7cab6407]",
"24: /lib64/libffi.so.6(ffi_call_unix64+0x4c) [0x7f4b6b95a04e]",
"24: /lib64/libffi.so.6(ffi_call+0x35f) [0x7f4b6b959a0f]",
"24:
/usr/lib64/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so(_ctypes_callproc+0x6df)
[0x7f4b6bb79b4f]",
"24:
/usr/lib64/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so(+0xfb17)
[0x7f4b6bb75b17]",
"24: /lib64/libpython3.6m.so.1.0(_PyObject_FastCallDict+0x36c)
[0x7f4b7bbd4bfc]",
"24: ",
"24: alloc.c: Items of type 'qd_connector_t' remain allocated at
shutdown: 1",
"24:
Leak,/opt/qpid-dispatch-src/build/tests/system_test.dir/system_tests_policy/ConnectorPolicyMisconfigured/setUpClass/connectorPolicyMisconfigured-qddebug.txt,2020-05-28
08:09:47.923745 -0400,qd_connector_t,0x15cf6d0",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_alloc+0x5cf)
[0x7f4b7caaf038]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(new_qd_connector_t+0x26)
[0x7f4b7cb19b35]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_server_connector+0x11)
[0x7f4b7cb1ef2f]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_dispatch_configure_connector+0x2c)
[0x7f4b7cab6407]",
"24: /lib64/libffi.so.6(ffi_call_unix64+0x4c) [0x7f4b6b95a04e]",
"24: /lib64/libffi.so.6(ffi_call+0x35f) [0x7f4b6b959a0f]",
"24:
/usr/lib64/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so(_ctypes_callproc+0x6df)
[0x7f4b6bb79b4f]",
"24:
/usr/lib64/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so(+0xfb17)
[0x7f4b6bb75b17]",
"24: /lib64/libpython3.6m.so.1.0(_PyObject_FastCallDict+0x36c)
[0x7f4b7bbd4bfc]",
"24: /lib64/libpython3.6m.so.1.0(+0x167bc8) [0x7f4b7bc26bc8]",
"24: ",
"24: test_32_connector_policy_max_sndr_rcvr
(system_tests_policy.ConnectorPolicyNSndrRcvr) ... ok",
"24: test_31_connector_policy
(system_tests_policy.ConnectorPolicySrcTgt) ... ok",
"24: ",
"24: Router B debug dump file:",
"24: alloc.c: Items of type 'qd_timer_t' remain allocated at shutdown:
1",
"24:
Leak,/opt/qpid-dispatch-src/build/tests/system_test.dir/system_tests_policy/InterrouterLinksAllowed/setUpClass/B-qddebug.txt,2020-05-28
08:10:20.261254 -0400,qd_timer_t,0x1e69910",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_alloc+0x20c)
[0x7fcd57f19c75]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(new_qd_timer_t+0x26)
[0x7fcd57f8a5bd]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_timer+0x19)
[0x7fcd57f8a9a7]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_server_connector+0x12b)
[0x7fcd57f8a049]",
"24:
/opt/qpid-dispatch-src/build/src/libqpid-dispatch.so(qd_dispatch_configure_connector+0x2c)
[0x7fcd57f21407]",
"24: /lib64/libffi.so.6(ffi_call_unix64+0x4c) [0x7fcd46dc504e]",
"24: /lib64/libffi.so.6(ffi_call+0x35f) [0x7fcd46dc4a0f]",
"24:
/usr/lib64/python3.6/lib-dynload/_ctypes.cpython-36m-x86_64-linux-gnu.so(_ctypes_callproc+0x6df)
[jira] [Resolved] (DISPATCH-1670) system_tests_edge_router.LinkRouteProxyTest.test_50_link_topology reports many objects that remain allocated after test finishes
[
https://issues.apache.org/jira/browse/DISPATCH-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1670.
-
Resolution: Fixed
> system_tests_edge_router.LinkRouteProxyTest.test_50_link_topology reports
> many objects that remain allocated after test finishes
>
>
> Key: DISPATCH-1670
> URL: https://issues.apache.org/jira/browse/DISPATCH-1670
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> [gmurthy@localhost build]$ /usr/bin/python
> "/home/gmurthy/opensource/qpid-dispatch/build/tests/run.py" "-m" "unittest"
> "-v" "system_tests_edge_router.LinkRouteProxyTest.test_50_link_topology"
> test_50_link_topology (system_tests_edge_router.LinkRouteProxyTest) ...
> okRouter EB1 debug dump file:
> alloc.c: Items of type 'qd_buffer_t' remain allocated at shutdown: 1
> Leak,/home/gmurthy/opensource/qpid-dispatch/build/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/setUpClass/EB1-qddebug.txt,2020-05-26
> 14:15:50.146413 -0400,qd_buffer_t,0x61700028f010
> /lib64/libasan.so.5(+0x6ce80) [0x7f8fc94eae80]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_alloc+0xf5d)
> [0x7f8fc8d4172e]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(new_qd_buffer_t+0x26)
> [0x7f8fc8d4be83]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_buffer+0x17)
> [0x7f8fc8d4c1c9]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message_receive+0x15b4)
> [0x7f8fc8db1909]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5b56f9)
> [0x7f8fc8f326f9]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x3f26ca)
> [0x7f8fc8d6f6ca]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_container_handle_event+0x2e06)
> [0x7f8fc8d75d37]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6063)
> [0x7f8fc8f53063]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6259)
> [0x7f8fc8f53259]alloc.c: Items of type 'qd_message_t' remain allocated at
> shutdown: 2
> Leak,/home/gmurthy/opensource/qpid-dispatch/build/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/setUpClass/EB1-qddebug.txt,2020-05-26
> 14:15:50.146401 -0400,qd_message_t,0x61396c50
> /lib64/libasan.so.5(+0x6ce80) [0x7f8fc94eae80]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_alloc+0xf5d)
> [0x7f8fc8d4172e]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(new_qd_message_t+0x26)
> [0x7f8fc8da4ff0]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message+0x10)
> [0x7f8fc8dab492]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message_receive+0x69)
> [0x7f8fc8db03be]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5b56f9)
> [0x7f8fc8f326f9]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x3f26ca)
> [0x7f8fc8d6f6ca]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_container_handle_event+0x2e06)
> [0x7f8fc8d75d37]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6063)
> [0x7f8fc8f53063]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6259)
>
> [0x7f8fc8f53259]Leak,/home/gmurthy/opensource/qpid-dispatch/build/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/setUpClass/EB1-qddebug.txt,2020-05-26
> 14:15:50.146606 -0400,qd_message_t,0x61376810
> /lib64/libasan.so.5(+0x6ce80) [0x7f8fc94eae80]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_alloc+0xf5d)
> [0x7f8fc8d4172e]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(new_qd_message_t+0x26)
> [0x7f8fc8da4ff0]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message_copy+0x91)
> [0x7f8fc8dacde2]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qdr_forward_new_delivery_CT+0x2e4)
> [0x7f8fc8e833e4]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x56b76a)
> [0x7f8fc8ee876a]
> /home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(router_core_thread+0x1009)
> [0x7f8fc8ec6c08]
> /lib64/libpthread.so.0(+0x84c0) [0x7f8fc891b4c0]
> /lib64/libc.so.6(clone+0x43) [0x7f8fc7c11133]alloc.c: Items of type
> 'qd_message_content_t' remain allocated at shutdown: 1
>
[jira] [Assigned] (DISPATCH-1675) system_tests_stuck_deliveries failure with AttributeError: 'DelayedSettlementTest' object has no attribute 'proxy'",
[
https://issues.apache.org/jira/browse/DISPATCH-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1675:
---
Assignee: Ted Ross
> system_tests_stuck_deliveries failure with AttributeError:
> 'DelayedSettlementTest' object has no attribute 'proxy'",
> -
>
> Key: DISPATCH-1675
> URL: https://issues.apache.org/jira/browse/DISPATCH-1675
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ted Ross
>Priority: Major
>
> {noformat}
> "64: Test command: /usr/bin/python
> \"/opt/qpid-dispatch-src/build/tests/run.py\" \"-m\" \"unittest\" \"-v\"
> \"system_tests_stuck_deliveries\"",
> "64: Test timeout computed to be: 600",
> "64: test_01_delayed_settlement_same_interior
> (system_tests_stuck_deliveries.RouterTest) ... ERROR",
> "64: test_02_delayed_settlement_different_edges_check_sender
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_03_delayed_settlement_different_edges_check_receiver
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_04_delayed_settlement_different_edges_check_interior
> (system_tests_stuck_deliveries.RouterTest) ... FAIL",
> "64: test_05_no_settlement_same_interior
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_06_no_settlement_different_edges_check_sender
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_07_no_settlement_different_edges_check_receiver
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_08_no_settlement_different_edges_check_interior
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_09_receiver_link_credit_test
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: test_10_sender_link_credit_test
> (system_tests_stuck_deliveries.RouterTest) ... ok",
> "64: ",
> "64:
> ==",
> "64: ERROR: test_01_delayed_settlement_same_interior
> (system_tests_stuck_deliveries.RouterTest)",
> "64:
> --",
> "64: Traceback (most recent call last):",
> "64: File
> \"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 97,
> in test_01_delayed_settlement_same_interior",
> "64: test.run()",
> "64: File
> \"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 264,
> in run",
> "64: Container(self).run()",
> "64: File
> \"/usr/lib64/python2.7/site-packages/proton/_reactor.py\", line 180, in run",
> "64: while self.process(): pass",
> "64: File
> \"/usr/lib64/python2.7/site-packages/proton/_reactor.py\", line 237, in
> process",
> "64: event.dispatch(handler)",
> "64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
> line 165, in dispatch",
> "64: self.dispatch(h, type)",
> "64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
> line 165, in dispatch",
> "64: self.dispatch(h, type)",
> "64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
> line 162, in dispatch",
> "64: _dispatch(handler, type.method, self)",
> "64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
> line 123, in _dispatch",
> "64: m(*args)",
> "64: File
> \"/usr/lib64/python2.7/site-packages/proton/_handlers.py\", line 260, in
> on_delivery",
> "64: self.on_message(event)",
> "64: File
> \"/usr/lib64/python2.7/site-packages/proton/_handlers.py\", line 286, in
> on_message",
> "64: _dispatch(self.delegate, 'on_message', event)",
> "64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
> line 123, in _dispatch",
> "64: m(*args)",
> "64: File
> \"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 236,
> in on_message",
> "64: self.query_stats(len(self.stuck_list) * 2)",
> "64: File
> \"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 257,
> in query_stats",
> "64: msg = self.proxy.query_router()",
> "64: AttributeError: 'DelayedSettlementTest' object has no attribute
> 'proxy'",
> "64: ",
> "64:
> ==",
> "64: FAIL:
[jira] [Closed] (DISPATCH-1674) QDR crashes when sending and reading on edge listener
[
https://issues.apache.org/jira/browse/DISPATCH-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy closed DISPATCH-1674.
---
Fix Version/s: 1.12.0
Resolution: Fixed
This crash cannot be reproduced in Qpid Dispatch 1.12.0.
Closing this issue.
> QDR crashes when sending and reading on edge listener
> -
>
> Key: DISPATCH-1674
> URL: https://issues.apache.org/jira/browse/DISPATCH-1674
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.8.0
> Environment: $ cat qdr-server.conf
> router {
> mode: interior
> }
> listener {
> host: 0.0.0.0
> port: 5666
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> role: edge
> }
> address {
> prefix: collectd
> distribution: multicast
> }
> address {
> prefix: anycast/ceilometer
> distribution: multicast
> }
> $
>Reporter: Martin
>Priority: Major
> Fix For: 1.12.0
>
>
> Ran
> $ podman run -d --net=host --name=qdr-server
> --volume=/home/stack/qdr-server.conf:/etc/qpid-dispatch/qdrouterd.conf:ro
> quay.io/interconnectedcloud/qdrouterd:1.8.0
>
> When one client listens on anycast/ceilometer/... address and another client
> sends to that address QDR crashes.
--
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] [Created] (DISPATCH-1675) system_tests_stuck_deliveries failure with AttributeError: 'DelayedSettlementTest' object has no attribute 'proxy'",
Ganesh Murthy created DISPATCH-1675:
---
Summary: system_tests_stuck_deliveries failure with
AttributeError: 'DelayedSettlementTest' object has no attribute 'proxy'",
Key: DISPATCH-1675
URL: https://issues.apache.org/jira/browse/DISPATCH-1675
Project: Qpid Dispatch
Issue Type: Improvement
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
"64: Test command: /usr/bin/python
\"/opt/qpid-dispatch-src/build/tests/run.py\" \"-m\" \"unittest\" \"-v\"
\"system_tests_stuck_deliveries\"",
"64: Test timeout computed to be: 600",
"64: test_01_delayed_settlement_same_interior
(system_tests_stuck_deliveries.RouterTest) ... ERROR",
"64: test_02_delayed_settlement_different_edges_check_sender
(system_tests_stuck_deliveries.RouterTest) ... ok",
"64: test_03_delayed_settlement_different_edges_check_receiver
(system_tests_stuck_deliveries.RouterTest) ... ok",
"64: test_04_delayed_settlement_different_edges_check_interior
(system_tests_stuck_deliveries.RouterTest) ... FAIL",
"64: test_05_no_settlement_same_interior
(system_tests_stuck_deliveries.RouterTest) ... ok",
"64: test_06_no_settlement_different_edges_check_sender
(system_tests_stuck_deliveries.RouterTest) ... ok",
"64: test_07_no_settlement_different_edges_check_receiver
(system_tests_stuck_deliveries.RouterTest) ... ok",
"64: test_08_no_settlement_different_edges_check_interior
(system_tests_stuck_deliveries.RouterTest) ... ok",
"64: test_09_receiver_link_credit_test
(system_tests_stuck_deliveries.RouterTest) ... ok",
"64: test_10_sender_link_credit_test
(system_tests_stuck_deliveries.RouterTest) ... ok",
"64: ",
"64:
==",
"64: ERROR: test_01_delayed_settlement_same_interior
(system_tests_stuck_deliveries.RouterTest)",
"64:
--",
"64: Traceback (most recent call last):",
"64: File
\"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 97, in
test_01_delayed_settlement_same_interior",
"64: test.run()",
"64: File
\"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 264, in
run",
"64: Container(self).run()",
"64: File \"/usr/lib64/python2.7/site-packages/proton/_reactor.py\",
line 180, in run",
"64: while self.process(): pass",
"64: File \"/usr/lib64/python2.7/site-packages/proton/_reactor.py\",
line 237, in process",
"64: event.dispatch(handler)",
"64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
line 165, in dispatch",
"64: self.dispatch(h, type)",
"64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
line 165, in dispatch",
"64: self.dispatch(h, type)",
"64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
line 162, in dispatch",
"64: _dispatch(handler, type.method, self)",
"64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
line 123, in _dispatch",
"64: m(*args)",
"64: File \"/usr/lib64/python2.7/site-packages/proton/_handlers.py\",
line 260, in on_delivery",
"64: self.on_message(event)",
"64: File \"/usr/lib64/python2.7/site-packages/proton/_handlers.py\",
line 286, in on_message",
"64: _dispatch(self.delegate, 'on_message', event)",
"64: File \"/usr/lib64/python2.7/site-packages/proton/_events.py\",
line 123, in _dispatch",
"64: m(*args)",
"64: File
\"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 236, in
on_message",
"64: self.query_stats(len(self.stuck_list) * 2)",
"64: File
\"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 257, in
query_stats",
"64: msg = self.proxy.query_router()",
"64: AttributeError: 'DelayedSettlementTest' object has no attribute
'proxy'",
"64: ",
"64:
==",
"64: FAIL: test_04_delayed_settlement_different_edges_check_interior
(system_tests_stuck_deliveries.RouterTest)",
"64:
--",
"64: Traceback (most recent call last):",
"64: File
\"/opt/qpid-dispatch-src/tests/system_tests_stuck_deliveries.py\", line 122, in
test_04_delayed_settlement_different_edges_check_interior",
"64: self.assertEqual(None, test.error)",
"64: AssertionError: None != u'Timeout Expired - n_tx=10, n_rx=10,
expected_stuck=8
[jira] [Resolved] (DISPATCH-1637) Adding new config address, autolinks and link routes become slower as more get added
[
https://issues.apache.org/jira/browse/DISPATCH-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1637.
-
Resolution: Fixed
> Adding new config address, autolinks and link routes become slower as more
> get added
> -
>
> Key: DISPATCH-1637
> URL: https://issues.apache.org/jira/browse/DISPATCH-1637
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
> Attachments: qdr_perf_core_369301_369302.svg
>
>
> Steps to reproduce -
> # Start the router with a default config file, nothing special
> # Run the following qdmanage command in a loop from 1 to 200,000
> ## qdmanage CREATE --type=address prefix=abc\{i} name=abc\{i}
> distribution=balanced waypoint=yes
> # watch qdstat -g
> # Over time, the rate at which the addresses get added comes to a crawl
> This happens for autoLinks and linkRoutes as well
--
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] [Created] (DISPATCH-1670) system_tests_edge_router.LinkRouteProxyTest.test_50_link_topology reports many objects that remain allocated after test finishes
Ganesh Murthy created DISPATCH-1670:
---
Summary:
system_tests_edge_router.LinkRouteProxyTest.test_50_link_topology reports many
objects that remain allocated after test finishes
Key: DISPATCH-1670
URL: https://issues.apache.org/jira/browse/DISPATCH-1670
Project: Qpid Dispatch
Issue Type: Improvement
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
Fix For: 1.13.0
{noformat}
[gmurthy@localhost build]$ /usr/bin/python
"/home/gmurthy/opensource/qpid-dispatch/build/tests/run.py" "-m" "unittest"
"-v" "system_tests_edge_router.LinkRouteProxyTest.test_50_link_topology"
test_50_link_topology (system_tests_edge_router.LinkRouteProxyTest) ...
okRouter EB1 debug dump file:
alloc.c: Items of type 'qd_buffer_t' remain allocated at shutdown: 1
Leak,/home/gmurthy/opensource/qpid-dispatch/build/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/setUpClass/EB1-qddebug.txt,2020-05-26
14:15:50.146413 -0400,qd_buffer_t,0x61700028f010
/lib64/libasan.so.5(+0x6ce80) [0x7f8fc94eae80]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_alloc+0xf5d)
[0x7f8fc8d4172e]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(new_qd_buffer_t+0x26)
[0x7f8fc8d4be83]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_buffer+0x17)
[0x7f8fc8d4c1c9]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message_receive+0x15b4)
[0x7f8fc8db1909]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5b56f9)
[0x7f8fc8f326f9]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x3f26ca)
[0x7f8fc8d6f6ca]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_container_handle_event+0x2e06)
[0x7f8fc8d75d37]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6063)
[0x7f8fc8f53063]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6259)
[0x7f8fc8f53259]alloc.c: Items of type 'qd_message_t' remain allocated at
shutdown: 2
Leak,/home/gmurthy/opensource/qpid-dispatch/build/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/setUpClass/EB1-qddebug.txt,2020-05-26
14:15:50.146401 -0400,qd_message_t,0x61396c50
/lib64/libasan.so.5(+0x6ce80) [0x7f8fc94eae80]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_alloc+0xf5d)
[0x7f8fc8d4172e]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(new_qd_message_t+0x26)
[0x7f8fc8da4ff0]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message+0x10)
[0x7f8fc8dab492]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message_receive+0x69)
[0x7f8fc8db03be]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5b56f9)
[0x7f8fc8f326f9]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x3f26ca)
[0x7f8fc8d6f6ca]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_container_handle_event+0x2e06)
[0x7f8fc8d75d37]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6063)
[0x7f8fc8f53063]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x5d6259)
[0x7f8fc8f53259]Leak,/home/gmurthy/opensource/qpid-dispatch/build/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/setUpClass/EB1-qddebug.txt,2020-05-26
14:15:50.146606 -0400,qd_message_t,0x61376810
/lib64/libasan.so.5(+0x6ce80) [0x7f8fc94eae80]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_alloc+0xf5d)
[0x7f8fc8d4172e]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(new_qd_message_t+0x26)
[0x7f8fc8da4ff0]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_message_copy+0x91)
[0x7f8fc8dacde2]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qdr_forward_new_delivery_CT+0x2e4)
[0x7f8fc8e833e4]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(+0x56b76a)
[0x7f8fc8ee876a]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(router_core_thread+0x1009)
[0x7f8fc8ec6c08]
/lib64/libpthread.so.0(+0x84c0) [0x7f8fc891b4c0]
/lib64/libc.so.6(clone+0x43) [0x7f8fc7c11133]alloc.c: Items of type
'qd_message_content_t' remain allocated at shutdown: 1
Leak,/home/gmurthy/opensource/qpid-dispatch/build/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/setUpClass/EB1-qddebug.txt,2020-05-26
14:15:50.146406 -0400,qd_message_content_t,0x61ab7110
/lib64/libasan.so.5(+0x6ce80) [0x7f8fc94eae80]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(qd_alloc+0xf5d)
[0x7f8fc8d4172e]
/home/gmurthy/opensource/qpid-dispatch/build/src/libqpid-dispatch.so(new_qd_message_content_t+0x26)
[0x7f8fc8da52fa]
[jira] [Resolved] (DISPATCH-1667) Increase minimum required LibWebSockets version from 2.1.0 to 2.4.2
[ https://issues.apache.org/jira/browse/DISPATCH-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1667. - Fix Version/s: 1.13.0 Resolution: Fixed > Increase minimum required LibWebSockets version from 2.1.0 to 2.4.2 > --- > > Key: DISPATCH-1667 > URL: https://issues.apache.org/jira/browse/DISPATCH-1667 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Affects Versions: 1.12.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.13.0 > > > LibWebSockets v2.1.0 was released on 2016-10-06 and is quite old. Move to a > more recent version 2.4.2 which was released on 2018-03-07. > 2.4.2 is a stable version and contains features like allowing deleting http > listener ports on demand. -- 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] [Assigned] (DISPATCH-1663) system_tests_edge_router fails with ASAN leak
[
https://issues.apache.org/jira/browse/DISPATCH-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1663:
---
Assignee: Ganesh Murthy
> system_tests_edge_router fails with ASAN leak
> -
>
> Key: DISPATCH-1663
> URL: https://issues.apache.org/jira/browse/DISPATCH-1663
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
>
> {noformat}
> 53: ==
> 53: ERROR: test_03_interior_conn_lost
> (system_tests_edge_router.LinkRouteProxyTest)
> 53: --
> 53: Traceback (most recent call last):
> 53: File
> "/home/gmurthy/opensource/qpid-dispatch/tests/system_tests_edge_router.py",
> line 1859, in test_03_interior_conn_lost
> 53: er.teardown()
> 53: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py",
> line 442, in teardown
> 53: super(Qdrouterd, self).teardown()
> 53: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py",
> line 295, in teardown
> 53: error("exit code %s, expected %s" % (status, self.expect))
> 53: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py",
> line 285, in error
> 53: self.outfile + '.cmd', f.read()));
> 53: RuntimeError: Process 16556 error: exit code 1, expected 0
> 53: qdrouterd -c Edge1.conf -I /home/gmurthy/opensource/qpid-dispatch/python
> 53:
> /home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/test_03_interior_conn_lost/Edge1-9.cmd
> 53:
> 53:
> 53: =
> 53: ==16556==ERROR: LeakSanitizer: detected memory leaks
> 53:
> 53: Indirect leak of 704 byte(s) in 1 object(s) allocated from:
> 53: #0 0x7f60c03a3bf5 in __interceptor_posix_memalign
> (/lib64/libasan.so.5+0x10ebf5)
> 53: #1 0x7f60bfb5ace3 in qd_alloc
> /home/gmurthy/opensource/qpid-dispatch/src/alloc_pool.c:347
> 53: #2 0x7f60bfb63e62 in new_qd_buffer_t
> /home/gmurthy/opensource/qpid-dispatch/src/buffer.c:31
> 53: #3 0x7f60bfb641a8 in qd_buffer
> /home/gmurthy/opensource/qpid-dispatch/src/buffer.c:44
> 53: #4 0x7f60bfb64628 in qd_buffer_list_clone
> /home/gmurthy/opensource/qpid-dispatch/src/buffer.c:71
> 53: #5 0x7f60bfbc4d98 in qd_message_copy
> /home/gmurthy/opensource/qpid-dispatch/src/message.c:1030
> 53: #6 0x7f60bfcf9bc9 in qdr_send_to2
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/transfer.c:293
> 53: #7 0x7f60bfcf064f in qdr_management_agent_on_message
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/management_agent.c:534
> 53: #8 0x7f60bfc9f707 in qdr_forward_on_message
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/forwarder.c:310
> 53: #9 0x7f60bfcd7e3c in qdr_general_handler
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:808
> 53: #10 0x7f60bfd7a303 in qd_timer_visit
> /home/gmurthy/opensource/qpid-dispatch/src/timer.c:201
> 53: #11 0x7f60bfd694f5 in handle
> /home/gmurthy/opensource/qpid-dispatch/src/server.c:937
> 53: #12 0x7f60bfd6b153 in thread_run
> /home/gmurthy/opensource/qpid-dispatch/src/server.c:1040
> 53: #13 0x7f60bf7334bf in start_thread (/lib64/libpthread.so.0+0x84bf)
> 53:
> 53: -
> 53: Suppressions used:
> 53: count bytes template
> 53: 5 3008 qd_message_receive
> 53: 2640 qdr_action
> 53: 2760 qdr_core_subscribe
> 53: 1320 qdr_forward_closest_CT
> 53: 2896 qdr_link_deliver
> 53: 1256 qdr_link_issue_credit_CT
> 53: 1192 qdr_delivery_push_CT
> 53:45453371352 *libpython*
> 53: 50788 *python2*
> 53: -
> 53:
> 53: SUMMARY: AddressSanitizer: 704 byte(s) leaked in 1 allocation(s).
> 53:
> 53:
> 53: --
> 53: Ran 90 tests in 240.786s
> 53:
> 53: FAILED (errors=1)
> 1/1 Test #53: system_tests_edge_router .***Failed 240.99 sec
> {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
[jira] [Commented] (DISPATCH-1667) Increase minimum required LibWebSockets version from 2.1.0 to 2.4.2
[ https://issues.apache.org/jira/browse/DISPATCH-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17114225#comment-17114225 ] Ganesh Murthy commented on DISPATCH-1667: - Always appreciate the prodding and yes, this Jira is a placeholder which we will use to increase the min version of LWS to 2.4.2 and yes DISPATCH-1646 effectively raised it to 2.3.0. I think we should link the JIRAs. I will do that. Thanks. > Increase minimum required LibWebSockets version from 2.1.0 to 2.4.2 > --- > > Key: DISPATCH-1667 > URL: https://issues.apache.org/jira/browse/DISPATCH-1667 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Affects Versions: 1.12.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > > LibWebSockets v2.1.0 was released on 2016-10-06 and is quite old. Move to a > more recent version 2.4.2 which was released on 2018-03-07. > 2.4.2 is a stable version and contains features like allowing deleting http > listener ports on demand. -- 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] [Commented] (DISPATCH-1667) Increase minimum required LibWebSockets version from 2.1.0 to 2.4.2
[ https://issues.apache.org/jira/browse/DISPATCH-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17114151#comment-17114151 ] Ganesh Murthy commented on DISPATCH-1667: - The fix for DISPATCH-1646 requires at least LibWebSockets 2.3.0. LibWebSockets 2.4.2 is known to be a stable version. Here is a list of default LWS versions in the following OSes - CentOS 6 No LibWebSockets RHEL 6 LibWebSockets: 2.1.0 (LWS 2.4.2 is available to upgrade) CentOS 7 LibWebSockets: 3.0.1 RHEL 7 LibWebSockets: 2.1.0 (LWS 2.4.2 is available to upgrade) CentOS 8 LibWebSockets: 3.0.1 Ubuntu:Xenial LibWebSockets: 1.7.0 Ubuntu:Bionic LibWebSockets 2.0.3 Ubuntu:latest LibWebSockets 3.2.0 Since RHEL 6 and RHEL 7 can upgrade to LWS 2.4.2, I proposed increasing the least LWS version to 2.4.2. > Increase minimum required LibWebSockets version from 2.1.0 to 2.4.2 > --- > > Key: DISPATCH-1667 > URL: https://issues.apache.org/jira/browse/DISPATCH-1667 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Affects Versions: 1.12.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > > LibWebSockets v2.1.0 was released on 2016-10-06 and is quite old. Move to a > more recent version 2.4.2 which was released on 2018-03-07. > 2.4.2 is a stable version and contains features like allowing deleting http > listener ports on demand. -- 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] [Created] (DISPATCH-1667) Increase minimum required LibWebSockets version from 2.1.0 to 2.4.2
Ganesh Murthy created DISPATCH-1667: --- Summary: Increase minimum required LibWebSockets version from 2.1.0 to 2.4.2 Key: DISPATCH-1667 URL: https://issues.apache.org/jira/browse/DISPATCH-1667 Project: Qpid Dispatch Issue Type: Improvement Components: Container Affects Versions: 1.12.0 Reporter: Ganesh Murthy Assignee: Ganesh Murthy LibWebSockets v2.1.0 was released on 2016-10-06 and is quite old. Move to a more recent version 2.4.2 which was released on 2018-03-07. 2.4.2 is a stable version and contains features like allowing deleting http listener ports on demand. -- 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-1665) Add libwebsockets-dev library to travis
[ https://issues.apache.org/jira/browse/DISPATCH-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1665: Fix Version/s: (was: 2.0.0) Backlog > Add libwebsockets-dev library to travis > --- > > Key: DISPATCH-1665 > URL: https://issues.apache.org/jira/browse/DISPATCH-1665 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests, Tools >Affects Versions: 1.12.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: Backlog > > > The travis build does not install the libwebsockets library. Install it to > see what version is being pulled down -- 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] [Commented] (DISPATCH-1665) Add libwebsockets-dev library to travis
[ https://issues.apache.org/jira/browse/DISPATCH-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17114035#comment-17114035 ] Ganesh Murthy commented on DISPATCH-1665: - Temporarily moving this to backlog > Add libwebsockets-dev library to travis > --- > > Key: DISPATCH-1665 > URL: https://issues.apache.org/jira/browse/DISPATCH-1665 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests, Tools >Affects Versions: 1.12.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 2.0.0 > > > The travis build does not install the libwebsockets library. Install it to > see what version is being pulled down -- 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] [Comment Edited] (DISPATCH-1665) Add libwebsockets-dev library to travis
[
https://issues.apache.org/jira/browse/DISPATCH-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113668#comment-17113668
]
Ganesh Murthy edited comment on DISPATCH-1665 at 5/22/20, 1:33 AM:
---
If no distribution is specified in the travis.yml file, the default OS is
{noformat}
Operating System Details
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Codename: xenial {noformat}
When I included libwebsockets-dev in Xenial, I see the following when compiling
Qpid Dispatch
{noformat}
Found libwebsockets version 1.7.0 but need at least 2.1.0 {noformat}
When I moved travis to use Bionic distribution instead of Xenial, I see the
following when compiling Qpid Dispatch
{noformat}
Found libwebsockets version 2.0.3 but need at least 2.1.0 {noformat}
Locally when I tried ubuntu:latest distribution via a docker file, I see
{noformat}
Found LibWebSockets: 3.2.0 {noformat}
Only the latest version of Ubuntu - Ubuntu 20.04 LTS (Focal Fossa) has a
version of LWS (3.2.0) that is above 2.1.0
Travis does not support the latest Ubuntu distribution (yet). We will have to
wait a while before we can start testing HTTP/LWS based stuff on Travis
was (Author: ganeshmurthy):
If no distribution is specified in the travis.yml file, the default OS is
{noformat}
Operating System Details
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Codename: xenial {noformat}
When I included libwebsockets-dev in Xenial, I see the following when compiling
Qpid Dispatch
{noformat}
Found libwebsockets version 1.7.0 but need at least 2.1.0 {noformat}
When I moved travis to use Bionic distribution instead of Xenial, I see the
following when compiling Qpid Dispatch
{noformat}
Found libwebsockets version 2.0.3 but need at least 2.1.0 {noformat}
Locally when I tried ubuntu:latest distribution via a docker file, I see
{noformat}
Found LibWebSockets: 3.2.0 {noformat}
Only the latest version of Ubuntu - Ubuntu 20.04 LTS (Focal Fossa) has a
version of LWS (3.2.0) that is above 2.1.0
Travis does not support the latest Ubuntu distribution. We will have to wait a
while before we can start testing HTTP/LWS based stuff on Travis
> Add libwebsockets-dev library to travis
> ---
>
> Key: DISPATCH-1665
> URL: https://issues.apache.org/jira/browse/DISPATCH-1665
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests, Tools
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 2.0.0
>
>
> The travis build does not install the libwebsockets library. Install it to
> see what version is being pulled down
--
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] [Commented] (DISPATCH-1665) Add libwebsockets-dev library to travis
[
https://issues.apache.org/jira/browse/DISPATCH-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113668#comment-17113668
]
Ganesh Murthy commented on DISPATCH-1665:
-
If no distribution is specified in the travis.yml file, the default OS is
{noformat}
Operating System Details
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Codename: xenial {noformat}
When I included libwebsockets-dev in Xenial, I see the following when compiling
Qpid Dispatch
{noformat}
Found libwebsockets version 1.7.0 but need at least 2.1.0 {noformat}
When I moved travis to use Bionic distribution instead of Xenial, I see the
following when compiling Qpid Dispatch
{noformat}
Found libwebsockets version 2.0.3 but need at least 2.1.0 {noformat}
Locally when I tried ubuntu:latest distribution via a docker file, I see
{noformat}
Found LibWebSockets: 3.2.0 {noformat}
Only the latest version of Ubuntu - Ubuntu 20.04 LTS (Focal Fossa) has a
version of LWS (3.2.0) that is above 2.1.0
Travis does not support the latest Ubuntu distribution. We will have to wait a
while before we can start testing HTTP/LWS based stuff on Travis
> Add libwebsockets-dev library to travis
> ---
>
> Key: DISPATCH-1665
> URL: https://issues.apache.org/jira/browse/DISPATCH-1665
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests, Tools
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 2.0.0
>
>
> The travis build does not install the libwebsockets library. Install it to
> see what version is being pulled down
--
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-1646) Unable to delete listener with http enabled
[ https://issues.apache.org/jira/browse/DISPATCH-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1646. - Fix Version/s: 1.13.0 Resolution: Fixed > Unable to delete listener with http enabled > --- > > Key: DISPATCH-1646 > URL: https://issues.apache.org/jira/browse/DISPATCH-1646 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Ulf Lilleengen >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.13.0 > > > I'm running into an issue when trying to delete a listener which has 'http: > true' set. The router returns the error message "HTTP listeners cannot be > deleted". I can see that there is a test for this in the router code as well. > However, in order for EnMasse to be able to create and delete listeners that > are used to handle websocket connections for different tenants, we need a way > to delete listeners with http: true set through AMQP management without > restarting the router. -- 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] [Created] (DISPATCH-1665) Add libwebsockets-dev library to travis
Ganesh Murthy created DISPATCH-1665: --- Summary: Add libwebsockets-dev library to travis Key: DISPATCH-1665 URL: https://issues.apache.org/jira/browse/DISPATCH-1665 Project: Qpid Dispatch Issue Type: Bug Components: Tests, Tools Affects Versions: 1.12.0 Reporter: Ganesh Murthy Assignee: Ganesh Murthy Fix For: 2.0.0 The travis build does not install the libwebsockets library. Install it to see what version is being pulled down -- 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] [Assigned] (DISPATCH-1660) Intermittent failure in system_tests_policy_oversize_basic
[
https://issues.apache.org/jira/browse/DISPATCH-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1660:
---
Assignee: Charles E. Rolke
> Intermittent failure in system_tests_policy_oversize_basic
> --
>
> Key: DISPATCH-1660
> URL: https://issues.apache.org/jira/browse/DISPATCH-1660
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Charles E. Rolke
>Priority: Major
>
> {noformat}
> Start 25: system_tests_policy_oversize_basic25: Test command:
> /usr/bin/python "/foo/qpid-dispatch/build/tests/run.py" "-m" "unittest" "-v"
> "system_tests_policy_oversize_basic"
> 25: Test timeout computed to be: 600
> 25: test_40_block_oversize_INTA_INTA
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
> 25: test_41_block_oversize_INTA_INTB
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
> 25: test_42_block_oversize_INTA_EA1
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
> 25: test_43_block_oversize_INTA_EB1
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
> 25: test_44_block_oversize_INTB_INTA
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
> 25: test_45_block_oversize_INTB_INTB
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
> 25: OversizeMessageTransferTest - e46
> 25: 2020-05-20 12:11:40.002177 on_start
> 25: 2020-05-20 12:11:40.002267 on_start: opening receiver connection to
> amqp://0.0.0.0:24197
> 25: 2020-05-20 12:11:40.002545 on_start: opening sender connection to
> amqp://0.0.0.0:24195
> 25: 2020-05-20 12:11:40.002714 on_start: Creating receiver
> 25: 2020-05-20 12:11:40.002878 on_start: Creating sender
> 25: 2020-05-20 12:11:40.002997 on_start: done
> 25: 2020-05-20 12:12:40.003628 self.timeout Timeout Expired: n_sent=0
> n_rcvd=0 n_rejected=0 n_aborted=0
> 25: 2020-05-20 12:12:45.289228 test_46 test error: Timeout Expired: n_sent=0
> n_rcvd=0 n_rejected=0 n_aborted=0
> 25: test_46_block_oversize_INTB_EA1
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... FAIL
> 25: OversizeMessageTransferTest - e47
> 25: 2020-05-20 12:12:45.310757 on_start
> 25: 2020-05-20 12:12:45.310873 on_start: opening receiver connection to
> amqp://0.0.0.0:24199
> 25: 2020-05-20 12:12:45.311197 on_start: opening sender connection to
> amqp://0.0.0.0:24195
> 25: 2020-05-20 12:12:45.311385 on_start: Creating receiver
> 25: 2020-05-20 12:12:45.311570 on_start: Creating sender
> 25: 2020-05-20 12:12:45.311701 on_start: done
> 25: 2020-05-20 12:13:45.311633 self.timeout Timeout Expired: n_sent=0
> n_rcvd=0 n_rejected=0 n_aborted=0
> 25: 2020-05-20 12:13:48.055263 test_47 test error: Timeout Expired: n_sent=0
> n_rcvd=0 n_rejected=0 n_aborted=0
> 25: test_47_block_oversize_INTB_EB1
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... FAIL
> 25: test_48_block_oversize_EA1_INTA
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
> 25: OversizeMessageTransferTest - e49
> 25: 2020-05-20 12:13:48.275921 on_start
> 25: 2020-05-20 12:13:48.275995 on_start: opening receiver connection to
> amqp://0.0.0.0:24195
> 25: 2020-05-20 12:13:48.276285 on_start: opening sender connection to
> amqp://0.0.0.0:24197
> 25: 2020-05-20 12:13:48.276454 on_start: Creating receiver
> 25: 2020-05-20 12:13:48.276615 on_start: Creating sender
> 25: 2020-05-20 12:13:48.276735 on_start: done
> 25: 2020-05-20 12:14:48.277283 self.timeout Timeout Expired: n_sent=0
> n_rcvd=0 n_rejected=0 n_aborted=0
> 25: 2020-05-20 12:14:51.017235 test_49 test error: Timeout Expired: n_sent=0
> n_rcvd=0 n_rejected=0 n_aborted=0
> 25: test_49_block_oversize_EA1_INTB
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... FAIL
> 25: test_4a_block_oversize_EA1_EA1
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
> 25: OversizeMessageTransferTest - e4b
> 25: 2020-05-20 12:14:51.235405 on_start
> 25: 2020-05-20 12:14:51.235481 on_start: opening receiver connection to
> amqp://0.0.0.0:24199
> 25: 2020-05-20 12:14:51.235753 on_start: opening sender connection to
> amqp://0.0.0.0:24197
> 25: 2020-05-20 12:14:51.235920 on_start: Creating receiver
> 25: 2020-05-20 12:14:51.236082 on_start: Creating sender
> 25: 2020-05-20 12:14:51.236201 on_start: done
> 25: 2020-05-20 12:15:51.236483 self.timeout Timeout Expired: n_sent=0
> n_rcvd=0 n_rejected=0 n_aborted=0
> 25: 2020-05-20 12:15:51.246181 test_4b test error: Timeout Expired: n_sent=0
> n_rcvd=0 n_rejected=0 n_aborted=0
> 25: test_4b_block_oversize_EA1_EB1
> (system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ...
[jira] [Assigned] (DISPATCH-1497) [test] system_tests_fallback_dest test times out occasionally
[
https://issues.apache.org/jira/browse/DISPATCH-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1497:
---
Assignee: Ted Ross
> [test] system_tests_fallback_dest test times out occasionally
> -
>
> Key: DISPATCH-1497
> URL: https://issues.apache.org/jira/browse/DISPATCH-1497
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node, Tools
>Affects Versions: 1.9.0
> Environment: Fedora 29. Proton 0.29.0
>Reporter: Charles E. Rolke
>Assignee: Ted Ross
>Priority: Major
>
> The fallback_dest typically completes in 40-45 seconds on my machine.
> Occasionally, the test times out with:
> {noformat}
> 61: File
> "/home/chug/git/qpid-dispatch/tests/system_tests_fallback_dest.py", line 350,
> in test_35_switchover_mix_1
> 61: self.assertEqual(None, test.error)
> 61: AssertionError: None != 'Timeout Expired - n_tx=0, n_rx=0, n_rel=2799,
> phase=1'
> 61: Ran 50 tests in 100.831s
> {noformat}
> Increasing the test timeout from 60 to 240 seconds produces the same result
> but it takes a total of 280 seconds.
> In all recorded failures the counters n_tx=0 and n_rx=0 are the same. The
> n_rel varies around 2800 (2799, 2816).
> The most successful loops before a failure was 120. Usually it fails in
> around 10 loops.
>
--
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] [Created] (DISPATCH-1664) test_verify_z_connection_stats failing in system_tests_policy
Ganesh Murthy created DISPATCH-1664:
---
Summary: test_verify_z_connection_stats failing in
system_tests_policy
Key: DISPATCH-1664
URL: https://issues.apache.org/jira/browse/DISPATCH-1664
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
system_tests_policy, SenderReceiverLimits, test_verify_z_connection_stats:
delay to wait for log to be written
system_tests_policy, SenderReceiverLimits, test_verify_z_connection_stats:
delay to wait for log to be written
system_tests_policy, SenderReceiverLimits, test_verify_z_connection_stats:
delay to wait for log to be written
system_tests_policy, SenderReceiverLimits, test_verify_z_connection_stats:
delay to wait for log to be written
system_tests_policy, SenderReceiverLimits, test_verify_z_connection_stats:
delay to wait for log to be written
test_verify_z_connection_stats (system_tests_policy.SenderReceiverLimits) ...
FAIL
test_verify_vhost_maximum_connections_override
(system_tests_policy.VhostPolicyConnLimit) ... ok
test_verify_vhost_maximum_connections
(system_tests_policy.VhostPolicyFromRouterConfig) ... ok
test_vhost_allowed_addresses (system_tests_policy.VhostPolicyFromRouterConfig)
... ok
test_vhost_denied_addresses (system_tests_policy.VhostPolicyFromRouterConfig)
... ok
test_01_id_vs_hostname (system_tests_policy.VhostPolicyNameField) ...
ok==
FAIL: test_verify_z_connection_stats (system_tests_policy.SenderReceiverLimits)
--
Traceback (most recent call last):
File "/opt/qpid-dispatch-src/tests/system_tests_policy.py", line 347, in
test_verify_z_connection_stats
self.assertTrue(verified, msg='Policy did not log sender and receiver
denials.')
AssertionError: False is not true : Policy did not log sender and receiver
denials.--
Ran 24 tests in 59.500sFAILED (failures=1) {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
[jira] [Created] (DISPATCH-1663) system_tests_edge_router fails with ASAN leak
Ganesh Murthy created DISPATCH-1663:
---
Summary: system_tests_edge_router fails with ASAN leak
Key: DISPATCH-1663
URL: https://issues.apache.org/jira/browse/DISPATCH-1663
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
53: ==
53: ERROR: test_03_interior_conn_lost
(system_tests_edge_router.LinkRouteProxyTest)
53: --
53: Traceback (most recent call last):
53: File
"/home/gmurthy/opensource/qpid-dispatch/tests/system_tests_edge_router.py",
line 1859, in test_03_interior_conn_lost
53: er.teardown()
53: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py", line
442, in teardown
53: super(Qdrouterd, self).teardown()
53: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py", line
295, in teardown
53: error("exit code %s, expected %s" % (status, self.expect))
53: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py", line
285, in error
53: self.outfile + '.cmd', f.read()));
53: RuntimeError: Process 16556 error: exit code 1, expected 0
53: qdrouterd -c Edge1.conf -I /home/gmurthy/opensource/qpid-dispatch/python
53:
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_edge_router/LinkRouteProxyTest/test_03_interior_conn_lost/Edge1-9.cmd
53:
53:
53: =
53: ==16556==ERROR: LeakSanitizer: detected memory leaks
53:
53: Indirect leak of 704 byte(s) in 1 object(s) allocated from:
53: #0 0x7f60c03a3bf5 in __interceptor_posix_memalign
(/lib64/libasan.so.5+0x10ebf5)
53: #1 0x7f60bfb5ace3 in qd_alloc
/home/gmurthy/opensource/qpid-dispatch/src/alloc_pool.c:347
53: #2 0x7f60bfb63e62 in new_qd_buffer_t
/home/gmurthy/opensource/qpid-dispatch/src/buffer.c:31
53: #3 0x7f60bfb641a8 in qd_buffer
/home/gmurthy/opensource/qpid-dispatch/src/buffer.c:44
53: #4 0x7f60bfb64628 in qd_buffer_list_clone
/home/gmurthy/opensource/qpid-dispatch/src/buffer.c:71
53: #5 0x7f60bfbc4d98 in qd_message_copy
/home/gmurthy/opensource/qpid-dispatch/src/message.c:1030
53: #6 0x7f60bfcf9bc9 in qdr_send_to2
/home/gmurthy/opensource/qpid-dispatch/src/router_core/transfer.c:293
53: #7 0x7f60bfcf064f in qdr_management_agent_on_message
/home/gmurthy/opensource/qpid-dispatch/src/router_core/management_agent.c:534
53: #8 0x7f60bfc9f707 in qdr_forward_on_message
/home/gmurthy/opensource/qpid-dispatch/src/router_core/forwarder.c:310
53: #9 0x7f60bfcd7e3c in qdr_general_handler
/home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core.c:808
53: #10 0x7f60bfd7a303 in qd_timer_visit
/home/gmurthy/opensource/qpid-dispatch/src/timer.c:201
53: #11 0x7f60bfd694f5 in handle
/home/gmurthy/opensource/qpid-dispatch/src/server.c:937
53: #12 0x7f60bfd6b153 in thread_run
/home/gmurthy/opensource/qpid-dispatch/src/server.c:1040
53: #13 0x7f60bf7334bf in start_thread (/lib64/libpthread.so.0+0x84bf)
53:
53: -
53: Suppressions used:
53: count bytes template
53: 5 3008 qd_message_receive
53: 2640 qdr_action
53: 2760 qdr_core_subscribe
53: 1320 qdr_forward_closest_CT
53: 2896 qdr_link_deliver
53: 1256 qdr_link_issue_credit_CT
53: 1192 qdr_delivery_push_CT
53:45453371352 *libpython*
53: 50788 *python2*
53: -
53:
53: SUMMARY: AddressSanitizer: 704 byte(s) leaked in 1 allocation(s).
53:
53:
53: --
53: Ran 90 tests in 240.786s
53:
53: FAILED (errors=1)
1/1 Test #53: system_tests_edge_router .***Failed 240.99 sec
{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
[jira] [Updated] (DISPATCH-1497) [test] system_tests_fallback_dest test times out occasionally
[
https://issues.apache.org/jira/browse/DISPATCH-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1497:
Summary: [test] system_tests_fallback_dest test times out occasionally
(was: [test] system tests fallback_dest test times out occasionally)
> [test] system_tests_fallback_dest test times out occasionally
> -
>
> Key: DISPATCH-1497
> URL: https://issues.apache.org/jira/browse/DISPATCH-1497
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node, Tools
>Affects Versions: 1.9.0
> Environment: Fedora 29. Proton 0.29.0
>Reporter: Charles E. Rolke
>Priority: Major
>
> The fallback_dest typically completes in 40-45 seconds on my machine.
> Occasionally, the test times out with:
> {noformat}
> 61: File
> "/home/chug/git/qpid-dispatch/tests/system_tests_fallback_dest.py", line 350,
> in test_35_switchover_mix_1
> 61: self.assertEqual(None, test.error)
> 61: AssertionError: None != 'Timeout Expired - n_tx=0, n_rx=0, n_rel=2799,
> phase=1'
> 61: Ran 50 tests in 100.831s
> {noformat}
> Increasing the test timeout from 60 to 240 seconds produces the same result
> but it takes a total of 280 seconds.
> In all recorded failures the counters n_tx=0 and n_rx=0 are the same. The
> n_rel varies around 2800 (2799, 2816).
> The most successful loops before a failure was 120. Usually it fails in
> around 10 loops.
>
--
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] [Created] (DISPATCH-1662) system_tests_policy_oversize_compound fails with ASAN leak
Ganesh Murthy created DISPATCH-1662:
---
Summary: system_tests_policy_oversize_compound fails with ASAN leak
Key: DISPATCH-1662
URL: https://issues.apache.org/jira/browse/DISPATCH-1662
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
26: Test command: /usr/bin/python
"/home/travis/build/apache/qpid-dispatch/build/tests/run.py" "-m" "unittest"
"-v" "system_tests_policy_oversize_compound"
26: Test timeout computed to be: 600
26: test_60_block_oversize_EB1_INTB_at_INTB
(system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
26: test_61_block_oversize_EB1_EA1_at_INTB
(system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
26: test_70_block_oversize_EB1_INTB_at_both
(system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
26: test_80_block_multicast_EB1_INTB_at_INTB
(system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
26: test_81_block_multicast_EA1
(system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
26: test_82_block_multicast_INTA
(system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize) ... ok
26:
26: Router EA1 debug dump file:
26: alloc.c: Items of type 'qd_iterator_t' remain allocated at shutdown: 12
26: alloc.c: Items of type 'qd_buffer_t' remain allocated at shutdown: 3
26: alloc.c: Items of type 'qd_parsed_field_t' remain allocated at shutdown: 5
26: alloc.c: Items of type 'qd_message_t' remain allocated at shutdown: 1
26: alloc.c: Items of type 'qd_message_content_t' remain allocated at shutdown:
1
26: alloc.c: Items of type 'qdr_delivery_t' remain allocated at shutdown: 1
26: alloc.c: Items of type 'qd_link_ref_t' remain allocated at shutdown: 1
26: ERROR
26: test_90_block_link_route_EB1_INTB
(system_tests_policy_oversize_compound.MaxMessageSizeLinkRouteOversize) ... ok
26:
26: Router INT.B debug dump file:
26: alloc.c: Items of type 'qd_timer_t' remain allocated at shutdown: 2
26: alloc.c: Items of type 'qd_connector_t' remain allocated at shutdown: 2
26:
26: ==
26: ERROR: tearDownClass
(system_tests_policy_oversize_compound.MaxMessageSizeBlockOversize)
26: --
26: Traceback (most recent call last):
26: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py", line
691, in tearDownClass
26: cls.tester.teardown()
26: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py", line
637, in teardown
26: raise RuntimeError("Errors during teardown: \n\n%s" %
"\n\n".join([str(e) for e in errors]))
26: RuntimeError: Errors during teardown:
26:
26: Process 12913 error: exit code 23, expected 0
26: qdrouterd -c INT.B.conf -I /home/travis/build/apache/qpid-dispatch/python
26:
/home/travis/build/apache/qpid-dispatch/build/tests/system_test.dir/system_tests_policy_oversize_compound/MaxMessageSizeBlockOversize/setUpClass/INT.B-2.cmd
26:
26:
26: =
26: ==12913==ERROR: LeakSanitizer: detected memory leaks
26:
26: Indirect leak of 576 byte(s) in 3 object(s) allocated from:
26: #0 0x7fd7c490a076 in __interceptor_posix_memalign
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x99076)
26: #1 0x7fd7c41e4d28 in qd_alloc
/home/travis/build/apache/qpid-dispatch/src/alloc_pool.c:347
26: #2 0x7fd7c4240c41 in qd_iterator_buffer
/home/travis/build/apache/qpid-dispatch/src/iterator.c:597
26: #3 0x7fd7c42f6d2d in qdr_field
/home/travis/build/apache/qpid-dispatch/src/router_core/router_core.c:265
26: #4 0x7fd7c431231f in qdr_terminus
/home/travis/build/apache/qpid-dispatch/src/router_core/terminus.c:47
26: #5 0x7fd7c434ca3b in AMQP_incoming_link_handler
/home/travis/build/apache/qpid-dispatch/src/router_node.c:817
26: #6 0x7fd7c4362674 in handle
/home/travis/build/apache/qpid-dispatch/src/server.c:1015
26: #7 0x7fd7c436819f in thread_run
/home/travis/build/apache/qpid-dispatch/src/server.c:1040
26: #8 0x7fd7c3d726b9 in start_thread
(/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9)
26:
26: -26: Suppressions used:
26: count bytes template
26: 2 1216 qd_message_receive
26: 13 4368 qdr_core_subscribe
26: 1192 qdr_forward_closest_CT
26: 1320 qdr_link_deliver
26: 1 64 qdr_node_connect_deliveries
26: 1 64 qdr_link_issue_credit_CT
26: 28 70 __strdup
26: 1128 qd_parse_internal
26:46153404212 *libpython*
26: 37120 *python2*
26: -
26:
26: SUMMARY: AddressSanitizer: 576 byte(s) leaked in 3 allocation(s).
26:
[jira] [Created] (DISPATCH-1661) system_tests_edge_router fails with ASAN leak
Ganesh Murthy created DISPATCH-1661:
---
Summary: system_tests_edge_router fails with ASAN leak
Key: DISPATCH-1661
URL: https://issues.apache.org/jira/browse/DISPATCH-1661
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
53: Router EB1 debug dump file:
53: alloc.c: Items of type 'qd_timer_t' remain allocated at shutdown: 2
53: alloc.c: Items of type 'qd_connector_t' remain allocated at shutdown: 2
53: ERROR
53:
53: ==
53: ERROR: tearDownClass (system_tests_edge_router.StreamingMessageTest)
53: --
53: Traceback (most recent call last):
53: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py", line
691, in tearDownClass
53: cls.tester.teardown()
53: File "/home/travis/build/apache/qpid-dispatch/tests/system_test.py", line
637, in teardown
53: raise RuntimeError("Errors during teardown: \n\n%s" %
"\n\n".join([str(e) for e in errors]))
53: RuntimeError: Errors during teardown:
53:
53: Process 14572 error: exit code 23, expected 0
53: qdrouterd -c EA1.conf -I /home/travis/build/apache/qpid-dispatch/python
53:
/home/travis/build/apache/qpid-dispatch/build/tests/system_test.dir/system_tests_edge_router/StreamingMessageTest/setUpClass/EA1-18.cmd
53:
53:
53: =
53: ==14572==ERROR: LeakSanitizer: detected memory leaks
53:
53: Indirect leak of 7488 byte(s) in 13 object(s) allocated from:
53: #0 0x7fdea74bb076 in __interceptor_posix_memalign
(/usr/lib/x86_64-linux-gnu/libasan.so.2+0x99076)
53: #1 0x7fdea6d95d28 in qd_alloc
/home/travis/build/apache/qpid-dispatch/src/alloc_pool.c:347
53: #2 0x7fdea6d9fddd in qd_buffer
/home/travis/build/apache/qpid-dispatch/src/buffer.c:44
53: #3 0x7fdea6ea7b8a in qdr_field
/home/travis/build/apache/qpid-dispatch/src/router_core/router_core.c:255
53: #4 0x7fdea6ec331f in qdr_terminus
/home/travis/build/apache/qpid-dispatch/src/router_core/terminus.c:47
53: #5 0x7fdea6efd6dd in AMQP_link_attach_handler
/home/travis/build/apache/qpid-dispatch/src/router_node.c:866
53: #6 0x7fdea6f13674 in handle
/home/travis/build/apache/qpid-dispatch/src/server.c:1015
53: #7 0x7fdea6f1919f in thread_run
/home/travis/build/apache/qpid-dispatch/src/server.c:1040
53: #8 0x7fdea69236b9 in start_thread
(/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9)
53:
53: -
53: Suppressions used:
53: count bytes template
53: 18 10944 qd_core_agent_query_handler
53: 73 41536 qd_message_receive
53: 13 7488 qdr_connection_opened
53: 15 8120 qdr_core_subscribe
53: 1192 qdr_link_deliver
53:3311244 *libpython*
53: 37120 *python2*
53: -
53:
53: SUMMARY: AddressSanitizer: 7488 byte(s) leaked in 13 allocation(s).
53:
53:
53: --
53: Ran 90 tests in 241.217s
53:
53: FAILED (errors=1)53/66 Test #53: system_tests_edge_router
..***Failed 241.32 sec {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
[jira] [Created] (DISPATCH-1660) Intermittent failure in system_tests_policy_oversize_basic
Ganesh Murthy created DISPATCH-1660:
---
Summary: Intermittent failure in system_tests_policy_oversize_basic
Key: DISPATCH-1660
URL: https://issues.apache.org/jira/browse/DISPATCH-1660
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
Start 25: system_tests_policy_oversize_basic25: Test command:
/usr/bin/python "/foo/qpid-dispatch/build/tests/run.py" "-m" "unittest" "-v"
"system_tests_policy_oversize_basic"
25: Test timeout computed to be: 600
25: test_40_block_oversize_INTA_INTA
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
25: test_41_block_oversize_INTA_INTB
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
25: test_42_block_oversize_INTA_EA1
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
25: test_43_block_oversize_INTA_EB1
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
25: test_44_block_oversize_INTB_INTA
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
25: test_45_block_oversize_INTB_INTB
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
25: OversizeMessageTransferTest - e46
25: 2020-05-20 12:11:40.002177 on_start
25: 2020-05-20 12:11:40.002267 on_start: opening receiver connection to
amqp://0.0.0.0:24197
25: 2020-05-20 12:11:40.002545 on_start: opening sender connection to
amqp://0.0.0.0:24195
25: 2020-05-20 12:11:40.002714 on_start: Creating receiver
25: 2020-05-20 12:11:40.002878 on_start: Creating sender
25: 2020-05-20 12:11:40.002997 on_start: done
25: 2020-05-20 12:12:40.003628 self.timeout Timeout Expired: n_sent=0 n_rcvd=0
n_rejected=0 n_aborted=0
25: 2020-05-20 12:12:45.289228 test_46 test error: Timeout Expired: n_sent=0
n_rcvd=0 n_rejected=0 n_aborted=0
25: test_46_block_oversize_INTB_EA1
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... FAIL
25: OversizeMessageTransferTest - e47
25: 2020-05-20 12:12:45.310757 on_start
25: 2020-05-20 12:12:45.310873 on_start: opening receiver connection to
amqp://0.0.0.0:24199
25: 2020-05-20 12:12:45.311197 on_start: opening sender connection to
amqp://0.0.0.0:24195
25: 2020-05-20 12:12:45.311385 on_start: Creating receiver
25: 2020-05-20 12:12:45.311570 on_start: Creating sender
25: 2020-05-20 12:12:45.311701 on_start: done
25: 2020-05-20 12:13:45.311633 self.timeout Timeout Expired: n_sent=0 n_rcvd=0
n_rejected=0 n_aborted=0
25: 2020-05-20 12:13:48.055263 test_47 test error: Timeout Expired: n_sent=0
n_rcvd=0 n_rejected=0 n_aborted=0
25: test_47_block_oversize_INTB_EB1
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... FAIL
25: test_48_block_oversize_EA1_INTA
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
25: OversizeMessageTransferTest - e49
25: 2020-05-20 12:13:48.275921 on_start
25: 2020-05-20 12:13:48.275995 on_start: opening receiver connection to
amqp://0.0.0.0:24195
25: 2020-05-20 12:13:48.276285 on_start: opening sender connection to
amqp://0.0.0.0:24197
25: 2020-05-20 12:13:48.276454 on_start: Creating receiver
25: 2020-05-20 12:13:48.276615 on_start: Creating sender
25: 2020-05-20 12:13:48.276735 on_start: done
25: 2020-05-20 12:14:48.277283 self.timeout Timeout Expired: n_sent=0 n_rcvd=0
n_rejected=0 n_aborted=0
25: 2020-05-20 12:14:51.017235 test_49 test error: Timeout Expired: n_sent=0
n_rcvd=0 n_rejected=0 n_aborted=0
25: test_49_block_oversize_EA1_INTB
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... FAIL
25: test_4a_block_oversize_EA1_EA1
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... ok
25: OversizeMessageTransferTest - e4b
25: 2020-05-20 12:14:51.235405 on_start
25: 2020-05-20 12:14:51.235481 on_start: opening receiver connection to
amqp://0.0.0.0:24199
25: 2020-05-20 12:14:51.235753 on_start: opening sender connection to
amqp://0.0.0.0:24197
25: 2020-05-20 12:14:51.235920 on_start: Creating receiver
25: 2020-05-20 12:14:51.236082 on_start: Creating sender
25: 2020-05-20 12:14:51.236201 on_start: done
25: 2020-05-20 12:15:51.236483 self.timeout Timeout Expired: n_sent=0 n_rcvd=0
n_rejected=0 n_aborted=0
25: 2020-05-20 12:15:51.246181 test_4b test error: Timeout Expired: n_sent=0
n_rcvd=0 n_rejected=0 n_aborted=0
25: test_4b_block_oversize_EA1_EB1
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... FAIL
25: test_4c_block_oversize_EB1_INTA
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... skipped
'EB1 sending to INT.A may be blocked by EB1 limit and also by INT.B limit. That
condition is tested in compound test.'
25: test_4d_block_oversize_EB1_INTB
(system_tests_policy_oversize_basic.MaxMessageSizeBlockOversize) ... skipped
'EB1 sending to INT.B may be blocked by EB1 limit and also by INT.B limit. That
condition is
[jira] [Resolved] (DISPATCH-1658) Receiver unable to receive messages on waypointed addresses
[ https://issues.apache.org/jira/browse/DISPATCH-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1658. - Fix Version/s: 1.13.0 Resolution: Fixed > Receiver unable to receive messages on waypointed addresses > --- > > Key: DISPATCH-1658 > URL: https://issues.apache.org/jira/browse/DISPATCH-1658 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.12.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.13.0 > > Attachments: EA1.conf, EA2.conf, EB1.conf, EB2.conf, INT.A.conf, > INT.B.conf > > > To reproduce > > # Start a broker on port amqp > # Use the attached configs and start the routers > # Send 200 messages on the waypointed address "examples" by connecting to > the EA2 router like this python simple_send.py --address > 0.0.0.0:28100/examples -m200. Make sure the messages reached the broker queue. > # Now receive one message from the same EA2 router - python simple_recv.py > --address 0.0.0.0:28100/examples -m1 - this will work > # Repeat step 4 more time. This receive will not work -- 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] [Commented] (DISPATCH-1658) Receiver unable to receive messages on waypointed addresses
[ https://issues.apache.org/jira/browse/DISPATCH-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17110481#comment-17110481 ] Ganesh Murthy commented on DISPATCH-1658: - I acccidentally commited the fix to this issue with the Jira number as DISPATCH-1614 This commit should fix the issue - https://github.com/apache/qpid-dispatch/commit/fdbe7c9ab68492c6902b60959f31371c42258aa8 > Receiver unable to receive messages on waypointed addresses > --- > > Key: DISPATCH-1658 > URL: https://issues.apache.org/jira/browse/DISPATCH-1658 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.12.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Attachments: EA1.conf, EA2.conf, EB1.conf, EB2.conf, INT.A.conf, > INT.B.conf > > > To reproduce > > # Start a broker on port amqp > # Use the attached configs and start the routers > # Send 200 messages on the waypointed address "examples" by connecting to > the EA2 router like this python simple_send.py --address > 0.0.0.0:28100/examples -m200. Make sure the messages reached the broker queue. > # Now receive one message from the same EA2 router - python simple_recv.py > --address 0.0.0.0:28100/examples -m1 - this will work > # Repeat step 4 more time. This receive will not work -- 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] [Closed] (DISPATCH-1614) Edge router crash when interior closes edge uplink connection
[ https://issues.apache.org/jira/browse/DISPATCH-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy closed DISPATCH-1614. --- > Edge router crash when interior closes edge uplink connection > - > > Key: DISPATCH-1614 > URL: https://issues.apache.org/jira/browse/DISPATCH-1614 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.11.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.12.0 > > Attachments: DISPATCH-1614-edge-router-log.txt > > > When the connection to the interior router goes down then the > addr.edge_outlink link proper is freed but the pointer to the link is still > in the addr struct. > Later when the addr is unbound the link is dereferenced causing a segfault. > An attached log trace shows the events. Search for link _0x1c31210_ using > mobile address _M0e61_. -- 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-1614) Edge router crash when interior closes edge uplink connection
[ https://issues.apache.org/jira/browse/DISPATCH-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1614. - Resolution: Fixed > Edge router crash when interior closes edge uplink connection > - > > Key: DISPATCH-1614 > URL: https://issues.apache.org/jira/browse/DISPATCH-1614 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.11.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.12.0 > > Attachments: DISPATCH-1614-edge-router-log.txt > > > When the connection to the interior router goes down then the > addr.edge_outlink link proper is freed but the pointer to the link is still > in the addr struct. > Later when the addr is unbound the link is dereferenced causing a segfault. > An attached log trace shows the events. Search for link _0x1c31210_ using > mobile address _M0e61_. -- 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-1614) Edge router crash when interior closes edge uplink connection
[ https://issues.apache.org/jira/browse/DISPATCH-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reopened DISPATCH-1614: - > Edge router crash when interior closes edge uplink connection > - > > Key: DISPATCH-1614 > URL: https://issues.apache.org/jira/browse/DISPATCH-1614 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.11.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.12.0 > > Attachments: DISPATCH-1614-edge-router-log.txt > > > When the connection to the interior router goes down then the > addr.edge_outlink link proper is freed but the pointer to the link is still > in the addr struct. > Later when the addr is unbound the link is dereferenced causing a segfault. > An attached log trace shows the events. Search for link _0x1c31210_ using > mobile address _M0e61_. -- 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] [Commented] (DISPATCH-1658) Receiver unable to receive messages on waypointed addresses
[ https://issues.apache.org/jira/browse/DISPATCH-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17108504#comment-17108504 ] Ganesh Murthy commented on DISPATCH-1658: - This bug is a regression and it is a direct result of fix for DISPATCH-1614 > Receiver unable to receive messages on waypointed addresses > --- > > Key: DISPATCH-1658 > URL: https://issues.apache.org/jira/browse/DISPATCH-1658 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.12.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Attachments: EA1.conf, EA2.conf, EB1.conf, EB2.conf, INT.A.conf, > INT.B.conf > > > To reproduce > > # Start a broker on port amqp > # Use the attached configs and start the routers > # Send 200 messages on the waypointed address "examples" by connecting to > the EA2 router like this python simple_send.py --address > 0.0.0.0:28100/examples -m200. Make sure the messages reached the broker queue. > # Now receive one message from the same EA2 router - python simple_recv.py > --address 0.0.0.0:28100/examples -m1 - this will work > # Repeat step 4 more time. This receive will not work -- 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-1658) Receiver unable to receive messages on waypointed addresses
[ https://issues.apache.org/jira/browse/DISPATCH-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1658: Attachment: EA1.conf EA2.conf INT.A.conf EB1.conf EB2.conf INT.B.conf EA1-qddebug.txt > Receiver unable to receive messages on waypointed addresses > --- > > Key: DISPATCH-1658 > URL: https://issues.apache.org/jira/browse/DISPATCH-1658 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.12.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Attachments: EA1.conf, EA2.conf, EB1.conf, EB2.conf, INT.A.conf, > INT.B.conf > > > To reproduce > > # Start a broker on port amqp > # Use the attached configs and start the routers > # Send 200 messages on the waypointed address "examples" by connecting to > the EA2 router like this python simple_send.py --address > 0.0.0.0:28100/examples -m200. Make sure the messages reached the broker queue. > # Now receive one message from the same EA2 router - python simple_recv.py > --address 0.0.0.0:28100/examples -m1 - this will work > # Repeat step 4 more time. This receive will not work -- 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-1658) Receiver unable to receive messages on waypointed addresses
[ https://issues.apache.org/jira/browse/DISPATCH-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1658: Attachment: (was: EA1-qddebug.txt) > Receiver unable to receive messages on waypointed addresses > --- > > Key: DISPATCH-1658 > URL: https://issues.apache.org/jira/browse/DISPATCH-1658 > Project: Qpid Dispatch > Issue Type: Bug > Components: Container >Affects Versions: 1.12.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Attachments: EA1.conf, EA2.conf, EB1.conf, EB2.conf, INT.A.conf, > INT.B.conf > > > To reproduce > > # Start a broker on port amqp > # Use the attached configs and start the routers > # Send 200 messages on the waypointed address "examples" by connecting to > the EA2 router like this python simple_send.py --address > 0.0.0.0:28100/examples -m200. Make sure the messages reached the broker queue. > # Now receive one message from the same EA2 router - python simple_recv.py > --address 0.0.0.0:28100/examples -m1 - this will work > # Repeat step 4 more time. This receive will not work -- 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] [Created] (DISPATCH-1658) Receiver unable to receive messages on waypointed addresses
Ganesh Murthy created DISPATCH-1658: --- Summary: Receiver unable to receive messages on waypointed addresses Key: DISPATCH-1658 URL: https://issues.apache.org/jira/browse/DISPATCH-1658 Project: Qpid Dispatch Issue Type: Bug Components: Container Affects Versions: 1.12.0 Reporter: Ganesh Murthy Assignee: Ganesh Murthy To reproduce # Start a broker on port amqp # Use the attached configs and start the routers # Send 200 messages on the waypointed address "examples" by connecting to the EA2 router like this python simple_send.py --address 0.0.0.0:28100/examples -m200. Make sure the messages reached the broker queue. # Now receive one message from the same EA2 router - python simple_recv.py --address 0.0.0.0:28100/examples -m1 - this will work # Repeat step 4 more time. This receive will not work -- 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] [Created] (DISPATCH-1657) system_tests_router_mesh ASAN failure
Ganesh Murthy created DISPATCH-1657:
---
Summary: system_tests_router_mesh ASAN failure
Key: DISPATCH-1657
URL: https://issues.apache.org/jira/browse/DISPATCH-1657
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Reporter: Ganesh Murthy
{noformat}
63: Test command: /usr/bin/python
"/home/gmurthy/opensource/qpid-dispatch/build/tests/run.py" "-m" "unittest"
"-v" "system_tests_router_mesh"
63: Test timeout computed to be: 600
63: test_01_rx_failover_clean (system_tests_router_mesh.ThreeRouterTest) ... ok
63: test_02_rx_failover_dirty (system_tests_router_mesh.ThreeRouterTest) ... ok
63: test_03_unavailable_link_attach (system_tests_router_mesh.ThreeRouterTest)
... ok
63: test_04_unavailable_anonymous_link_attach
(system_tests_router_mesh.ThreeRouterTest) ... ok
63: test_05_unavailable_anonymous_link_send
(system_tests_router_mesh.ThreeRouterTest) ... ok
63: test_06_parallel_priority (system_tests_router_mesh.ThreeRouterTest) ...
ERROR
63: ERROR
==
63: ERROR: test_06_parallel_priority (system_tests_router_mesh.ThreeRouterTest)
63: --
63: Traceback (most recent call last):
63: File
"/home/gmurthy/opensource/qpid-dispatch/tests/system_tests_router_mesh.py",
line 232, in test_06_parallel_priority
63: if rx.wait(timeout=TIMEOUT):
63: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py", line
311, in wait
63: raise Exception("Process did not terminate")
63: Exception: Process did not terminate
63:
63: ==
63: ERROR: test_06_parallel_priority (system_tests_router_mesh.ThreeRouterTest)
63: --
63: Traceback (most recent call last):
63: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py", line
713, in tearDown
63: Tester.teardown(self)
63: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py", line
637, in teardown
63: raise RuntimeError("Errors during teardown: \n\n%s" %
"\n\n".join([str(e) for e in errors]))
63: RuntimeError: Errors during teardown:
63:
63: Process 17794 error: still running
63: test-receiver -a 127.0.0.1:29417 -c 250 -s closest/test_06_address
63:
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_router_mesh/ThreeRouterTest/test_06_parallel_priority/test-receiver-45.cmd
63:
63:
63:
63: ==
63: ERROR: tearDownClass (system_tests_router_mesh.ThreeRouterTest)
63: --
63: Traceback (most recent call last):
63: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py", line
691, in tearDownClass
63: cls.tester.teardown()
63: File "/home/gmurthy/opensource/qpid-dispatch/tests/system_test.py", line
637, in teardown
63: raise RuntimeError("Errors during teardown: \n\n%s" %
"\n\n".join([str(e) for e in errors]))
63: RuntimeError: Errors during teardown:
63:
63: Process 17635 error: exit code 1, expected -1
63: qdrouterd -c RouterA.conf -I /home/gmurthy/opensource/qpid-dispatch/python
63:
/home/gmurthy/opensource/qpid-dispatch/build/tests/system_test.dir/system_tests_router_mesh/ThreeRouterTest/setUpClass/RouterA-1.cmd
63:
63: =
63: ==17635==ERROR: AddressSanitizer: heap-buffer-overflow on address
0x619000100978 at pc 0x7f04fafcbe12 bp 0x7f04e854afa0 sp 0x7f04e854af90
63: READ of size 8 at 0x619000100978 thread T1
63: #0 0x7f04fafcbe11 in qdr_forward_closest_CT
/home/gmurthy/opensource/qpid-dispatch/src/router_core/forwarder.c:668
63: #1 0x7f04fafd3016 in qdr_forward_message_CT
/home/gmurthy/opensource/qpid-dispatch/src/router_core/forwarder.c:1054
63: #2 0x7f04fb022bca in qdr_link_forward_CT
/home/gmurthy/opensource/qpid-dispatch/src/router_core/transfer.c:481
63: #3 0x7f04fb028c9d in qdr_link_deliver_CT
/home/gmurthy/opensource/qpid-dispatch/src/router_core/transfer.c:772
63: #4 0x7f04fb004c92 in router_core_thread
/home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core_thread.c:193
63: #5 0x7f04faa594bf in start_thread (/lib64/libpthread.so.0+0x84bf)
63: #6 0x7f04f9d4f132 in clone (/lib64/libc.so.6+0xfc132)
63:
63: 0x619000100978 is located 8 bytes to the left of 1024-byte region
[0x619000100980,0x619000100d80)
63: allocated by thread T1 here:
63: #0 0x7f04fb6c8d18 in __interceptor_malloc (/lib64/libasan.so.5+0x10dd18)
63: #1 0x7f04fb00930f in qdr_route_table_setup_CT
/home/gmurthy/opensource/qpid-dispatch/src/router_core/route_tables.c:249
63: #2 0x7f04fb003d41 in router_core_thread
[jira] [Resolved] (DISPATCH-1648) Uniformly use timeout as TIMEOUT in all system tests
[
https://issues.apache.org/jira/browse/DISPATCH-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1648.
-
Fix Version/s: 1.13.0
Resolution: Fixed
> Uniformly use timeout as TIMEOUT in all system tests
>
>
> Key: DISPATCH-1648
> URL: https://issues.apache.org/jira/browse/DISPATCH-1648
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> All tests should use TIMEOUT as their default scheduled timeout. There are
> cases where there are special timers that are needed for a shorter duration
> and it is OK for tests to do that but the main timeout should be scheduled
> with TIMEOUT.
>
> TIMEOUT is defined in system_test.py as follows
> {noformat}
> TIMEOUT = float(os.environ.get("QPID_SYSTEM_TEST_TIMEOUT", 60)) {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
[jira] [Assigned] (DISPATCH-1649) Tox failure, Python Checker error in config.py
[
https://issues.apache.org/jira/browse/DISPATCH-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-1649:
---
Assignee: Ken Giusti
> Tox failure, Python Checker error in config.py
> --
>
> Key: DISPATCH-1649
> URL: https://issues.apache.org/jira/browse/DISPATCH-1649
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
>Affects Versions: 1.12.0
>Reporter: Ganesh Murthy
>Assignee: Ken Giusti
>Priority: Major
>
> {noformat}
> st 67
> Start 67: python-checker
> 67: Test command: /usr/local/bin/tox
> 67: Test timeout computed to be: 600
> 67: py27 create: /foo/qpid-dispatch/build/tests/.tox/py27
> 67: py27 installdeps: hacking>=1.1.0
> 67: WARNING: Discarding $PYTHONPATH from environment, to override specify
> PYTHONPATH in 'passenv' in your configuration.
> 67: py27 installed: DEPRECATION: Python 2.7 reached the end of its life on
> January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer
> maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More
> details about Python 2 support in pip, can be found at
> https://pip.pypa.io/en/latest/development/release-process/#python-2-support,configparser==4.0.2,contextlib2==0.6.0.post1,enum34==1.1.10,flake8==3.8.1,functools32==3.2.3.post2,hacking==2.0.0,importlib-metadata==1.6.0,mccabe==0.6.1,pathlib2==2.3.5,pycodestyle==2.6.0,pyflakes==2.2.0,qpid-dispatch===1.13.0-SNAPSHOT,scandir==1.10.0,six==1.14.0,typing==3.7.4.1,zipp==1.2.0
> 67: py27 run-test-pre: PYTHONHASHSEED='1454137866'
> 67: py27 run-test: commands[0] | flake8 --count --show-source
> /foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
> /foo/qpid-dispatch/tests /foo/qpid-dispatch/tools
> /foo/qpid-dispatch/tools/qdstat /foo/qpid-dispatch/tools/qdmanage
> --ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E305,E306,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,E722,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503,W504
> 67:
> /foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:107:49:
> E741 ambiguous variable name 'l'
> 67: js_text = "[%s]"%("\n".join([sub(l) for l in lines]))
> 67: ^
> 67:
> /foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:122:47:
> E741 ambiguous variable name 'l'
> 67: js_text = "%s"%("\n".join([sub(l) for l in lines]))
> 67: ^
> 67:
> /foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:182:9:
> E741 ambiguous variable name 'l'
> 67: for l in config.by_type('log'):
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:378:26: E741 ambiguous variable
> name 'l'
> 67: def sub_elem(l, level):
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:407:30: E741 ambiguous variable
> name 'l'
> 67: default_log = [l for l in config if (l[0] == 'log' and
> l[1]['module'] == 'DEFAULT')]
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:466:13: E741 ambiguous variable
> name 'l'
> 67: for l in self.config.sections('listener'):
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:477:31: E741 ambiguous variable
> name 'l'
> 67: return [l['port'] for l in self.config.sections('listener')]
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_test.py:493:60: E741 ambiguous variable
> name 'l'
> 67: return ["amqp://%s" % self._cfg_2_host_port(l) for l in cfg]
> 67:^
> 67: /foo/qpid-dispatch/tests/system_test.py:504:46: E741 ambiguous variable
> name 'l'
> 67: return [self._cfg_2_host_port(l) for l in
> self.config.sections('listener')]
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1653:28: E741
> ambiguous variable name 'l'
> 67: lines = [l for l in inta_log.read().split("\n")
> 67:^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1666:17: E741
> ambiguous variable name 'l'
> 67: for l in lines:
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1682:17: E741
> ambiguous variable name 'l'
> 67: for l in lines:
> 67: ^
> 67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1794:29: E741
> ambiguous variable name 'l'
> 67: test_links = [l for l in ll if
> 67:
[jira] [Created] (DISPATCH-1650) test_01_parallel_link_routes failure in system_tests_link_route
Ganesh Murthy created DISPATCH-1650:
---
Summary: test_01_parallel_link_routes failure in
system_tests_link_route
Key: DISPATCH-1650
URL: https://issues.apache.org/jira/browse/DISPATCH-1650
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
Assignee: Ken Giusti
{noformat}
14: ==
14: ERROR: test_01_parallel_link_routes (system_tests_link_routes.LinkRoute3Hop)
14: --
14: Traceback (most recent call last):
14: File "/foo/qpid-dispatch/tests/system_tests_link_routes.py", line 2499,
in test_01_parallel_link_routes
14: if rx.wait(timeout=TIMEOUT):
14: File "/foo/qpid-dispatch/tests/system_test.py", line 311, in wait
14: raise Exception("Process did not terminate")
14: Exception: Process did not terminate
14:
14: ==
14: ERROR: test_01_parallel_link_routes (system_tests_link_routes.LinkRoute3Hop)
14: --
14: Traceback (most recent call last):
14: File "/foo/qpid-dispatch/tests/system_test.py", line 713, in tearDown
14: Tester.teardown(self)
14: File "/foo/qpid-dispatch/tests/system_test.py", line 637, in teardown
14: raise RuntimeError("Errors during teardown: \n\n%s" %
"\n\n".join([str(e) for e in errors]))
14: RuntimeError: Errors during teardown:
14:
14: Process 2743 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-9 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-24.cmd
14:
14:
14:
14: Process 2742 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-8 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-23.cmd
14:
14:
14:
14: Process 2741 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-7 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-22.cmd
14:
14:
14:
14: Process 2740 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-6 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-21.cmd
14:
14:
14:
14: Process 2739 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-5 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-20.cmd
14:
14:
14:
14: Process 2738 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-4 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-19.cmd
14:
14:
14:
14: Process 2737 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-3 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-18.cmd
14:
14:
14:
14: Process 2736 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-2 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-17.cmd
14:
14:
14:
14: Process 2735 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-1 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-16.cmd
14:
14:
14:
14: Process 2734 error: still running
14: test-sender -a amqp://0.0.0.0:25779 -c 25 -i TestSender-0 -sx -t
closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-sender-15.cmd
14:
14:
14:
14: Process 2733 error: still running
14: test-receiver -a amqp://0.0.0.0:25779 -c 250 -s closest/test-client
14:
/foo/qpid-dispatch/build/tests/system_test.dir/system_tests_link_routes/LinkRoute3Hop/test_01_parallel_link_routes/test-receiver-14.cmd
14:
14:
14:
14: --
14: Ran 36 tests in 113.953s {noformat}
--
This message was sent by Atlassian
[jira] [Created] (DISPATCH-1649) Tox failure, Python Checker error in config.py
Ganesh Murthy created DISPATCH-1649:
---
Summary: Tox failure, Python Checker error in config.py
Key: DISPATCH-1649
URL: https://issues.apache.org/jira/browse/DISPATCH-1649
Project: Qpid Dispatch
Issue Type: Bug
Components: Management Agent
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
{noformat}
st 67
Start 67: python-checker
67: Test command: /usr/local/bin/tox
67: Test timeout computed to be: 600
67: py27 create: /foo/qpid-dispatch/build/tests/.tox/py27
67: py27 installdeps: hacking>=1.1.0
67: WARNING: Discarding $PYTHONPATH from environment, to override specify
PYTHONPATH in 'passenv' in your configuration.
67: py27 installed: DEPRECATION: Python 2.7 reached the end of its life on
January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer
maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More
details about Python 2 support in pip, can be found at
https://pip.pypa.io/en/latest/development/release-process/#python-2-support,configparser==4.0.2,contextlib2==0.6.0.post1,enum34==1.1.10,flake8==3.8.1,functools32==3.2.3.post2,hacking==2.0.0,importlib-metadata==1.6.0,mccabe==0.6.1,pathlib2==2.3.5,pycodestyle==2.6.0,pyflakes==2.2.0,qpid-dispatch===1.13.0-SNAPSHOT,scandir==1.10.0,six==1.14.0,typing==3.7.4.1,zipp==1.2.0
67: py27 run-test-pre: PYTHONHASHSEED='1454137866'
67: py27 run-test: commands[0] | flake8 --count --show-source
/foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
/foo/qpid-dispatch/tests /foo/qpid-dispatch/tools
/foo/qpid-dispatch/tools/qdstat /foo/qpid-dispatch/tools/qdmanage
--ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E305,E306,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,E722,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503,W504
67:
/foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:107:49:
E741 ambiguous variable name 'l'
67: js_text = "[%s]"%("\n".join([sub(l) for l in lines]))
67: ^
67:
/foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:122:47:
E741 ambiguous variable name 'l'
67: js_text = "%s"%("\n".join([sub(l) for l in lines]))
67: ^
67:
/foo/qpid-dispatch/python/qpid_dispatch_internal/management/config.py:182:9:
E741 ambiguous variable name 'l'
67: for l in config.by_type('log'):
67: ^
67: /foo/qpid-dispatch/tests/system_test.py:378:26: E741 ambiguous variable
name 'l'
67: def sub_elem(l, level):
67: ^
67: /foo/qpid-dispatch/tests/system_test.py:407:30: E741 ambiguous variable
name 'l'
67: default_log = [l for l in config if (l[0] == 'log' and
l[1]['module'] == 'DEFAULT')]
67: ^
67: /foo/qpid-dispatch/tests/system_test.py:466:13: E741 ambiguous variable
name 'l'
67: for l in self.config.sections('listener'):
67: ^
67: /foo/qpid-dispatch/tests/system_test.py:477:31: E741 ambiguous variable
name 'l'
67: return [l['port'] for l in self.config.sections('listener')]
67: ^
67: /foo/qpid-dispatch/tests/system_test.py:493:60: E741 ambiguous variable
name 'l'
67: return ["amqp://%s" % self._cfg_2_host_port(l) for l in cfg]
67:^
67: /foo/qpid-dispatch/tests/system_test.py:504:46: E741 ambiguous variable
name 'l'
67: return [self._cfg_2_host_port(l) for l in
self.config.sections('listener')]
67: ^
67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1653:28: E741
ambiguous variable name 'l'
67: lines = [l for l in inta_log.read().split("\n")
67:^
67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1666:17: E741
ambiguous variable name 'l'
67: for l in lines:
67: ^
67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1682:17: E741
ambiguous variable name 'l'
67: for l in lines:
67: ^
67: /foo/qpid-dispatch/tests/system_tests_edge_router.py:1794:29: E741
ambiguous variable name 'l'
67: test_links = [l for l in ll if
67: ^
67: /foo/qpid-dispatch/tests/system_tests_management.py:204:13: E741 ambiguous
variable name 'l'
67: for l in response.get_dicts():
67: ^
67: /foo/qpid-dispatch/tests/system_tests_management.py:363:25: E741 ambiguous
variable name 'l'
67: mylink = [l for l in response.get_dicts()
67: ^
67:
[jira] [Created] (DISPATCH-1648) Uniformly use timeout as TIMEOUT in all system tests
Ganesh Murthy created DISPATCH-1648:
---
Summary: Uniformly use timeout as TIMEOUT in all system tests
Key: DISPATCH-1648
URL: https://issues.apache.org/jira/browse/DISPATCH-1648
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.12.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
All tests should use TIMEOUT as their default scheduled timeout. There are
cases where there are special timers that are needed for a shorter duration and
it is OK for tests to do that but the main timeout should be scheduled with
TIMEOUT.
TIMEOUT is defined in system_test.py as follows
{noformat}
TIMEOUT = float(os.environ.get("QPID_SYSTEM_TEST_TIMEOUT", 60)) {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
[jira] [Commented] (DISPATCH-1637) Adding new config address, autolinks and link routes become slower as more get added
[
https://issues.apache.org/jira/browse/DISPATCH-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101167#comment-17101167
]
Ganesh Murthy commented on DISPATCH-1637:
-
Not marking this as Resolved yet. [~kgiusti] might have another fix (parse tree)
> Adding new config address, autolinks and link routes become slower as more
> get added
> -
>
> Key: DISPATCH-1637
> URL: https://issues.apache.org/jira/browse/DISPATCH-1637
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
> Attachments: qdr_perf_core_369301_369302.svg
>
>
> Steps to reproduce -
> # Start the router with a default config file, nothing special
> # Run the following qdmanage command in a loop from 1 to 200,000
> ## qdmanage CREATE --type=address prefix=abc\{i} name=abc\{i}
> distribution=balanced waypoint=yes
> # watch qdstat -g
> # Over time, the rate at which the addresses get added comes to a crawl
> This happens for autoLinks and linkRoutes as well
--
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-1391) Proton link reference not cleared on router link objects during session close
[
https://issues.apache.org/jira/browse/DISPATCH-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1391:
Description:
When the following program is run against the router, it crashes -
{noformat}
from proton.utils import BlockingConnection
from time import sleep
ROUTER_ADDRESS = "amqp://127.0.0.1:5672"
RECEIVER_ADDRESS = "examples-receiver"
c = BlockingConnection(ROUTER_ADDRESS)
count = 0
while True:
count += 1
r = c.create_receiver(RECEIVER_ADDRESS + str(count))
r.session.close()
if count == 5:
break
Here is the backtrace
(gdb) bt
#0 pn_terminus_set_address (terminus=0x0, address=0x7f3dc8039aa0
"examples-receiver2") at
/home/gmurthy/opensource/qpid-proton/c/src/core/engine.c:1241
#1 0x7f3de2836a2a in qdr_terminus_copy (from=from@entry=0x7f3dc803dd18,
to=0x0) at /home/gmurthy/opensource/qpid-dispatch/src/router_core/terminus.c:92
#2 0x7f3de283fe1e in CORE_link_second_attach (context=,
link=, source=0x7f3dc803dd18, target=0x7f3dc803dc18) at
/home/gmurthy/opensource/qpid-dispatch/src/router_node.c:1322
#3 0x7f3de28279c1 in qdr_connection_process (conn=0x7f3dc801b198) at
/home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:253
#4 0x7f3de280f0f8 in writable_handler (container=0x171c000,
container=0x171c000, conn=0x7f3dc400eb58, qd_conn=0x7f3dc400eb58) at
/home/gmurthy/opensource/qpid-dispatch/src/container.c:332
#5 qd_container_handle_event (container=0x171c000,
event=event@entry=0x7f3dc80134e0, conn=conn@entry=0x7f3dc4018b00,
qd_conn=qd_conn@entry=0x7f3dc400eb58) at
/home/gmurthy/opensource/qpid-dispatch/src/container.c:642
#6 0x7f3de2845442 in handle (qd_server=qd_server@entry=0x1699ba0,
e=e@entry=0x7f3dc80134e0, pn_conn=pn_conn@entry=0x7f3dc4018b00,
ctx=ctx@entry=0x7f3dc400eb58) at
/home/gmurthy/opensource/qpid-dispatch/src/server.c:985
#7 0x7f3de284607c in thread_run (arg=0x1699ba0) at
/home/gmurthy/opensource/qpid-dispatch/src/server.c:1010
#8 0x7f3de275d4c0 in start_thread () from /lib64/libpthread.so.0
#9 0x7f3de23bb133 in clone () from /lib64/libc.so.6
(gdb)
{noformat}
This is happening because the pn_link references are not cleaned up on router
link objects (qd_link_t) during session close
was:
When the following program is run against the router, it crashes -
{noformat}
from proton.utils import BlockingConnection
from time import sleep
ROUTER_ADDRESS = "amqp://127.0.0.1:5672"
RECEIVER_ADDRESS = "examples-receiver"
c = BlockingConnection(ROUTER_ADDRESS)
count = 0
while True:
count += 1
r = c.create_receiver(RECEIVER_ADDRESS + str(count))
r.session.close()
if count == 5:
break
{noformat}
This is happening because the pn_link references are not cleaned up on router
link objects (qd_link_t) during session close
> Proton link reference not cleared on router link objects during session close
> -
>
> Key: DISPATCH-1391
> URL: https://issues.apache.org/jira/browse/DISPATCH-1391
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.8.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.9.0
>
>
> When the following program is run against the router, it crashes -
> {noformat}
> from proton.utils import BlockingConnection
> from time import sleep
> ROUTER_ADDRESS = "amqp://127.0.0.1:5672"
> RECEIVER_ADDRESS = "examples-receiver"
> c = BlockingConnection(ROUTER_ADDRESS)
> count = 0
> while True:
> count += 1
> r = c.create_receiver(RECEIVER_ADDRESS + str(count))
> r.session.close()
> if count == 5:
> break
> Here is the backtrace
> (gdb) bt
> #0 pn_terminus_set_address (terminus=0x0, address=0x7f3dc8039aa0
> "examples-receiver2") at
> /home/gmurthy/opensource/qpid-proton/c/src/core/engine.c:1241
> #1 0x7f3de2836a2a in qdr_terminus_copy (from=from@entry=0x7f3dc803dd18,
> to=0x0) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/terminus.c:92
> #2 0x7f3de283fe1e in CORE_link_second_attach (context=,
> link=, source=0x7f3dc803dd18, target=0x7f3dc803dc18) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_node.c:1322
> #3 0x7f3de28279c1 in qdr_connection_process (conn=0x7f3dc801b198) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:253
> #4 0x7f3de280f0f8 in writable_handler (container=0x171c000,
> container=0x171c000, conn=0x7f3dc400eb58, qd_conn=0x7f3dc400eb58) at
> /home/gmurthy/opensource/qpid-dispatch/src/container.c:332
> #5 qd_container_handle_event (container=0x171c000,
> event=event@entry=0x7f3dc80134e0, conn=conn@entry=0x7f3dc4018b00,
> qd_conn=qd_conn@entry=0x7f3dc400eb58) at
>
[jira] [Updated] (DISPATCH-1637) Adding new config address, autolinks and link routes become slower as more get added
[
https://issues.apache.org/jira/browse/DISPATCH-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1637:
Description:
Steps to reproduce -
# Start the router with a default config file, nothing special
# Run the following qdmanage command in a loop from 1 to 200,000
## qdmanage CREATE --type=address prefix=abc\{i} name=abc\{i}
distribution=balanced waypoint=yes
# watch qdstat -g
# Over time, the rate at which the addresses get added comes to a crawl
This happens for autoLinks and linkRoutes as well
was:
Steps to reproduce -
# Start the router with a default config file, nothing special
# Run the following qdmanage command in a loop from 1 to 200,000
## qdmanage CREATE --type=address prefix=abc\{i} name=abc\{i}
distribution=balanced waypoint=yes
# watch qdstat -g
# Over time, the rate at which the addresses get added comes to a crawl
> Adding new config address, autolinks and link routes become slower as more
> get added
> -
>
> Key: DISPATCH-1637
> URL: https://issues.apache.org/jira/browse/DISPATCH-1637
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
> Attachments: qdr_perf_core_369301_369302.svg
>
>
> Steps to reproduce -
> # Start the router with a default config file, nothing special
> # Run the following qdmanage command in a loop from 1 to 200,000
> ## qdmanage CREATE --type=address prefix=abc\{i} name=abc\{i}
> distribution=balanced waypoint=yes
> # watch qdstat -g
> # Over time, the rate at which the addresses get added comes to a crawl
> This happens for autoLinks and linkRoutes as well
--
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] [Commented] (DISPATCH-1638) system_tests_two_routers missing timeout() functions in some tests
[
https://issues.apache.org/jira/browse/DISPATCH-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17096598#comment-17096598
]
Ganesh Murthy commented on DISPATCH-1638:
-
Also see why the test is actually failing which is why it is calling the
timeout() function
> system_tests_two_routers missing timeout() functions in some tests
> --
>
> Key: DISPATCH-1638
> URL: https://issues.apache.org/jira/browse/DISPATCH-1638
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
>
> {noformat}
> "34:
> ==",
> "34: ERROR: test_03a_test_strip_message_annotations_no_add_trace
> (system_tests_two_routers.TwoRouterTest)",
> "34:
> --",
> "34: Traceback (most recent call last):",
> "34: File
> \"/opt/qpid-dispatch-src/tests/system_tests_two_routers.py\", line 154, in
> test_03a_test_strip_message_annotations_no_add_trace",
> "34: test.run()",
> "34: File
> \"/opt/qpid-dispatch-src/tests/system_tests_two_routers.py\", line 1098, in
> run",
> "34: Container(self).run()",
> "34: File
> \"/usr/lib64/python2.6/site-packages/proton/_reactor.py\", line 180, in run",
> "34: while self.process(): pass",
> "34: File
> \"/usr/lib64/python2.6/site-packages/proton/_reactor.py\", line 237, in
> process",
> "34: event.dispatch(handler)",
> "34: File \"/usr/lib64/python2.6/site-packages/proton/_events.py\",
> line 162, in dispatch",
> "34: _dispatch(handler, type.method, self)",
> "34: File \"/usr/lib64/python2.6/site-packages/proton/_events.py\",
> line 123, in _dispatch",
> "34: m(*args)",
> "34: File
> \"/opt/qpid-dispatch-src/tests/system_tests_two_routers.py\", line 492, in
> on_timer_task",
> "34: self.parent.timeout()",
> "34: AttributeError: 'MessageAnnotationsStripAddTraceTest' object has
> no attribute 'timeout'",
> "34: ",
> "34:
> --",
> "34: Ran 27 tests in 159.070s", {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
[jira] [Created] (DISPATCH-1638) system_tests_two_routers missing timeout() functions in some tests
Ganesh Murthy created DISPATCH-1638:
---
Summary: system_tests_two_routers missing timeout() functions in
some tests
Key: DISPATCH-1638
URL: https://issues.apache.org/jira/browse/DISPATCH-1638
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.11.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
{noformat}
"34:
==",
"34: ERROR: test_03a_test_strip_message_annotations_no_add_trace
(system_tests_two_routers.TwoRouterTest)",
"34:
--",
"34: Traceback (most recent call last):",
"34: File
\"/opt/qpid-dispatch-src/tests/system_tests_two_routers.py\", line 154, in
test_03a_test_strip_message_annotations_no_add_trace",
"34: test.run()",
"34: File
\"/opt/qpid-dispatch-src/tests/system_tests_two_routers.py\", line 1098, in
run",
"34: Container(self).run()",
"34: File \"/usr/lib64/python2.6/site-packages/proton/_reactor.py\",
line 180, in run",
"34: while self.process(): pass",
"34: File \"/usr/lib64/python2.6/site-packages/proton/_reactor.py\",
line 237, in process",
"34: event.dispatch(handler)",
"34: File \"/usr/lib64/python2.6/site-packages/proton/_events.py\",
line 162, in dispatch",
"34: _dispatch(handler, type.method, self)",
"34: File \"/usr/lib64/python2.6/site-packages/proton/_events.py\",
line 123, in _dispatch",
"34: m(*args)",
"34: File
\"/opt/qpid-dispatch-src/tests/system_tests_two_routers.py\", line 492, in
on_timer_task",
"34: self.parent.timeout()",
"34: AttributeError: 'MessageAnnotationsStripAddTraceTest' object has
no attribute 'timeout'",
"34: ",
"34:
--",
"34: Ran 27 tests in 159.070s", {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
[jira] [Created] (DISPATCH-1637) Adding new config address, autolinks and link routes become slower as more get added
Ganesh Murthy created DISPATCH-1637:
---
Summary: Adding new config address, autolinks and link routes
become slower as more get added
Key: DISPATCH-1637
URL: https://issues.apache.org/jira/browse/DISPATCH-1637
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Affects Versions: 1.11.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
Fix For: 1.13.0
Steps to reproduce -
# Start the router with a default config file, nothing special
# Run the following qdmanage command in a loop from 1 to 200,000
## qdmanage CREATE --type=address prefix=abc\{i} name=abc\{i}
distribution=balanced waypoint=yes
# watch qdstat -g
# Over time, the rate at which the addresses get added comes to a crawl
--
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-1633) system_tests_sasl_plain intermittent test failure
[
https://issues.apache.org/jira/browse/DISPATCH-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1633.
-
Resolution: Fixed
> system_tests_sasl_plain intermittent test failure
> -
>
> Key: DISPATCH-1633
> URL: https://issues.apache.org/jira/browse/DISPATCH-1633
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tests
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> FAIL: test_inter_router_sasl_fail
> (system_tests_sasl_plain.RouterTestPlainSaslFailure)
> 31: --
> 31: Traceback (most recent call last):
> 31: File \"/opt/qpid-dispatch-src/tests/system_test.py\", line 788, in wrap
> 31: return f(*args, **kwargs)
> 31: File \"/opt/qpid-dispatch-src/tests/system_tests_sasl_plain.py\", line
> 151, in test_inter_router_sasl_fail
> 31: self.assertTrue(sasl_failed)
> 31: AssertionError: False is not true{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
[jira] [Commented] (DISPATCH-1633) system_tests_sasl_plain intermittent test failure
[
https://issues.apache.org/jira/browse/DISPATCH-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17094855#comment-17094855
]
Ganesh Murthy commented on DISPATCH-1633:
-
This test failure happens because the router is not writing the log fast
enough. Added a sleep(3) after the router starts so that the connector will
have time to fail and write to the log.
> system_tests_sasl_plain intermittent test failure
> -
>
> Key: DISPATCH-1633
> URL: https://issues.apache.org/jira/browse/DISPATCH-1633
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tests
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> FAIL: test_inter_router_sasl_fail
> (system_tests_sasl_plain.RouterTestPlainSaslFailure)
> 31: --
> 31: Traceback (most recent call last):
> 31: File \"/opt/qpid-dispatch-src/tests/system_test.py\", line 788, in wrap
> 31: return f(*args, **kwargs)
> 31: File \"/opt/qpid-dispatch-src/tests/system_tests_sasl_plain.py\", line
> 151, in test_inter_router_sasl_fail
> 31: self.assertTrue(sasl_failed)
> 31: AssertionError: False is not true{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
[jira] [Updated] (DISPATCH-1633) system_tests_sasl_plain intermittent test failure
[
https://issues.apache.org/jira/browse/DISPATCH-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1633:
Description:
{noformat}
FAIL: test_inter_router_sasl_fail
(system_tests_sasl_plain.RouterTestPlainSaslFailure)
31: --
31: Traceback (most recent call last):
31: File \"/opt/qpid-dispatch-src/tests/system_test.py\", line 788, in wrap
31: return f(*args, **kwargs)
31: File \"/opt/qpid-dispatch-src/tests/system_tests_sasl_plain.py\", line 151,
in test_inter_router_sasl_fail
31: self.assertTrue(sasl_failed)
31: AssertionError: False is not true{noformat}
was:==\n31:
FAIL: test_inter_router_sasl_fail
(system_tests_sasl_plain.RouterTestPlainSaslFailure)\n31:
--\n31:
Traceback (most recent call last):\n31: File
\"/opt/qpid-dispatch-src/tests/system_test.py\", line 788, in wrap\n31:
return f(*args, **kwargs)\n31: File
\"/opt/qpid-dispatch-src/tests/system_tests_sasl_plain.py\", line 151, in
test_inter_router_sasl_fail\n31: self.assertTrue(sasl_failed)\n31:
AssertionError: False is not true
> system_tests_sasl_plain intermittent test failure
> -
>
> Key: DISPATCH-1633
> URL: https://issues.apache.org/jira/browse/DISPATCH-1633
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tests
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0
>
>
> {noformat}
> FAIL: test_inter_router_sasl_fail
> (system_tests_sasl_plain.RouterTestPlainSaslFailure)
> 31: --
> 31: Traceback (most recent call last):
> 31: File \"/opt/qpid-dispatch-src/tests/system_test.py\", line 788, in wrap
> 31: return f(*args, **kwargs)
> 31: File \"/opt/qpid-dispatch-src/tests/system_tests_sasl_plain.py\", line
> 151, in test_inter_router_sasl_fail
> 31: self.assertTrue(sasl_failed)
> 31: AssertionError: False is not true{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
[jira] [Created] (DISPATCH-1633) system_tests_sasl_plain intermittent test failure
Ganesh Murthy created DISPATCH-1633: --- Summary: system_tests_sasl_plain intermittent test failure Key: DISPATCH-1633 URL: https://issues.apache.org/jira/browse/DISPATCH-1633 Project: Qpid Dispatch Issue Type: Improvement Components: Tests Affects Versions: 1.11.0 Reporter: Ganesh Murthy Assignee: Ganesh Murthy Fix For: 1.13.0 ==\n31: FAIL: test_inter_router_sasl_fail (system_tests_sasl_plain.RouterTestPlainSaslFailure)\n31: --\n31: Traceback (most recent call last):\n31: File \"/opt/qpid-dispatch-src/tests/system_test.py\", line 788, in wrap\n31: return f(*args, **kwargs)\n31: File \"/opt/qpid-dispatch-src/tests/system_tests_sasl_plain.py\", line 151, in test_inter_router_sasl_fail\n31: self.assertTrue(sasl_failed)\n31: AssertionError: False is not true -- 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-975) Policy has no provision for limiting user message size
[ https://issues.apache.org/jira/browse/DISPATCH-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-975: --- Issue Type: New Feature (was: Bug) > Policy has no provision for limiting user message size > -- > > Key: DISPATCH-975 > URL: https://issues.apache.org/jira/browse/DISPATCH-975 > Project: Qpid Dispatch > Issue Type: New Feature >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.12.0 > > -- 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-975) Policy has no provision for limiting user message size
[ https://issues.apache.org/jira/browse/DISPATCH-975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-975: --- Fix Version/s: 1.12.0 > Policy has no provision for limiting user message size > -- > > Key: DISPATCH-975 > URL: https://issues.apache.org/jira/browse/DISPATCH-975 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.12.0 > > -- 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-1479) multicast/routing behaviour doc improvements
[
https://issues.apache.org/jira/browse/DISPATCH-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1479:
Issue Type: Improvement (was: Task)
> multicast/routing behaviour doc improvements
>
>
> Key: DISPATCH-1479
> URL: https://issues.apache.org/jira/browse/DISPATCH-1479
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Documentation
>Reporter: Robbie Gemmell
>Assignee: Ben Hardesty
>Priority: Minor
> Fix For: 1.12.0
>
>
> The description of the multicast 'accepted' behaviour could be improved and
> simplified. It is currently described as:
> {noformat}
> Either:
> * All consumers received the message,
> * Or, at least one consumer received the message, but no consumers rejected
> it.
> {noformat}
> (From
> [http://qpid.apache.org/releases/qpid-dispatch-1.9.0/user-guide/index.html#message_settlement_and_reliability],
> which seems to now be sourced on master from
> [https://github.com/apache/qpid-dispatch/blob/master/docs/books/modules/user-guide/routing.adoc])
>
> The 'received the message' bit could perhaps be clearer, e.g. by changing to
> 'accepted the message' (same would also apply in the anycast column), since
> many consumers may have received but not accepted the message.
> It also feels like the either-or distinction should just be removed, leaving
> only an 'at least one' style description. I dont believe there is a way to
> discern the number of recipients that have accepted, its just known 1-n
> consumers accepted without any reject, so it seems more confusing to describe
> it as an 'either or' situation.
>
> Related, the routing.adoc file referenced above seems to be an updated
> variant covering older content from
> [https://github.com/apache/qpid-dispatch/blob/master/docs/books/modules/user-guide/message-routing.adoc]
> and
> [https://github.com/apache/qpid-dispatch/blob/master/docs/books/modules/user-guide/link-routing.adoc]
> which each say they are included in routing.adoc but dont actually appear to
> be. Their content seems stale too, so perhaps they can be deleted?
--
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-1630) Coverity issues on master branch
[
https://issues.apache.org/jira/browse/DISPATCH-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1630:
Issue Type: Bug (was: Improvement)
> Coverity issues on master branch
>
>
> Key: DISPATCH-1630
> URL: https://issues.apache.org/jira/browse/DISPATCH-1630
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
>
> {noformat}
> New defect(s) Reported-by: Coverity Scan
> Showing 1 of 1 defect(s)
> ** CID 355485: Null pointer dereferences (FORWARD_NULL)
>
> *** CID 355485: Null pointer dereferences (FORWARD_NULL)
> /home/gmurthy/opensource/qpid-dispatch/src/http-libwebsockets.c: 181 in
> handle_events()
> 175 static int handle_events(connection_t* c) {
> 176 if (!c->qd_conn) {
> 177 return unexpected_close(c->wsi, "not-established");
> 178 }
> 179 pn_event_t *e;
> 180 while ((e = pn_connection_driver_next_event(>driver))) {
> >>> CID 355485: Null pointer dereferences (FORWARD_NULL)
> >>> Passing null pointer "c->qd_conn" to "qd_connection_handle", which
> >>>dereferences it.
> 181 if (!qd_connection_handle(c->qd_conn, e)) {
> 182 c->qd_conn = 0; // connection closed
> 183 }
> 184 }
> 185 if (pn_connection_driver_write_buffer(>driver).size) {
> 186 lws_callback_on_writable(c->wsi);
> {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
[jira] [Updated] (DISPATCH-1626) On released callback invoked twice for same delivery tag
[
https://issues.apache.org/jira/browse/DISPATCH-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1626:
Issue Type: Bug (was: Improvement)
> On released callback invoked twice for same delivery tag
>
>
> Key: DISPATCH-1626
> URL: https://issues.apache.org/jira/browse/DISPATCH-1626
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
> Attachments: qdrouterd.conf, simple_recv_release.py,
> simple_send_large.py
>
>
> In a python client application, that is connected to a dispatch router, I
> have observed that the on_released callback was invoked twice for the same
> delivery tag.
> Here are the disposition frames I was able to capture for the respective
> delivery:
> {noformat}
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981,
> state=@released(38) []]
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981, last=982,
> settled=true, state=@released(38) []]{noformat}
> The delivery tag 981 came first without the settlement and next with the
> settled as true. And the on_released was called twice for the 981 delivery
> tag.
--
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-1622) Router crash when trying to create connector via qdmanage
[
https://issues.apache.org/jira/browse/DISPATCH-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1622:
Issue Type: Bug (was: Improvement)
> Router crash when trying to create connector via qdmanage
> -
>
> Key: DISPATCH-1622
> URL: https://issues.apache.org/jira/browse/DISPATCH-1622
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
> Attachments: qdrouterd.conf
>
>
> Start the router using the attached config file. It is a simple router whose
> router mode can be edge or standalone.
> Now run this qdmanage command -
> {noformat}
> qdmanage CREATE --type=connector host=0.0.0.0 port=7 role=inter-router
> saslMechanisms=ANONYMOUS {noformat}
> The router will crash with the following backtrace
> {noformat}
> (gdb) bt
> #0 qd_bitmask_first_set (b=0x0, bitnum=bitnum@entry=0x7f0e1c0363e0) at
> /home/gmurthy/opensource/qpid-dispatch/src/bitmask.c:129
> #1 0x7f0e3746de99 in qdr_connection_opened_CT (core=0x1de0460,
> action=0x7f0e1c012e88, discard=) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/connections.c:1306
> #2 0x7f0e3747d2f3 in router_core_thread (arg=0x1de0460) at
> /home/gmurthy/opensource/qpid-dispatch/src/router_core/router_core_thread.c:193
> #3 0x7f0e373974c0 in start_thread () from /lib64/libpthread.so.0
> #4 0x7f0e36ff5163 in clone () from /lib64/libc.so.6
> (gdb) {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
[jira] [Updated] (DISPATCH-1610) qd_pn_free_link_session_t objects leaking when connections are socket closed
[
https://issues.apache.org/jira/browse/DISPATCH-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1610:
Issue Type: Bug (was: Improvement)
> qd_pn_free_link_session_t objects leaking when connections are socket closed
>
>
> Key: DISPATCH-1610
> URL: https://issues.apache.org/jira/browse/DISPATCH-1610
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
> Attachments: test-leak-1.sh
>
>
> Run the attached reproducer from the build/test directory and you will see
> that the qd_pn_free_link_session_t numbers go up in the output of qdstat -m.
>
> {noformat}
> [gmurthy@localhost src]$ qdstat -m | grep qd_pn_free_link_session_t
> qd_pn_free_link_session_t 32 64 128 256 256 0
> 0
> [gmurthy@localhost src]$ qdstat -m | grep qd_pn_free_link_session_t
> qd_pn_free_link_session_t 32 64 128 256 256 0
> 0
> [gmurthy@localhost src]$ qdstat -m | grep qd_pn_free_link_session_t
> qd_pn_free_link_session_t 32 64 128 256 256 0
>0
> [gmurthy@localhost src]$ qdstat -m | grep qd_pn_free_link_session_t
> qd_pn_free_link_session_t 32 64 128 1,024 1,024 0
> 0
> [gmurthy@localhost src]$ qdstat -m | grep qd_pn_free_link_session_t
> qd_pn_free_link_session_t 32 64 128 1,024 1,024 0
> 0
> [gmurthy@localhost src]$ qdstat -m | grep qd_pn_free_link_session_t
> qd_pn_free_link_session_t 32 64 128 1,024 1,024 0
> 0
> [gmurthy@localhost src]$
> [gmurthy@localhost src]$ qdstat -m | grep qd_pn_free_link_session_t
> qd_pn_free_link_session_t 32 64 128 1,024 1,024 0
> 0
> [gmurthy@localhost src]$ qdstat -m | grep qd_pn_free_link_session_t
> qd_pn_free_link_session_t 32 64 128 1,216 1,216 0
> 0
> [gmurthy@localhost src]$
> {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
[jira] [Resolved] (DISPATCH-1630) Coverity issues on master branch
[
https://issues.apache.org/jira/browse/DISPATCH-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1630.
-
Resolution: Fixed
> Coverity issues on master branch
>
>
> Key: DISPATCH-1630
> URL: https://issues.apache.org/jira/browse/DISPATCH-1630
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
>
> {noformat}
> New defect(s) Reported-by: Coverity Scan
> Showing 1 of 1 defect(s)
> ** CID 355485: Null pointer dereferences (FORWARD_NULL)
>
> *** CID 355485: Null pointer dereferences (FORWARD_NULL)
> /home/gmurthy/opensource/qpid-dispatch/src/http-libwebsockets.c: 181 in
> handle_events()
> 175 static int handle_events(connection_t* c) {
> 176 if (!c->qd_conn) {
> 177 return unexpected_close(c->wsi, "not-established");
> 178 }
> 179 pn_event_t *e;
> 180 while ((e = pn_connection_driver_next_event(>driver))) {
> >>> CID 355485: Null pointer dereferences (FORWARD_NULL)
> >>> Passing null pointer "c->qd_conn" to "qd_connection_handle", which
> >>>dereferences it.
> 181 if (!qd_connection_handle(c->qd_conn, e)) {
> 182 c->qd_conn = 0; // connection closed
> 183 }
> 184 }
> 185 if (pn_connection_driver_write_buffer(>driver).size) {
> 186 lws_callback_on_writable(c->wsi);
> {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
[jira] [Created] (DISPATCH-1630) Coverity issues on master branch
Ganesh Murthy created DISPATCH-1630:
---
Summary: Coverity issues on master branch
Key: DISPATCH-1630
URL: https://issues.apache.org/jira/browse/DISPATCH-1630
Project: Qpid Dispatch
Issue Type: Improvement
Components: Container
Affects Versions: 1.11.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
Fix For: 1.12.0
{noformat}
New defect(s) Reported-by: Coverity Scan
Showing 1 of 1 defect(s)
** CID 355485: Null pointer dereferences (FORWARD_NULL)
*** CID 355485: Null pointer dereferences (FORWARD_NULL)
/home/gmurthy/opensource/qpid-dispatch/src/http-libwebsockets.c: 181 in
handle_events()
175 static int handle_events(connection_t* c) {
176 if (!c->qd_conn) {
177 return unexpected_close(c->wsi, "not-established");
178 }
179 pn_event_t *e;
180 while ((e = pn_connection_driver_next_event(>driver))) {
>>> CID 355485: Null pointer dereferences (FORWARD_NULL)
>>> Passing null pointer "c->qd_conn" to "qd_connection_handle", which
>>>dereferences it.
181 if (!qd_connection_handle(c->qd_conn, e)) {
182 c->qd_conn = 0; // connection closed
183 }
184 }
185 if (pn_connection_driver_write_buffer(>driver).size) {
186 lws_callback_on_writable(c->wsi);
{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
[jira] [Resolved] (DISPATCH-1607) [test] one_router test_48_connection_uptime_last_dlv ConnectionUptimeLastDlvTest intermittent fail
[ https://issues.apache.org/jira/browse/DISPATCH-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1607. - Resolution: Fixed > [test] one_router test_48_connection_uptime_last_dlv > ConnectionUptimeLastDlvTest intermittent fail > -- > > Key: DISPATCH-1607 > URL: https://issues.apache.org/jira/browse/DISPATCH-1607 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.10.0 >Reporter: Charles E. Rolke >Priority: Major > Fix For: 1.12.0 > > > This test fails with a dubious indication that delivery arrived before a > predicted delivery time. > There is some uncertainty with respect to the test timing declarations based > on event.reactor.schedule calls with integer timing granularity and the > connection statistics gathered with Node queries, also with integer timing > granularity. > If the connection takes only a few hundred microseconds to start up then the > router's internal uptime and last delivery times may appear to be a full > second behind the test times. The router uptime may be 1.00 S and the > external test expects >= 2.00 S and so the test fails. This is normal for > systems where the times are rounded down to the nearest whole second. > The fix for this test is to relax the timing limits by one second. > h6. Normal Test > ||conn/iter||self.uptime||self.lastDlv||conn uptime||conn lastDlv|| > |send/1|5|None|5|None| > |recv/1|5|None|5|None| > |send/1|7|2|7|2| > |recv/1|7|2|7|2| > h6. Failing Test > ||conn/iter||self.uptime||self.lastDlv||conn uptime||conn lastDlv|| > |send/1|5|None|6|None| > |recv/1|5|None|6|None| > |send/1|7|2|7|1| > |recv/1|7|2|7|1| -- 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] [Assigned] (DISPATCH-1607) [test] one_router test_48_connection_uptime_last_dlv ConnectionUptimeLastDlvTest intermittent fail
[ https://issues.apache.org/jira/browse/DISPATCH-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-1607: --- Assignee: Charles E. Rolke > [test] one_router test_48_connection_uptime_last_dlv > ConnectionUptimeLastDlvTest intermittent fail > -- > > Key: DISPATCH-1607 > URL: https://issues.apache.org/jira/browse/DISPATCH-1607 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.10.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.12.0 > > > This test fails with a dubious indication that delivery arrived before a > predicted delivery time. > There is some uncertainty with respect to the test timing declarations based > on event.reactor.schedule calls with integer timing granularity and the > connection statistics gathered with Node queries, also with integer timing > granularity. > If the connection takes only a few hundred microseconds to start up then the > router's internal uptime and last delivery times may appear to be a full > second behind the test times. The router uptime may be 1.00 S and the > external test expects >= 2.00 S and so the test fails. This is normal for > systems where the times are rounded down to the nearest whole second. > The fix for this test is to relax the timing limits by one second. > h6. Normal Test > ||conn/iter||self.uptime||self.lastDlv||conn uptime||conn lastDlv|| > |send/1|5|None|5|None| > |recv/1|5|None|5|None| > |send/1|7|2|7|2| > |recv/1|7|2|7|2| > h6. Failing Test > ||conn/iter||self.uptime||self.lastDlv||conn uptime||conn lastDlv|| > |send/1|5|None|6|None| > |recv/1|5|None|6|None| > |send/1|7|2|7|1| > |recv/1|7|2|7|1| -- 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-1607) [test] one_router test_48_connection_uptime_last_dlv ConnectionUptimeLastDlvTest intermittent fail
[ https://issues.apache.org/jira/browse/DISPATCH-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1607: Summary: [test] one_router test_48_connection_uptime_last_dlv ConnectionUptimeLastDlvTest intermittent fail (was: [test] one_router test_48 ConnectionUptimeLastDlvTest intermittent fail) > [test] one_router test_48_connection_uptime_last_dlv > ConnectionUptimeLastDlvTest intermittent fail > -- > > Key: DISPATCH-1607 > URL: https://issues.apache.org/jira/browse/DISPATCH-1607 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.10.0 >Reporter: Charles E. Rolke >Priority: Major > Fix For: 1.12.0 > > > This test fails with a dubious indication that delivery arrived before a > predicted delivery time. > There is some uncertainty with respect to the test timing declarations based > on event.reactor.schedule calls with integer timing granularity and the > connection statistics gathered with Node queries, also with integer timing > granularity. > If the connection takes only a few hundred microseconds to start up then the > router's internal uptime and last delivery times may appear to be a full > second behind the test times. The router uptime may be 1.00 S and the > external test expects >= 2.00 S and so the test fails. This is normal for > systems where the times are rounded down to the nearest whole second. > The fix for this test is to relax the timing limits by one second. > h6. Normal Test > ||conn/iter||self.uptime||self.lastDlv||conn uptime||conn lastDlv|| > |send/1|5|None|5|None| > |recv/1|5|None|5|None| > |send/1|7|2|7|2| > |recv/1|7|2|7|2| > h6. Failing Test > ||conn/iter||self.uptime||self.lastDlv||conn uptime||conn lastDlv|| > |send/1|5|None|6|None| > |recv/1|5|None|6|None| > |send/1|7|2|7|1| > |recv/1|7|2|7|1| -- 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-1543) Inter router links that become detached or closed must be reestablished
[ https://issues.apache.org/jira/browse/DISPATCH-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1543: Fix Version/s: (was: 1.12.0) 1.13.0 > Inter router links that become detached or closed must be reestablished > --- > > Key: DISPATCH-1543 > URL: https://issues.apache.org/jira/browse/DISPATCH-1543 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Affects Versions: 1.10.0 >Reporter: Ganesh Murthy >Priority: Major > Fix For: 1.13.0 > > > Whenever any inter-router link fails (for any reason), the link must be > reestablished. When the inter-router link fails and is not restarted, that > link remains permanently down and inter-router communication is affected. To > remedy this situation, whenever an inter-router link goes down for some > reason, we should detect that and possibly reestablish the link or maybe even > bounce the connection so that all links are reestablished. -- 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-1594) router_core private header files are included by code outside of router_core
[ https://issues.apache.org/jira/browse/DISPATCH-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1594: Fix Version/s: (was: 1.12.0) 1.13.0 > router_core private header files are included by code outside of router_core > > > Key: DISPATCH-1594 > URL: https://issues.apache.org/jira/browse/DISPATCH-1594 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.10.0, 1.11.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Minor > Fix For: 1.13.0 > > > Remove the router_core subdirectory from the default include file paths. > Header files in router_core cannot be included by non-route_core source. -- 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-1545) Streaming deliveries can be delayed by head-of-line blocking on inter-router links
[ https://issues.apache.org/jira/browse/DISPATCH-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1545: Fix Version/s: (was: 1.12.0) 1.13.0 > Streaming deliveries can be delayed by head-of-line blocking on inter-router > links > -- > > Key: DISPATCH-1545 > URL: https://issues.apache.org/jira/browse/DISPATCH-1545 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.10.0 >Reporter: Ted Ross >Assignee: Ken Giusti >Priority: Major > Fix For: 1.13.0 > > > Message-routed deliveries (for the same priority) are forwarded over the same > inter-router link when moving from router to router. If a streaming delivery > is flowing over such a link, subsequent deliveries on that link will be > delayed until the streaming delivery is complete. A solution is needed that > allows an arbitrary number of streaming deliveries to concurrently flow from > router to router. -- 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-1502) large scale link disconnects can push memory up
[ https://issues.apache.org/jira/browse/DISPATCH-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1502: Fix Version/s: (was: 1.12.0) 1.13.0 > large scale link disconnects can push memory up > --- > > Key: DISPATCH-1502 > URL: https://issues.apache.org/jira/browse/DISPATCH-1502 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Assignee: Ted Ross >Priority: Minor > Fix For: 1.13.0 > > > If a router has some connections with large numbers of links on them, and > these connections get suddenly disconnected, the memory for the router can > grow quite a bit in processing the link disconnects (>30% in some cases). > The cause is that there are a large number of qdr_action_t and > qdr_general_work_t instances used as the work is passed from worker thread to > core and back to a worker thread again. As this happens very rapidly > instances are not returned to the pool before more are needed so the pool > grows (in my experiments it was growing by close to the number of links > involved). -- 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-1495) [tools] qdstat man - some help strings truncated
[
https://issues.apache.org/jira/browse/DISPATCH-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1495:
Fix Version/s: (was: 1.12.0)
1.13.0
> [tools] qdstat man - some help strings truncated
>
>
> Key: DISPATCH-1495
> URL: https://issues.apache.org/jira/browse/DISPATCH-1495
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tools
>Affects Versions: 1.9.0
> Environment: Fedora 29, Python 3.7.4
>Reporter: Charles E. Rolke
>Priority: Major
> Fix For: 1.13.0
>
>
> _man qdstat_ shows some help texts truncated
> {noformat}
> --limit LIMIT : Limit number of output rows. Unlimited if limit is
> --all-entities : Show all router entities. Can be combined with --all-
> --all-routers : Show entities for all routers in network. Can also be
> {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
[jira] [Resolved] (DISPATCH-1628) Crash after enforcing oversize message connection close
[ https://issues.apache.org/jira/browse/DISPATCH-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1628. - Resolution: Fixed > Crash after enforcing oversize message connection close > --- > > Key: DISPATCH-1628 > URL: https://issues.apache.org/jira/browse/DISPATCH-1628 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.11.0 >Reporter: Charles E. Rolke >Assignee: Charles E. Rolke >Priority: Major > Fix For: 1.12.0 > > > system_tests_policy_oversize_basic test_40 sends a barrage of oversize > messages to router INT.A. The router closes the connection to the sender but > before that can take effect all 10 messages have arrived at the router's > input link. > Internally the proton subsystem delivers the first two messages in the > context of the same pn_delivery. This causes an indexing error in dispatch > that leads to a use-after-free crash while attempting to clean up the > qdr_delivery lost by the duplicate index. > The error shows up commonly on rhel8 and occasionally on fedora 29. -- 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-1627) Occasional leak of qd_iterator_buffer during system_tests_link_route_credit test
[ https://issues.apache.org/jira/browse/DISPATCH-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1627. - Resolution: Fixed > Occasional leak of qd_iterator_buffer during system_tests_link_route_credit > test > > > Key: DISPATCH-1627 > URL: https://issues.apache.org/jira/browse/DISPATCH-1627 > Project: Qpid Dispatch > Issue Type: Bug > Components: Routing Engine >Affects Versions: 1.11.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Minor > Fix For: 1.12.0 > > > Can reproduce this using ASAN build on Ubuntu Xenial by repeatedly running > system_tests_link_route_credit: > > 16: ==18608==ERROR: LeakSanitizer: detected memory leaks > 16: > 16: Direct leak of 192 byte(s) in 1 object(s) allocated from: > 16: #0 0x7f99635ac7a0 in posix_memalign > (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdf7a0) > 16: #1 0x7f9962e10199 in qd_alloc > /home/kgiusti/work/qpid-dispatch/src/alloc_pool.c:320 > 16: #2 0x7f9962e73a91 in qd_iterator_buffer > /home/kgiusti/work/qpid-dispatch/src/iterator.c:597 > 16: #3 0x7f9962f2ff0d in qdr_field > /home/kgiusti/work/qpid-dispatch/src/router_core/router_core.c:250 > 16: #4 0x7f9962f4b027 in qdr_terminus > /home/kgiusti/work/qpid-dispatch/src/router_core/terminus.c:47 > 16: #5 0x7f9962f83cbd in AMQP_link_attach_handler > /home/kgiusti/work/qpid-dispatch/src/router_node.c:780 > 16: #6 0x7f9962f99d8e in handle > /home/kgiusti/work/qpid-dispatch/src/server.c:1015 > 16: #7 0x7f9962f9f820 in thread_run > /home/kgiusti/work/qpid-dispatch/src/server.c:1040 > 16: #8 0x7f99629966da in start_thread > (/lib/x86_64-linux-gnu/libpthread.so.0+0x76da) -- 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-1617) Prevent router startup if edge or standalone routers have 'edge' role listeners
[ https://issues.apache.org/jira/browse/DISPATCH-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1617. - Resolution: Fixed > Prevent router startup if edge or standalone routers have 'edge' role > listeners > --- > > Key: DISPATCH-1617 > URL: https://issues.apache.org/jira/browse/DISPATCH-1617 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Container >Affects Versions: 1.11.0 >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.12.0 > > > If the router has a mode of 'standalone' or 'edge', do not start the router > if the config has a listener of role 'edge' or 'interior'. Also prevent > qdmanage from adding listeners with role 'edge' or 'interior' to an edge > router. -- 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-1626) On released callback invoked twice for same delivery tag
[
https://issues.apache.org/jira/browse/DISPATCH-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1626.
-
Resolution: Fixed
> On released callback invoked twice for same delivery tag
>
>
> Key: DISPATCH-1626
> URL: https://issues.apache.org/jira/browse/DISPATCH-1626
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
> Attachments: qdrouterd.conf, simple_recv_release.py,
> simple_send_large.py
>
>
> In a python client application, that is connected to a dispatch router, I
> have observed that the on_released callback was invoked twice for the same
> delivery tag.
> Here are the disposition frames I was able to capture for the respective
> delivery:
> {noformat}
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981,
> state=@released(38) []]
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981, last=982,
> settled=true, state=@released(38) []]{noformat}
> The delivery tag 981 came first without the settlement and next with the
> settled as true. And the on_released was called twice for the 981 delivery
> tag.
--
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] [Commented] (DISPATCH-1626) On released callback invoked twice for same delivery tag
[
https://issues.apache.org/jira/browse/DISPATCH-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089994#comment-17089994
]
Ganesh Murthy commented on DISPATCH-1626:
-
To reproduce the issue follow these steps
# Start the router with the attached config file (qdrouterd.conf) -
PN_TRACE_FRM=1 qdrouterd -c etc/qdrouterd.conf
# Start the receiver like this - reset; python simple_recv_release.py
--address 0.0.0.0/examples -m500
# Start the sender like this - python simple_send_large.py --address
0.0.0.0/examples -m500
Look at the frame trace on the router. You will see at least one disposition
frame like the following -
[0x6140ac50]:0 -> @disposition(21) [role=true, first=285,
state=@released(38) []
followed by
[0x6140ac50]:0 -> @disposition(21) [role=true, first=283, last=285,
settled=true, state=@released(38) []]
> On released callback invoked twice for same delivery tag
>
>
> Key: DISPATCH-1626
> URL: https://issues.apache.org/jira/browse/DISPATCH-1626
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
> Attachments: qdrouterd.conf, simple_recv_release.py,
> simple_send_large.py
>
>
> In a python client application, that is connected to a dispatch router, I
> have observed that the on_released callback was invoked twice for the same
> delivery tag.
> Here are the disposition frames I was able to capture for the respective
> delivery:
> {noformat}
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981,
> state=@released(38) []]
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981, last=982,
> settled=true, state=@released(38) []]{noformat}
> The delivery tag 981 came first without the settlement and next with the
> settled as true. And the on_released was called twice for the 981 delivery
> tag.
--
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-1626) On released callback invoked twice for same delivery tag
[
https://issues.apache.org/jira/browse/DISPATCH-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1626:
Attachment: simple_recv_release.py
> On released callback invoked twice for same delivery tag
>
>
> Key: DISPATCH-1626
> URL: https://issues.apache.org/jira/browse/DISPATCH-1626
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
> Attachments: qdrouterd.conf, simple_recv_release.py,
> simple_send_large.py
>
>
> In a python client application, that is connected to a dispatch router, I
> have observed that the on_released callback was invoked twice for the same
> delivery tag.
> Here are the disposition frames I was able to capture for the respective
> delivery:
> {noformat}
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981,
> state=@released(38) []]
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981, last=982,
> settled=true, state=@released(38) []]{noformat}
> The delivery tag 981 came first without the settlement and next with the
> settled as true. And the on_released was called twice for the 981 delivery
> tag.
--
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-1626) On released callback invoked twice for same delivery tag
[
https://issues.apache.org/jira/browse/DISPATCH-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1626:
Attachment: simple_send_large.py
> On released callback invoked twice for same delivery tag
>
>
> Key: DISPATCH-1626
> URL: https://issues.apache.org/jira/browse/DISPATCH-1626
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
> Attachments: qdrouterd.conf, simple_send_large.py
>
>
> In a python client application, that is connected to a dispatch router, I
> have observed that the on_released callback was invoked twice for the same
> delivery tag.
> Here are the disposition frames I was able to capture for the respective
> delivery:
> {noformat}
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981,
> state=@released(38) []]
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981, last=982,
> settled=true, state=@released(38) []]{noformat}
> The delivery tag 981 came first without the settlement and next with the
> settled as true. And the on_released was called twice for the 981 delivery
> tag.
--
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-1626) On released callback invoked twice for same delivery tag
[
https://issues.apache.org/jira/browse/DISPATCH-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1626:
Attachment: qdrouterd.conf
> On released callback invoked twice for same delivery tag
>
>
> Key: DISPATCH-1626
> URL: https://issues.apache.org/jira/browse/DISPATCH-1626
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
> Attachments: qdrouterd.conf
>
>
> In a python client application, that is connected to a dispatch router, I
> have observed that the on_released callback was invoked twice for the same
> delivery tag.
> Here are the disposition frames I was able to capture for the respective
> delivery:
> {noformat}
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981,
> state=@released(38) []]
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981, last=982,
> settled=true, state=@released(38) []]{noformat}
> The delivery tag 981 came first without the settlement and next with the
> settled as true. And the on_released was called twice for the 981 delivery
> tag.
--
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] [Commented] (DISPATCH-1626) On released callback invoked twice for same delivery tag
[
https://issues.apache.org/jira/browse/DISPATCH-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089728#comment-17089728
]
Ganesh Murthy commented on DISPATCH-1626:
-
The router started sending these two part dispositions right after commit
417975e17406dcc48a648d9fc6da38651a4ff956
The pn_delivery_update() is called by a worker thread and control returns to
proton followed by another worker thread calling pn_delivery_settle(). This
causes proton to send the two part disposition. I have a patch that will add a
minor fix to the previous commit which will make sure the pn_delivery_update()
and pn_delivery_settle() will be called back to back by the same thread during
a single execution of the same function.
> On released callback invoked twice for same delivery tag
>
>
> Key: DISPATCH-1626
> URL: https://issues.apache.org/jira/browse/DISPATCH-1626
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
>Affects Versions: 1.11.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.12.0
>
>
> In a python client application, that is connected to a dispatch router, I
> have observed that the on_released callback was invoked twice for the same
> delivery tag.
> Here are the disposition frames I was able to capture for the respective
> delivery:
> {noformat}
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981,
> state=@released(38) []]
> [0x562a0083ed80]:0 <- @disposition(21) [role=true, first=981, last=982,
> settled=true, state=@released(38) []]{noformat}
> The delivery tag 981 came first without the settlement and next with the
> settled as true. And the on_released was called twice for the 981 delivery
> tag.
--
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
