[GitHub] qpid-dispatch pull request #343: DISPATCH-1067 - updates to policy doc (upda...
Github user fgiorgetti commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/343#discussion_r202810977
--- Diff: docs/books/user-guide/configuration-security.adoc ---
@@ -442,290 +442,367 @@ For more information about these attributes, see
xref:adding-sasl-authentication
== Authorizing Access to Messaging Resources
-You can restrict the number of user connections, and control access to
AMQP messaging resources by configuring _policies_.
+You can configure _policies_ to secure messaging resources in your
messaging environment. Policies ensure that only authorized users can access
messaging endpoints through the router network, and that the resources on those
endpoints are used in an authorized way.
-=== Types of Policies
-
-You can configure two different types of policies: _global policies_ and
_vhost policies_.
+{RouterName} provides the following types of policies:
Global policies::
-Settings for the router. A global policy defines the maximum number of
incoming user connections for the router (across all vhost policies), and
defines how the router should use vhost policies.
+Settings for the router. A global policy defines the maximum number of
incoming user connections for the router (across all messaging endpoints), and
defines how the router should use vhost policies.
Vhost policies::
-Connection and AMQP resource limits for a messaging endpoint (called an
AMQP virtual host, or _vhost_). A vhost policy defines what a client can access
on a messaging endpoint over a particular connection.
-+
-[NOTE]
-
-A vhost is typically the name of the host to which the client connection
is directed. For example, if a client application opens a connection to the
`amqp://mybroker.example.com:5672/queue01` URL, the vhost would be
`mybroker.example.com`.
-
+Connection and AMQP resource limits for a messaging endpoint (called an
AMQP virtual host, or vhost). A vhost policy defines what a client can access
on a messaging endpoint over a particular connection.
The resource limits defined in global and vhost policies are applied to
user connections only. The limits do not affect inter-router connections or
router connections that are outbound to waypoints.
-=== How {RouterName} Applies Policies
+=== How {RouterName} Enforces Connection and Resource Limits
-{RouterName} uses both global and vhost policies to determine whether to
permit a connection, and if it is permitted, to apply the appropriate resource
limits.
+{RouterName} uses policies to determine whether to permit a connection,
and if it is permitted, to apply the appropriate resource limits.
When a client creates a connection to the router, the router first
determines whether to allow or deny the connection. This decision is based on
the following criteria:
-* Whether the connection will exceed the router's global connection limit
(defined in the global policy)
-* Whether the connection will exceed the vhost's connection limits
(defined in the vhost policy that matches the host to which the connection is
directed)
+* Whether the connection will exceed the routerâs global connection
limit (defined in the global policy)
-If the connection is allowed, the router assigns the user (the
authenticated user name from the connection) to a user group, and enforces the
user group's resource limits for the lifetime of the connection.
+* Whether the connection will exceed the vhostâs connection limits
(defined in the vhost policy that matches the host to which the connection is
directed)
-=== Configuring Global Policies
+If the connection is allowed, the router assigns the user (the
authenticated user name from the connection) to a user group, and enforces the
user groupâs resource limits for the lifetime of the connection.
-You can set the incoming connection limit for the router and define how it
should use vhost policies by configuring a global policy.
+=== Setting Global Connection Limits
+
+You can set the incoming connection limit for the router. This limit
defines the total number of concurrent client connections that can be open for
this router.
.Procedure
-* In the router configuration file, add a `policy` section.
+* In the router configuration file, add a `policy` section and set the
`maxConnections`.
+
--
[options="nowrap",subs="+quotes"]
-policy = {
-maxConnections: 1 // <1>
-enableVhostPolicy: true // <2>
-policyDir: /etc/qpid-dispatch/policies/ // <3>
-defaultVhost: $default // <4>
+policy {
+maxConnections: 1
}
-<1> The maximum number of concurrent client connections allowed for this
router. This limit is always
[jira] [Commented] (DISPATCH-1067) Doc improvements for router policies
[
https://issues.apache.org/jira/browse/DISPATCH-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545775#comment-16545775
]
ASF GitHub Bot commented on DISPATCH-1067:
--
Github user fgiorgetti commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/343#discussion_r202826844
--- Diff: docs/books/user-guide/configuration-security.adoc ---
@@ -734,57 +811,57 @@ vhost {
<3> Any user can connect to this vhost. Users that are not part of the
`admin` group are assigned to the `$default` group.
-<4> If the `admin-01` or `admin-02` user connects to the vhost, they are
assigned to the `admin` user group.
+<4> If the `admin1` or `admin2` user connects to the vhost, they are
assigned to the `admin` user group.
<5> Users in the `admin` user group must connect from localhost. If the
admin user attempts to connect from any other host, the connection will be
denied.
-<6> Users in the admin user group can send and receive from any address
offered by the vhost.
+<6> Users in the admin user group can send to any address offered by the
vhost.
-<7> Any non-admin user is permitted to connect from any host.
+<7> Users in the admin user group can receive from any address offered by
the vhost.
--- End diff --
s/receive from/send to
> Doc improvements for router policies
>
>
> Key: DISPATCH-1067
> URL: https://issues.apache.org/jira/browse/DISPATCH-1067
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Documentation
>Affects Versions: 1.2.0
>Reporter: Ben Hardesty
>Assignee: Ben Hardesty
>Priority: Major
>
> The router policy doc needs to be updated to cover the following enhancements:
> * Patterns for policy hostnames (DISPATCH-990)
> * New policy config attributes (DISPATCH-976)
> * Policy username substitution improvements (DISPATCH-1011)
> * Allow vhost policies to be configured in the router configuration file
> (DISPATCH-1013)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1067) Doc improvements for router policies
[
https://issues.apache.org/jira/browse/DISPATCH-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545776#comment-16545776
]
ASF GitHub Bot commented on DISPATCH-1067:
--
Github user fgiorgetti commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/343#discussion_r202826788
--- Diff: docs/books/user-guide/configuration-security.adoc ---
@@ -734,57 +811,57 @@ vhost {
<3> Any user can connect to this vhost. Users that are not part of the
`admin` group are assigned to the `$default` group.
-<4> If the `admin-01` or `admin-02` user connects to the vhost, they are
assigned to the `admin` user group.
+<4> If the `admin1` or `admin2` user connects to the vhost, they are
assigned to the `admin` user group.
<5> Users in the `admin` user group must connect from localhost. If the
admin user attempts to connect from any other host, the connection will be
denied.
-<6> Users in the admin user group can send and receive from any address
offered by the vhost.
+<6> Users in the admin user group can send to any address offered by the
vhost.
--- End diff --
s/send to/receive from
> Doc improvements for router policies
>
>
> Key: DISPATCH-1067
> URL: https://issues.apache.org/jira/browse/DISPATCH-1067
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Documentation
>Affects Versions: 1.2.0
>Reporter: Ben Hardesty
>Assignee: Ben Hardesty
>Priority: Major
>
> The router policy doc needs to be updated to cover the following enhancements:
> * Patterns for policy hostnames (DISPATCH-990)
> * New policy config attributes (DISPATCH-976)
> * Policy username substitution improvements (DISPATCH-1011)
> * Allow vhost policies to be configured in the router configuration file
> (DISPATCH-1013)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1067) Doc improvements for router policies
[
https://issues.apache.org/jira/browse/DISPATCH-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545777#comment-16545777
]
ASF GitHub Bot commented on DISPATCH-1067:
--
Github user fgiorgetti commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/343#discussion_r202810977
--- Diff: docs/books/user-guide/configuration-security.adoc ---
@@ -442,290 +442,367 @@ For more information about these attributes, see
xref:adding-sasl-authentication
== Authorizing Access to Messaging Resources
-You can restrict the number of user connections, and control access to
AMQP messaging resources by configuring _policies_.
+You can configure _policies_ to secure messaging resources in your
messaging environment. Policies ensure that only authorized users can access
messaging endpoints through the router network, and that the resources on those
endpoints are used in an authorized way.
-=== Types of Policies
-
-You can configure two different types of policies: _global policies_ and
_vhost policies_.
+{RouterName} provides the following types of policies:
Global policies::
-Settings for the router. A global policy defines the maximum number of
incoming user connections for the router (across all vhost policies), and
defines how the router should use vhost policies.
+Settings for the router. A global policy defines the maximum number of
incoming user connections for the router (across all messaging endpoints), and
defines how the router should use vhost policies.
Vhost policies::
-Connection and AMQP resource limits for a messaging endpoint (called an
AMQP virtual host, or _vhost_). A vhost policy defines what a client can access
on a messaging endpoint over a particular connection.
-+
-[NOTE]
-
-A vhost is typically the name of the host to which the client connection
is directed. For example, if a client application opens a connection to the
`amqp://mybroker.example.com:5672/queue01` URL, the vhost would be
`mybroker.example.com`.
-
+Connection and AMQP resource limits for a messaging endpoint (called an
AMQP virtual host, or vhost). A vhost policy defines what a client can access
on a messaging endpoint over a particular connection.
The resource limits defined in global and vhost policies are applied to
user connections only. The limits do not affect inter-router connections or
router connections that are outbound to waypoints.
-=== How {RouterName} Applies Policies
+=== How {RouterName} Enforces Connection and Resource Limits
-{RouterName} uses both global and vhost policies to determine whether to
permit a connection, and if it is permitted, to apply the appropriate resource
limits.
+{RouterName} uses policies to determine whether to permit a connection,
and if it is permitted, to apply the appropriate resource limits.
When a client creates a connection to the router, the router first
determines whether to allow or deny the connection. This decision is based on
the following criteria:
-* Whether the connection will exceed the router's global connection limit
(defined in the global policy)
-* Whether the connection will exceed the vhost's connection limits
(defined in the vhost policy that matches the host to which the connection is
directed)
+* Whether the connection will exceed the router’s global connection limit
(defined in the global policy)
-If the connection is allowed, the router assigns the user (the
authenticated user name from the connection) to a user group, and enforces the
user group's resource limits for the lifetime of the connection.
+* Whether the connection will exceed the vhost’s connection limits
(defined in the vhost policy that matches the host to which the connection is
directed)
-=== Configuring Global Policies
+If the connection is allowed, the router assigns the user (the
authenticated user name from the connection) to a user group, and enforces the
user group’s resource limits for the lifetime of the connection.
-You can set the incoming connection limit for the router and define how it
should use vhost policies by configuring a global policy.
+=== Setting Global Connection Limits
+
+You can set the incoming connection limit for the router. This limit
defines the total number of concurrent client connections that can be open for
this router.
.Procedure
-* In the router configuration file, add a `policy` section.
+* In the router configuration file, add a `policy` section and set the
`maxConnections`.
+
--
[options="nowrap",subs="+quotes"]
-policy = {
-maxConnections: 1 // <1>
-enableVhostPolicy: true // <2>
-policyDir:
[GitHub] qpid-dispatch pull request #343: DISPATCH-1067 - updates to policy doc (upda...
Github user fgiorgetti commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/343#discussion_r202826844
--- Diff: docs/books/user-guide/configuration-security.adoc ---
@@ -734,57 +811,57 @@ vhost {
<3> Any user can connect to this vhost. Users that are not part of the
`admin` group are assigned to the `$default` group.
-<4> If the `admin-01` or `admin-02` user connects to the vhost, they are
assigned to the `admin` user group.
+<4> If the `admin1` or `admin2` user connects to the vhost, they are
assigned to the `admin` user group.
<5> Users in the `admin` user group must connect from localhost. If the
admin user attempts to connect from any other host, the connection will be
denied.
-<6> Users in the admin user group can send and receive from any address
offered by the vhost.
+<6> Users in the admin user group can send to any address offered by the
vhost.
-<7> Any non-admin user is permitted to connect from any host.
+<7> Users in the admin user group can receive from any address offered by
the vhost.
--- End diff --
s/receive from/send to
---
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #343: DISPATCH-1067 - updates to policy doc (upda...
Github user fgiorgetti commented on a diff in the pull request:
https://github.com/apache/qpid-dispatch/pull/343#discussion_r202826788
--- Diff: docs/books/user-guide/configuration-security.adoc ---
@@ -734,57 +811,57 @@ vhost {
<3> Any user can connect to this vhost. Users that are not part of the
`admin` group are assigned to the `$default` group.
-<4> If the `admin-01` or `admin-02` user connects to the vhost, they are
assigned to the `admin` user group.
+<4> If the `admin1` or `admin2` user connects to the vhost, they are
assigned to the `admin` user group.
<5> Users in the `admin` user group must connect from localhost. If the
admin user attempts to connect from any other host, the connection will be
denied.
-<6> Users in the admin user group can send and receive from any address
offered by the vhost.
+<6> Users in the admin user group can send to any address offered by the
vhost.
--- End diff --
s/send to/receive from
---
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1064) Doc link route reconnect behavior
[ https://issues.apache.org/jira/browse/DISPATCH-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545726#comment-16545726 ] ASF GitHub Bot commented on DISPATCH-1064: -- Github user jenmalloy commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/339#discussion_r202823498 --- Diff: docs/books/user-guide/routing.adoc --- @@ -551,6 +556,13 @@ Link routes establish a link between a sender and a receiver that travels throug With link routing, client traffic is handled on the broker, not the router. Clients have a direct link through the router to a broker's queue. Therefore, each client is a separate producer or consumer. +[NOTE] + +If the connection to the broker fails, the routed links are detached, and the router will attempt to reconnect to the broker (or its backup). Once the connection is reestablished, the link route to the broker will become reachable again. + +From the client's perspective, the client will see the detached links (that is, the senders or receivers), but not the failed connection. Therefore, if you want the client to reattach dropped links in the event of a broker connection failure, you must configure this functionality on the client. Alternatively, you can use message routing with autolinks instead of link routing. For more information, see xref:routing-messages-through-broker[Routing Messages through a Broker Queue] --- End diff -- Missing final period > Doc link route reconnect behavior > - > > Key: DISPATCH-1064 > URL: https://issues.apache.org/jira/browse/DISPATCH-1064 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.2.0 >Reporter: Ben Hardesty >Assignee: Ben Hardesty >Priority: Major > > When the router is configured with a linkRoute and client connects using > failover, the link will not be reestablished should the router's connection > to the broker fail. If auto-reconnect is required, the router should be > configured with autoLink. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #339: DISPATCH-1064 - Doc link route reconnect be...
Github user jenmalloy commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/339#discussion_r202823498 --- Diff: docs/books/user-guide/routing.adoc --- @@ -551,6 +556,13 @@ Link routes establish a link between a sender and a receiver that travels throug With link routing, client traffic is handled on the broker, not the router. Clients have a direct link through the router to a broker's queue. Therefore, each client is a separate producer or consumer. +[NOTE] + +If the connection to the broker fails, the routed links are detached, and the router will attempt to reconnect to the broker (or its backup). Once the connection is reestablished, the link route to the broker will become reachable again. + +From the client's perspective, the client will see the detached links (that is, the senders or receivers), but not the failed connection. Therefore, if you want the client to reattach dropped links in the event of a broker connection failure, you must configure this functionality on the client. Alternatively, you can use message routing with autolinks instead of link routing. For more information, see xref:routing-messages-through-broker[Routing Messages through a Broker Queue] --- End diff -- Missing final period --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1064) Doc link route reconnect behavior
[ https://issues.apache.org/jira/browse/DISPATCH-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545718#comment-16545718 ] ASF GitHub Bot commented on DISPATCH-1064: -- Github user bhardesty commented on the issue: https://github.com/apache/qpid-dispatch/pull/339 Thanks @ted-ross - I made some updates based on your review. > Doc link route reconnect behavior > - > > Key: DISPATCH-1064 > URL: https://issues.apache.org/jira/browse/DISPATCH-1064 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.2.0 >Reporter: Ben Hardesty >Assignee: Ben Hardesty >Priority: Major > > When the router is configured with a linkRoute and client connects using > failover, the link will not be reestablished should the router's connection > to the broker fail. If auto-reconnect is required, the router should be > configured with autoLink. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch issue #339: DISPATCH-1064 - Doc link route reconnect behavior
Github user bhardesty commented on the issue: https://github.com/apache/qpid-dispatch/pull/339 Thanks @ted-ross - I made some updates based on your review. --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1890) [c++] implement idle_timeout and heartbeats
[ https://issues.apache.org/jira/browse/PROTON-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545633#comment-16545633 ] Praveen Bodke commented on PROTON-1890: --- Thanks for the update Alan. I have tested the same reproducer in 0.24 version and i see that the issue is fixed. >From the Frame logs its visible that after the close frame is sent, the proton >immediately sending the EOS frame to close the socket. Following are the frame log snippets. [0x98780f0]:0 -> (EMPTY FRAME) push-while-in push-while-in [0x98780f0]:0 -> (EMPTY FRAME) push-while-in push-while-in push-while-in [0x98780f0]:0 -> (EMPTY FRAME) push-while-in push-while-in [0x98780f0]:0 -> (EMPTY FRAME) push-while-in push-while-in push-while-in [0x98780f0]:0 -> @close(24) [error=@error(29) [condition=:"amqp:resource-limit-exceeded", description="local-idle-timeout expired"]] [0x98780f0]: -> EOS amqp:resource-limit-exceeded: local-idle-timeout expired Is there a way to enable proton logs from the CPP code instead of using the PN_TRACE_FRM environment variable. My application is running under daemon and will not have the console to display the logs. > [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: 0.16.0 >Reporter: Praveen Bodke >Assignee: Alan Conway >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 (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1067) Doc improvements for router policies
[ https://issues.apache.org/jira/browse/DISPATCH-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545597#comment-16545597 ] ASF GitHub Bot commented on DISPATCH-1067: -- GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/343 DISPATCH-1067 - updates to policy doc (updated) You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch dispatch-1067-policy-doc-updates Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/343.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #343 commit 24e0df30ab71179a41d4f4d75379f5992df5a3cb Author: Ben Hardesty Date: 2018-07-10T20:18:14Z Update JSON map examples in the policy doc commit aa0b7643ef3468aa61407527113c0a2c34c7f8d2 Author: Ben Hardesty Date: 2018-07-10T21:29:29Z Add doc for configuring vhost policies in router config file commit b28eace9332488d194c12490b06ddafbdc43db4d Author: Ben Hardesty Date: 2018-07-12T18:05:57Z Reorganize policy doc commit 7afce1adc020251c5a3be8bbe20416fbe4a2a5ce Author: Ben Hardesty Date: 2018-07-12T20:20:46Z Add section on vhost hostname policy pattern matching for dispatch-990 commit 73873ed6d6f332124763b400bfb35a580b79180d Author: Ben Hardesty Date: 2018-07-13T16:58:09Z Update policy doc for dispatch-976 commit 20de09b8f17f30ca3510fea31d73571d3c5061a5 Author: Ben Hardesty Date: 2018-07-13T18:56:59Z Update user-specific address patterns for dispatch-1011 commit c51513df20fe1fc6194b7f37fa27c8bf7a779464 Author: Ben Hardesty Date: 2018-07-16T18:15:42Z Updates from sme review > Doc improvements for router policies > > > Key: DISPATCH-1067 > URL: https://issues.apache.org/jira/browse/DISPATCH-1067 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.2.0 >Reporter: Ben Hardesty >Assignee: Ben Hardesty >Priority: Major > > The router policy doc needs to be updated to cover the following enhancements: > * Patterns for policy hostnames (DISPATCH-990) > * New policy config attributes (DISPATCH-976) > * Policy username substitution improvements (DISPATCH-1011) > * Allow vhost policies to be configured in the router configuration file > (DISPATCH-1013) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1067) Doc improvements for router policies
[ https://issues.apache.org/jira/browse/DISPATCH-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545596#comment-16545596 ] ASF GitHub Bot commented on DISPATCH-1067: -- Github user bhardesty closed the pull request at: https://github.com/apache/qpid-dispatch/pull/342 > Doc improvements for router policies > > > Key: DISPATCH-1067 > URL: https://issues.apache.org/jira/browse/DISPATCH-1067 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.2.0 >Reporter: Ben Hardesty >Assignee: Ben Hardesty >Priority: Major > > The router policy doc needs to be updated to cover the following enhancements: > * Patterns for policy hostnames (DISPATCH-990) > * New policy config attributes (DISPATCH-976) > * Policy username substitution improvements (DISPATCH-1011) > * Allow vhost policies to be configured in the router configuration file > (DISPATCH-1013) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #343: DISPATCH-1067 - updates to policy doc (upda...
GitHub user bhardesty opened a pull request: https://github.com/apache/qpid-dispatch/pull/343 DISPATCH-1067 - updates to policy doc (updated) You can merge this pull request into a Git repository by running: $ git pull https://github.com/bhardesty/qpid-dispatch dispatch-1067-policy-doc-updates Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/343.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #343 commit 24e0df30ab71179a41d4f4d75379f5992df5a3cb Author: Ben Hardesty Date: 2018-07-10T20:18:14Z Update JSON map examples in the policy doc commit aa0b7643ef3468aa61407527113c0a2c34c7f8d2 Author: Ben Hardesty Date: 2018-07-10T21:29:29Z Add doc for configuring vhost policies in router config file commit b28eace9332488d194c12490b06ddafbdc43db4d Author: Ben Hardesty Date: 2018-07-12T18:05:57Z Reorganize policy doc commit 7afce1adc020251c5a3be8bbe20416fbe4a2a5ce Author: Ben Hardesty Date: 2018-07-12T20:20:46Z Add section on vhost hostname policy pattern matching for dispatch-990 commit 73873ed6d6f332124763b400bfb35a580b79180d Author: Ben Hardesty Date: 2018-07-13T16:58:09Z Update policy doc for dispatch-976 commit 20de09b8f17f30ca3510fea31d73571d3c5061a5 Author: Ben Hardesty Date: 2018-07-13T18:56:59Z Update user-specific address patterns for dispatch-1011 commit c51513df20fe1fc6194b7f37fa27c8bf7a779464 Author: Ben Hardesty Date: 2018-07-16T18:15:42Z Updates from sme review --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch pull request #342: DISPATCH-1067 - Improvements and updates to...
Github user bhardesty closed the pull request at: https://github.com/apache/qpid-dispatch/pull/342 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPIDIT-128) misuse of JAVA_HOME causes tests to error without clear indication why
[
https://issues.apache.org/jira/browse/QPIDIT-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPIDIT-128.
-
Resolution: Fixed
I have made the changes in this Jira so that JAVA_HOME defaults to /usr on
Linux systems, and hence the java executable can be found at ${JAVA_HOME}/bin.
However, this does not change the error message that is seen in the event the
jar file containing the shims is not found. I have added an error message to
the test itself that will print if the jar is not found.
> misuse of JAVA_HOME causes tests to error without clear indication why
> --
>
> Key: QPIDIT-128
> URL: https://issues.apache.org/jira/browse/QPIDIT-128
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: Qpid Jms Shim
>Affects Versions: 0.1.0, 0.2.0
>Reporter: Robbie Gemmell
>Assignee: Kim van der Riet
>Priority: Critical
> Fix For: 0.2.0
>
>
> The interop suite misuses JAVA_HOME, and in doing so Python tries to run java
> from the wrong place. This results in the tests erroring out with note of a
> file not found, but with no indication what file wasn't found. Resorting to
> some prints for debugging, it emerges that Python is being asked to run Java
> with the wrong location
> JAVA_HOME points to the root of the java installation, with the java command
> and various others then found in the bin subdir. The interop tests currently
> omit the bin subdir when JAVA_HOME was actually defined, but do include it
> (via a fragile and debatable hard coded default) when JAVA_HOME is not
> defined:
> {noformat}
> JAVA_HOME = os.getenv('JAVA_HOME', '/usr/bin') # Default only works in Linux
> JAVA_EXEC = os.path.join(JAVA_HOME, 'java')
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-128) misuse of JAVA_HOME causes tests to error without clear indication why
[
https://issues.apache.org/jira/browse/QPIDIT-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545321#comment-16545321
]
ASF subversion and git services commented on QPIDIT-128:
Commit 774f2564d084ed018f452ca60c4d7f612f0baa33 in qpid-interop-test's branch
refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=774f256 ]
QPIDIT-128: Changed construction of JAVA_HOME to be compliant with Java norms,
also added warning when shim jar file is not found at start of JMS tests.
> misuse of JAVA_HOME causes tests to error without clear indication why
> --
>
> Key: QPIDIT-128
> URL: https://issues.apache.org/jira/browse/QPIDIT-128
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: Qpid Jms Shim
>Affects Versions: 0.1.0, 0.2.0
>Reporter: Robbie Gemmell
>Assignee: Kim van der Riet
>Priority: Critical
> Fix For: 0.2.0
>
>
> The interop suite misuses JAVA_HOME, and in doing so Python tries to run java
> from the wrong place. This results in the tests erroring out with note of a
> file not found, but with no indication what file wasn't found. Resorting to
> some prints for debugging, it emerges that Python is being asked to run Java
> with the wrong location
> JAVA_HOME points to the root of the java installation, with the java command
> and various others then found in the bin subdir. The interop tests currently
> omit the bin subdir when JAVA_HOME was actually defined, but do include it
> (via a fragile and debatable hard coded default) when JAVA_HOME is not
> defined:
> {noformat}
> JAVA_HOME = os.getenv('JAVA_HOME', '/usr/bin') # Default only works in Linux
> JAVA_EXEC = os.path.join(JAVA_HOME, 'java')
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-125) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/QPIDIT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545322#comment-16545322 ] ASF subversion and git services commented on QPIDIT-125: Commit 50076724ab96214148c4dbc89d4290583ccb6949 in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=5007672 ] QPIDIT-125: Minor addition to QUICKSTART.md file > Release QIT 0.2.0 > - > > Key: QPIDIT-125 > URL: https://issues.apache.org/jira/browse/QPIDIT-125 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Update docs, create branches, tags, etc. for the release of Qpid Interop Test > v. 0.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-133) [complex_types_test]: Remove float types inf, +inf, -inf because of RHEL7 Proton bug
[ https://issues.apache.org/jira/browse/QPIDIT-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545320#comment-16545320 ] ASF subversion and git services commented on QPIDIT-133: Commit 0c128063ec46ffc7e64244f4487cdfa64ae15656 in qpid-interop-test's branch refs/heads/master from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=0c12806 ] QPIDIT-133: Removed float test values 'inf', '-inf' from amqp-complex-types-test becasue of Proton bug > [complex_types_test]: Remove float types inf, +inf, -inf because of RHEL7 > Proton bug > > > Key: QPIDIT-133 > URL: https://issues.apache.org/jira/browse/QPIDIT-133 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > A bug in RHEL7 / CentOS7 Proton causes an overflow error when using float > literals '+inf' or '-inf'. The error does not occur in double values, nor for > literal 'NaN'. See PROTON-1149 and PROTON-1838. > The amqp_complex_types_test uses JSON files to represent the values of the > test. However, these files do not allow for comments, so it is not possible > to comment out parts of the data. Data is either present or not. > In order to prevent this failure from causing the test to fail, remove the > test values 'inf', '+inf' and '-inf' from the test data until this bug is > fixed in Proton. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-125) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/QPIDIT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545305#comment-16545305 ] ASF subversion and git services commented on QPIDIT-125: Commit b4c42f2fe3b0cca66735de05bb33537ad179e411 in qpid-interop-test's branch refs/heads/0.2.0 from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=b4c42f2 ] QPIDIT-125: Minor addition to QUICKSTART.md file > Release QIT 0.2.0 > - > > Key: QPIDIT-125 > URL: https://issues.apache.org/jira/browse/QPIDIT-125 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Update docs, create branches, tags, etc. for the release of Qpid Interop Test > v. 0.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-128) misuse of JAVA_HOME causes tests to error without clear indication why
[
https://issues.apache.org/jira/browse/QPIDIT-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545302#comment-16545302
]
ASF subversion and git services commented on QPIDIT-128:
Commit 4117ea5073a956f67840b2858530cbe4f90c4f94 in qpid-interop-test's branch
refs/heads/0.2.0 from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=4117ea5 ]
QPIDIT-128: Changed construction of JAVA_HOME to be compliant with Java norms,
also added warning when shim jar file is not found at start of JMS tests.
> misuse of JAVA_HOME causes tests to error without clear indication why
> --
>
> Key: QPIDIT-128
> URL: https://issues.apache.org/jira/browse/QPIDIT-128
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: Qpid Jms Shim
>Affects Versions: 0.1.0, 0.2.0
>Reporter: Robbie Gemmell
>Assignee: Kim van der Riet
>Priority: Critical
> Fix For: 0.2.0
>
>
> The interop suite misuses JAVA_HOME, and in doing so Python tries to run java
> from the wrong place. This results in the tests erroring out with note of a
> file not found, but with no indication what file wasn't found. Resorting to
> some prints for debugging, it emerges that Python is being asked to run Java
> with the wrong location
> JAVA_HOME points to the root of the java installation, with the java command
> and various others then found in the bin subdir. The interop tests currently
> omit the bin subdir when JAVA_HOME was actually defined, but do include it
> (via a fragile and debatable hard coded default) when JAVA_HOME is not
> defined:
> {noformat}
> JAVA_HOME = os.getenv('JAVA_HOME', '/usr/bin') # Default only works in Linux
> JAVA_EXEC = os.path.join(JAVA_HOME, 'java')
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-134) Reinstate float values 'inf' and '-inf' to amqp_types_test and amqp_complex_types_test when Proton bug fixed
[ https://issues.apache.org/jira/browse/QPIDIT-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-134: Affects Version/s: 0.1.0 > Reinstate float values 'inf' and '-inf' to amqp_types_test and > amqp_complex_types_test when Proton bug fixed > > > Key: QPIDIT-134 > URL: https://issues.apache.org/jira/browse/QPIDIT-134 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Affects Versions: 0.1.0 >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > See PROTON-1149 and PROTON-1838: When these bugs are fixed, replace the float > values 'inf' and '-inf' into the test data for amqp_types_test and > amqp_complex_types_test. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDIT-134) Reinstate float values 'inf' and '-inf' to amqp_types_test and amqp_complex_types_test when Proton bug fixed
Kim van der Riet created QPIDIT-134: --- Summary: Reinstate float values 'inf' and '-inf' to amqp_types_test and amqp_complex_types_test when Proton bug fixed Key: QPIDIT-134 URL: https://issues.apache.org/jira/browse/QPIDIT-134 Project: Apache QPID Interoperability Test Suite Issue Type: Task Reporter: Kim van der Riet See PROTON-1149 and PROTON-1838: When these bugs are fixed, replace the float values 'inf' and '-inf' into the test data for amqp_types_test and amqp_complex_types_test. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPIDIT-134) Reinstate float values 'inf' and '-inf' to amqp_types_test and amqp_complex_types_test when Proton bug fixed
[ https://issues.apache.org/jira/browse/QPIDIT-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPIDIT-134: --- Assignee: Kim van der Riet > Reinstate float values 'inf' and '-inf' to amqp_types_test and > amqp_complex_types_test when Proton bug fixed > > > Key: QPIDIT-134 > URL: https://issues.apache.org/jira/browse/QPIDIT-134 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > See PROTON-1149 and PROTON-1838: When these bugs are fixed, replace the float > values 'inf' and '-inf' into the test data for amqp_types_test and > amqp_complex_types_test. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-133) [complex_types_test]: Remove float types inf, +inf, -inf because of RHEL7 Proton bug
[ https://issues.apache.org/jira/browse/QPIDIT-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-133: Description: A bug in RHEL7 / CentOS7 Proton causes an overflow error when using float literals '+inf' or '-inf'. The error does not occur in double values, nor for literal 'NaN'. See PROTON-1149 and PROTON-1838. The amqp_complex_types_test uses JSON files to represent the values of the test. However, these files do not allow for comments, so it is not possible to comment out parts of the data. Data is either present or not. In order to prevent this failure from causing the test to fail, remove the test values 'inf', '+inf' and '-inf' from the test data until this bug is fixed in Proton. was: A bug in RHEL7 / CentOS7 Proton causes an overflow error when using float literals '+inf' or '-inf'. The error does not occur in double values, nor for literal 'NaN'. See PROTON-1149. The amqp_complex_types_test uses JSON files to represent the values of the test. However, these files do not allow for comments, so it is not possible to comment out parts of the data. Data is either present or not. In order to prevent this failure from causing the test to fail, remove the test values 'inf', '+inf' and '-inf' from the test data until this bug is fixed in Proton. > [complex_types_test]: Remove float types inf, +inf, -inf because of RHEL7 > Proton bug > > > Key: QPIDIT-133 > URL: https://issues.apache.org/jira/browse/QPIDIT-133 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > A bug in RHEL7 / CentOS7 Proton causes an overflow error when using float > literals '+inf' or '-inf'. The error does not occur in double values, nor for > literal 'NaN'. See PROTON-1149 and PROTON-1838. > The amqp_complex_types_test uses JSON files to represent the values of the > test. However, these files do not allow for comments, so it is not possible > to comment out parts of the data. Data is either present or not. > In order to prevent this failure from causing the test to fail, remove the > test values 'inf', '+inf' and '-inf' from the test data until this bug is > fixed in Proton. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-133) [complex_types_test]: Remove float types inf, +inf, -inf because of RHEL7 Proton bug
[ https://issues.apache.org/jira/browse/QPIDIT-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545248#comment-16545248 ] ASF subversion and git services commented on QPIDIT-133: Commit 4a76b6c6d32cb69131ed77f22f19a05302da0a5d in qpid-interop-test's branch refs/heads/0.2.0 from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=4a76b6c ] QPIDIT-133: Removed float test values 'inf', '-inf' from amqp-complex-types-test becasue of Proton bug > [complex_types_test]: Remove float types inf, +inf, -inf because of RHEL7 > Proton bug > > > Key: QPIDIT-133 > URL: https://issues.apache.org/jira/browse/QPIDIT-133 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > A bug in RHEL7 / CentOS7 Proton causes an overflow error when using float > literals '+inf' or '-inf'. The error does not occur in double values, nor for > literal 'NaN'. See PROTON-1149. > The amqp_complex_types_test uses JSON files to represent the values of the > test. However, these files do not allow for comments, so it is not possible > to comment out parts of the data. Data is either present or not. > In order to prevent this failure from causing the test to fail, remove the > test values 'inf', '+inf' and '-inf' from the test data until this bug is > fixed in Proton. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDIT-133) [complex_types_test]: Remove float types inf, +inf, -inf because of RHEL7 Proton bug
[ https://issues.apache.org/jira/browse/QPIDIT-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-133: Description: A bug in RHEL7 / CentOS7 Proton causes an overflow error when using float literals '+inf' or '-inf'. The error does not occur in double values, nor for literal 'NaN'. See PROTON-1149. The amqp_complex_types_test uses JSON files to represent the values of the test. However, these files do not allow for comments, so it is not possible to comment out parts of the data. Data is either present or not. In order to prevent this failure from causing the test to fail, remove the test values 'inf', '+inf' and '-inf' from the test data until this bug is fixed in Proton. was: A bug in RHEL7 / CentOS7 Proton causes an overflow error when using float literals '+inf' or '-inf'. The error does not occur in double values, nor for literal 'NaN'. The amqp_complex_types_test uses JSON files to represent the values of the test. However, these files do not allow for comments, so it is not possible to comment out parts of the data. Data is either present or not. In order to prevent this failure from causing the test to fail, remove the test values 'inf', '+inf' and '-inf' from the test data until this bug is fixed in Proton. > [complex_types_test]: Remove float types inf, +inf, -inf because of RHEL7 > Proton bug > > > Key: QPIDIT-133 > URL: https://issues.apache.org/jira/browse/QPIDIT-133 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > A bug in RHEL7 / CentOS7 Proton causes an overflow error when using float > literals '+inf' or '-inf'. The error does not occur in double values, nor for > literal 'NaN'. See PROTON-1149. > The amqp_complex_types_test uses JSON files to represent the values of the > test. However, these files do not allow for comments, so it is not possible > to comment out parts of the data. Data is either present or not. > In order to prevent this failure from causing the test to fail, remove the > test values 'inf', '+inf' and '-inf' from the test data until this bug is > fixed in Proton. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDIT-133) [complex_types_test]: Remove float types inf, +inf, -inf because of RHEL7 Proton bug
Kim van der Riet created QPIDIT-133: --- Summary: [complex_types_test]: Remove float types inf, +inf, -inf because of RHEL7 Proton bug Key: QPIDIT-133 URL: https://issues.apache.org/jira/browse/QPIDIT-133 Project: Apache QPID Interoperability Test Suite Issue Type: Task Reporter: Kim van der Riet Assignee: Kim van der Riet A bug in RHEL7 / CentOS7 Proton causes an overflow error when using float literals '+inf' or '-inf'. The error does not occur in double values, nor for literal 'NaN'. The amqp_complex_types_test uses JSON files to represent the values of the test. However, these files do not allow for comments, so it is not possible to comment out parts of the data. Data is either present or not. In order to prevent this failure from causing the test to fail, remove the test values 'inf', '+inf' and '-inf' from the test data until this bug is fixed in Proton. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1080) system_tests_ssl failing consistently on Travis
Ganesh Murthy created DISPATCH-1080:
---
Summary: system_tests_ssl failing consistently on Travis
Key: DISPATCH-1080
URL: https://issues.apache.org/jira/browse/DISPATCH-1080
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.2.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
Fix For: 1.3.0
system_tests_ssl is consistently failing on Travis
{noformat}
Test command: /usr/bin/python
"/home/travis/build/apache/qpid-dispatch/build/tests/run.py" "-x" "unit2" "-v"
"system_tests_ssl"
47: Test timeout computed to be: 1500
47: test_ssl_invalid (system_tests_ssl.RouterTestSslClient) ... ok
47: test_ssl_sasl_client_invalid (system_tests_ssl.RouterTestSslClient) ... ok
47: test_ssl_sasl_client_valid (system_tests_ssl.RouterTestSslClient) ... FAIL
47: test_tls11_only (system_tests_ssl.RouterTestSslClient) ... FAIL
47: test_tls11_tls12_only (system_tests_ssl.RouterTestSslClient) ... FAIL
47: test_tls12_only (system_tests_ssl.RouterTestSslClient) ... FAIL
47: test_tls1_only (system_tests_ssl.RouterTestSslClient) ... FAIL
47: test_tls1_tls11_only (system_tests_ssl.RouterTestSslClient) ... FAIL
47: test_tls1_tls12_only (system_tests_ssl.RouterTestSslClient) ... FAIL
47: test_tls_all (system_tests_ssl.RouterTestSslClient) ... FAIL
47: test_connected_tls_sasl_routers (system_tests_ssl.RouterTestSslInterRouter)
... ERROR
47:
47: ==
47: ERROR: test_connected_tls_sasl_routers
(system_tests_ssl.RouterTestSslInterRouter)
47: --
47: Traceback (most recent call last):
47: File "/home/travis/build/apache/qpid-dispatch/tests/system_tests_ssl.py",
line 584, in test_connected_tls_sasl_routers
47: router_nodes = self.get_router_nodes()
47: File "/home/travis/build/apache/qpid-dispatch/tests/system_tests_ssl.py",
line 572, in get_router_nodes
47: node = Node.connect(url)
47: File
"/home/travis/build/apache/qpid-dispatch/python/qpid_dispatch/management/client.py",
line 111, in connect
47: return Node(Node.connection(url, router, timeout, ssl_domain, sasl))
47: File
"/home/travis/build/apache/qpid-dispatch/python/qpid_dispatch/management/client.py",
line 106, in connection
47: password=str(sasl.password) if sasl else None)
47: File
"/home/travis/build/apache/qpid-dispatch/qpid-proton/python/proton/utils.py",
line 237, in __init__
47: msg="Opening connection")
47: File
"/home/travis/build/apache/qpid-dispatch/qpid-proton/python/proton/utils.py",
line 314, in wait
47: "Connection %s disconnected: %s" % (self.url, self.disconnected))
47: ConnectionException: Connection amqp://0.0.0.0:0/$management disconnected:
Condition('proton:io', 'recv: Connection refused')
47:
47: ==
47: FAIL: test_ssl_sasl_client_valid (system_tests_ssl.RouterTestSslClient)
47: --
47: Traceback (most recent call last):
47: File "/home/travis/build/apache/qpid-dispatch/tests/system_tests_ssl.py",
line 374, in test_ssl_sasl_client_valid
47: self.assertTrue(self.is_ssl_sasl_client_accepted(self.PORT_TLS_SASL,
"TLSv1"))
47: AssertionError: False is not true
47:
47: ==
47: FAIL: test_tls11_only (system_tests_ssl.RouterTestSslClient)
47: --
47: Traceback (most recent call last):
47: File "/home/travis/build/apache/qpid-dispatch/tests/system_tests_ssl.py",
line 325, in test_tls11_only
47: self.get_allowed_protocols(self.PORT_TLS11))
47: AssertionError: Lists differ: [False, True, False] != [False, False, False]
47:
47: First differing element 1:
47: True
47: False
47:
47: - [False, True, False]
47: ? ^^^
47:
47: + [False, False, False]
47: ?
47:
47:
47: ==
47: FAIL: test_tls11_tls12_only (system_tests_ssl.RouterTestSslClient)
47: --
47: Traceback (most recent call last):
47: File "/home/travis/build/apache/qpid-dispatch/tests/system_tests_ssl.py",
line 353, in test_tls11_tls12_only
47: self.get_allowed_protocols(self.PORT_TLS11_TLS12))
47: AssertionError: Lists differ: [False, True, True] != [False, False, False]
47:
47: First differing element 1:
47: True
47: False
47:
47: - [False, True, True]
47: + [False, False, False]
47:
47: ==
47: FAIL: test_tls12_only (system_tests_ssl.RouterTestSslClient)
47: --
47: Traceback (most
[jira] [Resolved] (DISPATCH-1070) Use patternfly cards on overview page
[ https://issues.apache.org/jira/browse/DISPATCH-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-1070. Resolution: Fixed Fix Version/s: 1.3.0 Used patternfly card widget. > Use patternfly cards on overview page > - > > Key: DISPATCH-1070 > URL: https://issues.apache.org/jira/browse/DISPATCH-1070 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 1.2.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > Fix For: 1.3.0 > > > The overview page of the console should use patternfly cards to display the > following info: > Overall trends: > * outstanding deliveries > * throughput > Per address: (for top 5 addresses) > * throughput trend > * number of senders > * number or receivers > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1070) Use patternfly cards on overview page
[ https://issues.apache.org/jira/browse/DISPATCH-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16545054#comment-16545054 ] ASF subversion and git services commented on DISPATCH-1070: --- Commit a3b271e7948829129ff07d570e81d73fbcacaaea in qpid-dispatch's branch refs/heads/master from [~eallen] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=a3b271e ] DISPATCH-1070 Use patternfly trend cards on console's overview page. > Use patternfly cards on overview page > - > > Key: DISPATCH-1070 > URL: https://issues.apache.org/jira/browse/DISPATCH-1070 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 1.2.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > > The overview page of the console should use patternfly cards to display the > following info: > Overall trends: > * outstanding deliveries > * throughput > Per address: (for top 5 addresses) > * throughput trend > * number of senders > * number or receivers > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPIDJMS-391) Add support for SSL provider netty-tcnative-boringssl-static
[ https://issues.apache.org/jira/browse/QPIDJMS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johan Stenberg updated QPIDJMS-391: --- Labels: performance (was: ) Description: It would be great to have an option to use netty-tcnative-boringssl-static instead of the java based SSL provider. In the ActiveMQ Artemis this was implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649 In Netty 4.1.26 a new OpenSslX509KeyManagerFactory for easier configuration was introduced. https://github.com/netty/netty/pull/8084 was:It would be great to have an option to use netty-tcnative-boringssl-static instead of the java based SSL provider. In the ActiveMQ Artemis this was implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649 > Add support for SSL provider netty-tcnative-boringssl-static > > > Key: QPIDJMS-391 > URL: https://issues.apache.org/jira/browse/QPIDJMS-391 > Project: Qpid JMS > Issue Type: New Feature > Components: qpid-jms-client >Reporter: Johan Stenberg >Priority: Minor > Labels: performance > > It would be great to have an option to use netty-tcnative-boringssl-static > instead of the java based SSL provider. In the ActiveMQ Artemis this was > implemented as part of https://issues.apache.org/jira/browse/ARTEMIS-1649 > In Netty 4.1.26 a new OpenSslX509KeyManagerFactory for easier configuration > was introduced. https://github.com/netty/netty/pull/8084 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
