[jira] [Updated] (DISPATCH-1560) Compilation error on Fedora 32 (fedora rawhide)
[
https://issues.apache.org/jira/browse/DISPATCH-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated DISPATCH-1560:
-
Description:
{noformat}
/usr/bin/ld:
CMakeFiles/qpid-dispatch.dir/router_node.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
multiple definition of `qd_amqp_type_t';
CMakeFiles/qpid-dispatch.dir/amqp.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
first defined here
/usr/bin/ld:
CMakeFiles/qpid-dispatch.dir/router_pynode.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
multiple definition of `qd_amqp_type_t';
CMakeFiles/qpid-dispatch.dir/amqp.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
first defined here
/usr/bin/ld:
CMakeFiles/qpid-dispatch.dir/server.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
multiple definition of `qd_amqp_type_t';
CMakeFiles/qpid-dispatch.dir/amqp.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
first defined here
/usr/bin/ld:
CMakeFiles/qpid-dispatch.dir/timer.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
multiple definition of `qd_amqp_type_t';
CMakeFiles/qpid-dispatch.dir/amqp.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
first defined here
/usr/bin/ld:
CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
multiple definition of `qd_amqp_type_t';
CMakeFiles/qpid-dispatch.dir/amqp.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
first defined here {noformat}
was:
{noformat}
[ 79%] Linking C shared library libqpid-dispatch.so
cd /builddir/build/BUILD/qpid-dispatch-1.10.0/src && /usr/bin/cmake -E
cmake_link_script CMakeFiles/qpid-dispatch.dir/link.txt --verbose=1
/usr/bin/cc -fPIC -O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions
-fstack-protector-strong -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-Wno-pointer-to-int-cast -Wno-int-to-pointer-cast -Wno-stringop-overflow -O2 -g
-DNDEBUG -Wl,-z,defs -Wl,-z,relro -Wl,--as-needed -Wl,-z,now
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld -shared
-Wl,-soname,libqpid-dispatch.so -o libqpid-dispatch.so
CMakeFiles/qpid-dispatch.dir/alloc_pool.c.o
CMakeFiles/qpid-dispatch.dir/amqp.c.o CMakeFiles/qpid-dispatch.dir/bitmask.c.o
CMakeFiles/qpid-dispatch.dir/buffer.c.o CMakeFiles/qpid-dispatch.dir/error.c.o
CMakeFiles/qpid-dispatch.dir/compose.c.o
CMakeFiles/qpid-dispatch.dir/connection_manager.c.o
CMakeFiles/qpid-dispatch.dir/container.c.o
CMakeFiles/qpid-dispatch.dir/discriminator.c.o
CMakeFiles/qpid-dispatch.dir/dispatch.c.o
CMakeFiles/qpid-dispatch.dir/entity.c.o
CMakeFiles/qpid-dispatch.dir/entity_cache.c.o
CMakeFiles/qpid-dispatch.dir/failoverlist.c.o
CMakeFiles/qpid-dispatch.dir/hash.c.o CMakeFiles/qpid-dispatch.dir/iterator.c.o
CMakeFiles/qpid-dispatch.dir/log.c.o CMakeFiles/qpid-dispatch.dir/message.c.o
CMakeFiles/qpid-dispatch.dir/parse.c.o
CMakeFiles/qpid-dispatch.dir/parse_tree.c.o
CMakeFiles/qpid-dispatch.dir/policy.c.o
CMakeFiles/qpid-dispatch.dir/proton_utils.c.o
CMakeFiles/qpid-dispatch.dir/remote_sasl.c.o
CMakeFiles/qpid-dispatch.dir/posix/threading.c.o
CMakeFiles/qpid-dispatch.dir/python_embedded.c.o
CMakeFiles/qpid-dispatch.dir/router_agent.c.o
CMakeFiles/qpid-dispatch.dir/router_config.c.o
CMakeFiles/qpid-dispatch.dir/address_lookup_utils.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_address.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_config_address.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_config_auto_link.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_connection.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_config_link_route.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_link.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_router.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_conn_link_route.c.o
CMakeFiles/qpid-dispatch.dir/router_core/connections.c.o
CMakeFiles/qpid-dispatch.dir/router_core/core_events.c.o
CMakeFiles/qpid-dispatch.dir/router_core/core_link_endpoint.c.o
CMakeFiles/qpid-dispatch.dir/router_core/core_client_api.c.o
CMakeFiles/qpid-dispatch.dir/router_core/delivery.c.o
CMakeFiles/qpid-dispatch.dir/router_core/error.c.o
CMakeFiles/qpid-dispatch.dir/router_core/exchange_bindings.c.o
CMakeFiles/qpid-dispatch.dir/router_core/forwarder.c.o
CMakeFiles/qpid-dispatch.dir/router_core/route_control.c.o
CMakeFiles/qpid-dispatch.dir/router_core/router_core.c.o
[jira] [Updated] (QPID-8403) [Broker-J] Configuring HTTP port for External Authentication causes Web Management Console to throw HTTP 403 errors
[ https://issues.apache.org/jira/browse/QPID-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8403: - Summary: [Broker-J] Configuring HTTP port for External Authentication causes Web Management Console to throw HTTP 403 errors (was: Configuring HTTP port for External Authentication causes Web Management Console to throw HTTP 403 errors ) > [Broker-J] Configuring HTTP port for External Authentication causes Web > Management Console to throw HTTP 403 errors > > > Key: QPID-8403 > URL: https://issues.apache.org/jira/browse/QPID-8403 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.1, qpid-java-broker-7.1.2, > qpid-java-broker-7.1.3, qpid-java-broker-7.1.4, qpid-java-broker-7.1.5, > qpid-java-broker-7.1.6, qpid-java-broker-7.1.7 > Environment: QPID 7.1.0 (also verified on 7.1.7) > CentOS 7 with kernel 3.10.0-693.2.2.el7.x86_64 > JVM: OpenJDK 11+28 >Reporter: David Gillingham >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > Attachments: > 0001-QPID-8403-Broker-J-WMC-Add-interactive-authenticator.patch, config.json > > > I am attempting to configure QPID Broker-J's Web Management Console to > operate via HTTPS using only certificates for authentication. I created the > necessary auth provider, trust store and key store and configured the HTTP > port to use only the SSL transport and to use the auth provider, trust store > and key store. > When I attempt to connect to the web management console I am present with a > web page titled HTTP ERROR 403 and message that states "Problem accessing /. > Reason:Forbidden". This happens regardless if I attempt to connect using > Firefox or cURL. > However, the REST API will allow connections using this configuration. > Running the command "curl --cacert root.crt --cert guest.crt --key guest.key > https://localhost:8080/api/latest/queue; correctly returns "[ ]". > Changing the HTTP port to use a "Plain" or "MD5" authentication provider > allows operation of both interfaces, but I'd rather not require user/password > on top of the certificate. > Attached is the config.json I used to replicate the problem on QPID Broker-J > 7.1.7. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8404) [Broker-J] Use of TLS client certificates in versions > = 7.1.5 broken by Jetty changes
[ https://issues.apache.org/jira/browse/QPID-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8404. -- Resolution: Fixed > [Broker-J] Use of TLS client certificates in versions > = 7.1.5 broken by > Jetty changes > --- > > Key: QPID-8404 > URL: https://issues.apache.org/jira/browse/QPID-8404 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.5, qpid-java-broker-7.1.6, > qpid-java-broker-7.1.7 >Reporter: Robert Godfrey >Assignee: Robert Godfrey >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > Attachments: > 0001-QPID-8404-Fix-usage-of-Jetty-for-TLS-client-certs.patch > > > Changes in Jetty aimed at improving the client side use of TLS using that > library broke implementations using it for server side usage of client certs. > (See also https://github.com/eclipse/jetty.project/issues/3554) -- 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] (QPID-8403) Configuring HTTP port for External Authentication causes Web Management Console to throw HTTP 403 errors
[ https://issues.apache.org/jira/browse/QPID-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8403: - Status: Reviewable (was: In Progress) > Configuring HTTP port for External Authentication causes Web Management > Console to throw HTTP 403 errors > - > > Key: QPID-8403 > URL: https://issues.apache.org/jira/browse/QPID-8403 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.1, qpid-java-broker-7.1.2, > qpid-java-broker-7.1.3, qpid-java-broker-7.1.4, qpid-java-broker-7.1.5, > qpid-java-broker-7.1.6, qpid-java-broker-7.1.7 > Environment: QPID 7.1.0 (also verified on 7.1.7) > CentOS 7 with kernel 3.10.0-693.2.2.el7.x86_64 > JVM: OpenJDK 11+28 >Reporter: David Gillingham >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > Attachments: > 0001-QPID-8403-Broker-J-WMC-Add-interactive-authenticator.patch, config.json > > > I am attempting to configure QPID Broker-J's Web Management Console to > operate via HTTPS using only certificates for authentication. I created the > necessary auth provider, trust store and key store and configured the HTTP > port to use only the SSL transport and to use the auth provider, trust store > and key store. > When I attempt to connect to the web management console I am present with a > web page titled HTTP ERROR 403 and message that states "Problem accessing /. > Reason:Forbidden". This happens regardless if I attempt to connect using > Firefox or cURL. > However, the REST API will allow connections using this configuration. > Running the command "curl --cacert root.crt --cert guest.crt --key guest.key > https://localhost:8080/api/latest/queue; correctly returns "[ ]". > Changing the HTTP port to use a "Plain" or "MD5" authentication provider > allows operation of both interfaces, but I'd rather not require user/password > on top of the certificate. > Attached is the config.json I used to replicate the problem on QPID Broker-J > 7.1.7. -- 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] (QPID-8407) [Broker-J][BDB HA] Asynchronous message store recoverer can fail to recover messages on switching the master node
[ https://issues.apache.org/jira/browse/QPID-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8407: Assignee: Alex Rudyy > [Broker-J][BDB HA] Asynchronous message store recoverer can fail to recover > messages on switching the master node > - > > Key: QPID-8407 > URL: https://issues.apache.org/jira/browse/QPID-8407 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, > qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, > qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1, > qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, > qpid-java-broker-7.1.4, qpid-java-broker-7.1.5, qpid-java-broker-7.1.6, > qpid-java-broker-7.1.7 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > > With asynchronous message store recovery, when mastership is changed and > flipped back to the previous node, the cached sequence object resumes > sequence id generation from the previous value (before the masteship was > changed). As result, the asynchronous message store recoverer fails to > recover the messages with IDs greater than maximum sequence range value (in > cached sequence object). Such messages are not get recovered from the > message store. On follow-up restart, the messages can be potentially > recovered, if the message id sequence is sufficiently incremented, however, > the issue might result in unordered delivery and generation of duplicate > message IDs. > The synchronous message store recoverer is not effected by the issue. Thus, > switching to synchronous message store recovery (turned on by default) would > allow to work around the problem. -- 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] (QPID-8406) [Broker-J] Display connection transport information in web management console
[
https://issues.apache.org/jira/browse/QPID-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8406:
-
Status: Reviewable (was: In Progress)
> [Broker-J] Display connection transport information in web management console
> -
>
> Key: QPID-8406
> URL: https://issues.apache.org/jira/browse/QPID-8406
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Trivial
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8
>
>
> The information about connection TLS version is provided via {{Connection}}
> attribute {{transportInfo}}. It would be beneficial to display that
> information in Web management Console on connection tab.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-8407) [Broker-J][BDB HA] Asynchronous message store recoverer can fail to recover messages on switching the master node
[ https://issues.apache.org/jira/browse/QPID-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8407. -- Resolution: Fixed > [Broker-J][BDB HA] Asynchronous message store recoverer can fail to recover > messages on switching the master node > - > > Key: QPID-8407 > URL: https://issues.apache.org/jira/browse/QPID-8407 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, > qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, > qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1, > qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, > qpid-java-broker-7.1.4, qpid-java-broker-7.1.5, qpid-java-broker-7.1.6, > qpid-java-broker-7.1.7 >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > > With asynchronous message store recovery, when mastership is changed and > flipped back to the previous node, the cached sequence object resumes > sequence id generation from the previous value (before the masteship was > changed). As result, the asynchronous message store recoverer fails to > recover the messages with IDs greater than maximum sequence range value (in > cached sequence object). Such messages are not get recovered from the > message store. On follow-up restart, the messages can be potentially > recovered, if the message id sequence is sufficiently incremented, however, > the issue might result in unordered delivery and generation of duplicate > message IDs. > The synchronous message store recoverer is not effected by the issue. Thus, > switching to synchronous message store recovery (turned on by default) would > allow to work around the problem. -- 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] (QPID-8407) [Broker-J][BDB HA] Asynchronous message store recoverer can fail to recover messages on switching the master node
[ https://issues.apache.org/jira/browse/QPID-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030852#comment-17030852 ] ASF subversion and git services commented on QPID-8407: --- Commit 17640005301ee061bd962a24c35a107f89b49704 in qpid-broker-j's branch refs/heads/7.1.x from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=1764000 ] QPID-8407: [Broker-J] Fix test (cherry picked from commit f39588d3df938412ba736f560beb71ebd22cb2c6) > [Broker-J][BDB HA] Asynchronous message store recoverer can fail to recover > messages on switching the master node > - > > Key: QPID-8407 > URL: https://issues.apache.org/jira/browse/QPID-8407 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, > qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, > qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1, > qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, > qpid-java-broker-7.1.4, qpid-java-broker-7.1.5, qpid-java-broker-7.1.6, > qpid-java-broker-7.1.7 >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > > With asynchronous message store recovery, when mastership is changed and > flipped back to the previous node, the cached sequence object resumes > sequence id generation from the previous value (before the masteship was > changed). As result, the asynchronous message store recoverer fails to > recover the messages with IDs greater than maximum sequence range value (in > cached sequence object). Such messages are not get recovered from the > message store. On follow-up restart, the messages can be potentially > recovered, if the message id sequence is sufficiently incremented, however, > the issue might result in unordered delivery and generation of duplicate > message IDs. > The synchronous message store recoverer is not effected by the issue. Thus, > switching to synchronous message store recovery (turned on by default) would > allow to work around the problem. -- 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] (QPID-8403) Configuring HTTP port for External Authentication causes Web Management Console to throw HTTP 403 errors
[ https://issues.apache.org/jira/browse/QPID-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030853#comment-17030853 ] ASF subversion and git services commented on QPID-8403: --- Commit 14b5537017b3123570d4830b3227bf7f74678b72 in qpid-broker-j's branch refs/heads/7.1.x from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=14b5537 ] QPID-8403: [Broker-J][WMC] Add interactive authenticator for certificate based authentication (cherry picked from commit ee4bcd43c110bfd5ac8bc110a55dd2a3f549c925) > Configuring HTTP port for External Authentication causes Web Management > Console to throw HTTP 403 errors > - > > Key: QPID-8403 > URL: https://issues.apache.org/jira/browse/QPID-8403 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.1, qpid-java-broker-7.1.2, > qpid-java-broker-7.1.3, qpid-java-broker-7.1.4, qpid-java-broker-7.1.5, > qpid-java-broker-7.1.6, qpid-java-broker-7.1.7 > Environment: QPID 7.1.0 (also verified on 7.1.7) > CentOS 7 with kernel 3.10.0-693.2.2.el7.x86_64 > JVM: OpenJDK 11+28 >Reporter: David Gillingham >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > Attachments: > 0001-QPID-8403-Broker-J-WMC-Add-interactive-authenticator.patch, config.json > > > I am attempting to configure QPID Broker-J's Web Management Console to > operate via HTTPS using only certificates for authentication. I created the > necessary auth provider, trust store and key store and configured the HTTP > port to use only the SSL transport and to use the auth provider, trust store > and key store. > When I attempt to connect to the web management console I am present with a > web page titled HTTP ERROR 403 and message that states "Problem accessing /. > Reason:Forbidden". This happens regardless if I attempt to connect using > Firefox or cURL. > However, the REST API will allow connections using this configuration. > Running the command "curl --cacert root.crt --cert guest.crt --key guest.key > https://localhost:8080/api/latest/queue; correctly returns "[ ]". > Changing the HTTP port to use a "Plain" or "MD5" authentication provider > allows operation of both interfaces, but I'd rather not require user/password > on top of the certificate. > Attached is the config.json I used to replicate the problem on QPID Broker-J > 7.1.7. -- 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] (QPID-8406) [Broker-J] Display connection transport information in web management console
[
https://issues.apache.org/jira/browse/QPID-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030855#comment-17030855
]
ASF subversion and git services commented on QPID-8406:
---
Commit b8729b25061098ef903a8670aff9fce3242b0831 in qpid-broker-j's branch
refs/heads/7.1.x from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=b8729b2 ]
QPID-8406: [Broker-J][WMC] Display connection transport information in web
management console
(cherry picked from commit c06b962bb9a3914933fc296564d4df2e4fbeb09f)
> [Broker-J] Display connection transport information in web management console
> -
>
> Key: QPID-8406
> URL: https://issues.apache.org/jira/browse/QPID-8406
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Alex Rudyy
>Priority: Trivial
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8
>
>
> The information about connection TLS version is provided via {{Connection}}
> attribute {{transportInfo}}. It would be beneficial to display that
> information in Web management Console on connection tab.
--
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] (QPID-8404) [Broker-J] Use of TLS client certificates in versions > = 7.1.5 broken by Jetty changes
[ https://issues.apache.org/jira/browse/QPID-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030854#comment-17030854 ] ASF subversion and git services commented on QPID-8404: --- Commit 17bee345f4dde5b0985c07bd589db5007b1ec33b in qpid-broker-j's branch refs/heads/7.1.x from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=17bee34 ] QPID-8404: [Broker-J] Change jetty ssl context factory to SslContextFactory.Server (cherry picked from commit e8725e904e0ce013f7e50ffb5dd5e95b7520c578) > [Broker-J] Use of TLS client certificates in versions > = 7.1.5 broken by > Jetty changes > --- > > Key: QPID-8404 > URL: https://issues.apache.org/jira/browse/QPID-8404 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.5, qpid-java-broker-7.1.6, > qpid-java-broker-7.1.7 >Reporter: Robert Godfrey >Assignee: Robert Godfrey >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > Attachments: > 0001-QPID-8404-Fix-usage-of-Jetty-for-TLS-client-certs.patch > > > Changes in Jetty aimed at improving the client side use of TLS using that > library broke implementations using it for server side usage of client certs. > (See also https://github.com/eclipse/jetty.project/issues/3554) -- 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] (QPID-8404) [Broker-J] Use of TLS client certificates in versions > = 7.1.5 broken by Jetty changes
[ https://issues.apache.org/jira/browse/QPID-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030850#comment-17030850 ] ASF subversion and git services commented on QPID-8404: --- Commit c7c207f14b42ef485a888795e20d8c636d79a3ba in qpid-broker-j's branch refs/heads/7.1.x from Robert Godfrey [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=c7c207f ] QPID-8404 : Fix usage of Jetty for TLS client certs (cherry picked from commit 5330ba51e9c48eaec15b8886ca14746ae093671a) > [Broker-J] Use of TLS client certificates in versions > = 7.1.5 broken by > Jetty changes > --- > > Key: QPID-8404 > URL: https://issues.apache.org/jira/browse/QPID-8404 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.5, qpid-java-broker-7.1.6, > qpid-java-broker-7.1.7 >Reporter: Robert Godfrey >Assignee: Robert Godfrey >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > Attachments: > 0001-QPID-8404-Fix-usage-of-Jetty-for-TLS-client-certs.patch > > > Changes in Jetty aimed at improving the client side use of TLS using that > library broke implementations using it for server side usage of client certs. > (See also https://github.com/eclipse/jetty.project/issues/3554) -- 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] (QPID-8407) [Broker-J][BDB HA] Asynchronous message store recoverer can fail to recover messages on switching the master node
[ https://issues.apache.org/jira/browse/QPID-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030851#comment-17030851 ] ASF subversion and git services commented on QPID-8407: --- Commit 119960d47d576833fc947fc05814ea7601b5a955 in qpid-broker-j's branch refs/heads/7.1.x from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=119960d ] QPID-8407: [Broker-J][BDB HA] Clean cached sequences and databases on BDB HA node transition into a Master role (cherry picked from commit 32878798a32c9dc1c762ecb9f870837ff365f350) > [Broker-J][BDB HA] Asynchronous message store recoverer can fail to recover > messages on switching the master node > - > > Key: QPID-8407 > URL: https://issues.apache.org/jira/browse/QPID-8407 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.0.0, qpid-java-broker-7.0.1, > qpid-java-broker-7.1.0, qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, > qpid-java-broker-7.0.6, qpid-java-broker-7.0.7, qpid-java-broker-7.1.1, > qpid-java-broker-7.1.2, qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, > qpid-java-broker-7.1.4, qpid-java-broker-7.1.5, qpid-java-broker-7.1.6, > qpid-java-broker-7.1.7 >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > > With asynchronous message store recovery, when mastership is changed and > flipped back to the previous node, the cached sequence object resumes > sequence id generation from the previous value (before the masteship was > changed). As result, the asynchronous message store recoverer fails to > recover the messages with IDs greater than maximum sequence range value (in > cached sequence object). Such messages are not get recovered from the > message store. On follow-up restart, the messages can be potentially > recovered, if the message id sequence is sufficiently incremented, however, > the issue might result in unordered delivery and generation of duplicate > message IDs. > The synchronous message store recoverer is not effected by the issue. Thus, > switching to synchronous message store recovery (turned on by default) would > allow to work around the problem. -- 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] (QPID-8404) [Broker-J] Use of TLS client certificates in versions > = 7.1.5 broken by Jetty changes
[ https://issues.apache.org/jira/browse/QPID-8404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030837#comment-17030837 ] ASF subversion and git services commented on QPID-8404: --- Commit e8725e904e0ce013f7e50ffb5dd5e95b7520c578 in qpid-broker-j's branch refs/heads/master from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=e8725e9 ] QPID-8404: [Broker-J] Change jetty ssl context factory to SslContextFactory.Server > [Broker-J] Use of TLS client certificates in versions > = 7.1.5 broken by > Jetty changes > --- > > Key: QPID-8404 > URL: https://issues.apache.org/jira/browse/QPID-8404 > Project: Qpid > Issue Type: Bug > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.5, qpid-java-broker-7.1.6, > qpid-java-broker-7.1.7 >Reporter: Robert Godfrey >Assignee: Robert Godfrey >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8 > > Attachments: > 0001-QPID-8404-Fix-usage-of-Jetty-for-TLS-client-certs.patch > > > Changes in Jetty aimed at improving the client side use of TLS using that > library broke implementations using it for server side usage of client certs. > (See also https://github.com/eclipse/jetty.project/issues/3554) -- 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] (QPID-8406) [Broker-J] Display connection transport information in web management console
[
https://issues.apache.org/jira/browse/QPID-8406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030838#comment-17030838
]
ASF subversion and git services commented on QPID-8406:
---
Commit c06b962bb9a3914933fc296564d4df2e4fbeb09f in qpid-broker-j's branch
refs/heads/master from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=c06b962 ]
QPID-8406: [Broker-J][WMC] Display connection transport information in web
management console
> [Broker-J] Display connection transport information in web management console
> -
>
> Key: QPID-8406
> URL: https://issues.apache.org/jira/browse/QPID-8406
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Alex Rudyy
>Priority: Trivial
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.8
>
>
> The information about connection TLS version is provided via {{Connection}}
> attribute {{transportInfo}}. It would be beneficial to display that
> information in Web management Console on connection tab.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1565) SIGSEGV or failed NEW should handle clean disconnect of clients
[ https://issues.apache.org/jira/browse/DISPATCH-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Nigro updated DISPATCH-1565: -- Summary: SIGSEGV or failed NEW should handle clean disconnect of clients (was: SEGV or failed NEW should handle clean disconnect of clients) > SIGSEGV or failed NEW should handle clean disconnect of clients > --- > > Key: DISPATCH-1565 > URL: https://issues.apache.org/jira/browse/DISPATCH-1565 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Francesco Nigro >Priority: Major > > This could be achieved preallocating the necessary default responses and by > registering the proper signal handler with the OS -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1566) safe_snpritf is not safe.
Nicolas created DISPATCH-1566:
-
Summary: safe_snpritf is not safe.
Key: DISPATCH-1566
URL: https://issues.apache.org/jira/browse/DISPATCH-1566
Project: Qpid Dispatch
Issue Type: Bug
Components: Router Node
Reporter: Nicolas
{{/* */}}
{{static inline int safe_snprintf(char *str, size_t size, const char *format,
...)}}
{{{ }}{{}}}
This function fails for size = 0, and ... inside it calls vsnprintf, without
considering that in case of error vsnprintf returns a negative number.
PR in progress.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPID-8367) [Broker-J] Trusted CA revocation list
[ https://issues.apache.org/jira/browse/QPID-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy closed QPID-8367. Resolution: Fixed > [Broker-J] Trusted CA revocation list > - > > Key: QPID-8367 > URL: https://issues.apache.org/jira/browse/QPID-8367 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Tomas Vavricka >Priority: Major > Fix For: qpid-java-broker-8.0.0 > > > Qpid Broker-J supports custom CA. When in place clients then can connect with > certificate signed by custom CA. > However there is no way to reject compromised certificates. Implementation of > revocation list for custom CA can solve this issue. -- 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] (QPID-8367) [Broker-J] Trusted CA revocation list
[ https://issues.apache.org/jira/browse/QPID-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030728#comment-17030728 ] ASF subversion and git services commented on QPID-8367: --- Commit 088b49e30847db044c7b4e4fad3a3fcd431fec7f in qpid-broker-j's branch refs/heads/master from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=088b49e ] QPID-8367: [Broker-J] Fix trust store html template > [Broker-J] Trusted CA revocation list > - > > Key: QPID-8367 > URL: https://issues.apache.org/jira/browse/QPID-8367 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Tomas Vavricka >Priority: Major > Fix For: qpid-java-broker-8.0.0 > > > Qpid Broker-J supports custom CA. When in place clients then can connect with > certificate signed by custom CA. > However there is no way to reject compromised certificates. Implementation of > revocation list for custom CA can solve this issue. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1565) SEGV or failed NEW should handle clean disconnect of clients
Francesco Nigro created DISPATCH-1565: - Summary: SEGV or failed NEW should handle clean disconnect of clients Key: DISPATCH-1565 URL: https://issues.apache.org/jira/browse/DISPATCH-1565 Project: Qpid Dispatch Issue Type: Improvement Reporter: Francesco Nigro This could be achieved preallocating the necessary default responses and by registering the proper signal handler with the OS -- 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] (QPID-8402) [Broker-J][Tests] Use Bouncy Castle API to generate certificate resources on the fly in unit and system tests
[
https://issues.apache.org/jira/browse/QPID-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-8402:
Assignee: Alex Rudyy
> [Broker-J][Tests] Use Bouncy Castle API to generate certificate resources on
> the fly in unit and system tests
> -
>
> Key: QPID-8402
> URL: https://issues.apache.org/jira/browse/QPID-8402
> Project: Qpid
> Issue Type: Task
> Components: Broker-J
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0
>
> Attachments:
> 0001-QPID-8402-Broker-J-Add-bouncycastle-test-dependecies.patch,
> 0002-QPID-8402-Broker-J-Add-generation-of-self-signed-cer.patch
>
>
> Qpid Broker-J unit tests rely on a number of pre-generated kesstores,
> truststores, certificates, etc located either in module test resources folder
> or/and project folder {{./test-profiles/test_resources/ssl}}. Those
> resources need to be regenerated periodically in order to keep them valid and
> up to date. As part of work at QPID-8367, the number of required test
> resources has increased.
> A bash script was created in order to automate the generation, though, it
> seems, that a better approach would be to generate the required resources on
> runtime using Bouncy Castle API.
> It is not exactly clear whether Bouncy Castle API would allow to generate
> all required test resources (including those added in QPID-8367). Though, we
> should switch to using Bouncy Castle API where it is possible, especially,
> for generation of self-signed certificates and test CA authority certificates
> and corresponding keystores/truststores.
--
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] (QPID-8402) [Broker-J][Tests] Use Bouncy Castle API to generate certificate resources on the fly in unit and system tests
[
https://issues.apache.org/jira/browse/QPID-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8402:
-
Status: Reviewable (was: In Progress)
> [Broker-J][Tests] Use Bouncy Castle API to generate certificate resources on
> the fly in unit and system tests
> -
>
> Key: QPID-8402
> URL: https://issues.apache.org/jira/browse/QPID-8402
> Project: Qpid
> Issue Type: Task
> Components: Broker-J
>Reporter: Alex Rudyy
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0
>
> Attachments:
> 0001-QPID-8402-Broker-J-Add-bouncycastle-test-dependecies.patch,
> 0002-QPID-8402-Broker-J-Add-generation-of-self-signed-cer.patch
>
>
> Qpid Broker-J unit tests rely on a number of pre-generated kesstores,
> truststores, certificates, etc located either in module test resources folder
> or/and project folder {{./test-profiles/test_resources/ssl}}. Those
> resources need to be regenerated periodically in order to keep them valid and
> up to date. As part of work at QPID-8367, the number of required test
> resources has increased.
> A bash script was created in order to automate the generation, though, it
> seems, that a better approach would be to generate the required resources on
> runtime using Bouncy Castle API.
> It is not exactly clear whether Bouncy Castle API would allow to generate
> all required test resources (including those added in QPID-8367). Though, we
> should switch to using Bouncy Castle API where it is possible, especially,
> for generation of self-signed certificates and test CA authority certificates
> and corresponding keystores/truststores.
--
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] (QPID-8402) [Broker-J][Tests] Use Bouncy Castle API to generate certificate resources on the fly in unit and system tests
[
https://issues.apache.org/jira/browse/QPID-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030712#comment-17030712
]
ASF subversion and git services commented on QPID-8402:
---
Commit 5801bb8358e6bde61f41fc7268431881f3d5f858 in qpid-broker-j's branch
refs/heads/master from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=5801bb8 ]
QPID-8402: [Broker-J] Fix failing tests on IBM JDK
> [Broker-J][Tests] Use Bouncy Castle API to generate certificate resources on
> the fly in unit and system tests
> -
>
> Key: QPID-8402
> URL: https://issues.apache.org/jira/browse/QPID-8402
> Project: Qpid
> Issue Type: Task
> Components: Broker-J
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0
>
> Attachments:
> 0001-QPID-8402-Broker-J-Add-bouncycastle-test-dependecies.patch,
> 0002-QPID-8402-Broker-J-Add-generation-of-self-signed-cer.patch
>
>
> Qpid Broker-J unit tests rely on a number of pre-generated kesstores,
> truststores, certificates, etc located either in module test resources folder
> or/and project folder {{./test-profiles/test_resources/ssl}}. Those
> resources need to be regenerated periodically in order to keep them valid and
> up to date. As part of work at QPID-8367, the number of required test
> resources has increased.
> A bash script was created in order to automate the generation, though, it
> seems, that a better approach would be to generate the required resources on
> runtime using Bouncy Castle API.
> It is not exactly clear whether Bouncy Castle API would allow to generate
> all required test resources (including those added in QPID-8367). Though, we
> should switch to using Bouncy Castle API where it is possible, especially,
> for generation of self-signed certificates and test CA authority certificates
> and corresponding keystores/truststores.
--
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] (QPID-8367) [Broker-J] Trusted CA revocation list
[ https://issues.apache.org/jira/browse/QPID-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030710#comment-17030710 ] ASF subversion and git services commented on QPID-8367: --- Commit d99a8fc1edb9de74912286866f79bb4cd17003f9 in qpid-broker-j's branch refs/heads/master from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=d99a8fc ] QPID-8367: [Broker-J] Discover CertificateFactory independently from other sun API > [Broker-J] Trusted CA revocation list > - > > Key: QPID-8367 > URL: https://issues.apache.org/jira/browse/QPID-8367 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Tomas Vavricka >Priority: Major > Fix For: qpid-java-broker-8.0.0 > > > Qpid Broker-J supports custom CA. When in place clients then can connect with > certificate signed by custom CA. > However there is no way to reject compromised certificates. Implementation of > revocation list for custom CA can solve this issue. -- 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] (QPID-8402) [Broker-J][Tests] Use Bouncy Castle API to generate certificate resources on the fly in unit and system tests
[
https://issues.apache.org/jira/browse/QPID-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030711#comment-17030711
]
ASF subversion and git services commented on QPID-8402:
---
Commit c413f3156e2339b47da23b4c981cddaf92454e07 in qpid-broker-j's branch
refs/heads/master from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=c413f31 ]
QPID-8402: [Broker-J] Include Bouncycastle license into allowed licenses
> [Broker-J][Tests] Use Bouncy Castle API to generate certificate resources on
> the fly in unit and system tests
> -
>
> Key: QPID-8402
> URL: https://issues.apache.org/jira/browse/QPID-8402
> Project: Qpid
> Issue Type: Task
> Components: Broker-J
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0
>
> Attachments:
> 0001-QPID-8402-Broker-J-Add-bouncycastle-test-dependecies.patch,
> 0002-QPID-8402-Broker-J-Add-generation-of-self-signed-cer.patch
>
>
> Qpid Broker-J unit tests rely on a number of pre-generated kesstores,
> truststores, certificates, etc located either in module test resources folder
> or/and project folder {{./test-profiles/test_resources/ssl}}. Those
> resources need to be regenerated periodically in order to keep them valid and
> up to date. As part of work at QPID-8367, the number of required test
> resources has increased.
> A bash script was created in order to automate the generation, though, it
> seems, that a better approach would be to generate the required resources on
> runtime using Bouncy Castle API.
> It is not exactly clear whether Bouncy Castle API would allow to generate
> all required test resources (including those added in QPID-8367). Though, we
> should switch to using Bouncy Castle API where it is possible, especially,
> for generation of self-signed certificates and test CA authority certificates
> and corresponding keystores/truststores.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1560) Compilation error on Fedora 32 (fedora rawhide)
[
https://issues.apache.org/jira/browse/DISPATCH-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1560:
Description:
{noformat}
[ 79%] Linking C shared library libqpid-dispatch.so
cd /builddir/build/BUILD/qpid-dispatch-1.10.0/src && /usr/bin/cmake -E
cmake_link_script CMakeFiles/qpid-dispatch.dir/link.txt --verbose=1
/usr/bin/cc -fPIC -O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions
-fstack-protector-strong -grecord-gcc-switches
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-Wno-pointer-to-int-cast -Wno-int-to-pointer-cast -Wno-stringop-overflow -O2 -g
-DNDEBUG -Wl,-z,defs -Wl,-z,relro -Wl,--as-needed -Wl,-z,now
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld -shared
-Wl,-soname,libqpid-dispatch.so -o libqpid-dispatch.so
CMakeFiles/qpid-dispatch.dir/alloc_pool.c.o
CMakeFiles/qpid-dispatch.dir/amqp.c.o CMakeFiles/qpid-dispatch.dir/bitmask.c.o
CMakeFiles/qpid-dispatch.dir/buffer.c.o CMakeFiles/qpid-dispatch.dir/error.c.o
CMakeFiles/qpid-dispatch.dir/compose.c.o
CMakeFiles/qpid-dispatch.dir/connection_manager.c.o
CMakeFiles/qpid-dispatch.dir/container.c.o
CMakeFiles/qpid-dispatch.dir/discriminator.c.o
CMakeFiles/qpid-dispatch.dir/dispatch.c.o
CMakeFiles/qpid-dispatch.dir/entity.c.o
CMakeFiles/qpid-dispatch.dir/entity_cache.c.o
CMakeFiles/qpid-dispatch.dir/failoverlist.c.o
CMakeFiles/qpid-dispatch.dir/hash.c.o CMakeFiles/qpid-dispatch.dir/iterator.c.o
CMakeFiles/qpid-dispatch.dir/log.c.o CMakeFiles/qpid-dispatch.dir/message.c.o
CMakeFiles/qpid-dispatch.dir/parse.c.o
CMakeFiles/qpid-dispatch.dir/parse_tree.c.o
CMakeFiles/qpid-dispatch.dir/policy.c.o
CMakeFiles/qpid-dispatch.dir/proton_utils.c.o
CMakeFiles/qpid-dispatch.dir/remote_sasl.c.o
CMakeFiles/qpid-dispatch.dir/posix/threading.c.o
CMakeFiles/qpid-dispatch.dir/python_embedded.c.o
CMakeFiles/qpid-dispatch.dir/router_agent.c.o
CMakeFiles/qpid-dispatch.dir/router_config.c.o
CMakeFiles/qpid-dispatch.dir/address_lookup_utils.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_address.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_config_address.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_config_auto_link.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_connection.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_config_link_route.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_link.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_router.c.o
CMakeFiles/qpid-dispatch.dir/router_core/agent_conn_link_route.c.o
CMakeFiles/qpid-dispatch.dir/router_core/connections.c.o
CMakeFiles/qpid-dispatch.dir/router_core/core_events.c.o
CMakeFiles/qpid-dispatch.dir/router_core/core_link_endpoint.c.o
CMakeFiles/qpid-dispatch.dir/router_core/core_client_api.c.o
CMakeFiles/qpid-dispatch.dir/router_core/delivery.c.o
CMakeFiles/qpid-dispatch.dir/router_core/error.c.o
CMakeFiles/qpid-dispatch.dir/router_core/exchange_bindings.c.o
CMakeFiles/qpid-dispatch.dir/router_core/forwarder.c.o
CMakeFiles/qpid-dispatch.dir/router_core/route_control.c.o
CMakeFiles/qpid-dispatch.dir/router_core/router_core.c.o
CMakeFiles/qpid-dispatch.dir/router_core/router_core_thread.c.o
CMakeFiles/qpid-dispatch.dir/router_core/route_tables.c.o
CMakeFiles/qpid-dispatch.dir/router_core/management_agent.c.o
CMakeFiles/qpid-dispatch.dir/router_core/terminus.c.o
CMakeFiles/qpid-dispatch.dir/router_core/transfer.c.o
CMakeFiles/qpid-dispatch.dir/router_core/core_timer.c.o
CMakeFiles/qpid-dispatch.dir/router_core/modules/edge_router/module.c.o
CMakeFiles/qpid-dispatch.dir/router_core/modules/edge_router/addr_proxy.c.o
CMakeFiles/qpid-dispatch.dir/router_core/modules/edge_router/connection_manager.c.o
CMakeFiles/qpid-dispatch.dir/router_core/modules/edge_router/link_route_proxy.c.o
CMakeFiles/qpid-dispatch.dir/router_core/modules/edge_router/edge_mgmt.c.o
CMakeFiles/qpid-dispatch.dir/router_core/modules/test_hooks/core_test_hooks.c.o
CMakeFiles/qpid-dispatch.dir/router_core/modules/edge_addr_tracking/edge_addr_tracking.c.o
CMakeFiles/qpid-dispatch.dir/router_core/modules/address_lookup_server/address_lookup_server.c.o
CMakeFiles/qpid-dispatch.dir/router_core/modules/address_lookup_client/lookup_client.c.o
CMakeFiles/qpid-dispatch.dir/router_core/modules/stuck_delivery_detection/delivery_tracker.c.o
CMakeFiles/qpid-dispatch.dir/router_node.c.o
CMakeFiles/qpid-dispatch.dir/router_pynode.c.o
CMakeFiles/qpid-dispatch.dir/schema_enum.c.o
CMakeFiles/qpid-dispatch.dir/server.c.o CMakeFiles/qpid-dispatch.dir/timer.c.o
CMakeFiles/qpid-dispatch.dir/trace_mask.c.o
CMakeFiles/qpid-dispatch.dir/python_utils.c.o
CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o -lqpid-proton-core
[jira] [Created] (DISPATCH-1564) Two system tests fail on Fedora 32(fedora:rawhide)
Ganesh Murthy created DISPATCH-1564:
---
Summary: Two system tests fail on Fedora 32(fedora:rawhide)
Key: DISPATCH-1564
URL: https://issues.apache.org/jira/browse/DISPATCH-1564
Project: Qpid Dispatch
Issue Type: Improvement
Components: Tests
Affects Versions: 1.10.0
Reporter: Ganesh Murthy
{noformat}
22: Test command: /usr/bin/python "/main/qpid-dispatch/build/tests/run.py" "-m"
"unittest" "-v" "system_tests_default_distribution"
22: Test timeout computed to be: 600
22: test_anonymous_sender
(system_tests_default_distribution.DefaultDistributionTest) ... ok
22: test_create_unavailable_receiver
(system_tests_default_distribution.DefaultDistributionTest) ... ok
22: test_create_unavailable_sender
(system_tests_default_distribution.DefaultDistributionTest) ... ok
22: test_general (system_tests_default_distribution.DefaultDistributionTest)
... FAIL
22:
22: ==
22: FAIL: test_general
(system_tests_default_distribution.DefaultDistributionTest)
22: --
22: Traceback (most recent call last):
22: File "/main/qpid-dispatch/tests/system_tests_default_distribution.py",
line 83, in test_general
22: self.assertTrue("Connections 1" in out)
22: AssertionError: False is not true
{noformat}
Another test failure
{noformat}
28: Test command: /usr/bin/python "/main/qpid-dispatch/build/tests/run.py" "-m"
"unittest" "-v" "system_tests_qdstat"
28: Test timeout computed to be: 600
28: test_all_entities (system_tests_qdstat.QdstatLinkPriorityTest) ... ok
28: test_all_entities_all_routers (system_tests_qdstat.QdstatLinkPriorityTest)
... ok
28: test_all_entities_all_routers_csv
(system_tests_qdstat.QdstatLinkPriorityTest) ... ok
28: test_all_entities_csv (system_tests_qdstat.QdstatLinkPriorityTest) ... ok
28: test_link_priority (system_tests_qdstat.QdstatLinkPriorityTest) ... ok
28: test_link_priority_csv (system_tests_qdstat.QdstatLinkPriorityTest) ...
ERROR
28: test_links_all_routers (system_tests_qdstat.QdstatLinkPriorityTest) ... ok
28: test_links_all_routers_csv (system_tests_qdstat.QdstatLinkPriorityTest) ...
ok
28: test_ssl_cert_to_auth_fail_no_sasl_external
(system_tests_qdstat.QdstatSslNoExternalTest) ... ok
28: test_ssl_trustfile_cert_to_auth_fail_no_sasl_external
(system_tests_qdstat.QdstatSslNoExternalTest) ... ok
28: test_ssl_bad_trustfile_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_bad_trustfile_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_bad_trustfile_to_unsecured (system_tests_qdstat.QdstatSslTest) ...
ok
28: test_ssl_cert_explicit_external_to_auth (system_tests_qdstat.QdstatSslTest)
... ok
28: test_ssl_cert_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_cert_to_none (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_cert_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_cert_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_none (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_none_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_none_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_none_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_schema_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_schema_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_schema_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_scheme_to_none (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_trustfile_cert_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_trustfile_cert_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_trustfile_cert_to_unsecured (system_tests_qdstat.QdstatSslTest)
... ok
28: test_ssl_trustfile_to_auth (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_trustfile_to_strict (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_trustfile_to_unsecured (system_tests_qdstat.QdstatSslTest) ... ok
28: test_ssl_bad_trustfile_to_auth
(system_tests_qdstat.QdstatSslTestSslPasswordFile) ... ok
28: test_ssl_bad_trustfile_to_strict
(system_tests_qdstat.QdstatSslTestSslPasswordFile) ... ok
28: test_ssl_bad_trustfile_to_unsecured
(system_tests_qdstat.QdstatSslTestSslPasswordFile) ... ok
28: test_ssl_cert_explicit_external_to_auth
(system_tests_qdstat.QdstatSslTestSslPasswordFile) ... ok
28: test_ssl_cert_to_auth (system_tests_qdstat.QdstatSslTestSslPasswordFile)
... ok
28: test_ssl_cert_to_none (system_tests_qdstat.QdstatSslTestSslPasswordFile)
... ok
28: test_ssl_cert_to_strict (system_tests_qdstat.QdstatSslTestSslPasswordFile)
... ok
28: test_ssl_cert_to_unsecured
(system_tests_qdstat.QdstatSslTestSslPasswordFile) ... ok
28: test_ssl_none
[jira] [Commented] (DISPATCH-1560) Compilation error on Fedora 32 (fedora rawhide)
[
https://issues.apache.org/jira/browse/DISPATCH-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030513#comment-17030513
]
ASF GitHub Bot commented on DISPATCH-1560:
--
ganeshmurthy commented on pull request #677: DISPATCH-1560: Fix fedora rawhide
compilation issues
URL: https://github.com/apache/qpid-dispatch/pull/677
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Compilation error on Fedora 32 (fedora rawhide)
> ---
>
> Key: DISPATCH-1560
> URL: https://issues.apache.org/jira/browse/DISPATCH-1560
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
>Affects Versions: 1.10.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
>
> {noformat}
> /usr/bin/ld:
> CMakeFiles/qpid-dispatch.dir/router_node.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
> multiple definition of `qd_amqp_type_t';
> CMakeFiles/qpid-dispatch.dir/amqp.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
> first defined here
> /usr/bin/ld:
> CMakeFiles/qpid-dispatch.dir/router_pynode.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
> multiple definition of `qd_amqp_type_t';
> CMakeFiles/qpid-dispatch.dir/amqp.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
> first defined here
> /usr/bin/ld:
> CMakeFiles/qpid-dispatch.dir/server.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
> multiple definition of `qd_amqp_type_t';
> CMakeFiles/qpid-dispatch.dir/amqp.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
> first defined here
> /usr/bin/ld:
> CMakeFiles/qpid-dispatch.dir/timer.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
> multiple definition of `qd_amqp_type_t';
> CMakeFiles/qpid-dispatch.dir/amqp.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
> first defined here
> /usr/bin/ld:
> CMakeFiles/qpid-dispatch.dir/http-libwebsockets.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
> multiple definition of `qd_amqp_type_t';
> CMakeFiles/qpid-dispatch.dir/amqp.c.o:/builddir/build/BUILD/qpid-dispatch-1.9.0/include/qpid/dispatch/amqp.h:105:
> first defined here {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
[GitHub] [qpid-dispatch] ganeshmurthy opened a new pull request #677: DISPATCH-1560: Fix fedora rawhide compilation issues
ganeshmurthy opened a new pull request #677: DISPATCH-1560: Fix fedora rawhide compilation issues URL: https://github.com/apache/qpid-dispatch/pull/677 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1563) Map logging messages to logging codes
Ganesh Murthy created DISPATCH-1563: --- Summary: Map logging messages to logging codes Key: DISPATCH-1563 URL: https://issues.apache.org/jira/browse/DISPATCH-1563 Project: Qpid Dispatch Issue Type: Improvement Components: Container Affects Versions: 1.10.0 Reporter: Ganesh Murthy Show log code in the log files. Have a properties file which maps log codes to log messages. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1562) Make attribute names provided to Prometheus more router specific
Ganesh Murthy created DISPATCH-1562: --- Summary: Make attribute names provided to Prometheus more router specific Key: DISPATCH-1562 URL: https://issues.apache.org/jira/browse/DISPATCH-1562 Project: Qpid Dispatch Issue Type: Improvement Components: Container Affects Versions: 1.10.0 Reporter: Ganesh Murthy Some of the attribute names used here are too generic - [https://github.com/apache/qpid-dispatch/blob/1.10.0/src/http-libwebsockets.c#L478] Make them more router specific so they can be easily distinguished from other metrics that come from other systems. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1561) Write system test to test writing different log modules to different output files
[ https://issues.apache.org/jira/browse/DISPATCH-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1561: Issue Type: Bug (was: Improvement) > Write system test to test writing different log modules to different output > files > - > > Key: DISPATCH-1561 > URL: https://issues.apache.org/jira/browse/DISPATCH-1561 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.10.0 >Reporter: Ganesh Murthy >Priority: Major > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1561) Write system test to test writing different log modules to different output files
[
https://issues.apache.org/jira/browse/DISPATCH-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030457#comment-17030457
]
Ganesh Murthy commented on DISPATCH-1561:
-
In other words, does the following work -
{noformat}
log {
module: SERVER
enable: trace+
outputFile: /tmp/qdrouterd-server.log
}
log {
module: ROUTER_CORE
enable: trace+
outputFile: /tmp/qdrouterd-router-core.log
}
{noformat}
> Write system test to test writing different log modules to different output
> files
> -
>
> Key: DISPATCH-1561
> URL: https://issues.apache.org/jira/browse/DISPATCH-1561
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Tests
>Affects Versions: 1.10.0
>Reporter: Ganesh Murthy
>Priority: Major
> Fix For: 1.11.0
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1561) Write system test to test writing different log modules to different output files
[ https://issues.apache.org/jira/browse/DISPATCH-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1561: Priority: Blocker (was: Major) > Write system test to test writing different log modules to different output > files > - > > Key: DISPATCH-1561 > URL: https://issues.apache.org/jira/browse/DISPATCH-1561 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.10.0 >Reporter: Ganesh Murthy >Priority: Blocker > Fix For: 1.11.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-dispatch] nicob87 commented on a change in pull request #560: NO-JIRA: add a document explaining the router's threading implementat…
nicob87 commented on a change in pull request #560: NO-JIRA: add a document explaining the router's threading implementat… URL: https://github.com/apache/qpid-dispatch/pull/560#discussion_r375124642 ## File path: docs/notes/threading-info.txt ## @@ -0,0 +1,591 @@ +# +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. +# + + += +Router Threading and Interprocess Communication Guide += + +The Qpid Dispatch Router (qdrouterd) threading architecture is based +on two classes of threads: + + *) A Worker thread which interfaces with the Proton subsystem, and + *) The Core Routing thread which manages the routing database and +performs forwarding. + +In a running router there is a single Core Routing thread (core) and +one or more Worker threads. The number of Worker threads is +determined by the router configuration setting "workerThreads", which +defaults to four. + +IPC between these threads is done using Action queues, Work queues, +and manipulation of shared data. + + +Worker Threads +== + +The Worker thread is responsible for interfacing with the Proton +subsystem. Only a worker thread can safely call directly into the +Proton library. The core thread must communicate with a worker thread +in order to have the worker manipulate Proton state on the core's +behalf. + +The Proton subsystem limits concurrency to a single connection. That +is, only one thread can be processing a given Proton connection (and +all of its child elements, such as links and deliveries) at a time. +The router honors this requirement by restricting access to a given +Proton connection (and its children) to a single worker thread at a +time. To say this another way, a particular Proton connection can be +processed by any worker threads but not concurrently. + +A worker thread is driven by the Proton proactor API. The worker's +main loop blocks on the proactor waiting for events, processes +incoming events, then blocks again. + + +Core Thread +=== + +The one core thread has several responsibilities, including: + + *) Managing the forwarding state + *) Forwarding messages across the router + *) Forwarding disposition and settlement state changes across the router + *) Managing link credit flow + *) Responding to management requests for data owned by the core thread + +The core thread can be thought of as sitting in between the worker +threads, moving messages and state between them. + +When a worker thread needs to forward a received message it passes the +message, its associated delivery state, and incoming link identifier +to the core thread. + +The core thread uses the information supplied by the worker thread to +determine the outgoing link(s) for the message. Once the outgoing +link(s) are identified the core creates the necessary outgoing +delivery state(s) for sending the message out each link. + +The core binds together the incoming and outgoing deliveries (or +incoming and outgoing links in the case of link routing) so state +updates at one endpoint can be efficiently communicated to the peer +endpoint. + +The core then queues the message and outgoing delivery state to the +proper outgoing link(s). The core wakes the worker thread(s) (via the +Proton proactor) so the message(s) can be written out the Proton link. + +When delivery disposition or settlement changes are detected by a +worker thread it notifies the core thread. The core thread then uses +the linkage between incoming and outgoing state to propagate the +change to the peer. This results in the core thread setting the new +state in the peer link/delivery and waking a worker thread to update +the new state in Proton. + +The core also manages credit flow. The core grants credit to inbound +links. The core grants an initial batch of credit to a non-anonymous +link (a link with a target address) when the target address is +available for routing. The core will continue granting credit to the +link as long as the address is routable. The core ties the +replenishment of credit with the settlement of messages arriving on +the link: when the message is settled a single credit is
[jira] [Created] (DISPATCH-1561) Write system test to test writing different log modules to different output files
Ganesh Murthy created DISPATCH-1561: --- Summary: Write system test to test writing different log modules to different output files Key: DISPATCH-1561 URL: https://issues.apache.org/jira/browse/DISPATCH-1561 Project: Qpid Dispatch Issue Type: Improvement Components: Tests Affects Versions: 1.10.0 Reporter: Ganesh Murthy Fix For: 1.11.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-140) [QIT] Build and run failure on Fedora 31
[
https://issues.apache.org/jira/browse/QPIDIT-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17030421#comment-17030421
]
ASF subversion and git services commented on QPIDIT-140:
Commit 0693a8a8d985bbeb9897d19a3e5d4aabe4aa4216 in qpid-interop-test's branch
refs/heads/master from Kim van der Riet
[ https://gitbox.apache.org/repos/asf?p=qpid-interop-test.git;h=0693a8a ]
QPIDIT-140: Fix for python pointing to Python 3.x in Fedora 31. Changed all
references to python to python2.
> [QIT] Build and run failure on Fedora 31
>
>
> Key: QPIDIT-140
> URL: https://issues.apache.org/jira/browse/QPIDIT-140
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: Installation
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> Fedora 31 has changed the default {{python}} link to point to python 3.x
> rather than python 2.x which the previous versions of Fedroa had used. This
> has caused both the build, install and running of the Python 2 shims to fail.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDIT-140) [QIT] Build and run failure on Fedora 31
[
https://issues.apache.org/jira/browse/QPIDIT-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPIDIT-140.
-
Resolution: Fixed
> [QIT] Build and run failure on Fedora 31
>
>
> Key: QPIDIT-140
> URL: https://issues.apache.org/jira/browse/QPIDIT-140
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: Installation
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
>
> Fedora 31 has changed the default {{python}} link to point to python 3.x
> rather than python 2.x which the previous versions of Fedroa had used. This
> has caused both the build, install and running of the Python 2 shims to fail.
--
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
