[jira] [Assigned] (PROTON-2545) raw connection: client disconnect is ignored if no read buffers are available.
[ https://issues.apache.org/jira/browse/PROTON-2545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-2545: --- Assignee: Clifford Jansen (was: Andrew Stitcher) > raw connection: client disconnect is ignored if no read buffers are available. > -- > > Key: PROTON-2545 > URL: https://issues.apache.org/jira/browse/PROTON-2545 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.37.0 >Reporter: Ken Giusti >Assignee: Clifford Jansen >Priority: Major > > Refer to [https://github.com/skupperproject/skupper-router/issues/477] > TL;DR - if a client closes its TCP connection (full drop - not half close), > the proactor cannot post a PN_RAW_CONNECTION_DISCONNECTED event unless read > buffers have been provided to the raw connection. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2183) [cpp client] No messaging_handler callback for aborted messages
[
https://issues.apache.org/jira/browse/PROTON-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross reassigned PROTON-2183:
---
Assignee: Rakhi Kumari
> [cpp client] No messaging_handler callback for aborted messages
> ---
>
> Key: PROTON-2183
> URL: https://issues.apache.org/jira/browse/PROTON-2183
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding
>Affects Versions: proton-c-0.30.0
>Reporter: Charles E. Rolke
>Assignee: Rakhi Kumari
>Priority: Major
> Attachments: PROTON-2183-send-receive-console.log
>
>
> A cpp receiver throws "receiver read failure" when an aborted message is
> received.
> A client based on:
> {{ class simple_recv : public proton::messaging_handler}}
> does not get called at (on_transport_error, on_connection_error,
> on_session_error, on_sender_error, on_receiver_error, on_error). The
> exception is thrown back to main() and the client application has no way to
> intercept it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2183) [cpp client] No messaging_handler callback for aborted messages
[
https://issues.apache.org/jira/browse/PROTON-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-2183:
Issue Type: Improvement (was: Bug)
> [cpp client] No messaging_handler callback for aborted messages
> ---
>
> Key: PROTON-2183
> URL: https://issues.apache.org/jira/browse/PROTON-2183
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding
>Affects Versions: proton-c-0.30.0
>Reporter: Charles E. Rolke
>Priority: Major
> Attachments: PROTON-2183-send-receive-console.log
>
>
> A cpp receiver throws "receiver read failure" when an aborted message is
> received.
> A client based on:
> {{ class simple_recv : public proton::messaging_handler}}
> does not get called at (on_transport_error, on_connection_error,
> on_session_error, on_sender_error, on_receiver_error, on_error). The
> exception is thrown back to main() and the client application has no way to
> intercept it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2459) Use std::chrono in cpp binding
[
https://issues.apache.org/jira/browse/PROTON-2459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross reassigned PROTON-2459:
---
Assignee: Rakhi Kumari
> Use std::chrono in cpp binding
> --
>
> Key: PROTON-2459
> URL: https://issues.apache.org/jira/browse/PROTON-2459
> Project: Qpid Proton
> Issue Type: Improvement
> Components: cpp-binding
>Affects Versions: proton-c-0.36.0
>Reporter: Jiri Daněk
>Assignee: Rakhi Kumari
>Priority: Major
>
> {noformat}
> // Can't use std::chrono since we still support C++03, sigh.
> {noformat}
> This is not true anymore, C++11 is now the minimum supported, so we may be
> able to remove some ifdefs there, in {{cpp/src/timestamp.cpp}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2438) [cpp] Cancellable tasks
[ https://issues.apache.org/jira/browse/PROTON-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-2438: --- Assignee: Rakhi Kumari (was: Justin Ross) > [cpp] Cancellable tasks > --- > > Key: PROTON-2438 > URL: https://issues.apache.org/jira/browse/PROTON-2438 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Božo Dragojevič >Assignee: Rakhi Kumari >Priority: Major > Fix For: proton-c-0.38.0 > > > Allow scheduled tasks to be cancelled. > A cancelled task does not keep reactor from stoping running -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-2470) [cpp] Access to the local host and port for a connection
[ https://issues.apache.org/jira/browse/PROTON-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-2470. --- Resolution: Won't Do > [cpp] Access to the local host and port for a connection > > > Key: PROTON-2470 > URL: https://issues.apache.org/jira/browse/PROTON-2470 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Rakhi Kumari >Assignee: Rakhi Kumari >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-1594) Expose remote host and port on transport
[ https://issues.apache.org/jira/browse/PROTON-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-1594. --- Resolution: Duplicate > Expose remote host and port on transport > > > Key: PROTON-1594 > URL: https://issues.apache.org/jira/browse/PROTON-1594 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.18.0 >Reporter: Justin Ross >Assignee: Rakhi Kumari >Priority: Major > > So you can, for instance, log where you are connected to. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1594) Expose remote host and port on transport
[ https://issues.apache.org/jira/browse/PROTON-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1594: Fix Version/s: (was: proton-c-future) > Expose remote host and port on transport > > > Key: PROTON-1594 > URL: https://issues.apache.org/jira/browse/PROTON-1594 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.18.0 >Reporter: Justin Ross >Assignee: Rakhi Kumari >Priority: Major > > So you can, for instance, log where you are connected to. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-1594) Expose remote host and port on transport
[ https://issues.apache.org/jira/browse/PROTON-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-1594: --- Assignee: Rakhi Kumari > Expose remote host and port on transport > > > Key: PROTON-1594 > URL: https://issues.apache.org/jira/browse/PROTON-1594 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.18.0 >Reporter: Justin Ross >Assignee: Rakhi Kumari >Priority: Major > Fix For: proton-c-future > > > So you can, for instance, log where you are connected to. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2561) User/Pass connection to ActiveMQ Artemis from Ruby doesn't work
[
https://issues.apache.org/jira/browse/PROTON-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17559166#comment-17559166
]
Justin Ross commented on PROTON-2561:
-
This worked for me with Artemis:
{code:java}
container.connect(@conn_url, {:user => "alice", :password => "secret",
:sasl_allow_insecure_mechs => true})
{code}
If you are not connecting over TLS (or some other secure transport), the Ruby
client won't let you send a password on the wire. The
"sasl_allow_insecure_mechs" option overrides it.
> User/Pass connection to ActiveMQ Artemis from Ruby doesn't work
> ---
>
> Key: PROTON-2561
> URL: https://issues.apache.org/jira/browse/PROTON-2561
> Project: Qpid Proton
> Issue Type: Bug
> Components: ruby-binding
>Affects Versions: proton-c-0.36.0, proton-c-0.37.0
> Environment: MacOS, Ubuntu
>Reporter: Alexandr Kovalenko
>Assignee: Alan Conway
>Priority: Minor
>
> ActiveMQ Artemis 2.22.0
> File {{login.config}} contains:
> {code:java}
> activemq {
> org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLoginModule
> sufficient
> debug=false
> reload=true
> org.apache.activemq.jaas.properties.user="artemis-users.properties"
> org.apache.activemq.jaas.properties.role="artemis-roles.properties";
> };{code}
> Ruby {{helloworld.rb}}
> Set user/pass connection in the past line of code
> {code:java}
> Qpid::Proton::Container.new(HelloWorld.new('amqp://artemis:artemis@localhost:5672',
> 'examples')).run{code}
> The message isn't sent and i see in the Artemis's logs:
> {code:java}
> 2022-06-13 12:07:09,253 WARN [org.apache.activemq.artemis.core.server]
> AMQ16: Security problem while authenticating: AMQ229031: Unable to
> validate user from /172.19.0.1:59864. Username: null; SSL certificate subject
> DN: unavailable
> artemis_1 | 2022-06-13 12:07:09,254 WARN
> [org.apache.activemq.artemis.protocol.amqp.proton.AMQPConnectionContext]
> AMQ229031: Unable to validate user from /172.19.0.1:59864. Username: null;
> SSL certificate subject DN: unavailable:
> ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ229031:
> Unable to validate user from /172.19.0.1:59864. Username: null; SSL
> certificate subject DN: unavailable]{code}
> So Artemis says that it receives username {*}null{*}.
>
> If i try to do the same in Python example - it works correct.
> Python {{helloworld.py}}
> Set user/pass connection in the past line of code
> {code:java}
> Container(HelloWorld("amqp://artemis:artemis@localhost:5672",
> "examples")).run(){code}
> As a result - the message sent and in Artemis's logs all is ok:
> {code:java}
> artemis_1 | 2022-06-13 11:46:30,860 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841000: created
> connection:
> org.apache.activemq.artemis.protocol.amqp.broker.ActiveMQProtonRemotingConnection@151ad103
> artemis_1 | 2022-06-13 11:46:30,970 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841010: routed
> message with ID: 8589934599, result: NO_BINDINGS
> artemis_1 | 2022-06-13 11:46:30,972 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841002: created
> session name: 778f929c-eb0e-11ec-8863-0242ac130002, session connectionID:
> 933989dd
> artemis_1 | 2022-06-13 11:46:30,990 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841010: routed
> message with ID: 8589934600, result: NO_BINDINGS
> artemis_1 | 2022-06-13 11:46:30,992 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841003: closed
> session with session name: 778f929c-eb0e-11ec-8863-0242ac130002, failed: false
> artemis_1 | 2022-06-13 11:46:30,993 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841001: destroyed
> connection:
> org.apache.activemq.artemis.protocol.amqp.broker.ActiveMQProtonRemotingConnection@151ad103{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (PROTON-2561) User/Pass connection to ActiveMQ Artemis from Ruby doesn't work
[
https://issues.apache.org/jira/browse/PROTON-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17559166#comment-17559166
]
Justin Ross edited comment on PROTON-2561 at 6/27/22 1:27 PM:
--
This worked for me with Artemis:
{code:java}
container.connect(@conn_url, {:user => "alice", :password => "secret",
:sasl_allow_insecure_mechs => true})
{code}
If you are not connecting over TLS (or some other secure transport), the Ruby
client won't let you send a password on the wire. The
"sasl_allow_insecure_mechs" option overrides it.
was (Author: justi9):
This worked for me with Artemis:
{code:java}
container.connect(@conn_url, {:user => "alice", :password => "secret",
:sasl_allow_insecure_mechs => true})
{code}
If you are not connecting over TLS (or some other secure transport), the Ruby
client won't let you send a password on the wire. The
"sasl_allow_insecure_mechs" option overrides it.
> User/Pass connection to ActiveMQ Artemis from Ruby doesn't work
> ---
>
> Key: PROTON-2561
> URL: https://issues.apache.org/jira/browse/PROTON-2561
> Project: Qpid Proton
> Issue Type: Bug
> Components: ruby-binding
>Affects Versions: proton-c-0.36.0, proton-c-0.37.0
> Environment: MacOS, Ubuntu
>Reporter: Alexandr Kovalenko
>Assignee: Alan Conway
>Priority: Minor
>
> ActiveMQ Artemis 2.22.0
> File {{login.config}} contains:
> {code:java}
> activemq {
> org.apache.activemq.artemis.spi.core.security.jaas.PropertiesLoginModule
> sufficient
> debug=false
> reload=true
> org.apache.activemq.jaas.properties.user="artemis-users.properties"
> org.apache.activemq.jaas.properties.role="artemis-roles.properties";
> };{code}
> Ruby {{helloworld.rb}}
> Set user/pass connection in the past line of code
> {code:java}
> Qpid::Proton::Container.new(HelloWorld.new('amqp://artemis:artemis@localhost:5672',
> 'examples')).run{code}
> The message isn't sent and i see in the Artemis's logs:
> {code:java}
> 2022-06-13 12:07:09,253 WARN [org.apache.activemq.artemis.core.server]
> AMQ16: Security problem while authenticating: AMQ229031: Unable to
> validate user from /172.19.0.1:59864. Username: null; SSL certificate subject
> DN: unavailable
> artemis_1 | 2022-06-13 12:07:09,254 WARN
> [org.apache.activemq.artemis.protocol.amqp.proton.AMQPConnectionContext]
> AMQ229031: Unable to validate user from /172.19.0.1:59864. Username: null;
> SSL certificate subject DN: unavailable:
> ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ229031:
> Unable to validate user from /172.19.0.1:59864. Username: null; SSL
> certificate subject DN: unavailable]{code}
> So Artemis says that it receives username {*}null{*}.
>
> If i try to do the same in Python example - it works correct.
> Python {{helloworld.py}}
> Set user/pass connection in the past line of code
> {code:java}
> Container(HelloWorld("amqp://artemis:artemis@localhost:5672",
> "examples")).run(){code}
> As a result - the message sent and in Artemis's logs all is ok:
> {code:java}
> artemis_1 | 2022-06-13 11:46:30,860 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841000: created
> connection:
> org.apache.activemq.artemis.protocol.amqp.broker.ActiveMQProtonRemotingConnection@151ad103
> artemis_1 | 2022-06-13 11:46:30,970 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841010: routed
> message with ID: 8589934599, result: NO_BINDINGS
> artemis_1 | 2022-06-13 11:46:30,972 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841002: created
> session name: 778f929c-eb0e-11ec-8863-0242ac130002, session connectionID:
> 933989dd
> artemis_1 | 2022-06-13 11:46:30,990 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841010: routed
> message with ID: 8589934600, result: NO_BINDINGS
> artemis_1 | 2022-06-13 11:46:30,992 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841003: closed
> session with session name: 778f929c-eb0e-11ec-8863-0242ac130002, failed: false
> artemis_1 | 2022-06-13 11:46:30,993 INFO
> [org.apache.activemq.artemis.core.server.plugin.impl] AMQ841001: destroyed
> connection:
> org.apache.activemq.artemis.protocol.amqp.broker.ActiveMQProtonRemotingConnection@151ad103{code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2544) Build fails on Fedora 36
[
https://issues.apache.org/jira/browse/PROTON-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross reassigned PROTON-2544:
---
Assignee: Clifford Jansen
> Build fails on Fedora 36
>
>
> Key: PROTON-2544
> URL: https://issues.apache.org/jira/browse/PROTON-2544
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Reporter: Justin Ross
>Assignee: Clifford Jansen
>Priority: Major
>
> Fedora 36 has GCC 12 and OpenSSL 3.
> {noformat}
> ~/code/qpid-proton/bld$ cmake .. -DCMAKE_INSTALL_PREFIX=~/.local
> -- The C compiler identification is GNU 12.1.1
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Found OpenSSL: /usr/lib64/libcrypto.so (found version "3.0.2")
> -- Looking for pthread.h
> -- Looking for pthread.h - found
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
> -- Found Threads: TRUE
> -- Found SWIG: /usr/bin/swig (found version "4.0.2")
> -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.0")
> -- Found CyrusSASL: /usr/lib64/libsasl2.so (found version "2.1.27")
> -- Found Python: /usr/bin/python3.10 (found suitable version "3.10.4",
> minimum required is "3.6") found components: Interpreter Development
> Development.Module Development.Embed
> -- Looking for a CXX compiler
> -- Looking for a CXX compiler - /usr/bin/c++
> -- The CXX compiler identification is GNU 12.1.1
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Build type is "RelWithDebInfo" (has debug symbols)
> -- PN_VERSION: 0.38.0 (dev)
> -- Looking for clock_gettime
> -- Looking for clock_gettime - found
> -- Looking for strerror_r
> -- Looking for strerror_r - found
> -- Looking for epoll_wait
> -- Looking for epoll_wait - found
> -- Building the epoll proactor
> -- Found Doxygen: /usr/bin/doxygen (found version "1.9.1") found components:
> doxygen dot
> CMake Deprecation Warning at CMakeLists.txt:374 (cmake_policy):
> The OLD behavior for policy CMP0078 will be removed from a future version
> of CMake. The cmake-policies(7) manual explains that the OLD behaviors of
> all
> policies are deprecated and that a policy should be set to OLD only under
> specific short-term circumstances. Projects should be ported to the NEW
> behavior and not rely on setting a policy to OLD.
> CMake Deprecation Warning at CMakeLists.txt:377 (cmake_policy):
> The OLD behavior for policy CMP0086 will be removed from a future version
> of CMake. The cmake-policies(7) manual explains that the OLD behaviors of
> all
> policies are deprecated and that a policy should be set to OLD only under
> specific short-term circumstances. Projects should be ported to the NEW
> behavior and not rely on setting a policy to OLD.
> -- Found Ruby: /usr/bin/ruby (found suitable version "3.1.2", minimum
> required is "1.8.0")
> -- Found JsonCpp: /lib64/libjsoncpp.so (found version "1.9.5")
> -- Looking for Python module sphinx - found
> -- Looking for Python module setuptools - found
> -- Looking for Python module wheel - not found
> -- Looking for Python module flake8 - not found
> -- Looking for Python module tox - not found
> -- The tox tool is not available; skipping the python-tox-tests
> -- Ruby tests will not run, minitest is not installed
> -- Configuring done
> -- Generating done
> -- Build files have been written to:
> /home/jross/code/qpid-proton/bld~/code/qpid-proton/bld$ make -j $(nproc)
> Scanning dependencies of target cproton_swig_compilation
> Scanning dependencies of target cproton-ruby_swig_compilation
> [ 1%] Building C object
> c/CMakeFiles/qpid-proton-platform-io-objects.dir/src/reactor/io/posix/io.c.o
> [ 1%] Building C object
> c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/epoll.c.o
> [ 1%] Building C object
> c/CMakeFiles/qpid-proton-platform-io-objects.dir/src/platform/platform.c.o
> [ 1%] Generating src/protocol.h
> [ 2%] Generating src/encodings.h
> [ 2%] Generating src/core/frame_generators.c, src/core/frame_generators.h
> [ 3%] Generating src/core/frame_consumers.c, src/core/frame_consumers.h
> [ 3%] Building CXX object c/tests/CMakeFiles/test_main.dir/test_main.cpp.o
> [ 3%] Building C object
> c/tests/fuzz/CMakeFiles/StandaloneFuzzTargetMain.dir/StandaloneFuzzTargetMain.c.o
> [ 3%] Building C object
> c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/epoll_timer.c.o
> [ 3%] Building C object
> c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/netaddr-internal.c.o
[jira] [Updated] (PROTON-2544) Build fails on Fedora 36
[
https://issues.apache.org/jira/browse/PROTON-2544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-2544:
Component/s: proton-c
> Build fails on Fedora 36
>
>
> Key: PROTON-2544
> URL: https://issues.apache.org/jira/browse/PROTON-2544
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Reporter: Justin Ross
>Priority: Major
>
> Fedora 36 has GCC 12 and OpenSSL 3.
> {noformat}
> ~/code/qpid-proton/bld$ cmake .. -DCMAKE_INSTALL_PREFIX=~/.local
> -- The C compiler identification is GNU 12.1.1
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Check for working C compiler: /usr/bin/cc - skipped
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Found OpenSSL: /usr/lib64/libcrypto.so (found version "3.0.2")
> -- Looking for pthread.h
> -- Looking for pthread.h - found
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
> -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
> -- Found Threads: TRUE
> -- Found SWIG: /usr/bin/swig (found version "4.0.2")
> -- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.0")
> -- Found CyrusSASL: /usr/lib64/libsasl2.so (found version "2.1.27")
> -- Found Python: /usr/bin/python3.10 (found suitable version "3.10.4",
> minimum required is "3.6") found components: Interpreter Development
> Development.Module Development.Embed
> -- Looking for a CXX compiler
> -- Looking for a CXX compiler - /usr/bin/c++
> -- The CXX compiler identification is GNU 12.1.1
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Check for working CXX compiler: /usr/bin/c++ - skipped
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Build type is "RelWithDebInfo" (has debug symbols)
> -- PN_VERSION: 0.38.0 (dev)
> -- Looking for clock_gettime
> -- Looking for clock_gettime - found
> -- Looking for strerror_r
> -- Looking for strerror_r - found
> -- Looking for epoll_wait
> -- Looking for epoll_wait - found
> -- Building the epoll proactor
> -- Found Doxygen: /usr/bin/doxygen (found version "1.9.1") found components:
> doxygen dot
> CMake Deprecation Warning at CMakeLists.txt:374 (cmake_policy):
> The OLD behavior for policy CMP0078 will be removed from a future version
> of CMake. The cmake-policies(7) manual explains that the OLD behaviors of
> all
> policies are deprecated and that a policy should be set to OLD only under
> specific short-term circumstances. Projects should be ported to the NEW
> behavior and not rely on setting a policy to OLD.
> CMake Deprecation Warning at CMakeLists.txt:377 (cmake_policy):
> The OLD behavior for policy CMP0086 will be removed from a future version
> of CMake. The cmake-policies(7) manual explains that the OLD behaviors of
> all
> policies are deprecated and that a policy should be set to OLD only under
> specific short-term circumstances. Projects should be ported to the NEW
> behavior and not rely on setting a policy to OLD.
> -- Found Ruby: /usr/bin/ruby (found suitable version "3.1.2", minimum
> required is "1.8.0")
> -- Found JsonCpp: /lib64/libjsoncpp.so (found version "1.9.5")
> -- Looking for Python module sphinx - found
> -- Looking for Python module setuptools - found
> -- Looking for Python module wheel - not found
> -- Looking for Python module flake8 - not found
> -- Looking for Python module tox - not found
> -- The tox tool is not available; skipping the python-tox-tests
> -- Ruby tests will not run, minitest is not installed
> -- Configuring done
> -- Generating done
> -- Build files have been written to:
> /home/jross/code/qpid-proton/bld~/code/qpid-proton/bld$ make -j $(nproc)
> Scanning dependencies of target cproton_swig_compilation
> Scanning dependencies of target cproton-ruby_swig_compilation
> [ 1%] Building C object
> c/CMakeFiles/qpid-proton-platform-io-objects.dir/src/reactor/io/posix/io.c.o
> [ 1%] Building C object
> c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/epoll.c.o
> [ 1%] Building C object
> c/CMakeFiles/qpid-proton-platform-io-objects.dir/src/platform/platform.c.o
> [ 1%] Generating src/protocol.h
> [ 2%] Generating src/encodings.h
> [ 2%] Generating src/core/frame_generators.c, src/core/frame_generators.h
> [ 3%] Generating src/core/frame_consumers.c, src/core/frame_consumers.h
> [ 3%] Building CXX object c/tests/CMakeFiles/test_main.dir/test_main.cpp.o
> [ 3%] Building C object
> c/tests/fuzz/CMakeFiles/StandaloneFuzzTargetMain.dir/StandaloneFuzzTargetMain.c.o
> [ 3%] Building C object
> c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/epoll_timer.c.o
> [ 3%] Building C object
> c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/netaddr-internal.c.o
> [ 4%] Building C object
> c/CMakeFiles/qpid-p
[jira] [Created] (PROTON-2544) Build fails on Fedora 36
Justin Ross created PROTON-2544:
---
Summary: Build fails on Fedora 36
Key: PROTON-2544
URL: https://issues.apache.org/jira/browse/PROTON-2544
Project: Qpid Proton
Issue Type: Bug
Reporter: Justin Ross
Fedora 36 has GCC 12 and OpenSSL 3.
{noformat}
~/code/qpid-proton/bld$ cmake .. -DCMAKE_INSTALL_PREFIX=~/.local
-- The C compiler identification is GNU 12.1.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Found OpenSSL: /usr/lib64/libcrypto.so (found version "3.0.2")
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Found SWIG: /usr/bin/swig (found version "4.0.2")
-- Found PkgConfig: /usr/bin/pkg-config (found version "1.8.0")
-- Found CyrusSASL: /usr/lib64/libsasl2.so (found version "2.1.27")
-- Found Python: /usr/bin/python3.10 (found suitable version "3.10.4", minimum
required is "3.6") found components: Interpreter Development Development.Module
Development.Embed
-- Looking for a CXX compiler
-- Looking for a CXX compiler - /usr/bin/c++
-- The CXX compiler identification is GNU 12.1.1
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Build type is "RelWithDebInfo" (has debug symbols)
-- PN_VERSION: 0.38.0 (dev)
-- Looking for clock_gettime
-- Looking for clock_gettime - found
-- Looking for strerror_r
-- Looking for strerror_r - found
-- Looking for epoll_wait
-- Looking for epoll_wait - found
-- Building the epoll proactor
-- Found Doxygen: /usr/bin/doxygen (found version "1.9.1") found components:
doxygen dot
CMake Deprecation Warning at CMakeLists.txt:374 (cmake_policy):
The OLD behavior for policy CMP0078 will be removed from a future version
of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all
policies are deprecated and that a policy should be set to OLD only under
specific short-term circumstances. Projects should be ported to the NEW
behavior and not rely on setting a policy to OLD.
CMake Deprecation Warning at CMakeLists.txt:377 (cmake_policy):
The OLD behavior for policy CMP0086 will be removed from a future version
of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all
policies are deprecated and that a policy should be set to OLD only under
specific short-term circumstances. Projects should be ported to the NEW
behavior and not rely on setting a policy to OLD.
-- Found Ruby: /usr/bin/ruby (found suitable version "3.1.2", minimum required
is "1.8.0")
-- Found JsonCpp: /lib64/libjsoncpp.so (found version "1.9.5")
-- Looking for Python module sphinx - found
-- Looking for Python module setuptools - found
-- Looking for Python module wheel - not found
-- Looking for Python module flake8 - not found
-- Looking for Python module tox - not found
-- The tox tool is not available; skipping the python-tox-tests
-- Ruby tests will not run, minitest is not installed
-- Configuring done
-- Generating done
-- Build files have been written to:
/home/jross/code/qpid-proton/bld~/code/qpid-proton/bld$ make -j $(nproc)
Scanning dependencies of target cproton_swig_compilation
Scanning dependencies of target cproton-ruby_swig_compilation
[ 1%] Building C object
c/CMakeFiles/qpid-proton-platform-io-objects.dir/src/reactor/io/posix/io.c.o
[ 1%] Building C object
c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/epoll.c.o
[ 1%] Building C object
c/CMakeFiles/qpid-proton-platform-io-objects.dir/src/platform/platform.c.o
[ 1%] Generating src/protocol.h
[ 2%] Generating src/encodings.h
[ 2%] Generating src/core/frame_generators.c, src/core/frame_generators.h
[ 3%] Generating src/core/frame_consumers.c, src/core/frame_consumers.h
[ 3%] Building CXX object c/tests/CMakeFiles/test_main.dir/test_main.cpp.o
[ 3%] Building C object
c/tests/fuzz/CMakeFiles/StandaloneFuzzTargetMain.dir/StandaloneFuzzTargetMain.c.o
[ 3%] Building C object
c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/epoll_timer.c.o
[ 3%] Building C object
c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/netaddr-internal.c.o
[ 4%] Building C object
c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/proactor-internal.c.o
[ 4%] Building C object
c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/raw_connection.c.o
[ 5%] Building C object
c/tests/fuzz/CMakeFiles/StandaloneFuzzTargetMain.dir/StandaloneFuzzTargetInit.c.o
[ 5%] Building C object
c/CMakeFiles/qpid-proton-platform-io-objects.dir/src/reactor/io/posix/selector.c.o
[ 5%] Building C object
[jira] [Assigned] (PROTON-2543) Crash in epoll.c resched_pop_front
[ https://issues.apache.org/jira/browse/PROTON-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-2543: --- Assignee: Clifford Jansen > Crash in epoll.c resched_pop_front > -- > > Key: PROTON-2543 > URL: https://issues.apache.org/jira/browse/PROTON-2543 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Fredrik Hallenberg >Assignee: Clifford Jansen >Priority: Major > Attachments: qpid-epoll-crash.patch > > > During stress testing it is fairly easy to reproduce a segfault in > resched_pop_front. Using gdb it is easy to see that polled_resched_front can > be zero when entering this function which causes the value to wrap and then a > crash in later calls. > polled_resched_front is not checked when calling this function in one > instance, the trivial fix to check this value is seen in the attached patch > seems to work. > Tested with Qpid Proton C++ 0.37. > -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2543) Crash in epoll.c resched_pop_front
[ https://issues.apache.org/jira/browse/PROTON-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2543: Component/s: proton-c > Crash in epoll.c resched_pop_front > -- > > Key: PROTON-2543 > URL: https://issues.apache.org/jira/browse/PROTON-2543 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Fredrik Hallenberg >Priority: Major > Attachments: qpid-epoll-crash.patch > > > During stress testing it is fairly easy to reproduce a segfault in > resched_pop_front. Using gdb it is easy to see that polled_resched_front can > be zero when entering this function which causes the value to wrap and then a > crash in later calls. > polled_resched_front is not checked when calling this function in one > instance, the trivial fix to check this value is seen in the attached patch > seems to work. > Tested with Qpid Proton C++ 0.37. > -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-1840) [cpp] Nested complex types fail compilation with "incomplete type" error
[
https://issues.apache.org/jira/browse/PROTON-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross closed PROTON-1840.
---
Resolution: Won't Fix
> [cpp] Nested complex types fail compilation with "incomplete type" error
>
>
> Key: PROTON-1840
> URL: https://issues.apache.org/jira/browse/PROTON-1840
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Reporter: Kim van der Riet
>Priority: Major
> Labels: codec
>
> When using nested complex types (for example, a list of maps or an array of
> lists), the compiler fails to compile. For example, the following code
> snippet (saved as {{ctt.cpp}}):
> {noformat}
> #include
> #include
> #include
> int main(int, char**) {
> std::map m1 = {{uint8_t(0), "zero"},
> {uint8_t(1), "one"}};
> std::map m2 = {{true, "true"}, {false,
> "false"}};
> std::vector > am = {m1, m2};
> proton::value pv = am;
> }{noformat}
> fails compilation with the following error:
> {noformat}
> In file included from install/include/proton/types.hpp:47:0,
> from ctt.cpp:3:
> install/include/proton/./codec/vector.hpp: In instantiation of
> ‘proton::codec::encoder& proton::codec::operator<<(proton::codec::encoder&,
> const std::vector<_Tp, _Alloc>&) [with T = std::map proton::value>; A = std::allocator >]’:
> install/include/proton/./value.hpp:84:11: required from ‘typename
> proton::value::assignable::type
> proton::value::operator=(const T&) [with T =
> std::vector >; typename
> proton::value::assignable::type = proton::value&]’
> install/include/proton/./value.hpp:79:85: required from
> ‘proton::value::value(const T&, typename proton::value::assignable::type*)
> [with T = std::vector >; typename
> proton::value::assignable::type = void]’
> ctt.cpp:9:24: required from here
> install/include/proton/./codec/vector.hpp:39:31: error: incomplete type
> ‘proton::internal::type_id_of >’ used
> in nested name specifier
> return e << encoder::array(x, internal::type_id_of::value);
> ~~^~~
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1840) [cpp] Nested complex types fail compilation with "incomplete type" error
[
https://issues.apache.org/jira/browse/PROTON-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17538290#comment-17538290
]
Justin Ross commented on PROTON-1840:
-
Closing, since this has a good workaround and we don't think it's worth
addressing right now.
> [cpp] Nested complex types fail compilation with "incomplete type" error
>
>
> Key: PROTON-1840
> URL: https://issues.apache.org/jira/browse/PROTON-1840
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Reporter: Kim van der Riet
>Priority: Major
> Labels: codec
>
> When using nested complex types (for example, a list of maps or an array of
> lists), the compiler fails to compile. For example, the following code
> snippet (saved as {{ctt.cpp}}):
> {noformat}
> #include
> #include
> #include
> int main(int, char**) {
> std::map m1 = {{uint8_t(0), "zero"},
> {uint8_t(1), "one"}};
> std::map m2 = {{true, "true"}, {false,
> "false"}};
> std::vector > am = {m1, m2};
> proton::value pv = am;
> }{noformat}
> fails compilation with the following error:
> {noformat}
> In file included from install/include/proton/types.hpp:47:0,
> from ctt.cpp:3:
> install/include/proton/./codec/vector.hpp: In instantiation of
> ‘proton::codec::encoder& proton::codec::operator<<(proton::codec::encoder&,
> const std::vector<_Tp, _Alloc>&) [with T = std::map proton::value>; A = std::allocator >]’:
> install/include/proton/./value.hpp:84:11: required from ‘typename
> proton::value::assignable::type
> proton::value::operator=(const T&) [with T =
> std::vector >; typename
> proton::value::assignable::type = proton::value&]’
> install/include/proton/./value.hpp:79:85: required from
> ‘proton::value::value(const T&, typename proton::value::assignable::type*)
> [with T = std::vector >; typename
> proton::value::assignable::type = void]’
> ctt.cpp:9:24: required from here
> install/include/proton/./codec/vector.hpp:39:31: error: incomplete type
> ‘proton::internal::type_id_of >’ used
> in nested name specifier
> return e << encoder::array(x, internal::type_id_of::value);
> ~~^~~
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-2139) [cpp] Configuration for TLS versions and ciphers
[ https://issues.apache.org/jira/browse/PROTON-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-2139. --- Resolution: Won't Do OpenSSL provides a way to configure this at the system level. > [cpp] Configuration for TLS versions and ciphers > > > Key: PROTON-2139 > URL: https://issues.apache.org/jira/browse/PROTON-2139 > Project: Qpid Proton > Issue Type: New Feature > Components: cpp-binding >Affects Versions: proton-c-0.29.0 >Reporter: Justin Ross >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2502) Stop using deprecated (and insecure) SASL mechanisms based on MD5
[ https://issues.apache.org/jira/browse/PROTON-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531266#comment-17531266 ] Justin Ross commented on PROTON-2502: - Proposed resolution to one aspect of this: Take the SASL encryption code path out of Proton. Users should use TLS for encryption. > Stop using deprecated (and insecure) SASL mechanisms based on MD5 > - > > Key: PROTON-2502 > URL: https://issues.apache.org/jira/browse/PROTON-2502 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Minor > > MD5 has been considered broken and hence insecure for about a decade now. We > should stop requiring it to test proton so that we can build on machines > configured without insecure SASL mechanisms. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-2391) Non existing binding specified in -DBUILD_BINDINGS are skipped without raising error
[ https://issues.apache.org/jira/browse/PROTON-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-2391. --- Resolution: Not A Problem > Non existing binding specified in -DBUILD_BINDINGS are skipped without > raising error > > > Key: PROTON-2391 > URL: https://issues.apache.org/jira/browse/PROTON-2391 > Project: Qpid Proton > Issue Type: Bug > Components: build >Reporter: Arunagirinadan Sudharshan >Priority: Major > > If non-existing binding specified in cmake command for -DBUILD_BINDING, they > are skipped and doesn't raise any error or warning. > cmake .. -DMAKE_INSTALL_PREFIX=install -DBUILD_BINDINGS='python;something' > The correct separator is `;`, if `,` is used it is requesting a single > binding has `python,something`. Documentation for option are needed. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2391) Non existing binding specified in -DBUILD_BINDINGS are skipped without raising error
[ https://issues.apache.org/jira/browse/PROTON-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531261#comment-17531261 ] Justin Ross commented on PROTON-2391: - BUILD_BINDINGS is internal interface. We recommend using BUILD_ instead. > Non existing binding specified in -DBUILD_BINDINGS are skipped without > raising error > > > Key: PROTON-2391 > URL: https://issues.apache.org/jira/browse/PROTON-2391 > Project: Qpid Proton > Issue Type: Bug > Components: build >Reporter: Arunagirinadan Sudharshan >Priority: Major > > If non-existing binding specified in cmake command for -DBUILD_BINDING, they > are skipped and doesn't raise any error or warning. > cmake .. -DMAKE_INSTALL_PREFIX=install -DBUILD_BINDINGS='python;something' > The correct separator is `;`, if `,` is used it is requesting a single > binding has `python,something`. Documentation for option are needed. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-2107) Go module support
[ https://issues.apache.org/jira/browse/PROTON-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-2107. --- Resolution: Fixed > Go module support > - > > Key: PROTON-2107 > URL: https://issues.apache.org/jira/browse/PROTON-2107 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Affects Versions: proton-c-0.29.0 >Reporter: Thtiphong Anansukkasem >Assignee: Roddie Kieley >Priority: Major > > I found the error , when i run "go get" command in go module enabled project > $go get -v qpid.apache.org/electron > go: finding qpid.apache.org latest > go get qpid.apache.org/electron: module qpid.apache.org@upgrade > (v0.0.0-20190919033840-551513f49822) found, but does not contain package > qpid.apache.org/electron > $ go get -v qpid.apache.org/amqp > go: finding qpid.apache.org latest > go get qpid.apache.org/amqp: module qpid.apache.org@upgrade > (v0.0.0-20190919033840-551513f49822) found, but does not contain package > qpid.apache.org/amqp > -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-1746) Add ability to build both Python 2.x and Python 3.x bindings in a single build
[ https://issues.apache.org/jira/browse/PROTON-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-1746. --- Resolution: Won't Fix > Add ability to build both Python 2.x and Python 3.x bindings in a single build > -- > > Key: PROTON-1746 > URL: https://issues.apache.org/jira/browse/PROTON-1746 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Reporter: Kim van der Riet >Priority: Major > > Currently the Cmake build process detects the available Python version and > builds according to a default if more than one version is available (at > present 2.7 willl be built even if 3.x is available). > Add the ability to detect and build for each of the major versions of Python > in the same build. I suggest that if both Python 2.x and 3.x is available, > then by default, both are built. However, a switch should be available to > disable one or the other version if desired. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-2090) [macOS] Update Travis CI for latest macOS Mojave 10.14.z
[ https://issues.apache.org/jira/browse/PROTON-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-2090. --- Resolution: Won't Fix > [macOS] Update Travis CI for latest macOS Mojave 10.14.z > > > Key: PROTON-2090 > URL: https://issues.apache.org/jira/browse/PROTON-2090 > Project: Qpid Proton > Issue Type: Improvement > Components: build >Reporter: Roddie Kieley >Assignee: Roddie Kieley >Priority: Minor > > At the moment the Travis CI is configured for macOS 10.12/Xcode 8.3 at the > low end and 10.13/Xcode10.1 at the upper end, while the latest available is > 10.14/Xcode11. It may be beneficial to update the travis configuration to > utilize the new upper end configuration. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2070) [ASAN] some tests always fail when using sanitizer builds
[ https://issues.apache.org/jira/browse/PROTON-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531257#comment-17531257 ] Justin Ross commented on PROTON-2070: - Proposed resolution: Disable the Tox tests (and maybe the Ruby tests) when using ASAN. CI is doing this: [https://github.com/apache/qpid-proton/blob/700781bd137bdac9ad0165f96ee2056305c89d67/.travis.yml#L66] > [ASAN] some tests always fail when using sanitizer builds > - > > Key: PROTON-2070 > URL: https://issues.apache.org/jira/browse/PROTON-2070 > Project: Qpid Proton > Issue Type: Bug > Components: build, python-binding, ruby-binding >Reporter: Andrew Stitcher >Assignee: Alan Conway >Priority: Major > > But the test failures don't indicate anything about our code: > python-tox-test: > This fails because the sanitiser preload gets applied to python and gcc which > reports leaks. In this case we should probably not do the preload anyway or > not run the test. > ruby-example-test: > This case fails due to the preload not being active - however if the preload > is added to this test then it finds leaks in the ruby interpreter. Again > probably we should not include this test when sanitizers are being tested. -- This message was sent by Atlassian Jira (v8.20.7#820007) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-1950) [proton-c] build intermittently fails to produce good python tox header file
[
https://issues.apache.org/jira/browse/PROTON-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross closed PROTON-1950.
---
Resolution: Cannot Reproduce
We believe this is stale.
> [proton-c] build intermittently fails to produce good python tox header file
>
>
> Key: PROTON-1950
> URL: https://issues.apache.org/jira/browse/PROTON-1950
> Project: Qpid Proton
> Issue Type: Bug
> Components: build
>Affects Versions: proton-c-0.25.0
>Reporter: Charles E. Rolke
>Priority: Major
>
> Building from source, not installed, and running tests:
> {{ mkdir build
> cdbuild
> cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/opt/local ..
> make -j 8
> make test
> }}
> fails python-tox-test. To see what's wrong:
> {{ ctest -VV -R python-tox-test
> }}
> shows:
> {{ 33:
> /home/chug/tmp/proton-0.26-rc2/qpid-proton-0.26.0/build/python/dist/src/core/message.c:118:24:
>
> error: ‘HEADER_PRIORITY_DEFAULT’ undeclared (first use in this function)
> 33:if (msg->priority != HEADER_PRIORITY_DEFAULT) {
> }}
> It looks like the header file that defines HEADER_PRIORITY_DEFAULT has an
> issue.
> By running 'make' again python-tox-test passes. I suspect that there is some
> kind of race with doing 'make -j 8' if running make again fixes things.
> This error does not always happen. Sometimes I can do clean cmake/build and
> it works just fine.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-2538) [python] Address lookup failure stops further reconnect attempts
[
https://issues.apache.org/jira/browse/PROTON-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-2538:
Description:
Client program:
[https://github.com/amqphub/equipage/blob/main/qpid-proton-python/connect.py]
Test output:
{noformat}
~/code/equipage/qpid-proton-python$ python connect.py notthere.net
Traceback (most recent call last):
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 134, in _dispatch
m = getattr(handler, method)
AttributeError: 'GlobalOverrides' object has no attribute
'on_connection_bound'During handling of the above exception, another exception
occurred:Traceback (most recent call last):
File "/home/jross/code/equipage/qpid-proton-python/connect.py", line 56, in
main()
File "/home/jross/code/equipage/qpid-proton-python/connect.py", line 52, in
main
container.run()
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_reactor.py",
line 197, in run
while self.process():
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_reactor.py",
line 262, in process
event.dispatch(self._global_handler)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 170, in dispatch
_dispatch(handler, type.method, self)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 137, in _dispatch
handler.on_unhandled(method, *args)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_reactor.py",
line 905, in on_unhandled
event.dispatch(self.base)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 170, in dispatch
_dispatch(handler, type.method, self)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 139, in _dispatch
m(*args)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_handlers.py",
line 1278, in on_connection_bound
addrs = socket.getaddrinfo(host, port, socket.AF_UNSPEC, socket.SOCK_STREAM)
File "/usr/lib64/python3.9/socket.py", line 954, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
~/code/equipage/qpid-proton-python$ python connect.py example.net
^C
~/code/equipage/qpid-proton-python$
{noformat}
[https://github.com/apache/qpid-proton/blob/700781bd137bdac9ad0165f96ee2056305c89d67/python/proton/_handlers.py#L1278]
was:
Client program:
[https://github.com/amqphub/equipage/blob/main/qpid-proton-python/connect.py]
Test output:
{noformat}
~/code/equipage/qpid-proton-python$ python connect.py notthere.net
Traceback (most recent call last):
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 134, in _dispatch
m = getattr(handler, method)
AttributeError: 'GlobalOverrides' object has no attribute
'on_connection_bound'During handling of the above exception, another exception
occurred:Traceback (most recent call last):
File "/home/jross/code/equipage/qpid-proton-python/connect.py", line 56, in
main()
File "/home/jross/code/equipage/qpid-proton-python/connect.py", line 52, in
main
container.run()
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_reactor.py",
line 197, in run
while self.process():
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_reactor.py",
line 262, in process
event.dispatch(self._global_handler)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 170, in dispatch
_dispatch(handler, type.method, self)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 137, in _dispatch
handler.on_unhandled(method, *args)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_reactor.py",
line 905, in on_unhandled
event.dispatch(self.base)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 170, in dispatch
_dispatch(handler, type.method, self)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 139, in _dispatch
[jira] [Created] (PROTON-2538) [python] Address lookup failure stops further reconnect attempts
Justin Ross created PROTON-2538:
---
Summary: [python] Address lookup failure stops further reconnect
attempts
Key: PROTON-2538
URL: https://issues.apache.org/jira/browse/PROTON-2538
Project: Qpid Proton
Issue Type: Bug
Components: python-binding
Reporter: Justin Ross
Client program:
[https://github.com/amqphub/equipage/blob/main/qpid-proton-python/connect.py]
Test output:
{noformat}
~/code/equipage/qpid-proton-python$ python connect.py notthere.net
Traceback (most recent call last):
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 134, in _dispatch
m = getattr(handler, method)
AttributeError: 'GlobalOverrides' object has no attribute
'on_connection_bound'During handling of the above exception, another exception
occurred:Traceback (most recent call last):
File "/home/jross/code/equipage/qpid-proton-python/connect.py", line 56, in
main()
File "/home/jross/code/equipage/qpid-proton-python/connect.py", line 52, in
main
container.run()
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_reactor.py",
line 197, in run
while self.process():
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_reactor.py",
line 262, in process
event.dispatch(self._global_handler)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 170, in dispatch
_dispatch(handler, type.method, self)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 137, in _dispatch
handler.on_unhandled(method, *args)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_reactor.py",
line 905, in on_unhandled
event.dispatch(self.base)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 170, in dispatch
_dispatch(handler, type.method, self)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_events.py",
line 139, in _dispatch
m(*args)
File
"/home/jross/.local/lib/python3.9/site-packages/python_qpid_proton-0.38.0-py3.9-linux-x86_64.egg/proton/_handlers.py",
line 1278, in on_connection_bound
addrs = socket.getaddrinfo(host, port, socket.AF_UNSPEC, socket.SOCK_STREAM)
File "/usr/lib64/python3.9/socket.py", line 954, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not
known~/code/equipage/qpid-proton-python$ python connect.py example.net
^C
~/code/equipage/qpid-proton-python$
{noformat}
https://github.com/apache/qpid-proton/blob/700781bd137bdac9ad0165f96ee2056305c89d67/python/proton/_handlers.py#L1278
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (PROTON-2121) python-qpid-proton 0.28 BlockingConnection leaks connections (does not close file descriptors)
[
https://issues.apache.org/jira/browse/PROTON-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross reassigned PROTON-2121:
---
Assignee: Clifford Jansen
> python-qpid-proton 0.28 BlockingConnection leaks connections (does not close
> file descriptors)
> --
>
> Key: PROTON-2121
> URL: https://issues.apache.org/jira/browse/PROTON-2121
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: proton-c-0.28.0, proton-c-0.30.0
>Reporter: Lukas
>Assignee: Clifford Jansen
>Priority: Major
> Labels: leak
>
> Starting in proton 0.28.0 and verified in 0.29.0b1 (pre-release) I can
> confirm following issue:
>
> {code:java}
> from proton.utils import BlockingConnection
> c = BlockingConnection(YOUR_ADDRESS)
> c.close()
> # ^^ FINE, all file descriptors closed properly
> from proton.utils import BlockingConnection
> c = BlockingConnection(YOUR_ADDRESS)
> s = c.create_sender(YOUR_EXCHANGE)
> s.close()
> c.close()
> # ^^ leaks the socket file descriptor - connection not closed properly (ls
> /proc/YOUR_PID/fd to verify){code}
>
> Version 0.27.0 is *not* affected by this issue.
>
> Having a quick look at the proton bindings, this very well might be bug in
> the qpid proton library itself, not the python bindings!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (PROTON-2176) CLOSE_WAIT after BlockingSender close
[ https://issues.apache.org/jira/browse/PROTON-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reopened PROTON-2176: - Assignee: Clifford Jansen > CLOSE_WAIT after BlockingSender close > - > > Key: PROTON-2176 > URL: https://issues.apache.org/jira/browse/PROTON-2176 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding > Environment: Linux >Reporter: Stefan Rijnhart >Assignee: Clifford Jansen >Priority: Major > Attachments: 20200130-proton_close_wait.log > > > from proton.utils import BlockingConnection > connection = BlockingConnection(url) > sender = connection.create_sender(queue_name) > sender.send(message) > sender.close() > connection.close() > Leaves a CLOSE_WAIT lingering indefinitely every time, leading to ValueError: > filedescriptor out of range in select() when ulimit is reached. > python_qpid_proton-0.30.0-py2.7-linux-x86_64 talking to ActiveMQ 5.14.5. > Problem also occurs in 0.29.0, 0.28.0 but not in 0.27.0. > Debug log attached. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2512) Proton raw TLS library does not build on aarch64 Ubuntu in Travis CI
[
https://issues.apache.org/jira/browse/PROTON-2512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501428#comment-17501428
]
Justin Ross commented on PROTON-2512:
-
This is on Ubuntu Focal.
> Proton raw TLS library does not build on aarch64 Ubuntu in Travis CI
>
>
> Key: PROTON-2512
> URL: https://issues.apache.org/jira/browse/PROTON-2512
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.37.0
>Reporter: Jiri Daněk
>Priority: Major
>
> https://app.travis-ci.com/github/jiridanek/skupper-router/jobs/562112202#L605
> {noformat}
> cmake ..
> -DCMAKE_INSTALL_PREFIX=/home/travis/build/jiridanek/skupper-router/install
> -DCMAKE_BUILD_TYPE=RelWithDebInfo -DBUILD_BINDINGS=python -DBUILD_TLS=ON
> {noformat}
> [...]
> {noformat}
> [ 8%] Building C object
> c/CMakeFiles/qpid-proton-proactor-objects.dir/src/proactor/epoll_raw_connection.c.o
> /home/travis/build/jiridanek/skupper-router/qpid-proton/c/src/tls/openssl.c:1465:22:
> error: unused function 'size_min' [-Werror,-Wunused-function]
> static inline size_t size_min(uint32_t a, uint32_t b) {
> ^
> 1 error generated.
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (PROTON-2440) Configured heartbeats sometimes don't function in inter-cloud environments
[ https://issues.apache.org/jira/browse/PROTON-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reopened PROTON-2440: - > Configured heartbeats sometimes don't function in inter-cloud environments > -- > > Key: PROTON-2440 > URL: https://issues.apache.org/jira/browse/PROTON-2440 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.35.0 >Reporter: Ted Ross >Priority: Major > > The context is Qpid Dispatch Routers connected together with one router in > Edge mode and the other in Interior mode. The router modes are probably not > important for this issue. The connecting (client) router is running on a > bare-metal Fedora Linux system in a container under Minikube. The listening > router is running in a container in Microsoft Azure Kubernetes Service. > There are unknown layers of networks and load balancers between the routers. > The problem is that configured heartbeats sometimes don't occur. In other > words, a trace on the connection shows no heartbeat (empty) frames flowing. > Furthermore, when this happens, the connection is never closed due to lack of > heartbeats. > This lack of heartbeat protection often results in half-disconnected > connections. When this happens, the client-side sees a connection error > (usually related to TLS), closes the connection and reconnects with a new > connection. The server-side sees no error and winds up with two live > connections from the client, only one of which can actually carry messages > to/from the client. > Qpid Dispatch can work around this problem by establishing an > application-level keepalive using message delivery. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-2440) Configured heartbeats sometimes don't function in inter-cloud environments
[ https://issues.apache.org/jira/browse/PROTON-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-2440. --- Resolution: Information Provided > Configured heartbeats sometimes don't function in inter-cloud environments > -- > > Key: PROTON-2440 > URL: https://issues.apache.org/jira/browse/PROTON-2440 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.35.0 >Reporter: Ted Ross >Priority: Major > > The context is Qpid Dispatch Routers connected together with one router in > Edge mode and the other in Interior mode. The router modes are probably not > important for this issue. The connecting (client) router is running on a > bare-metal Fedora Linux system in a container under Minikube. The listening > router is running in a container in Microsoft Azure Kubernetes Service. > There are unknown layers of networks and load balancers between the routers. > The problem is that configured heartbeats sometimes don't occur. In other > words, a trace on the connection shows no heartbeat (empty) frames flowing. > Furthermore, when this happens, the connection is never closed due to lack of > heartbeats. > This lack of heartbeat protection often results in half-disconnected > connections. When this happens, the client-side sees a connection error > (usually related to TLS), closes the connection and reconnects with a new > connection. The server-side sees no error and winds up with two live > connections from the client, only one of which can actually carry messages > to/from the client. > Qpid Dispatch can work around this problem by establishing an > application-level keepalive using message delivery. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-2440) Configured heartbeats sometimes don't function in inter-cloud environments
[ https://issues.apache.org/jira/browse/PROTON-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed PROTON-2440. --- Resolution: Fixed > Configured heartbeats sometimes don't function in inter-cloud environments > -- > > Key: PROTON-2440 > URL: https://issues.apache.org/jira/browse/PROTON-2440 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.35.0 >Reporter: Ted Ross >Priority: Major > > The context is Qpid Dispatch Routers connected together with one router in > Edge mode and the other in Interior mode. The router modes are probably not > important for this issue. The connecting (client) router is running on a > bare-metal Fedora Linux system in a container under Minikube. The listening > router is running in a container in Microsoft Azure Kubernetes Service. > There are unknown layers of networks and load balancers between the routers. > The problem is that configured heartbeats sometimes don't occur. In other > words, a trace on the connection shows no heartbeat (empty) frames flowing. > Furthermore, when this happens, the connection is never closed due to lack of > heartbeats. > This lack of heartbeat protection often results in half-disconnected > connections. When this happens, the client-side sees a connection error > (usually related to TLS), closes the connection and reconnects with a new > connection. The server-side sees no error and winds up with two live > connections from the client, only one of which can actually carry messages > to/from the client. > Qpid Dispatch can work around this problem by establishing an > application-level keepalive using message delivery. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2440) Configured heartbeats sometimes don't function in inter-cloud environments
[ https://issues.apache.org/jira/browse/PROTON-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472863#comment-17472863 ] Justin Ross commented on PROTON-2440: - We think this arose from the timer bug linked above, so we'll close it and let it come back if necessary. > Configured heartbeats sometimes don't function in inter-cloud environments > -- > > Key: PROTON-2440 > URL: https://issues.apache.org/jira/browse/PROTON-2440 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.35.0 >Reporter: Ted Ross >Priority: Major > > The context is Qpid Dispatch Routers connected together with one router in > Edge mode and the other in Interior mode. The router modes are probably not > important for this issue. The connecting (client) router is running on a > bare-metal Fedora Linux system in a container under Minikube. The listening > router is running in a container in Microsoft Azure Kubernetes Service. > There are unknown layers of networks and load balancers between the routers. > The problem is that configured heartbeats sometimes don't occur. In other > words, a trace on the connection shows no heartbeat (empty) frames flowing. > Furthermore, when this happens, the connection is never closed due to lack of > heartbeats. > This lack of heartbeat protection often results in half-disconnected > connections. When this happens, the client-side sees a connection error > (usually related to TLS), closes the connection and reconnects with a new > connection. The server-side sees no error and winds up with two live > connections from the client, only one of which can actually carry messages > to/from the client. > Qpid Dispatch can work around this problem by establishing an > application-level keepalive using message delivery. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDIT-144) The build metadata hard codes a "build" dir
Justin Ross created QPIDIT-144:
--
Summary: The build metadata hard codes a "build" dir
Key: QPIDIT-144
URL: https://issues.apache.org/jira/browse/QPIDIT-144
Project: Apache QPID Interoperability Test Suite
Issue Type: Bug
Reporter: Justin Ross
[https://github.com/apache/qpid-interop-test/blob/2ae24aa2ac6998b9598b02e5b181f187f7b51212/CMakeLists.txt#L121]
I typically use "bld", so this resulted in an error for me:
{code:java}
CMake Error at cmake_install.cmake:96 (file):
file INSTALL cannot find
"/tmp/tmp.byVENbKXMb/qpid-interop-test-0.3.0/build/bin/qpid-interop-test":
No such file or directory.{code}
--
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] (PROTON-1647) [go] support for crypto.tls connections
[ https://issues.apache.org/jira/browse/PROTON-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1647: Fix Version/s: proton-c-future > [go] support for crypto.tls connections > --- > > Key: PROTON-1647 > URL: https://issues.apache.org/jira/browse/PROTON-1647 > Project: Qpid Proton > Issue Type: Bug > Components: go-binding >Affects Versions: proton-c-0.18.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > Labels: tls > Fix For: proton-c-future > > > The electron and proton Go bindings do not expose proton's built-in SSL layer > because Go provides it's own TLS layer in the crypto.tls package which is > more portable, capable and familiar to Go programmers. > You can already use a tls.Conn with proton or electron, but there are several > points that should be cleaned up: > - when a TLS connection is in use set allow-insecure-mechs in proton-C > automatically > - make sure the AMQP virtual-host matches the TLS virtual-host by default > - provide access to the net.Conn used by an electron.Connection, which in > turn will give access to TLS details if the user needs them > - provide an example of using TLS (maybe with SASL PLAIN auth?) -- 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] (PROTON-2376) container.listen may support amqps
[
https://issues.apache.org/jira/browse/PROTON-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-2376:
Labels: tls (was: )
> container.listen may support amqps
> --
>
> Key: PROTON-2376
> URL: https://issues.apache.org/jira/browse/PROTON-2376
> Project: Qpid Proton
> Issue Type: New Feature
> Components: proton-c
>Affects Versions: proton-c-0.33.0
>Reporter: carawang
>Priority: Major
> Labels: tls
>
> Hi, Whether the container.listen support the amqps?
> see the below:
> {code:java}
> def listen(url, handler=Listener::Handler.new)
> not_stopped
> url = Qpid::Proton::uri url
> # TODO aconway 2017-11-01: amqps, SSL
> listen_io(TCPServer.new(url.host, url.port), handler)
> end
> {code}
> The broker.rb[1] of ruby example setting the ssl but seems it does 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] (PROTON-2122) Hardcoded limit of 16 sasl mechanisms is insufficient on macOS
[
https://issues.apache.org/jira/browse/PROTON-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-2122:
Labels: sasl (was: )
> Hardcoded limit of 16 sasl mechanisms is insufficient on macOS
> --
>
> Key: PROTON-2122
> URL: https://issues.apache.org/jira/browse/PROTON-2122
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.29.0
> Environment: macOS 10.14
>Reporter: Jiri Daněk
>Priority: Major
> Labels: sasl
>
> On macOS, any time a SASL exchange happens in tests, e.g.
> {{cpp-example-container}} or qpid dispatch tests, or when
> {{cpp/examples/simple_send}} connects to {{cpp/examples/broker}}, the broker
> crashes with the following stack trace
> {noformat}
> Thread 1 Crashed:
> 0 libsystem_kernel.dylib 0x7fff697c62c6 __pthread_kill + 10
> 1 libsystem_pthread.dylib 0x7fff69881bf1 pthread_kill + 284
> 2 libsystem_c.dylib 0x7fff69730745 __abort + 144
> 3 libsystem_c.dylib 0x7fff69730ff3 __stack_chk_fail +
> 205
> 4 libqpid-proton-core.10.dylib0x000106d81f89
> pni_post_sasl_frame + 1321
> 5 ??? 0x7fd57acb59bb 0 + 140554864908731
> {noformat}
> AddressSanitizer (Valgrind does not run on most recent macOS releases) points
> out the reason.
> {noformat}
> $ ../cmake-build-debug/cpp/examples/broker
> broker listening on 5672
> =
> ==42793==ERROR: AddressSanitizer: stack-buffer-overflow on address
> 0x7c4bcbe0 at pc 0x0001013663e1 bp 0x7c4bc830 sp 0x7c4bc828
> WRITE of size 8 at 0x7c4bcbe0 thread T3
> #0 0x1013663e0 in pni_split_mechs sasl.c:443
> #1 0x1013646ea in pni_post_sasl_frame sasl.c:480
> #2 0x101357fad in pn_output_write_sasl sasl.c:677
> #3 0x101323909 in transport_produce transport.c:2751
> #4 0x10131ffd3 in pn_transport_pending transport.c:3030
> #5 0x1012b8755 in pn_connection_driver_write_buffer
> connection_driver.c:120
> #6 0x10120240f in leader_process_pconnection libuv.c:909
> #7 0x1011f8b48 in leader_lead_lh libuv.c:1008
> #8 0x1011f94f3 in pn_proactor_wait libuv.c:1062
> #9 0x10188c55d in proton::container::impl::thread()
> proactor_container_impl.cpp:753
> #10 0x1018bca31 in void*
> std::__1::__thread_proxy std::__1::default_delete >, void
> (proton::container::impl::*)(), proton::container::impl*> >(void*) thread:352
> #11 0x7fff6987f2ea in _pthread_body
> (libsystem_pthread.dylib:x86_64+0x32ea)
> #12 0x7fff69882248 in _pthread_start
> (libsystem_pthread.dylib:x86_64+0x6248)
> #13 0x7fff6987e40c in thread_start (libsystem_pthread.dylib:x86_64+0x240c)
> Address 0x7c4bcbe0 is located in stack of thread T3 at offset 192 in frame
> #0 0x101363ccf in pni_post_sasl_frame sasl.c:462
> This frame has 3 object(s):
> [32, 48) 'out' (line 464)
> [64, 192) 'mechs' (line 475) <== Memory access at offset 192 overflows
> this variable
> [224, 228) 'count' (line 478)
> HINT: this may be a false positive if your program uses some custom stack
> unwind mechanism, swapcontext or vfork
> (longjmp and C++ exceptions *are* supported)
> Thread T3 created by T0 here:
> #0 0x101f5dadd in wrap_pthread_create
> (libclang_rt.asan_osx_dynamic.dylib:x86_64+0x56add)
> #1 0x1018bc4ab in std::__1::thread::thread (proton::container::impl::*)(), proton::container::impl*, void>(void
> (proton::container::impl::*&&)(), proton::container::impl*&&) thread:368
> #2 0x10188da97 in proton::container::impl::run(int)
> proactor_container_impl.cpp:802
> #3 0x100f0223c in main broker.cpp:427
> #4 0x7fff6968b3d4 in start (libdyld.dylib:x86_64+0x163d4)
> SUMMARY: AddressSanitizer: stack-buffer-overflow sasl.c:443 in pni_split_mechs
> Shadow bytes around the buggy address:
> 0x1e0001897920: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0x1e0001897930: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0x1e0001897940: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0x1e0001897950: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0x1e0001897960: 00 00 00 00 f1 f1 f1 f1 00 00 f2 f2 00 00 00 00
> =>0x1e0001897970: 00 00 00 00 00 00 00 00 00 00 00 00[f2]f2 f2 f2
> 0x1e0001897980: 04 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00
> 0x1e0001897990: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0x1e00018979a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0x1e00018979b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0x1e00018979c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> Shadow byte legend (one shadow byte represents 8 application bytes):
> Addressable:
[jira] [Updated] (PROTON-2434) Container.connect doesn't set virtual_host by default, making peer verification harder than it should be
[
https://issues.apache.org/jira/browse/PROTON-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-2434:
Labels: tls (was: )
> Container.connect doesn't set virtual_host by default, making peer
> verification harder than it should be
>
>
> Key: PROTON-2434
> URL: https://issues.apache.org/jira/browse/PROTON-2434
> Project: Qpid Proton
> Issue Type: Bug
>Affects Versions: proton-c-0.35.0
>Reporter: Evgeni Golov
>Priority: Major
> Labels: tls
>
> In 0.35 proton-c started to default to PN_SSL_VERIFY_PEER_NAME in client
> mode, which is good. However, it seems that it does not (by default) extract
> the peer name from the URL, so a connection can not be established, even if
> the certs and everything matches, as there is no name to verify against.
> Looking at the Ruby examples
> ([https://qpid.apache.org/releases/qpid-proton-0.35.0/proton/ruby/examples/ssl_send.rb.html),]
> you suggest to roll back the default VERIFY_PEER_NAME to ANONYMOUS_PEER:
> {code:ruby}
> ssl_domain =
> Qpid::Proton::SSLDomain.new(Qpid::Proton::SSLDomain::MODE_CLIENT)
> ssl_domain.peer_authentication(Qpid::Proton::SSLDomain::ANONYMOUS_PEER)
> c = container.connect(@url, { :ssl_domain => ssl_domain })
> {code}
> And indeed, dropping the ANONYMOUS_PEER fails the connection attempt.
> Instead, we can explicitly set the virtual_host of the connection, thus
> allowing the PEER_NAME verification to succeed:
> {code:ruby}
> ssl_domain =
> Qpid::Proton::SSLDomain.new(Qpid::Proton::SSLDomain::MODE_CLIENT)
> c = container.connect(@url, { :ssl_domain => ssl_domain, :virtual_host =>
> URI.parse(@url).host })
> {code}
> However, I think this is cumbersome and makes users lifes harder than they
> should be.
> If container.connect would automatically set the virtual_host to the host
> part of the URL (unless it was defined by the user), SSL verification would
> just work.
> FWIW, I only tested this all with the Ruby bindings on Ruby 2.7, OpenSSL
> 1.0.2k-21.el7_9.x86_64 (CentOS 7), so this might behave differently on other
> environments.
--
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] (PROTON-1057) Windows SChannel SSL test failure
[ https://issues.apache.org/jira/browse/PROTON-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1057: Labels: tls windows (was: windows) > Windows SChannel SSL test failure > - > > Key: PROTON-1057 > URL: https://issues.apache.org/jira/browse/PROTON-1057 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-0.12.0 > Environment: Windows only. >Reporter: Clifford Jansen >Assignee: Clifford Jansen >Priority: Major > Labels: tls, windows > Fix For: proton-c-future > > > This problem started since PROTON-1048 which did not touch the Proton-C > SChannel related code - it just tweaked the test infrastructure to use > alternate certificate formats for Windows. > The proton_tests.ssl.SslTest.test_server_hostname_authentication test > randomly crashes on Windows, presumably from some memory corruption > somewhere. It often runs fine. Seems to happen more frequently on some > systems than others. Not yet seen on a 64 bit build. -- 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] (PROTON-1802) Support compiling with -DSSL_IMPL=openssl on Windows
[ https://issues.apache.org/jira/browse/PROTON-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1802: Labels: tls (was: ) > Support compiling with -DSSL_IMPL=openssl on Windows > > > Key: PROTON-1802 > URL: https://issues.apache.org/jira/browse/PROTON-1802 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Affects Versions: proton-c-0.21.0 > Environment: OpenSSL 1.1.0-stable > qpid-proton-0.21.0 > Visual Studio 2015 > -DSSL_IMPL=openssl >Reporter: Meng Zhou >Priority: Major > Labels: tls > > I am using > OpenSSL 1.1.0-stable > qpid-proton-0.21.0 > Visual Studio 2015 > When I set SSL_IMPL=openssl the compiler report > openssl.c > \qpid-proton-0.21.0\proton-c\src\ssl\openssl.c(1540): error C2065: > 'initialize': undeclared identifier > \qpid-proton-0.21.0\proton-c\src\ssl\openssl.c(1540): error C3861: > 'InitOnceExecuteOnce': identifier not found -- 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] (PROTON-2009) OpenSSL API has changed and now deprecates SSL_OP_NO_TLSv* used with SSL_CTX_set_options
[ https://issues.apache.org/jira/browse/PROTON-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2009: Labels: tls (was: ) > OpenSSL API has changed and now deprecates SSL_OP_NO_TLSv* used with > SSL_CTX_set_options > > > Key: PROTON-2009 > URL: https://issues.apache.org/jira/browse/PROTON-2009 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.26.0 > Environment: Fedora 29, OpenSSL 1.1.1 FIPS 11 Sep 2018 >Reporter: Charles E. Rolke >Assignee: Andrew Stitcher >Priority: Major > Labels: tls > > The OpenSSL SSL_OP_NO_TLSvxxx options are deprecated for use in > SSL_CTX_set_options(). > As of OpenSSL 1.1 way to specify TLS versions is through a min-version and > max-version scheme - this is more code future proof. > You can specify a minimum version and 0 for the maximum meaning the latest > version. > Proton's interface to this allows more than can be specified using the > min/max API as you can specify each protocol individually. > The proton code is also not future proof in that it "knows" about each TLS > protocol individually in the code. -- 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] (PROTON-1864) [c] No way of indicating that a transport is ssl or encrypted or already authenticated
[ https://issues.apache.org/jira/browse/PROTON-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1864: Labels: tls (was: ) > [c] No way of indicating that a transport is ssl or encrypted or already > authenticated > -- > > Key: PROTON-1864 > URL: https://issues.apache.org/jira/browse/PROTON-1864 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Gordon Sim >Priority: Major > Labels: tls > > This is needed e.g. for DISPATCH-1040 -- 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] (PROTON-855) Add axTLS (embedded SSL) support to proton-c
[ https://issues.apache.org/jira/browse/PROTON-855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-855: --- Labels: features patch tls (was: features patch) > Add axTLS (embedded SSL) support to proton-c > > > Key: PROTON-855 > URL: https://issues.apache.org/jira/browse/PROTON-855 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c >Affects Versions: proton-0.9, proton-0.9.1, proton-0.10 > Environment: Platform independent >Reporter: Tomasz Nowicki >Priority: Major > Labels: features, patch, tls > Fix For: proton-c-future > > Attachments: axtls.c, axtls_proton_example.c, qpidproton-AXTLS.patch, > ssl_io.h > > Original Estimate: 0h > Remaining Estimate: 0h > > The axTLS embedded SSL project is a highly configurable client/server > TLSv1 SSL library designed for platforms with small memory requirements. > It comes with a small HTTP/HTTPS server and additional test tools. > axTLS It's free! (BSD style licensing) > http://axtls.sourceforge.net/ > axTLS integration with proton is done on socket layer(posix layer). On the > other hand OpenSSL integration with proton is done on the transport layer. To > use both solutions we had to add two methods pn_ssl_recv i pn_ssl_send > (daclared in include/ssl_io.h) which in openssl mode, without crypting, > invoke native proton "pn_send" and "pn_receive (io.c)". In axTLS mode, those > methods are replaced with proper axtls comunication methods. Those are > defined in openssl.c, ssl_stub.c, axtls.c and located in src/ssl. > Methods pn_ssl_recv and pn_ssl_send replace original pn_send and pn_recv used > in pni_connection_writable(pn_selectable_t *sel), > pni_connection_readable(pn_selectable_t *sel) (connection.c). > Moreover we introduced new file axtls.c located in src/ssl. The file is an > equivalent of openssl.c, implementing base ssl methods: PN_EXTERN > pn_ssl_domain_t *pn_ssl_domain( pn_ssl_mode_t mode); > PN_EXTERN void pn_ssl_domain_free( pn_ssl_domain_t *domain ); etc > Example of axTLS integration with ex ActiveMQ > atatched(axtls_proton_example.c): > It's based on > http://mail-archives.us.apache.org/mod_mbox/qpid-proton/201501.mbox/%3ccacl1bnc5jerbnikd_4fgkjqh13h5nl_2z-sszp3jg2t+ywa...@mail.gmail.com%3E -- 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] (PROTON-1870) better logging for ssl
[ https://issues.apache.org/jira/browse/PROTON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1870: Labels: logging tls usability (was: logging usability) > better logging for ssl > -- > > Key: PROTON-1870 > URL: https://issues.apache.org/jira/browse/PROTON-1870 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: proton-0.9.1, proton-c-0.31.0 >Reporter: Gordon Sim >Priority: Major > Labels: logging, tls, usability > > Would be nice to have better logging for ssl connections, particularly where > they fail, e.g. the sni used, the ca the peer cert is signed with etc -- 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] (PROTON-2303) SSL Unknown Error
[
https://issues.apache.org/jira/browse/PROTON-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-2303:
Labels: tls (was: )
> SSL Unknown Error
> -
>
> Key: PROTON-2303
> URL: https://issues.apache.org/jira/browse/PROTON-2303
> Project: Qpid Proton
> Issue Type: Bug
>Reporter: Angelo Mendonca
>Priority: Major
> Labels: tls
>
> ERROR - ActiveMQ connection exception, Retrying, Connection
> amqps://x...@id-1.mq.us-east-1.amazonaws.com:5671 disconnected:
> Condition('amqp:connection:framing-error', 'SSL Failure: Unknown error')
--
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] (PROTON-2308) [cpp] Add support for setting Dynamic Node Properties
[ https://issues.apache.org/jira/browse/PROTON-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2308: Labels: api-addition (was: ) > [cpp] Add support for setting Dynamic Node Properties > - > > Key: PROTON-2308 > URL: https://issues.apache.org/jira/browse/PROTON-2308 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.33.0 >Reporter: James Henry >Assignee: Rakhi Kumari >Priority: Major > Labels: api-addition > > Requesting support for setting the dynamic node properties be added to the > source and target options. > This would allow the setting of termini node properties for senders and > receivers. > Similar to the following request made for Python here: > https://issues.apache.org/jira/browse/PROTON-816 -- 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] (PROTON-2104) [cpp] Error specifying url with IPv6 literal host address
[
https://issues.apache.org/jira/browse/PROTON-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-2104:
Summary: [cpp] Error specifying url with IPv6 literal host address (was:
[c++ client] Error specifying url with IPv6 literal host address)
> [cpp] Error specifying url with IPv6 literal host address
> -
>
> Key: PROTON-2104
> URL: https://issues.apache.org/jira/browse/PROTON-2104
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
>Affects Versions: proton-c-0.29.0, proton-c-0.33.0
>Reporter: Charles E. Rolke
>Priority: Major
>
> C++ examples simple_send and simple_recv accept IPv6 loopback address [::1]
> but have issues with other apparently legal addresses.
> These work on my system:
> {noformat}
> ping6 fe80::c662:ab36:1ef1:1596
> ping6 fe80::c662:ab36:1ef1:1596%wlp4s0
> ping6 fe80::::c662:ab36:1ef1:1596
> {noformat}
> Wrapping the host part in square brackets and sending that address to
> simple_send fails:
> {noformat}
> ./simple_send -a [fe80::c662:ab36:1ef1:1596]:5672/abc
> proton:io: Invalid argument - on connect fe80::c662:ab36:1ef1:1596:5672
> {noformat}
> All three variants of the address that work with ping6 fail with the same
> error on the simple_send command line.
>
--
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] (PROTON-2308) Proton CPP: Add support for setting Dynamic Node Properties
[ https://issues.apache.org/jira/browse/PROTON-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-2308: --- Assignee: Rakhi Kumari > Proton CPP: Add support for setting Dynamic Node Properties > --- > > Key: PROTON-2308 > URL: https://issues.apache.org/jira/browse/PROTON-2308 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.33.0 >Reporter: James Henry >Assignee: Rakhi Kumari >Priority: Major > > Requesting support for setting the dynamic node properties be added to the > source and target options. > This would allow the setting of termini node properties for senders and > receivers. > Similar to the following request made for Python here: > https://issues.apache.org/jira/browse/PROTON-816 -- 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] (PROTON-2308) [cpp] Add support for setting Dynamic Node Properties
[ https://issues.apache.org/jira/browse/PROTON-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2308: Summary: [cpp] Add support for setting Dynamic Node Properties (was: Proton CPP: Add support for setting Dynamic Node Properties) > [cpp] Add support for setting Dynamic Node Properties > - > > Key: PROTON-2308 > URL: https://issues.apache.org/jira/browse/PROTON-2308 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.33.0 >Reporter: James Henry >Assignee: Rakhi Kumari >Priority: Major > > Requesting support for setting the dynamic node properties be added to the > source and target options. > This would allow the setting of termini node properties for senders and > receivers. > Similar to the following request made for Python here: > https://issues.apache.org/jira/browse/PROTON-816 -- 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] (PROTON-2330) [cpp] Allow access to session properties in cpp binding
[ https://issues.apache.org/jira/browse/PROTON-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2330: Summary: [cpp] Allow access to session properties in cpp binding (was: Allow access to session properties in cpp binding ) > [cpp] Allow access to session properties in cpp binding > > > Key: PROTON-2330 > URL: https://issues.apache.org/jira/browse/PROTON-2330 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Affects Versions: proton-c-0.33.0 >Reporter: Pete Fawcett >Priority: Minor > > As per the work done in PROTON-2307 for connection properties, and > PROTON-2332 for links, extend the same approach to allow the setting of > custom properties on sessions and allow retrieval of such properties as set > by remote end on sessions. -- 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] (PROTON-2396) [cpp] Seed in uuid.cpp can lead to duplicates
[ https://issues.apache.org/jira/browse/PROTON-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-2396: --- Assignee: Rakhi Kumari > [cpp] Seed in uuid.cpp can lead to duplicates > - > > Key: PROTON-2396 > URL: https://issues.apache.org/jira/browse/PROTON-2396 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding > Environment: RHEL7 running in OpenStack > docker-ce 19.03.5 > qpid-proton 0.28.0 > qpid-cpp 1.37.0 >Reporter: Ryan Herbert >Assignee: Rakhi Kumari >Priority: Major > > The random number seed used in qpid-proton/cpp/src/uuid.cpp is based on the > current time and the PID of the running process. When starting multiple > proton instances simultaneously in Docker containers via automated > deployment, there is a high probability that multiple instances will get the > same seed since the PID within the Docker container is consistent and the > same across multiple copies of the same Docker container. > This results in duplicate link names when binding to exchanges. When this > happens, the queue gets bound to two different exchanges, and requests sent > to one exchange will get responses from both services. > To work around this error, we are specifying the link name via > sender_options/receiver_options every time we open a new sender/receiver, and > we also specify the container_id in connection_options. We are using > std::mt19937_64 seeded with > std::chrono::system_clock::now().time_since_epoch().count() to generate the > random part of our link names, which seems to have enough randomness that it > has eliminated the problem for us. > As pointed out in the Proton user forum, std::random_device is probably a > better choice for initializing the seed. > -- 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] (PROTON-2396) [cpp] Seed in uuid.cpp can lead to duplicates
[ https://issues.apache.org/jira/browse/PROTON-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2396: Summary: [cpp] Seed in uuid.cpp can lead to duplicates (was: Seed in uuid.cpp can lead to duplicates) > [cpp] Seed in uuid.cpp can lead to duplicates > - > > Key: PROTON-2396 > URL: https://issues.apache.org/jira/browse/PROTON-2396 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding > Environment: RHEL7 running in OpenStack > docker-ce 19.03.5 > qpid-proton 0.28.0 > qpid-cpp 1.37.0 >Reporter: Ryan Herbert >Priority: Major > > The random number seed used in qpid-proton/cpp/src/uuid.cpp is based on the > current time and the PID of the running process. When starting multiple > proton instances simultaneously in Docker containers via automated > deployment, there is a high probability that multiple instances will get the > same seed since the PID within the Docker container is consistent and the > same across multiple copies of the same Docker container. > This results in duplicate link names when binding to exchanges. When this > happens, the queue gets bound to two different exchanges, and requests sent > to one exchange will get responses from both services. > To work around this error, we are specifying the link name via > sender_options/receiver_options every time we open a new sender/receiver, and > we also specify the container_id in connection_options. We are using > std::mt19937_64 seeded with > std::chrono::system_clock::now().time_since_epoch().count() to generate the > random part of our link names, which seems to have enough randomness that it > has eliminated the problem for us. > As pointed out in the Proton user forum, std::random_device is probably a > better choice for initializing the seed. > -- 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] (PROTON-2406) [cpp] Use of reconnect_options::failover_urls triggers -Wdeprecated-declarations in examples/cpp/reconnect_client.cpp
[
https://issues.apache.org/jira/browse/PROTON-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross reassigned PROTON-2406:
---
Assignee: Rakhi Kumari
> [cpp] Use of reconnect_options::failover_urls triggers
> -Wdeprecated-declarations in examples/cpp/reconnect_client.cpp
> -
>
> Key: PROTON-2406
> URL: https://issues.apache.org/jira/browse/PROTON-2406
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, examples
>Affects Versions: proton-c-0.35.0
>Reporter: Jiri Daněk
>Assignee: Rakhi Kumari
>Priority: Minor
>
> {noformat}
> [ 56%] Building CXX object
> CMakeFiles/reconnect_client.dir/reconnect_client.cpp.o
> /usr/share/proton/examples/cpp/reconnect_client.cpp: In member function
> ‘virtual void reconnect_client::on_container_start(proton::container&)’:
> /usr/share/proton/examples/cpp/reconnect_client.cpp:59:35: warning:
> ‘proton::reconnect_options& proton::reconnect_options::failover_urls(const
> std::vector >&)’ is deprecated (declared at
> /usr/include/proton/reconnect_options.hpp:82): use
> connection_options::failover_urls() [-Wdeprecated-declarations]
> ro.failover_urls(failovers);
> {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] (PROTON-2406) [cpp] Use of reconnect_options::failover_urls triggers -Wdeprecated-declarations in examples/cpp/reconnect_client.cpp
[
https://issues.apache.org/jira/browse/PROTON-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-2406:
Summary: [cpp] Use of reconnect_options::failover_urls triggers
-Wdeprecated-declarations in examples/cpp/reconnect_client.cpp (was: Use of
reconnect_options::failover_urls triggers -Wdeprecated-declarations in
examples/cpp/reconnect_client.cpp)
> [cpp] Use of reconnect_options::failover_urls triggers
> -Wdeprecated-declarations in examples/cpp/reconnect_client.cpp
> -
>
> Key: PROTON-2406
> URL: https://issues.apache.org/jira/browse/PROTON-2406
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, examples
>Affects Versions: proton-c-0.35.0
>Reporter: Jiri Daněk
>Priority: Minor
>
> {noformat}
> [ 56%] Building CXX object
> CMakeFiles/reconnect_client.dir/reconnect_client.cpp.o
> /usr/share/proton/examples/cpp/reconnect_client.cpp: In member function
> ‘virtual void reconnect_client::on_container_start(proton::container&)’:
> /usr/share/proton/examples/cpp/reconnect_client.cpp:59:35: warning:
> ‘proton::reconnect_options& proton::reconnect_options::failover_urls(const
> std::vector >&)’ is deprecated (declared at
> /usr/include/proton/reconnect_options.hpp:82): use
> connection_options::failover_urls() [-Wdeprecated-declarations]
> ro.failover_urls(failovers);
> {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-1870) better logging for ssl
[ https://issues.apache.org/jira/browse/PROTON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430039#comment-17430039 ] Justin Ross commented on PROTON-1870: - Like Gordon, I've run into the "unsupported certificate purpose" problem. I've also seen "verification failed: self-signed cert" (so, you need to explicitly trust that cert)". I get the more detailed failure reasons from the "openssl s_client", "openssl s_server", and "openssl verify" commands. > better logging for ssl > -- > > Key: PROTON-1870 > URL: https://issues.apache.org/jira/browse/PROTON-1870 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Affects Versions: proton-0.9.1, proton-c-0.31.0 >Reporter: Gordon Sim >Priority: Major > Labels: logging, usability > > Would be nice to have better logging for ssl connections, particularly where > they fail, e.g. the sni used, the ca the peer cert is signed with etc -- 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] (PROTON-2438) [cpp] Cancellable tasks
[ https://issues.apache.org/jira/browse/PROTON-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2438: Fix Version/s: (was: proton-0.10) > [cpp] Cancellable tasks > --- > > Key: PROTON-2438 > URL: https://issues.apache.org/jira/browse/PROTON-2438 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c, proton-j, python-binding >Reporter: Božo Dragojevič >Assignee: Božo Dragojevič >Priority: Major > > Allow scheduled tasks to be cancelled. > A cancelled task does not keep reactor from stoping running -- 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] (PROTON-2438) [cpp] Cancellable tasks
[ https://issues.apache.org/jira/browse/PROTON-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-2438: --- Assignee: Justin Ross (was: Božo Dragojevič) > [cpp] Cancellable tasks > --- > > Key: PROTON-2438 > URL: https://issues.apache.org/jira/browse/PROTON-2438 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Božo Dragojevič >Assignee: Justin Ross >Priority: Major > > Allow scheduled tasks to be cancelled. > A cancelled task does not keep reactor from stoping running -- 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] (PROTON-2438) [cpp] Cancellable tasks
[ https://issues.apache.org/jira/browse/PROTON-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2438: Component/s: (was: python-binding) (was: proton-j) (was: proton-c) cpp-binding > [cpp] Cancellable tasks > --- > > Key: PROTON-2438 > URL: https://issues.apache.org/jira/browse/PROTON-2438 > Project: Qpid Proton > Issue Type: Improvement > Components: cpp-binding >Reporter: Božo Dragojevič >Assignee: Božo Dragojevič >Priority: Major > > Allow scheduled tasks to be cancelled. > A cancelled task does not keep reactor from stoping running -- 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-2438) [cpp] Cancellable tasks
Justin Ross created PROTON-2438: --- Summary: [cpp] Cancellable tasks Key: PROTON-2438 URL: https://issues.apache.org/jira/browse/PROTON-2438 Project: Qpid Proton Issue Type: Improvement Components: proton-c, proton-j, python-binding Reporter: Božo Dragojevič Assignee: Božo Dragojevič Fix For: proton-0.10 Allow scheduled tasks to be cancelled. A cancelled task does not keep reactor from stoping running -- 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] (PROTON-2411) Simultaneous idle timeout sequencing errors
[ https://issues.apache.org/jira/browse/PROTON-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-2411: --- Assignee: Andrew Stitcher > Simultaneous idle timeout sequencing errors > --- > > Key: PROTON-2411 > URL: https://issues.apache.org/jira/browse/PROTON-2411 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.34.0 >Reporter: Jaap Wiggelinkhuizen >Assignee: Andrew Stitcher >Priority: Critical > Fix For: proton-c-0.36.0 > > Attachments: p2411_0.diff > > > In our mission critical software we use Qpid proton 0.34.0 in our C++-client > software together with the Qpid dispatch router 1.16.0. We updated to these > versions not so long ago, before we used proton 0.25.0 and dispatch 1.3.0. > Our application runs on several VM’s with a router on each VM. All clients > connect to the local router only and the routers connect to eachother in a > hub spoke pattern. In both the client configuration as the router > configuration we have configured an idle timeout of 30 seconds. > On July 4th we were confronted with an incident in production where a lot of > our client processes reported problems regarding the idle timeouts. These > client processes were already running stable for more than 3 weeks. The > problem appeared in two flavors: > # Transport error “error: amqp:resource-limit-exceeded: local-idle-timeout > expired” > # epoll proactor failure in epoll_timer.c:263: “idle timeout sequencing > error” > On each VM at least 3 processes showed one of these problems in a total time > window of less than a minute. We haven’t found any cause in the underlying > hardware, hypervisor, network or operating system until now. > Although we don’t know the root cause of the problems, we can solve the first > situation by using the proper reconnect settings (by mistake we handled > on_transport_error() as a fatal situation and will correct that so that only > on_transport_close() will be handled as fatal). However the second situation > is more odd because it results in an abort within proton itself. The comments > in epoll_timer.c explain that this error occurs when a connection timer is > moved backwards a second time. We don’t understand how this can happen > suddenly. > > Last sunday the problem occurred again on two more production sites where our > software was operational just over 3 weeks now. And again it has happened on > all VM's within a short timeframe. It's interesting that it only occurs on > sunday mornings until now. Maybe it has something to do with how long the > software is running and the fact that on sunday mornings there is less > messaging traffic, i.e. more heartbeats?... > > Unfortunately we haven't been able to reproduce the issue at our test > facilities and hence can not provide a reproducer. -- 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] (PROTON-2422) Proton will sometimes fail to send empty frame if the idle timeout ratio between peers is greater than 2.
[
https://issues.apache.org/jira/browse/PROTON-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross reassigned PROTON-2422:
---
Assignee: Clifford Jansen
> Proton will sometimes fail to send empty frame if the idle timeout ratio
> between peers is greater than 2.
> --
>
> Key: PROTON-2422
> URL: https://issues.apache.org/jira/browse/PROTON-2422
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, proton-c
>Affects Versions: proton-c-0.33.0
> Environment: RHEL 8
>Reporter: Jesse Hulsizer
>Assignee: Clifford Jansen
>Priority: Minor
> Attachments: instrument.patch, reproducer.cpp
>
>
> When a connection is made to a proton listener with both sides having
> different idle timeout intervals, the epoll_timer can fail to trigger,
> resulting in no empty frames being sent, and the connection dropped with a
> 'amqp:resource-limit-exceeded: local-idle-timeout expired' exception.
> Instrumentation of the proton library showed that when the an epoll timer
> deadline was rolled back and the timer resequenced due to the peer idle
> timeout being shorter than the local, the new timer is pushed on the timer
> manager heap incorrectly. The timer deadline object should be pushed on the
> timer heap in order by deadline, by in fact the timer is pushed on the head
> by timer deadline object address. This causes the invalidated timer to be
> first on the list, and the proactor timer set incorrectly. When enough time
> has elapsed, the remote peer will close the connection due to inactivity.
> Note that if the newly created resequenced timer deadline object has an
> address lower than the old invalidated timer deadline object, proton will
> work correctly.
> I've attached a reproducer as well as a patch for the instrumentation.
> Annotated proton logging from the reproducer is below.
> This issue does not occur prior to 0.33.0
> {code:java}
> [builder@SE-RHEL8-ITCM-TEST-01 qpid-proton-idle-timeout-repo $ ]
> PN_LOG='frame info+' ./a.out
> listening on 9030
> # The initial connection
> [0x7fdb3c001be0]: SASL:FRAME: -> SASL
> [0x7fdb44002620]: SASL:FRAME: <- SASL
> [0x7fdb44002620]: SASL:FRAME: -> SASL
> [0x7fdb44002620]: AMQP:FRAME:0 -> @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fdb3c001be0]: SASL:FRAME: <- SASL
> [0x7fdb3c001be0]: AMQP:FRAME:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x7fdb4ca21e20]:EVENT: INFO:In pni_timer_set - timer* 0x7fdb3c008570,
> deadline 5189836829, proactor_timer* 0x10B9660
> [0x7fdb4ca21e20]:EVENT: INFO:Start of timer heap dump
> [0x7fdb4ca21e20]:EVENT: INFO:Stop of timer heap dump
> [0x7fdb4ca21e20]:EVENT: INFO:Start of timer heap dump post
> [0x7fdb4ca21e20]:EVENT: INFO:Heap position 0: td=0x0167fdb3c0085b0,
> td->list_deadline=5189836829, td->timer=0x7fdb3c008570,
> td->resequenced=false
> [0x7fdb4ca21e20]:EVENT: INFO:Stop of timer heap dump
> [0x7fdb3c001be0]: AMQP:FRAME:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"anonymous@SE-RHEL8-ITCM-TEST-01"]
> [0x7fdb44002620]: AMQP:FRAME:0 <- @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"anonymous@SE-RHEL8-ITCM-TEST-01"]
> [0x7fdb44002620]: SASL: INFO:Authenticated user: anonymous for anonymous with
> mechanism ANONYMOUS
> [0x7fdb44002620]: AMQP:FRAME:0 -> @sasl-outcome(68) [code=0]
> [0x7fdb3c001be0]: AMQP:FRAME:0 <- @sasl-outcome(68) [code=0]
> [0x7fdb4ca21e20]:EVENT: INFO:In pni_timer_set - timer* 0x7fdb3c008570,
> deadline 5189836829, proactor_timer* 0x10B9660
> [0x7fdb4ca21e20]:EVENT: INFO:Start of timer heap dump
> [0x7fdb4ca21e20]:EVENT: INFO:Heap position 0: td=0x0167fdb3c0085b0,
> td->list_deadline=5189836829, td->timer=0x7fdb3c008570,
> td->resequenced=false
> [0x7fdb4ca21e20]:EVENT: INFO:Stop of timer heap dump
> [0x7fdb3c001be0]: AMQP:FRAME: -> AMQP
> [0x7fdb3c001be0]: AMQP:FRAME:0 -> @open(16)
> [container-id="cf87e911-f46b-471a-a664-e34de8a57b6b", hostname="127.0.0.1",
> channel-max=32767, idle-time-out=2]
> [0x7fdb44002620]: AMQP:FRAME: <- AMQP
> [0x7fdb44002620]: AMQP:FRAME:0 <- @open(16)
> [container-id="cf87e911-f46b-471a-a664-e34de8a57b6b", hostname="127.0.0.1",
> channel-max=32767, idle-time-out=2]
> [0x7fdb4ca21e20]:EVENT: INFO:In pni_timer_set - timer* 0x7fdb44008fb0,
> deadline 5189806830, proactor_timer* 0x10B7D30
> [0x7fdb4ca21e20]:EVENT: INFO:Start of timer heap dump
> [0x7fdb4ca21e20]:EVENT: INFO:Stop of timer heap dump
> [0x7fdb4ca21e20]:EVENT: INFO:Start of timer heap dump post
> [0x7fdb4ca21e20]:EVENT: INFO:Heap position 0: td=0x0167fdb44008ff0,
> td->list_deadline=5189806830, td->timer=0x7fdb44008fb0,
> td->resequenced=false
> [0x7fdb4ca21e20]:EVENT: INFO:Sto
[jira] [Assigned] (PROTON-1890) [c++] implement idle_timeout and heartbeats
[ https://issues.apache.org/jira/browse/PROTON-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-1890: --- Assignee: Clifford Jansen (was: Alan Conway) > [c++] implement idle_timeout and heartbeats > --- > > Key: PROTON-1890 > URL: https://issues.apache.org/jira/browse/PROTON-1890 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-0.16.0 >Reporter: Praveen Bodke >Assignee: Clifford Jansen >Priority: Major > Attachments: PROTON-1890.zip, examples.diff > > > This is similar issue reported in PROTON-1782 for ruby. > We are facing this issue in cpp binding and i am able to reproduce the issue > with scheduled_send_03.cpp example. The test scenario is to drop all the > packets from both the interfaces after the successful connection. The only > change i made to this example is to send messages continuously inside the > send() method. The other end is detecting the error as it is sending the > empty frames and no response is heard. > The proton is not sending the heartbeat messages (empty frames) as the sender > is busy in sending the data frames. Is it not necessary to send empty frames > even if the data frames are sent? > -- 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-2359) Segfault in pn_class_free, called from pn_connection_finalize
[
https://issues.apache.org/jira/browse/PROTON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382111#comment-17382111
]
Justin Ross commented on PROTON-2359:
-
How often are connections torn down in your app? And what kinds of things is
the app doing (multiple sessions, for instance?) inside the connection? If you
have any details like that, it will help us to write a reproducer.
> Segfault in pn_class_free, called from pn_connection_finalize
> -
>
> Key: PROTON-2359
> URL: https://issues.apache.org/jira/browse/PROTON-2359
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.32.0, proton-c-0.33.0
>Reporter: Nicolas Riebesel
>Priority: Major
>
> Hello everyone,
> we are using the qpid-proton-c cpp-bindings together with the
> Qpid-C++ qpidd broker with AMQP 1.0. Since the upgrade to
> proton-c 0.32 we are experiencing segmentation faults inside
> {{pn_class_free}} called from {{pn_connection_finalize}}. It seems that
> the reify'ed {{clazz}} is corrupt.
> At first we thought that this is related to
> [PROTON-2293|https://issues.apache.org/jira/projects/PROTON/issues/PROTON-2293]
> which was
> supposed to be fixed in 0.33 but apparently we are still experiencing
> the crash.
> This is the stacktrace:
> {code:java}
> #0 0x in ?? ()
> #1 0xb634ed00 in pn_class_free (clazz=0x1e0490, object=0x1e0910) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/object/object.c:120
> #2 0xb634ed54 in pn_free (object=) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/object/object.c:266
> #3 0xb634edb8 in pni_free_children (children=0x1e0910, freed=0x1e0978) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/engine.c:476
> #4 0xb634f0fc in pn_connection_finalize (object=,
> object=) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/engine.c:495
> #5 0xb634e900 in pn_class_decref (clazz=0xb636ee14 , object=0x1e0870)
> at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/object/object.c:98
> #6 0xb634f814 in pn_event_finalize (event=0x1efd60) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/event.c:226
> #7 pn_event_finalize_cast (object=0x1efd60) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/event.c:271
> #8 0xb634e900 in pn_class_decref (clazz=0xb636ebd8 ,
> object=0x1efd60) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/object/object.c:98
> #9 0xb634ebd4 in pn_decref (object=) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/object/object.c:256
> #10 0xb634ec08 in pn_collector_next (collector=0x1efd20) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/event.c:197
> #11 0xb6351fd0 in batch_next (d=0x1efc5c) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/connection_driver.c:44
> #12 pn_connection_driver_next_event (d=0x1efc5c) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/connection_driver.c:137
> #13 0xb6377614 in pconnection_batch_next (batch=0x1efc58) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/proactor/epoll.c:879
> #14 0xb64da328 in proton::container::impl::thread()
> (this=this@entry=0x1ceb68) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/cpp/src/proactor_container_impl.cpp:757
> #15 0xb64da930 in proton::container::impl::run(int) (this=0x1ceb68,
> threads=threads@entry=1) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/cpp/src/proactor_container_impl.cpp:805
> #16 0xb64cbcec in proton::container::run() (this=) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/cpp/src/container.cpp:92
> {code}
> This is the {{clazz }}that was reify'ed inside frame 1 {{(pn_class_free):}}
> {code:java}
> >>> frame 1
> #1 0xb634ed00 in pn_class_free (clazz=0x1e0490, object=0x1e0910) at
> /usr/src/debug/qpid-proton/0.33.0-r0/qpid-proton-0.33.0/c/src/core/object/object.c:120
> 120 int rc = clazz->refcount(object);
> >>> p *clazz
> $2 = {
> name = 0x48 ,
> cid = CID_pn_raw_connection,
> newinst = 0x1e0428,
> initialize = 0x0,
> incref = 0xb636e938 ,
> decref = 0x10,
> refcount = 0x0,
> finalize = 0x1e04b8,
> free = 0x0,
> reify = 0x49,
> hashcode = 0x1e0448,
> compare = 0x1e0540,
> inspect = 0x0
> }
> {code}
> I have a coredump of the crash, so it is quiet easy for me, to provide more
> information, if you have any idea, where I can start. It takes quite a while
> to get to this bug, normally the bug only surfaces if the service is running
> > 12 hours. If you have any other idea what I can trace, to get this bug
> fixed, please tell me.
[jira] [Created] (PROTON-2370) [cpp] An accessor for the delivery tag
Justin Ross created PROTON-2370: --- Summary: [cpp] An accessor for the delivery tag Key: PROTON-2370 URL: https://issues.apache.org/jira/browse/PROTON-2370 Project: Qpid Proton Issue Type: Improvement Components: cpp-binding Reporter: Justin Ross *Assignee: Rakhi* Steps: * Get familiar with the AMQP idea of a delivery tag * Add a delivery tag accessor to the C++ delivery class * Document the accessor in the C++ header * Add a test for the accessor to the C++ test suite Resources: * [http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#doc-idp438000] * [http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#type-delivery-tag] * [https://github.com/apache/qpid-proton/blob/main/c/include/proton/delivery.h#L106] * [https://github.com/apache/qpid-proton/blob/main/cpp/include/proton/delivery.hpp] -- 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-2357) [cpp] Improve test coverage in url.cpp
[ https://issues.apache.org/jira/browse/PROTON-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313429#comment-17313429 ] Justin Ross commented on PROTON-2357: - It also seems that the check for bad() is redundant, since fail() already checks that: http://www.cplusplus.com/reference/ios/ios/fail/ > [cpp] Improve test coverage in url.cpp > -- > > Key: PROTON-2357 > URL: https://issues.apache.org/jira/browse/PROTON-2357 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Labels: starter > > *Assignee: Rakhi Kumari* > Url.cpp currently has 76% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in url_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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-2357) [cpp] Improve test coverage in url.cpp
[ https://issues.apache.org/jira/browse/PROTON-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313428#comment-17313428 ] Justin Ross commented on PROTON-2357: - I think I agree about the empty side of that branch. I don't see how it can be triggered. > [cpp] Improve test coverage in url.cpp > -- > > Key: PROTON-2357 > URL: https://issues.apache.org/jira/browse/PROTON-2357 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Labels: starter > > *Assignee: Rakhi Kumari* > Url.cpp currently has 76% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in url_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2364) [cpp] Improve test coverage in decoder.cpp
[ https://issues.apache.org/jira/browse/PROTON-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2364: Description: *Assignee: Shivani Singh* Decoder.cpp currently has 74% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in codec_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results was: *Assignee: Kajal Sah* Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results > [cpp] Improve test coverage in decoder.cpp > -- > > Key: PROTON-2364 > URL: https://issues.apache.org/jira/browse/PROTON-2364 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Labels: starter > > *Assignee: Shivani Singh* > Decoder.cpp currently has 74% line coverage after running the tests. > Increase the coverage to 100% or as close as is practical. To do this, add > or modify tests in codec_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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-2364) [cpp] Improve test coverage in decoder.cpp
Justin Ross created PROTON-2364: --- Summary: [cpp] Improve test coverage in decoder.cpp Key: PROTON-2364 URL: https://issues.apache.org/jira/browse/PROTON-2364 Project: Qpid Proton Issue Type: Test Components: cpp-binding Reporter: Justin Ross Assignee: Justin Ross *Assignee: Kajal Sah* Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results -- 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] (PROTON-2363) [cpp] Improve test coverage in map.cpp
[ https://issues.apache.org/jira/browse/PROTON-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2363: Description: *Assignee: Sushma Unnibhavi* Map.cpp currently has 57% line coverage after running the tests (for my local config). Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in map_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results was: *Assignee: Kajal Sah* Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results > [cpp] Improve test coverage in map.cpp > -- > > Key: PROTON-2363 > URL: https://issues.apache.org/jira/browse/PROTON-2363 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Labels: starter > > *Assignee: Sushma Unnibhavi* > Map.cpp currently has 57% line coverage after running the tests (for my local > config). Increase the coverage to 100% or as close as is practical. To do > this, add or modify tests in map_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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-2363) [cpp] Improve test coverage in map.cpp
Justin Ross created PROTON-2363: --- Summary: [cpp] Improve test coverage in map.cpp Key: PROTON-2363 URL: https://issues.apache.org/jira/browse/PROTON-2363 Project: Qpid Proton Issue Type: Test Components: cpp-binding Reporter: Justin Ross Assignee: Justin Ross *Assignee: Kajal Sah* Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results -- 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] (PROTON-2357) [cpp] Improve test coverage in url.cpp
[ https://issues.apache.org/jira/browse/PROTON-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2357: Labels: starter (was: ) > [cpp] Improve test coverage in url.cpp > -- > > Key: PROTON-2357 > URL: https://issues.apache.org/jira/browse/PROTON-2357 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Labels: starter > > *Assignee: Rakhi Kumari* > Url.cpp currently has 76% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in url_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2360) [cpp] Improve test coverage in link.cpp
[ https://issues.apache.org/jira/browse/PROTON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2360: Labels: starter (was: ) > [cpp] Improve test coverage in link.cpp > --- > > Key: PROTON-2360 > URL: https://issues.apache.org/jira/browse/PROTON-2360 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Labels: starter > > *Assignee: Sunday Mgbogu* > Link.cpp currently has 82% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in link_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2356) [cpp] Improve test coverage in message.cpp
[ https://issues.apache.org/jira/browse/PROTON-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2356: Labels: starter (was: ) > [cpp] Improve test coverage in message.cpp > -- > > Key: PROTON-2356 > URL: https://issues.apache.org/jira/browse/PROTON-2356 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Labels: starter > > *Assignee: Kajal Sah* > Message.cpp currently has 84% line coverage after running the tests. > Increase the coverage to 100% or as close as is practical. To do this, add > or modify tests in message_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2358) [cpp] Improve test coverage in container.cpp
[ https://issues.apache.org/jira/browse/PROTON-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2358: Labels: starter (was: ) > [cpp] Improve test coverage in container.cpp > > > Key: PROTON-2358 > URL: https://issues.apache.org/jira/browse/PROTON-2358 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > Labels: starter > > *Assignee: Mehaboob Shariff* > Container.cpp currently has 70% line coverage after running the tests. > Increase the coverage to 100% or as close as is practical. To do this, add > or modify tests in container_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2358) [cpp] Improve test coverage in container.cpp
[ https://issues.apache.org/jira/browse/PROTON-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2358: Description: *Assignee: Mehaboob Shariff* Container.cpp currently has 70% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in container_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results was: Container.cpp currently has 70% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in container_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results > [cpp] Improve test coverage in container.cpp > > > Key: PROTON-2358 > URL: https://issues.apache.org/jira/browse/PROTON-2358 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > *Assignee: Mehaboob Shariff* > Container.cpp currently has 70% line coverage after running the tests. > Increase the coverage to 100% or as close as is practical. To do this, add > or modify tests in container_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2356) [cpp] Improve test coverage in message.cpp
[ https://issues.apache.org/jira/browse/PROTON-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2356: Description: *Assignee: Kajal Sah* Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results was: Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results > [cpp] Improve test coverage in message.cpp > -- > > Key: PROTON-2356 > URL: https://issues.apache.org/jira/browse/PROTON-2356 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > *Assignee: Kajal Sah* > Message.cpp currently has 84% line coverage after running the tests. > Increase the coverage to 100% or as close as is practical. To do this, add > or modify tests in message_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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-2360) [cpp] Improve test coverage in link.cpp
[ https://issues.apache.org/jira/browse/PROTON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313257#comment-17313257 ] Justin Ross commented on PROTON-2360: - [~digitalsimboja], when you have something that increases the coverage, I recommend raising a PR to get some early feedback. > [cpp] Improve test coverage in link.cpp > --- > > Key: PROTON-2360 > URL: https://issues.apache.org/jira/browse/PROTON-2360 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > *Assignee: Sunday Mgbogu* > Link.cpp currently has 82% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in link_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2360) [cpp] Improve test coverage in link.cpp
[ https://issues.apache.org/jira/browse/PROTON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2360: Description: *Assignee: Sunday Mgbogu* Link.cpp currently has 82% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in link_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results was: Link.cpp currently has 82% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in link_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results > [cpp] Improve test coverage in link.cpp > --- > > Key: PROTON-2360 > URL: https://issues.apache.org/jira/browse/PROTON-2360 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > *Assignee: Sunday Mgbogu* > Link.cpp currently has 82% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in link_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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-2357) [cpp] Improve test coverage in url.cpp
[ https://issues.apache.org/jira/browse/PROTON-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313250#comment-17313250 ] Justin Ross commented on PROTON-2357: - [~DreamPearl], if you are already at 98%, I think raising a PR for initial review is a good idea. You'll likely get comments about how to structure the tests and that kind of thing. > [cpp] Improve test coverage in url.cpp > -- > > Key: PROTON-2357 > URL: https://issues.apache.org/jira/browse/PROTON-2357 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > *Assignee: Rakhi Kumari* > Url.cpp currently has 76% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in url_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2357) [cpp] Improve test coverage in url.cpp
[ https://issues.apache.org/jira/browse/PROTON-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2357: Description: *Assignee: Rakhi Kumari* Url.cpp currently has 76% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in url_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results was: Url.cpp currently has 76% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in url_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results > [cpp] Improve test coverage in url.cpp > -- > > Key: PROTON-2357 > URL: https://issues.apache.org/jira/browse/PROTON-2357 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > *Assignee: Rakhi Kumari* > Url.cpp currently has 76% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in url_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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-2357) [cpp] Improve test coverage in url.cpp
[ https://issues.apache.org/jira/browse/PROTON-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313242#comment-17313242 ] Justin Ross commented on PROTON-2357: - Hi, [~sushmau]. I assigned this one to Rakhi. I'll find another task for you. > [cpp] Improve test coverage in url.cpp > -- > > Key: PROTON-2357 > URL: https://issues.apache.org/jira/browse/PROTON-2357 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > Url.cpp currently has 76% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in url_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2357) [cpp] Improve test coverage in url.cpp
[ https://issues.apache.org/jira/browse/PROTON-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2357: Description: Url.cpp currently has 76% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in url_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results was: Url.cpp currently has 76% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in url_test.cpp. To set up coverage builds: - Install lcov, the code coverage tool - Compile proton with -DCMAKE_BUILD_TYPE=Coverage - Run the tests: make test - Generate coverage results: make coverage - View the results at /coverage_results > [cpp] Improve test coverage in url.cpp > -- > > Key: PROTON-2357 > URL: https://issues.apache.org/jira/browse/PROTON-2357 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > Url.cpp currently has 76% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in url_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2360) [cpp] Improve test coverage in link.cpp
[ https://issues.apache.org/jira/browse/PROTON-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2360: Description: Link.cpp currently has 82% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in link_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results was: Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results > [cpp] Improve test coverage in link.cpp > --- > > Key: PROTON-2360 > URL: https://issues.apache.org/jira/browse/PROTON-2360 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > Link.cpp currently has 82% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in link_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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-2360) [cpp] Improve test coverage in link.cpp
Justin Ross created PROTON-2360: --- Summary: [cpp] Improve test coverage in link.cpp Key: PROTON-2360 URL: https://issues.apache.org/jira/browse/PROTON-2360 Project: Qpid Proton Issue Type: Test Components: cpp-binding Reporter: Justin Ross Assignee: Justin Ross Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results -- 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] (PROTON-2358) [cpp] Improve test coverage in container.cpp
[ https://issues.apache.org/jira/browse/PROTON-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2358: Description: Container.cpp currently has 70% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in container_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results was: Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results > [cpp] Improve test coverage in container.cpp > > > Key: PROTON-2358 > URL: https://issues.apache.org/jira/browse/PROTON-2358 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > Container.cpp currently has 70% line coverage after running the tests. > Increase the coverage to 100% or as close as is practical. To do this, add > or modify tests in container_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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-2358) [cpp] Improve test coverage in container.cpp
Justin Ross created PROTON-2358: --- Summary: [cpp] Improve test coverage in container.cpp Key: PROTON-2358 URL: https://issues.apache.org/jira/browse/PROTON-2358 Project: Qpid Proton Issue Type: Test Components: cpp-binding Reporter: Justin Ross Assignee: Justin Ross Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results -- 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] (PROTON-2356) [cpp] Improve test coverage in message.cpp
[ https://issues.apache.org/jira/browse/PROTON-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2356: Description: Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: # Install lcov, the code coverage tool # Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] # Build the code: make build # Run the tests: make test # Generate coverage results: make coverage # View the results at /coverage_results was: Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: - Install lcov, the code coverage tool - Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] - Build the code: make build - Run the tests: make test - Generate coverage results: make coverage - View the results at /coverage_results > [cpp] Improve test coverage in message.cpp > -- > > Key: PROTON-2356 > URL: https://issues.apache.org/jira/browse/PROTON-2356 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > Message.cpp currently has 84% line coverage after running the tests. > Increase the coverage to 100% or as close as is practical. To do this, add > or modify tests in message_test.cpp. > To set up coverage builds: > # Install lcov, the code coverage tool > # Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > # Build the code: make build > # Run the tests: make test > # Generate coverage results: make coverage > # View the results at /coverage_results -- 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] (PROTON-2356) [cpp] Improve test coverage in message.cpp
[ https://issues.apache.org/jira/browse/PROTON-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2356: Description: Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: - Install lcov, the code coverage tool - Configure the build for coverage analysis: cmake -DCMAKE_BUILD_TYPE=Coverage [...] - Build the code: make build - Run the tests: make test - Generate coverage results: make coverage - View the results at /coverage_results was: Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: - Install lcov, the code coverage tool - Compile proton with -DCMAKE_BUILD_TYPE=Coverage - Run the tests: make test - Generate coverage results: make coverage - View the results at /coverage_results > [cpp] Improve test coverage in message.cpp > -- > > Key: PROTON-2356 > URL: https://issues.apache.org/jira/browse/PROTON-2356 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > Message.cpp currently has 84% line coverage after running the tests. > Increase the coverage to 100% or as close as is practical. To do this, add > or modify tests in message_test.cpp. > > To set up coverage builds: > - Install lcov, the code coverage tool > - Configure the build for coverage analysis: cmake > -DCMAKE_BUILD_TYPE=Coverage [...] > - Build the code: make build > - Run the tests: make test > - Generate coverage results: make coverage > - View the results at /coverage_results > -- 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] (PROTON-2357) [cpp] Improve test coverage in url.cpp
[ https://issues.apache.org/jira/browse/PROTON-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2357: Description: Url.cpp currently has 76% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in url_test.cpp. To set up coverage builds: - Install lcov, the code coverage tool - Compile proton with -DCMAKE_BUILD_TYPE=Coverage - Run the tests: make test - Generate coverage results: make coverage - View the results at /coverage_results was: Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add tests to message_test.cpp. To set up coverage builds: - Install lcov, the code coverage tool - Compile proton with -DCMAKE_BUILD_TYPE=Coverage - Run the tests: make test - Generate coverage results: make coverage - View the results at /coverage_results > [cpp] Improve test coverage in url.cpp > -- > > Key: PROTON-2357 > URL: https://issues.apache.org/jira/browse/PROTON-2357 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > Url.cpp currently has 76% line coverage after running the tests. Increase > the coverage to 100% or as close as is practical. To do this, add or modify > tests in url_test.cpp. > > To set up coverage builds: > - Install lcov, the code coverage tool > - Compile proton with -DCMAKE_BUILD_TYPE=Coverage > - Run the tests: make test > - Generate coverage results: make coverage > - View the results at /coverage_results > -- 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] (PROTON-2356) [cpp] Improve test coverage in message.cpp
[ https://issues.apache.org/jira/browse/PROTON-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-2356: Description: Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add or modify tests in message_test.cpp. To set up coverage builds: - Install lcov, the code coverage tool - Compile proton with -DCMAKE_BUILD_TYPE=Coverage - Run the tests: make test - Generate coverage results: make coverage - View the results at /coverage_results was: Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add tests to message_test.cpp. To set up coverage builds: - Install lcov, the code coverage tool - Compile proton with -DCMAKE_BUILD_TYPE=Coverage - Run the tests: make test - Generate coverage results: make coverage - View the results at /coverage_results > [cpp] Improve test coverage in message.cpp > -- > > Key: PROTON-2356 > URL: https://issues.apache.org/jira/browse/PROTON-2356 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > Message.cpp currently has 84% line coverage after running the tests. > Increase the coverage to 100% or as close as is practical. To do this, add > or modify tests in message_test.cpp. > > To set up coverage builds: > - Install lcov, the code coverage tool > - Compile proton with -DCMAKE_BUILD_TYPE=Coverage > - Run the tests: make test > - Generate coverage results: make coverage > - View the results at /coverage_results > -- 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-2357) [cpp] Improve test coverage in url.cpp
Justin Ross created PROTON-2357: --- Summary: [cpp] Improve test coverage in url.cpp Key: PROTON-2357 URL: https://issues.apache.org/jira/browse/PROTON-2357 Project: Qpid Proton Issue Type: Test Components: cpp-binding Reporter: Justin Ross Assignee: Justin Ross Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add tests to message_test.cpp. To set up coverage builds: - Install lcov, the code coverage tool - Compile proton with -DCMAKE_BUILD_TYPE=Coverage - Run the tests: make test - Generate coverage results: make coverage - View the results at /coverage_results -- 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] (PROTON-2356) [cpp] Improve test coverage in message.cpp
[ https://issues.apache.org/jira/browse/PROTON-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross reassigned PROTON-2356: --- Assignee: Justin Ross > [cpp] Improve test coverage in message.cpp > -- > > Key: PROTON-2356 > URL: https://issues.apache.org/jira/browse/PROTON-2356 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >Priority: Major > > Message.cpp currently has 84% line coverage after running the tests. > Increase the coverage to 100% or as close as is practical. To do this, add > tests to message_test.cpp. > > To set up coverage builds: > - Install lcov, the code coverage tool > - Compile proton with -DCMAKE_BUILD_TYPE=Coverage > - Run the tests: make test > - Generate coverage results: make coverage > - View the results at /coverage_results > -- 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-2356) [cpp] Improve test coverage in message.cpp
Justin Ross created PROTON-2356: --- Summary: [cpp] Improve test coverage in message.cpp Key: PROTON-2356 URL: https://issues.apache.org/jira/browse/PROTON-2356 Project: Qpid Proton Issue Type: Test Components: cpp-binding Reporter: Justin Ross Message.cpp currently has 84% line coverage after running the tests. Increase the coverage to 100% or as close as is practical. To do this, add tests to message_test.cpp. To set up coverage builds: - Install lcov, the code coverage tool - Compile proton with -DCMAKE_BUILD_TYPE=Coverage - Run the tests: make test - Generate coverage results: make coverage - View the results at /coverage_results -- 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] (PROTON-1786) Multiframe transfer wire traffic patterns differ substantially
[
https://issues.apache.org/jira/browse/PROTON-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-1786:
Component/s: proton-c
> Multiframe transfer wire traffic patterns differ substantially
> --
>
> Key: PROTON-1786
> URL: https://issues.apache.org/jira/browse/PROTON-1786
> Project: Qpid Proton
> Issue Type: Task
> Components: proton-c
>Reporter: Kim van der Riet
>Priority: Major
> Attachments: dispatch.multiframe.07.pcapng
>
>
> This is not a bug (although it could become one), but rather an observation
> of large message transfer patterns observed using Wireshark while running
> Qpid Interop Test's amqp_large_content_test.
> The test sends large messages through a broker (in this case, dispatch
> router) of size 1MB and 10MB.
> I hope to add other observable patterns from other clients and/or brokers if
> they are significant. If there is consensus that this is a potential large
> message transfer efficiency issue, then this Jira can be a placeholder for
> this issue.
> See the attached file for an example. In this test, the receiver is using
> TCP port 59806 and the sender port 59808. The router is using the standard
> AMQP port.
> h2. C++ client:
> The client in this case uses the Proton C++ API and is based on the
> SimpleSender.cpp example. To isolate the traffic from this client, use the
> following filter in Wireshark:
> {noformat}
> amqp.performative == transfer && tcp.srcport == 59808{noformat}
> It can be seen that although there is a large message being sent, the sender
> appears to be restricted to a single transfer of 16kB or a 64kB frame
> containing 4 transfers (very occasionally, 2, 3 or 5 transfers) - for example:
> {noformat}
> 351.972620::1 ::1 AMQP16470 transfer
> 1177 2.032878::1 ::1 AMQP65550 transfer transfer
> transfer transfer
> {noformat}
> h2. Dispatch Router:
> This uses Proton through its native C interface. To isolate the traffic from
> the router to the receiver, use the following Wireshark filter:
> {noformat}
> amqp.performative == transfer && tcp.dstport == 59806{noformat}
> The traffic for this broker looks very different. Each frame contains only a
> single transfer, and the size of the transfers differ widely, from 196 bytes
> to the full 64kB max. I am assuming that the router is sending on message
> content it has received as soon as it becomes available no matter the size.
--
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] (PROTON-1765) [ruby] auto-test of installed gem
[
https://issues.apache.org/jira/browse/PROTON-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated PROTON-1765:
Component/s: ruby-binding
> [ruby] auto-test of installed gem
> -
>
> Key: PROTON-1765
> URL: https://issues.apache.org/jira/browse/PROTON-1765
> Project: Qpid Proton
> Issue Type: Improvement
> Components: ruby-binding
>Reporter: Alan Conway
>Priority: Trivial
>
> Restore the following tests to the ruby/CMakeLists.txt section that builds a
> gem:
> {code:java}
> # Test installing the gem.
> to_native_path("${bin}/install" gem_home)
> set(gem_env ${env_py} -- "GEM_HOME=${gem_home}"
> "LD_LIBRARY_PATH=${c_lib_dir}")
> add_test(
> NAME ruby-gem-install
> COMMAND ${gem_env} ${GEM_EXE} install "${GEM_FILE}" --
> "--with-qpid-proton-include=${CMAKE_SOURCE_DIR}/proton-c/include"
> "--with-qpid-proton-lib=${c_lib_dir}"
> )
> # Test running examples against the installed gem
> add_test(
> NAME ruby-gem-examples
> COMMAND ${gem_env} ${RUBY_EXECUTABLE} example_test.rb -v
> WORKING_DIRECTORY ${CMAKE_SOURCE_DIR}/examples/ruby
> )
> SET_TESTS_PROPERTIES(ruby-gem-examples PROPERTIES DEPENDS ruby-gem-install) #
> Run after install{code}
> This works on some platforms (fedora 26) but fails on Travis CI builds in
> the ruby-gem-examples test, e.g.
> [https://travis-ci.org/alanconway/qpid-proton/jobs/342502018]
> Doesn't seem to indicate a problem with the Gem, but rather with the test
> setup. The error is like this:
> {code:java}
> 2: Test command: /opt/pyenv/shims/python
> "/home/travis/build/alanconway/qpid-proton/proton-c/env.py" "--"
> "GEM_HOME=/home/travis/build/alanconway/qpid-proton/build/proton-c/bindings/ruby/install"
> "LD_LIBRARY_PATH=/home/travis/build/alanconway/qpid-proton/build/proton-c"
> "/home/travis/.rvm/rubies/ruby-2.4.1/bin/ruby" "example_test.rb" "-v"
> 2: Test timeout computed to be: 1500
> 2:
> /home/travis/.rvm/rubies/ruby-2.4.1/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
> `require': incompatible library version -
> /home/travis/build/alanconway/qpid-proton/build/proton-c/bindings/ruby/install/gems/qpid_proton-0.21.0/lib/cproton.so
> (LoadError)
> 2:from
> /home/travis/.rvm/rubies/ruby-2.4.1/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in
> `require'
> 2:from
> /home/travis/build/alanconway/qpid-proton/build/proton-c/bindings/ruby/install/gems/qpid_proton-0.21.0/lib/qpid_proton.rb:19:in
> `'
> 2:from
> /home/travis/.rvm/rubies/ruby-2.4.1/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:133:in
> `require'
> 2:from
> /home/travis/.rvm/rubies/ruby-2.4.1/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:133:in
> `rescue in require'
> 2:from
> /home/travis/.rvm/rubies/ruby-2.4.1/lib/ruby/site_ruby/2.4.0/rubygems/core_ext/kernel_require.rb:40:in
> `require'
> 2:from example_test.rb:22:in `'
> 2/32 Test #2: ruby-gem-examples ***Failed0.15 sec{code}
--
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] (PROTON-1864) [c] No way of indicating that a transport is ssl or encrypted or already authenticated
[ https://issues.apache.org/jira/browse/PROTON-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1864: Summary: [c] No way of indicating that a transport is ssl or encrypted or already authenticated (was: No way of indicating that a transport is ssl or encrypted or already authenticated) > [c] No way of indicating that a transport is ssl or encrypted or already > authenticated > -- > > Key: PROTON-1864 > URL: https://issues.apache.org/jira/browse/PROTON-1864 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Gordon Sim >Priority: Major > > This is needed e.g. for DISPATCH-1040 -- 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] (PROTON-1864) No way of indicating that a transport is ssl or encrypted or already authenticated
[ https://issues.apache.org/jira/browse/PROTON-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1864: Component/s: proton-c > No way of indicating that a transport is ssl or encrypted or already > authenticated > -- > > Key: PROTON-1864 > URL: https://issues.apache.org/jira/browse/PROTON-1864 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Gordon Sim >Priority: Major > > This is needed e.g. for DISPATCH-1040 -- 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
