[jira] [Commented] (DISPATCH-1776) HTTP/2 - grpc call causes segfault
[
https://issues.apache.org/jira/browse/DISPATCH-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227695#comment-17227695
]
ASF subversion and git services commented on DISPATCH-1776:
---
Commit 4e9a0982115e1a56edd3d53b04c47d3b2740b6a8 in qpid-dispatch's branch
refs/heads/dev-protocol-adaptors-2 from Ganesh Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=4e9a098 ]
DISPATCH-1776: Additional fix. Create nghttp2 client session on creation of new
connection
> HTTP/2 - grpc call causes segfault
> --
>
> Key: DISPATCH-1776
> URL: https://issues.apache.org/jira/browse/DISPATCH-1776
> Project: Qpid Dispatch
> Issue Type: Sub-task
> Components: Protocol Adaptors
>Reporter: Gordon Sim
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.15.0
>
>
> Running a simple grpc echo (over http2) through the router causes a segfault.
> To reproduce run router with (you can change the ports if desired, just be
> consistent with the server and client):
> {noformat}
> router {
> mode: interior
> }
> listener {
> host: 0.0.0.0
> port: amqp
> authenticatePeer: no
> saslMechanisms: ANONYMOUS
> }
> httpListener {
> host: 0.0.0.0
> port: 9090
> address: foo
> protocolVersion: HTTP2
> }
> httpConnector {
> host: 127.0.0.1
> port: 8080
> address: foo
> protocolVersion: HTTP2
> }
> log {
> module: HTTP_ADAPTOR
> enable: trace+
> }
> {noformat}
> Then run grpc server with podman (or docker):
> {noformat}
> podman run -it -p8080:9000 quay.io/mhausenblas/yages:0.1.0
> {noformat}
> Then run grpc client, again with podman (or docker):
> {noformat}
> podman run -it --network=host quay.io/mhausenblas/gump:0.1 grpcurl
> --plaintext 127.0.0.1:9090 yages.Echo.Ping
> {noformat}
> I see segfault with following backtrace:
> {noformat}
> Thread 4 "qdrouterd" received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fffeedb5700 (LWP 3841832)]
> 0x77f4a417 in qd_compose_end_map () at
> /home/gordon/projects/dispatch/src/compose.c:179
> 179 DEQ_INSERT_HEAD(field->fieldStack, comp);
> Missing separate debuginfos, use: dnf debuginfo-install
> cyrus-sasl-lib-2.1.27-2.fc31.x86_64 keyutils-libs-1.6-3.fc31.x86_64
> krb5-libs-1.17-46.fc31.x86_64 libcom_err-1.45.5-1.fc31.x86_64
> libev-4.27-1.fc31.x86_64 libffi-3.1-23.fc31.x86_64
> libnghttp2-1.41.0-1.fc31.x86_64 libselinux-2.9-5.fc31.x86_64
> libuv-1.34.2-1.fc31.x86_64 libwebsockets-3.2.1-1.fc31.x86_64
> libxcrypt-4.4.15-1.fc31.x86_64 openssl-libs-1.1.1d-2.fc31.x86_64
> pcre2-10.34-8.fc31.x86_64 python3-libs-3.7.6-2.fc31.x86_64
> zlib-1.2.11-20.fc31.x86_64
> (gdb) bt
> #0 0x77f4a417 in qd_compose_end_map () at
> /home/gordon/projects/dispatch/src/compose.c:179
> #1 0x77f4008a in on_frame_recv_callback (session=,
> frame=0x64ea70, user_data=0x64a308) at
> /home/gordon/projects/dispatch/src/adaptors/http2/http2_adaptor.c:702
> #2 0x77a8c32e in nghttp2_session_mem_recv () from
> /lib64/libnghttp2.so.14
> #3 0x77f41bdd in handle_incoming_http (conn=0x64a308) at
> /home/gordon/projects/dispatch/src/adaptors/http2/http2_adaptor.h:149
> #4 handle_connection_event (e=, qd_server=,
> context=0x64a308) at
> /home/gordon/projects/dispatch/src/adaptors/http2/http2_adaptor.c:1456
> #5 0x77f933f1 in handle_event_with_context (context=,
> qd_server=, e=) at
> /home/gordon/projects/dispatch/src/server.c:781
> #6 do_handle_raw_connection_event (qd_server=, e= out>) at /home/gordon/projects/dispatch/src/server.c:787
> #7 handle (qd_server=qd_server@entry=0x4371d0, e=e@entry=0x7fffe4000c20,
> pn_conn=pn_conn@entry=0x0, ctx=ctx@entry=0x0) at
> /home/gordon/projects/dispatch/src/server.c:1067
> #8 0x77f942c8 in thread_run (arg=0x4371d0) at
> /home/gordon/projects/dispatch/src/server.c:1099
> #9 0x77e7f4e2 in start_thread () from /lib64/libpthread.so.0
> #10 0x779b46d3 in clone () from /lib64/libc.so.6
> {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-1746) system_tests_multi_tenancy failure on test test_36_two_router_waypoint_external_addr
[
https://issues.apache.org/jira/browse/DISPATCH-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227623#comment-17227623
]
ASF subversion and git services commented on DISPATCH-1746:
---
Commit 3037ee5ee16865519631b489ba3d9a04e63be007 in qpid-dispatch's branch
refs/heads/master from Ganesh Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=3037ee5 ]
DISPATCH-1746: Added some log messages. Created the first_sender when flow is
available for self.waypoint_sender
> system_tests_multi_tenancy failure on test
> test_36_two_router_waypoint_external_addr
>
>
> Key: DISPATCH-1746
> URL: https://issues.apache.org/jira/browse/DISPATCH-1746
> Project: Qpid Dispatch
> Issue Type: Test
> Components: Tests
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.13.0, 1.15.0
>
>
> {noformat}
> 37: ==
> 37: FAIL: test_36_two_router_waypoint_external_addr
> (system_tests_multi_tenancy.RouterTest)
> 37: --
> 37: Traceback (most recent call last):
> 37: File
> "/home/travis/build/apache/qpid-dispatch/tests/system_tests_multi_tenancy.py",
> line 457, in test_36_two_router_waypoint_external_addr
> 37: self.assertEqual(None, test.error)
> 37: AssertionError: None != u'Timeout Expired: n_sent=10 n_rcvd=0 n_thru=0'
> 37:
> 37: --
> 37: Ran 36 tests in 73.309s
> 37:
> 37: FAILED (failures=1)
> 37/69 Test #37: system_tests_multi_tenancy ***Failed
> 73.38 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] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227570#comment-17227570
]
Roddie Kieley commented on PROTON-2231:
---
After collecting lots of logging using the -debug method via:
{code}
./c-threaderciser -time 10 -threads 12 -debug -no-timeout -no-cancel-timeout
{code}
A very short reproduction of the assertion was recorded:
{code}
i7mbp:tests rkieley$ ./c-threaderciser -time 10 -threads 12 -debug -no-timeout
-no-cancel-timeout 2>&1 >>
/wip/issues/issues.apache.org/PROTON-2231/threader-110620-4-no-timeouts-1.out |
tee
/wip/issues/issues.apache.org/PROTON-2231/threader-110620-4-no-timeouts-1.out
(1053a35c0) [0x7fb3c8802800] listen
(709b) user_thread start
(70a33000) proactor_thread start
(70ab6000) user_thread start
(70b39000) proactor_thread start
(70c3f000) proactor_thread start
(709b) [0x7fb3c7d006a0] connect
(70cc2000) user_thread start
(70bbc000) user_thread start
(70d45000) proactor_thread start
(70dc8000) user_thread start
(70bbc000) [0x7fb3c9100070] connect
(70e4b000) proactor_thread start
(70ece000) user_thread start
(70f51000) proactor_thread start
(709b) [0x7fb3c8802800] close-listen
(709b) [0x7fb3c9100070] wake
(70dc8000) [0x7fb3c7d01f10] connect
(70dc8000) [0x7fb3c980d200] listen
(70dc8000) [0x7fb3c8802800] close-listen
(70dc8000) [0x7fb3c9100070] wake
(70ece000) [0x7fb3c7f02eb0] connect
(709b) [0x7fb3c980de00] listen
(70bbc000) [0x7fb3c7d006a0] wake
(70ece000) [0x7fb3c980d200] close-listen
(70cc2000) [0x7fb3c7d006a0] wake
(70bbc000) [0x7fb3c7f041f0] connect
(70bbc000) [0x7fb3c7f02eb0] wake
(70ece000) [0x7fb3c9100070] wake
(70a33000) [0x7fb3c8802800] listening on :::62859
(70a33000) [0x7fb3c7c04e60] connect
(70c3f000) [0x7fb3c980de00] listening on :::62860
(70c3f000) [0x7fb3c9101200] connect
(70dc8000) [0x7fb3c7f02c90] connect
(70dc8000) [0x7fb3c7f02c90] wake
(709b) [0x7fb3c7f02c90] wake
(70bbc000) [0x7fb3c980de00] close-listen
Assertion failed: (p->active > 0), function remove_active_lh, file
/wip/src/github.com/apache/qpid-proton/c/src/proactor/libuv.c, line 394.
i7mbp:tests rkieley$
{code}
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
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-1829) multi-hop TCP does not seem to work
Gordon Sim created DISPATCH-1829: Summary: multi-hop TCP does not seem to work Key: DISPATCH-1829 URL: https://issues.apache.org/jira/browse/DISPATCH-1829 Project: Qpid Dispatch Issue Type: Bug Components: Protocol Adaptors Reporter: Gordon Sim Attempting to connect through a chain of three routers, ingress->interior->egress, does not work. This seems to be independent of whether the ingress and egress routers are edge or interior mode. However connecting with TCP through the interior to egress does 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] (PROTON-2289) cpp-connect_config_test fails on fedora:latest: 1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher
[
https://issues.apache.org/jira/browse/PROTON-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227537#comment-17227537
]
Jiri Daněk commented on PROTON-2289:
I'll leave this one closed, then, and won't create separate issue for the leak.
(When I previously said "example", I meant "test")
> cpp-connect_config_test fails on fedora:latest: 1417A0C1:SSL
> routines:tls_post_process_client_hello:no shared cipher
>
>
> Key: PROTON-2289
> URL: https://issues.apache.org/jira/browse/PROTON-2289
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Reporter: Kim van der Riet
>Priority: Major
>
> The following tests fail with the same error message:
> * test_tls
> * test_tls_default_fail
> * test_tls_external
> * test_tls_plain
> Error message:
> {noformat}
> /foo/proton/cpp/src/connect_config_test.cpp:193: unexpected error
> amqp:connection:framing-error: SSL Failure: error:1417A0C1:SSL
> routines:tls_post_process_client_hello:no shared cipher
> {noformat}
> In addition, valgrind finds a memory loss error which is possibly associated
> with these errors:
> {noformat}
> 23: ==2466== 149,899 (1,408 direct, 148,491 indirect) bytes in 1 blocks are
> definitely lost in loss record 760 of 764
> 23: ==2466==at 0x483CAE9: calloc (vg_replace_malloc.c:760)
> 23: ==2466==by 0x4E3A0D5: pn_listener (epoll.c:1635)
> 23: ==2466==by 0x487CFF8:
> proton::container::impl::listen_common_lh(std::__cxx11::basic_string std::char_traits, std::allocator > const&)
> (proactor_container_impl.cpp:434)
> 23: ==2466==by 0x487D220:
> proton::container::impl::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> proton::listen_handler&) (proactor_container_impl.cpp:456)
> 23: ==2466==by 0x487B17C:
> proton::container::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> proton::listen_handler&) (container.cpp:90)
> 23: ==2466==by 0x40CE7B: (anonymous
> namespace)::test_handler::on_container_start(proton::container&)
> (connect_config_test.cpp:180)
> 23: ==2466==by 0x4904ACE: __pthread_once_slow (in
> /usr/lib64/libpthread-2.31.so)
> 23: ==2466==by 0x487F539: __gthread_once (gthr-default.h:700)
> 23: ==2466==by 0x487F539: call_once proton::container::impl*> (mutex:729)
> 23: ==2466==by 0x487F539: proton::container::impl::run(int)
> (proactor_container_impl.cpp:794)
> 23: ==2466==by 0x40D2D2: (anonymous
> namespace)::test_tls_default_fail::run() (connect_config_test.cpp:345)
> 23: ==2466==by 0x40BD4B: main (connect_config_test.cpp:432)
> {noformat}
> and which occurs once for each of the tests which failed above.
--
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] (PROTON-2289) cpp-connect_config_test fails on fedora:latest: 1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher
[
https://issues.apache.org/jira/browse/PROTON-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227535#comment-17227535
]
Andrew Stitcher commented on PROTON-2289:
-
[~jdanek] I think it's likely a problem with the test rather than the library -
I haven't checked, but I expect that in case of assertion failures in the test
the listener just doesn't get cleaned up - pr not worth fixing per se as it
likely only happens on test failures.
> cpp-connect_config_test fails on fedora:latest: 1417A0C1:SSL
> routines:tls_post_process_client_hello:no shared cipher
>
>
> Key: PROTON-2289
> URL: https://issues.apache.org/jira/browse/PROTON-2289
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Reporter: Kim van der Riet
>Priority: Major
>
> The following tests fail with the same error message:
> * test_tls
> * test_tls_default_fail
> * test_tls_external
> * test_tls_plain
> Error message:
> {noformat}
> /foo/proton/cpp/src/connect_config_test.cpp:193: unexpected error
> amqp:connection:framing-error: SSL Failure: error:1417A0C1:SSL
> routines:tls_post_process_client_hello:no shared cipher
> {noformat}
> In addition, valgrind finds a memory loss error which is possibly associated
> with these errors:
> {noformat}
> 23: ==2466== 149,899 (1,408 direct, 148,491 indirect) bytes in 1 blocks are
> definitely lost in loss record 760 of 764
> 23: ==2466==at 0x483CAE9: calloc (vg_replace_malloc.c:760)
> 23: ==2466==by 0x4E3A0D5: pn_listener (epoll.c:1635)
> 23: ==2466==by 0x487CFF8:
> proton::container::impl::listen_common_lh(std::__cxx11::basic_string std::char_traits, std::allocator > const&)
> (proactor_container_impl.cpp:434)
> 23: ==2466==by 0x487D220:
> proton::container::impl::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> proton::listen_handler&) (proactor_container_impl.cpp:456)
> 23: ==2466==by 0x487B17C:
> proton::container::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> proton::listen_handler&) (container.cpp:90)
> 23: ==2466==by 0x40CE7B: (anonymous
> namespace)::test_handler::on_container_start(proton::container&)
> (connect_config_test.cpp:180)
> 23: ==2466==by 0x4904ACE: __pthread_once_slow (in
> /usr/lib64/libpthread-2.31.so)
> 23: ==2466==by 0x487F539: __gthread_once (gthr-default.h:700)
> 23: ==2466==by 0x487F539: call_once proton::container::impl*> (mutex:729)
> 23: ==2466==by 0x487F539: proton::container::impl::run(int)
> (proactor_container_impl.cpp:794)
> 23: ==2466==by 0x40D2D2: (anonymous
> namespace)::test_tls_default_fail::run() (connect_config_test.cpp:345)
> 23: ==2466==by 0x40BD4B: main (connect_config_test.cpp:432)
> {noformat}
> and which occurs once for each of the tests which failed above.
--
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] (PROTON-2289) cpp-connect_config_test fails on fedora:latest: 1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher
[
https://issues.apache.org/jira/browse/PROTON-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227513#comment-17227513
]
Jiri Daněk commented on PROTON-2289:
The valgrind issue looks like some missing error handling for the case that TLS
connection fails. It could either be missing from the example itself, or from
the Proton library (the cpp binding). It seems to me one of those issues that
either get fixed right away, or never. CC [~astitcher]
> cpp-connect_config_test fails on fedora:latest: 1417A0C1:SSL
> routines:tls_post_process_client_hello:no shared cipher
>
>
> Key: PROTON-2289
> URL: https://issues.apache.org/jira/browse/PROTON-2289
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Reporter: Kim van der Riet
>Priority: Major
>
> The following tests fail with the same error message:
> * test_tls
> * test_tls_default_fail
> * test_tls_external
> * test_tls_plain
> Error message:
> {noformat}
> /foo/proton/cpp/src/connect_config_test.cpp:193: unexpected error
> amqp:connection:framing-error: SSL Failure: error:1417A0C1:SSL
> routines:tls_post_process_client_hello:no shared cipher
> {noformat}
> In addition, valgrind finds a memory loss error which is possibly associated
> with these errors:
> {noformat}
> 23: ==2466== 149,899 (1,408 direct, 148,491 indirect) bytes in 1 blocks are
> definitely lost in loss record 760 of 764
> 23: ==2466==at 0x483CAE9: calloc (vg_replace_malloc.c:760)
> 23: ==2466==by 0x4E3A0D5: pn_listener (epoll.c:1635)
> 23: ==2466==by 0x487CFF8:
> proton::container::impl::listen_common_lh(std::__cxx11::basic_string std::char_traits, std::allocator > const&)
> (proactor_container_impl.cpp:434)
> 23: ==2466==by 0x487D220:
> proton::container::impl::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> proton::listen_handler&) (proactor_container_impl.cpp:456)
> 23: ==2466==by 0x487B17C:
> proton::container::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> proton::listen_handler&) (container.cpp:90)
> 23: ==2466==by 0x40CE7B: (anonymous
> namespace)::test_handler::on_container_start(proton::container&)
> (connect_config_test.cpp:180)
> 23: ==2466==by 0x4904ACE: __pthread_once_slow (in
> /usr/lib64/libpthread-2.31.so)
> 23: ==2466==by 0x487F539: __gthread_once (gthr-default.h:700)
> 23: ==2466==by 0x487F539: call_once proton::container::impl*> (mutex:729)
> 23: ==2466==by 0x487F539: proton::container::impl::run(int)
> (proactor_container_impl.cpp:794)
> 23: ==2466==by 0x40D2D2: (anonymous
> namespace)::test_tls_default_fail::run() (connect_config_test.cpp:345)
> 23: ==2466==by 0x40BD4B: main (connect_config_test.cpp:432)
> {noformat}
> and which occurs once for each of the tests which failed above.
--
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] (PROTON-2289) cpp-connect_config_test fails on fedora:latest: 1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher
[
https://issues.apache.org/jira/browse/PROTON-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk closed PROTON-2289.
--
Resolution: Duplicate
> cpp-connect_config_test fails on fedora:latest: 1417A0C1:SSL
> routines:tls_post_process_client_hello:no shared cipher
>
>
> Key: PROTON-2289
> URL: https://issues.apache.org/jira/browse/PROTON-2289
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Reporter: Kim van der Riet
>Priority: Major
>
> The following tests fail with the same error message:
> * test_tls
> * test_tls_default_fail
> * test_tls_external
> * test_tls_plain
> Error message:
> {noformat}
> /foo/proton/cpp/src/connect_config_test.cpp:193: unexpected error
> amqp:connection:framing-error: SSL Failure: error:1417A0C1:SSL
> routines:tls_post_process_client_hello:no shared cipher
> {noformat}
> In addition, valgrind finds a memory loss error which is possibly associated
> with these errors:
> {noformat}
> 23: ==2466== 149,899 (1,408 direct, 148,491 indirect) bytes in 1 blocks are
> definitely lost in loss record 760 of 764
> 23: ==2466==at 0x483CAE9: calloc (vg_replace_malloc.c:760)
> 23: ==2466==by 0x4E3A0D5: pn_listener (epoll.c:1635)
> 23: ==2466==by 0x487CFF8:
> proton::container::impl::listen_common_lh(std::__cxx11::basic_string std::char_traits, std::allocator > const&)
> (proactor_container_impl.cpp:434)
> 23: ==2466==by 0x487D220:
> proton::container::impl::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> proton::listen_handler&) (proactor_container_impl.cpp:456)
> 23: ==2466==by 0x487B17C:
> proton::container::listen(std::__cxx11::basic_string std::char_traits, std::allocator > const&,
> proton::listen_handler&) (container.cpp:90)
> 23: ==2466==by 0x40CE7B: (anonymous
> namespace)::test_handler::on_container_start(proton::container&)
> (connect_config_test.cpp:180)
> 23: ==2466==by 0x4904ACE: __pthread_once_slow (in
> /usr/lib64/libpthread-2.31.so)
> 23: ==2466==by 0x487F539: __gthread_once (gthr-default.h:700)
> 23: ==2466==by 0x487F539: call_once proton::container::impl*> (mutex:729)
> 23: ==2466==by 0x487F539: proton::container::impl::run(int)
> (proactor_container_impl.cpp:794)
> 23: ==2466==by 0x40D2D2: (anonymous
> namespace)::test_tls_default_fail::run() (connect_config_test.cpp:345)
> 23: ==2466==by 0x40BD4B: main (connect_config_test.cpp:432)
> {noformat}
> and which occurs once for each of the tests which failed above.
--
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] (PROTON-2231) Assertion fail on macOS with libuv in c-threaderciser test
[
https://issues.apache.org/jira/browse/PROTON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227457#comment-17227457
]
Roddie Kieley commented on PROTON-2231:
---
Investigation ongoing. Seeing two variations of the hang at the end of the
threaderciser using the following on a 6 core i7 based mac:
{code}
for i in {1..10}; do `echo echo $i; date +%H:%M:%S; ./c-threaderciser -time 10
-threads 12`; done;
{code}
This hangs the very first time it runs in many cases in one of two places
{code}
for (i = 0; i < threads/2; ++i) pthread_join(proactor_threads[i], );
{code}
with 6 of the 7 threads sitting in pn_proactor_wait
OR threaderciser hangs at
{code}
global_destroy()
{code}
which itself is hung on
{code}
pn_proactor_free(g->proactor);
{code}
As well I also see the Assertion failed from the above comment periodically.
More investigation and understanding required to put the pieces together.
> Assertion fail on macOS with libuv in c-threaderciser test
> --
>
> Key: PROTON-2231
> URL: https://issues.apache.org/jira/browse/PROTON-2231
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0
>Reporter: Jiri Daněk
>Assignee: Roddie Kieley
>Priority: Major
> Labels: macOS
>
> As described on PROTON-2225, the test fails with assertion error. It is
> currently disabled on macOS for this reason (in .travis.yml).
> {noformat}
> 6: Test command: /usr/local/opt/python/libexec/bin/python
> "/Users/travis/build/jiridanek/qpid-proton/scripts/env.py" "--"
> "/Users/travis/build/jiridanek/qpid-proton/build/c/tests/c-threaderciser"
> 6: Test timeout computed to be: 1500
> 6: threaderciser start: threads=8, time=1, actions=[listen, close-listen,
> connect, close-connect, wake, timeout, cancel-timeout]
> 6: Assertion failed: (p->active > 0), function remove_active_lh, file
> /Users/travis/build/jiridanek/qpid-proton/c/src/proactor/libuv.c, line 392.
> 6/31 Test #6: c-threaderciser ..***Failed0.18 sec
> {noformat}
> If the test is meant to stay disabled for a longer time, it will have to be
> disabled in CMakeLists.txt, so that users compiling the project do not run it
> accidentally.
--
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
[GitHub] [qpid-broker-j] Dedeepya-T opened a new pull request #68: QPID-8485:[Broker-J]Upgrade guava dependency on 7.1.x
Dedeepya-T opened a new pull request #68: URL: https://github.com/apache/qpid-broker-j/pull/68 Upgrade guava version to 30.0-jre Removed stale exclusion entries of guava This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8485) Upgrade guava version to latest
[ https://issues.apache.org/jira/browse/QPID-8485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227454#comment-17227454 ] ASF GitHub Bot commented on QPID-8485: -- Dedeepya-T opened a new pull request #68: URL: https://github.com/apache/qpid-broker-j/pull/68 Upgrade guava version to 30.0-jre Removed stale exclusion entries of guava This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade guava version to latest > --- > > Key: QPID-8485 > URL: https://issues.apache.org/jira/browse/QPID-8485 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-8.0.2, qpid-java-broker-7.1.10 >Reporter: Dedeepya >Priority: Minor > Fix For: qpid-java-broker-8.0.3 > > > Security vulnerabilities are reported with the guava version below 26. So > upgrade the guava version to the latest -- 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-2289) cpp-connect_config_test fails on fedora:latest: 1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher
Kim van der Riet created PROTON-2289:
Summary: cpp-connect_config_test fails on fedora:latest:
1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher
Key: PROTON-2289
URL: https://issues.apache.org/jira/browse/PROTON-2289
Project: Qpid Proton
Issue Type: Bug
Components: proton-c
Reporter: Kim van der Riet
The following tests fail with the same error message:
* test_tls
* test_tls_default_fail
* test_tls_external
* test_tls_plain
Error message:
{noformat}
/foo/proton/cpp/src/connect_config_test.cpp:193: unexpected error
amqp:connection:framing-error: SSL Failure: error:1417A0C1:SSL
routines:tls_post_process_client_hello:no shared cipher
{noformat}
In addition, valgrind finds a memory loss error which is possibly associated
with these errors:
{noformat}
23: ==2466== 149,899 (1,408 direct, 148,491 indirect) bytes in 1 blocks are
definitely lost in loss record 760 of 764
23: ==2466==at 0x483CAE9: calloc (vg_replace_malloc.c:760)
23: ==2466==by 0x4E3A0D5: pn_listener (epoll.c:1635)
23: ==2466==by 0x487CFF8:
proton::container::impl::listen_common_lh(std::__cxx11::basic_string, std::allocator > const&)
(proactor_container_impl.cpp:434)
23: ==2466==by 0x487D220:
proton::container::impl::listen(std::__cxx11::basic_string, std::allocator > const&, proton::listen_handler&)
(proactor_container_impl.cpp:456)
23: ==2466==by 0x487B17C:
proton::container::listen(std::__cxx11::basic_string, std::allocator > const&, proton::listen_handler&)
(container.cpp:90)
23: ==2466==by 0x40CE7B: (anonymous
namespace)::test_handler::on_container_start(proton::container&)
(connect_config_test.cpp:180)
23: ==2466==by 0x4904ACE: __pthread_once_slow (in
/usr/lib64/libpthread-2.31.so)
23: ==2466==by 0x487F539: __gthread_once (gthr-default.h:700)
23: ==2466==by 0x487F539: call_once (mutex:729)
23: ==2466==by 0x487F539: proton::container::impl::run(int)
(proactor_container_impl.cpp:794)
23: ==2466==by 0x40D2D2: (anonymous
namespace)::test_tls_default_fail::run() (connect_config_test.cpp:345)
23: ==2466==by 0x40BD4B: main (connect_config_test.cpp:432)
{noformat}
and which occurs once for each of the tests which failed above.
--
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] (QPID-8485) Upgrade guava version to latest
Dedeepya created QPID-8485: -- Summary: Upgrade guava version to latest Key: QPID-8485 URL: https://issues.apache.org/jira/browse/QPID-8485 Project: Qpid Issue Type: Improvement Components: Broker-J Affects Versions: qpid-java-broker-7.1.10, qpid-java-broker-8.0.2 Reporter: Dedeepya Fix For: qpid-java-broker-8.0.3 Security vulnerabilities are reported with the guava version below 26. So upgrade the guava version to the latest -- 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
