[jira] [Updated] (QPID-8311) [Broker-J][WMC] Allow setting replaceExistingArguments in UI for bind creation
[ https://issues.apache.org/jira/browse/QPID-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8311: - Summary: [Broker-J][WMC] Allow setting replaceExistingArguments in UI for bind creation (was: [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI) > [Broker-J][WMC] Allow setting replaceExistingArguments in UI for bind creation > -- > > Key: QPID-8311 > URL: https://issues.apache.org/jira/browse/QPID-8311 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > Modify add binding UI to allow setting replaceExistingArguments in bind > operation -- 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] (QPID-8307) [Broker-J] Document the virtualHostInitialConfiguration
[
https://issues.apache.org/jira/browse/QPID-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8307:
-
Summary: [Broker-J] Document the virtualHostInitialConfiguration (was:
Broker-J - Document the virtualHostInitialConfiguration)
> [Broker-J] Document the virtualHostInitialConfiguration
> ---
>
> Key: QPID-8307
> URL: https://issues.apache.org/jira/browse/QPID-8307
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J, Java Documentation
>Affects Versions: qpid-java-broker-7.1.2
>Reporter: Tom Jordahl
>Assignee: Alex Rudyy
>Priority: Trivial
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3
>
>
> There is no document of the virtualHostInitialConfiguration item in the JSON
> initial configuration file.
> This is important for any automated configuration of the Qpid broker - for
> instance a chef recipe configuration of a virtual host that wants a "Node
> Creation Policy" defined at startup.
> In response to a question on Qpid-users (reference
> [http://qpid.2158936.n2.nabble.com/Qpid-Broker-J-Configuring-nodeAutoCreationPolicies-for-an-BDB-HA-cluster-from-json-td7683530.html]
> )
> On 5/1/19, 3:09 PM, "Oleksandr Rudyy" wrote:
> Hi Tom,
> The node auto creation policies can be set on virtual host only, as it is
> an attribute of virtual host. Adding policies into virtual host node
> configuration does not have any effect. The settings are simply ignored
> and
> removed on configuration update.
> If you need to have the policies in broker initial configuration, you can
> add them into virtual host inital configuration. Though, at the moment,
> virtualHostInitialConfigurati can only have string values. Thus, you need
> to stringify your policy json.
> For example,
> ...
> "virtualHostInitialConfiguration":
>
> "\{\"type\":\"BDB_HA\",\"context\":{},\"name\":\"$parent.name\",\"nodeAutoCreationPolicies\":
> [\{\"pattern\":\"*\",\"nodeType\":\"Queue\" ... }]}"
> ...
> Kind Regards,
> Alex
--
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] [Resolved] (QPID-8310) [AMQP 1.0] JMS receiver on exchange causes non-autodeleted queues by default
[ https://issues.apache.org/jira/browse/QPID-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-8310. -- Resolution: Fixed > [AMQP 1.0] JMS receiver on exchange causes non-autodeleted queues by default > > > Key: QPID-8310 > URL: https://issues.apache.org/jira/browse/QPID-8310 > Project: Qpid > Issue Type: Bug >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > Fix For: qpid-cpp-1.40.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] (QPID-8310) [AMQP 1.0] JMS receiver on exchange causes non-autodeleted queues by default
[ https://issues.apache.org/jira/browse/QPID-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835938#comment-16835938 ] ASF subversion and git services commented on QPID-8310: --- Commit 2c4691b04aab7b1c1a7c3d1596966bc187aa436e in qpid-cpp's branch refs/heads/master from Gordon Sim [ https://gitbox.apache.org/repos/asf?p=qpid-cpp.git;h=2c4691b ] QPID-8310: fix determination of autodelete for subscription queues > [AMQP 1.0] JMS receiver on exchange causes non-autodeleted queues by default > > > Key: QPID-8310 > URL: https://issues.apache.org/jira/browse/QPID-8310 > Project: Qpid > Issue Type: Bug >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > Fix For: qpid-cpp-1.40.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] [Assigned] (QPID-8312) [Broker-J] Release Qpid Broker-J version 7.1.3
[ https://issues.apache.org/jira/browse/QPID-8312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8312: Assignee: Alex Rudyy > [Broker-J] Release Qpid Broker-J version 7.1.3 > -- > > Key: QPID-8312 > URL: https://issues.apache.org/jira/browse/QPID-8312 > Project: Qpid > Issue Type: Task >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-7.1.3 > > > Release Qpid Broker-J version 7.1.3 as per instructions at > [https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Broker-J] -- 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] (QPID-8312) [Broker-J] Release Qpid Broker-J version 7.1.3
Alex Rudyy created QPID-8312: Summary: [Broker-J] Release Qpid Broker-J version 7.1.3 Key: QPID-8312 URL: https://issues.apache.org/jira/browse/QPID-8312 Project: Qpid Issue Type: Task Reporter: Alex Rudyy Fix For: qpid-java-broker-7.1.3 Release Qpid Broker-J version 7.1.3 as per instructions at [https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Broker-J] -- 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] (QPID-8307) Broker-J - Document the virtualHostInitialConfiguration
[
https://issues.apache.org/jira/browse/QPID-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8307:
-
Priority: Trivial (was: Major)
Issue Type: Improvement (was: Bug)
> Broker-J - Document the virtualHostInitialConfiguration
> ---
>
> Key: QPID-8307
> URL: https://issues.apache.org/jira/browse/QPID-8307
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J, Java Documentation
>Affects Versions: qpid-java-broker-7.1.2
>Reporter: Tom Jordahl
>Assignee: Alex Rudyy
>Priority: Trivial
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3
>
>
> There is no document of the virtualHostInitialConfiguration item in the JSON
> initial configuration file.
> This is important for any automated configuration of the Qpid broker - for
> instance a chef recipe configuration of a virtual host that wants a "Node
> Creation Policy" defined at startup.
> In response to a question on Qpid-users (reference
> [http://qpid.2158936.n2.nabble.com/Qpid-Broker-J-Configuring-nodeAutoCreationPolicies-for-an-BDB-HA-cluster-from-json-td7683530.html]
> )
> On 5/1/19, 3:09 PM, "Oleksandr Rudyy" wrote:
> Hi Tom,
> The node auto creation policies can be set on virtual host only, as it is
> an attribute of virtual host. Adding policies into virtual host node
> configuration does not have any effect. The settings are simply ignored
> and
> removed on configuration update.
> If you need to have the policies in broker initial configuration, you can
> add them into virtual host inital configuration. Though, at the moment,
> virtualHostInitialConfigurati can only have string values. Thus, you need
> to stringify your policy json.
> For example,
> ...
> "virtualHostInitialConfiguration":
>
> "\{\"type\":\"BDB_HA\",\"context\":{},\"name\":\"$parent.name\",\"nodeAutoCreationPolicies\":
> [\{\"pattern\":\"*\",\"nodeType\":\"Queue\" ... }]}"
> ...
> Kind Regards,
> Alex
--
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] [Resolved] (QPID-8305) [Broker-J][JDBC Message Store] Performance regression when increasing the number of queues linked to a topic
[ https://issues.apache.org/jira/browse/QPID-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8305. -- Resolution: Fixed > [Broker-J][JDBC Message Store] Performance regression when increasing the > number of queues linked to a topic > > > Key: QPID-8305 > URL: https://issues.apache.org/jira/browse/QPID-8305 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Olivier VERMEULEN >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > When sending a message to a topic, if this message is routed to N queues then > we will do N+2 database inserts: 1 for the metadata, 1 for the content and 1 > for each message/queue mapping (QPID_QUEUE_ENTRIES). The last N inserts could > be batched in a single operation. -- 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] (QPID-8305) [Broker-J][JDBC Message Store] Performance regression when increasing the number of queues linked to a topic
[ https://issues.apache.org/jira/browse/QPID-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8305: Assignee: Alex Rudyy > [Broker-J][JDBC Message Store] Performance regression when increasing the > number of queues linked to a topic > > > Key: QPID-8305 > URL: https://issues.apache.org/jira/browse/QPID-8305 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Olivier VERMEULEN >Assignee: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > When sending a message to a topic, if this message is routed to N queues then > we will do N+2 database inserts: 1 for the metadata, 1 for the content and 1 > for each message/queue mapping (QPID_QUEUE_ENTRIES). The last N inserts could > be batched in a single operation. -- 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] (QPID-8311) [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI
[ https://issues.apache.org/jira/browse/QPID-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8311: - Status: Reviewable (was: In Progress) > [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI > - > > Key: QPID-8311 > URL: https://issues.apache.org/jira/browse/QPID-8311 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > Modify add binding UI to allow setting replaceExistingArguments in bind > operation -- 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] (QPID-8311) [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI
[ https://issues.apache.org/jira/browse/QPID-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8311: Assignee: Alex Rudyy > [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI > - > > Key: QPID-8311 > URL: https://issues.apache.org/jira/browse/QPID-8311 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > Modify add binding UI to allow setting replaceExistingArguments in bind > operation -- 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] (QPID-8306) [Broker-J] Add ability to update TLS transport on AMQP port after changing keystore, trustores or other TLS related attributes
[ https://issues.apache.org/jira/browse/QPID-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8306: - Fix Version/s: (was: qpid-java-broker-7.1.3) > [Broker-J] Add ability to update TLS transport on AMQP port after changing > keystore, trustores or other TLS related attributes > -- > > Key: QPID-8306 > URL: https://issues.apache.org/jira/browse/QPID-8306 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0 > > > Broker restart is required after changes to AMQP port TLS attributes, > keystore and trust stores. It should be possible to update TLS transport > without affecting existing AMQP connections. -- 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] (QPID-8311) [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI
[ https://issues.apache.org/jira/browse/QPID-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835930#comment-16835930 ] ASF subversion and git services commented on QPID-8311: --- Commit 901fede7df24341a5321b6f8665cb0d8451342ac 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=901fede ] QPID-8311: [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI > [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI > - > > Key: QPID-8311 > URL: https://issues.apache.org/jira/browse/QPID-8311 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > Modify add binding UI to allow setting replaceExistingArguments in bind > operation -- 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] (QPID-8311) [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI
[ https://issues.apache.org/jira/browse/QPID-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835923#comment-16835923 ] ASF subversion and git services commented on QPID-8311: --- Commit facb51a6eb2a65d3ec36b9193c50bf06f134cb4d in qpid-broker-j's branch refs/heads/master from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=facb51a ] QPID-8311: [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI > [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI > - > > Key: QPID-8311 > URL: https://issues.apache.org/jira/browse/QPID-8311 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > Modify add binding UI to allow setting replaceExistingArguments in bind > operation -- 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] (QPID-8311) [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI
Alex Rudyy created QPID-8311: Summary: [Broker-J][WMC] Allow setting replaceExistingArguments in add bind UI Key: QPID-8311 URL: https://issues.apache.org/jira/browse/QPID-8311 Project: Qpid Issue Type: Improvement Components: Broker-J Reporter: Alex Rudyy Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 Modify add binding UI to allow setting replaceExistingArguments in bind operation -- 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] (QPID-8310) [AMQP 1.0] JMS receiver on exchange causes non-autodeleted queues by default
Gordon Sim created QPID-8310: Summary: [AMQP 1.0] JMS receiver on exchange causes non-autodeleted queues by default Key: QPID-8310 URL: https://issues.apache.org/jira/browse/QPID-8310 Project: Qpid Issue Type: Bug Reporter: Gordon Sim Assignee: Gordon Sim Fix For: qpid-cpp-1.40.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] (QPID-8305) [Broker-J][JDBC Message Store] Performance regression when increasing the number of queues linked to a topic
[ https://issues.apache.org/jira/browse/QPID-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835906#comment-16835906 ] ASF subversion and git services commented on QPID-8305: --- Commit fccae34c184dd45b2a057d7bf6658b152c687e11 in qpid-broker-j's branch refs/heads/master from overmeulen [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=fccae34 ] QPID-8305: [Broker-J][JDBC Message Store] Performance regression when increasing the number of queues linked to a topic > [Broker-J][JDBC Message Store] Performance regression when increasing the > number of queues linked to a topic > > > Key: QPID-8305 > URL: https://issues.apache.org/jira/browse/QPID-8305 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Olivier VERMEULEN >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > When sending a message to a topic, if this message is routed to N queues then > we will do N+2 database inserts: 1 for the metadata, 1 for the content and 1 > for each message/queue mapping (QPID_QUEUE_ENTRIES). The last N inserts could > be batched in a single operation. -- 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] (QPID-8305) [Broker-J][JDBC Message Store] Performance regression when increasing the number of queues linked to a topic
[ https://issues.apache.org/jira/browse/QPID-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835908#comment-16835908 ] ASF subversion and git services commented on QPID-8305: --- Commit cadb26d58e8ace35dc544ab2402c911f6174b5fe in qpid-broker-j's branch refs/heads/master from overmeulen [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=cadb26d ] QPID-8305: [Broker-J][JDBC Message Store] Create the pre-commit action in the constructor of JBDCTransaction This closes #30 > [Broker-J][JDBC Message Store] Performance regression when increasing the > number of queues linked to a topic > > > Key: QPID-8305 > URL: https://issues.apache.org/jira/browse/QPID-8305 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Olivier VERMEULEN >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > When sending a message to a topic, if this message is routed to N queues then > we will do N+2 database inserts: 1 for the metadata, 1 for the content and 1 > for each message/queue mapping (QPID_QUEUE_ENTRIES). The last N inserts could > be batched in a single operation. -- 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] (QPID-8306) [Broker-J] Add ability to update TLS transport on AMQP port after changing keystore, trustores or other TLS related attributes
[ https://issues.apache.org/jira/browse/QPID-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835912#comment-16835912 ] ASF subversion and git services commented on QPID-8306: --- Commit 4289e149821f0040f4f3465647b18318ea265994 in qpid-broker-j's branch refs/heads/master from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=4289e14 ] QPID-8306: Add missing header > [Broker-J] Add ability to update TLS transport on AMQP port after changing > keystore, trustores or other TLS related attributes > -- > > Key: QPID-8306 > URL: https://issues.apache.org/jira/browse/QPID-8306 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > Broker restart is required after changes to AMQP port TLS attributes, > keystore and trust stores. It should be possible to update TLS transport > without affecting existing AMQP connections. -- 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] (QPID-8305) [Broker-J][JDBC Message Store] Performance regression when increasing the number of queues linked to a topic
[ https://issues.apache.org/jira/browse/QPID-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835910#comment-16835910 ] ASF subversion and git services commented on QPID-8305: --- Commit d0692ad993c6cf97f11ee3588ef9089026b9142d in qpid-broker-j's branch refs/heads/7.1.x from overmeulen [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=d0692ad ] QPID-8305: [Broker-J][JDBC Message Store] Create the pre-commit action in the constructor of JBDCTransaction This closes #30 (cherry picked from commit cadb26d58e8ace35dc544ab2402c911f6174b5fe) > [Broker-J][JDBC Message Store] Performance regression when increasing the > number of queues linked to a topic > > > Key: QPID-8305 > URL: https://issues.apache.org/jira/browse/QPID-8305 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Affects Versions: qpid-java-broker-7.1.0 >Reporter: Olivier VERMEULEN >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > When sending a message to a topic, if this message is routed to N queues then > we will do N+2 database inserts: 1 for the metadata, 1 for the content and 1 > for each message/queue mapping (QPID_QUEUE_ENTRIES). The last N inserts could > be batched in a single operation. -- 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-broker-j] asfgit closed pull request #30: QPID-8305: [Broker-J][JDBC Message Store] Performance regression when increasing the number of queues linked to a topic
asfgit closed pull request #30: QPID-8305: [Broker-J][JDBC Message Store] Performance regression when increasing the number of queues linked to a topic URL: https://github.com/apache/qpid-broker-j/pull/30 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] [Assigned] (QPID-8307) Broker-J - Document the virtualHostInitialConfiguration
[
https://issues.apache.org/jira/browse/QPID-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy reassigned QPID-8307:
Assignee: Alex Rudyy
> Broker-J - Document the virtualHostInitialConfiguration
> ---
>
> Key: QPID-8307
> URL: https://issues.apache.org/jira/browse/QPID-8307
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J, Java Documentation
>Affects Versions: qpid-java-broker-7.1.2
>Reporter: Tom Jordahl
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3
>
>
> There is no document of the virtualHostInitialConfiguration item in the JSON
> initial configuration file.
> This is important for any automated configuration of the Qpid broker - for
> instance a chef recipe configuration of a virtual host that wants a "Node
> Creation Policy" defined at startup.
> In response to a question on Qpid-users (reference
> [http://qpid.2158936.n2.nabble.com/Qpid-Broker-J-Configuring-nodeAutoCreationPolicies-for-an-BDB-HA-cluster-from-json-td7683530.html]
> )
> On 5/1/19, 3:09 PM, "Oleksandr Rudyy" wrote:
> Hi Tom,
> The node auto creation policies can be set on virtual host only, as it is
> an attribute of virtual host. Adding policies into virtual host node
> configuration does not have any effect. The settings are simply ignored
> and
> removed on configuration update.
> If you need to have the policies in broker initial configuration, you can
> add them into virtual host inital configuration. Though, at the moment,
> virtualHostInitialConfigurati can only have string values. Thus, you need
> to stringify your policy json.
> For example,
> ...
> "virtualHostInitialConfiguration":
>
> "\{\"type\":\"BDB_HA\",\"context\":{},\"name\":\"$parent.name\",\"nodeAutoCreationPolicies\":
> [\{\"pattern\":\"*\",\"nodeType\":\"Queue\" ... }]}"
> ...
> Kind Regards,
> Alex
--
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] (QPID-8307) Broker-J - Document the virtualHostInitialConfiguration
[
https://issues.apache.org/jira/browse/QPID-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8307:
-
Fix Version/s: qpid-java-broker-7.1.3
qpid-java-broker-8.0.0
> Broker-J - Document the virtualHostInitialConfiguration
> ---
>
> Key: QPID-8307
> URL: https://issues.apache.org/jira/browse/QPID-8307
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J, Java Documentation
>Affects Versions: qpid-java-broker-7.1.2
>Reporter: Tom Jordahl
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3
>
>
> There is no document of the virtualHostInitialConfiguration item in the JSON
> initial configuration file.
> This is important for any automated configuration of the Qpid broker - for
> instance a chef recipe configuration of a virtual host that wants a "Node
> Creation Policy" defined at startup.
> In response to a question on Qpid-users (reference
> [http://qpid.2158936.n2.nabble.com/Qpid-Broker-J-Configuring-nodeAutoCreationPolicies-for-an-BDB-HA-cluster-from-json-td7683530.html]
> )
> On 5/1/19, 3:09 PM, "Oleksandr Rudyy" wrote:
> Hi Tom,
> The node auto creation policies can be set on virtual host only, as it is
> an attribute of virtual host. Adding policies into virtual host node
> configuration does not have any effect. The settings are simply ignored
> and
> removed on configuration update.
> If you need to have the policies in broker initial configuration, you can
> add them into virtual host inital configuration. Though, at the moment,
> virtualHostInitialConfigurati can only have string values. Thus, you need
> to stringify your policy json.
> For example,
> ...
> "virtualHostInitialConfiguration":
>
> "\{\"type\":\"BDB_HA\",\"context\":{},\"name\":\"$parent.name\",\"nodeAutoCreationPolicies\":
> [\{\"pattern\":\"*\",\"nodeType\":\"Queue\" ... }]}"
> ...
> Kind Regards,
> Alex
--
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] (QPID-8307) Broker-J - Document the virtualHostInitialConfiguration
[
https://issues.apache.org/jira/browse/QPID-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835879#comment-16835879
]
ASF subversion and git services commented on QPID-8307:
---
Commit 13bcee3126ca99506713bcc29921583715cac9f0 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=13bcee3 ]
QPID-8307:[Broker-J][Documentation] Document how to specify virtualhost initial
configuration
(cherry picked from commit 6dc4f78e7fca09b6466103324f388715d5c43327)
> Broker-J - Document the virtualHostInitialConfiguration
> ---
>
> Key: QPID-8307
> URL: https://issues.apache.org/jira/browse/QPID-8307
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J, Java Documentation
>Affects Versions: qpid-java-broker-7.1.2
>Reporter: Tom Jordahl
>Priority: Major
>
> There is no document of the virtualHostInitialConfiguration item in the JSON
> initial configuration file.
> This is important for any automated configuration of the Qpid broker - for
> instance a chef recipe configuration of a virtual host that wants a "Node
> Creation Policy" defined at startup.
> In response to a question on Qpid-users (reference
> [http://qpid.2158936.n2.nabble.com/Qpid-Broker-J-Configuring-nodeAutoCreationPolicies-for-an-BDB-HA-cluster-from-json-td7683530.html]
> )
> On 5/1/19, 3:09 PM, "Oleksandr Rudyy" wrote:
> Hi Tom,
> The node auto creation policies can be set on virtual host only, as it is
> an attribute of virtual host. Adding policies into virtual host node
> configuration does not have any effect. The settings are simply ignored
> and
> removed on configuration update.
> If you need to have the policies in broker initial configuration, you can
> add them into virtual host inital configuration. Though, at the moment,
> virtualHostInitialConfigurati can only have string values. Thus, you need
> to stringify your policy json.
> For example,
> ...
> "virtualHostInitialConfiguration":
>
> "\{\"type\":\"BDB_HA\",\"context\":{},\"name\":\"$parent.name\",\"nodeAutoCreationPolicies\":
> [\{\"pattern\":\"*\",\"nodeType\":\"Queue\" ... }]}"
> ...
> Kind Regards,
> Alex
--
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] (QPID-8307) Broker-J - Document the virtualHostInitialConfiguration
[
https://issues.apache.org/jira/browse/QPID-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8307:
-
Status: Reviewable (was: In Progress)
> Broker-J - Document the virtualHostInitialConfiguration
> ---
>
> Key: QPID-8307
> URL: https://issues.apache.org/jira/browse/QPID-8307
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J, Java Documentation
>Affects Versions: qpid-java-broker-7.1.2
>Reporter: Tom Jordahl
>Assignee: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3
>
>
> There is no document of the virtualHostInitialConfiguration item in the JSON
> initial configuration file.
> This is important for any automated configuration of the Qpid broker - for
> instance a chef recipe configuration of a virtual host that wants a "Node
> Creation Policy" defined at startup.
> In response to a question on Qpid-users (reference
> [http://qpid.2158936.n2.nabble.com/Qpid-Broker-J-Configuring-nodeAutoCreationPolicies-for-an-BDB-HA-cluster-from-json-td7683530.html]
> )
> On 5/1/19, 3:09 PM, "Oleksandr Rudyy" wrote:
> Hi Tom,
> The node auto creation policies can be set on virtual host only, as it is
> an attribute of virtual host. Adding policies into virtual host node
> configuration does not have any effect. The settings are simply ignored
> and
> removed on configuration update.
> If you need to have the policies in broker initial configuration, you can
> add them into virtual host inital configuration. Though, at the moment,
> virtualHostInitialConfigurati can only have string values. Thus, you need
> to stringify your policy json.
> For example,
> ...
> "virtualHostInitialConfiguration":
>
> "\{\"type\":\"BDB_HA\",\"context\":{},\"name\":\"$parent.name\",\"nodeAutoCreationPolicies\":
> [\{\"pattern\":\"*\",\"nodeType\":\"Queue\" ... }]}"
> ...
> Kind Regards,
> Alex
--
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] (QPID-8307) Broker-J - Document the virtualHostInitialConfiguration
[
https://issues.apache.org/jira/browse/QPID-8307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835866#comment-16835866
]
ASF subversion and git services commented on QPID-8307:
---
Commit 6dc4f78e7fca09b6466103324f388715d5c43327 in qpid-broker-j's branch
refs/heads/master from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=6dc4f78 ]
QPID-8307:[Broker-J][Documentation] Document how to specify virtualhost initial
configuration
> Broker-J - Document the virtualHostInitialConfiguration
> ---
>
> Key: QPID-8307
> URL: https://issues.apache.org/jira/browse/QPID-8307
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J, Java Documentation
>Affects Versions: qpid-java-broker-7.1.2
>Reporter: Tom Jordahl
>Priority: Major
>
> There is no document of the virtualHostInitialConfiguration item in the JSON
> initial configuration file.
> This is important for any automated configuration of the Qpid broker - for
> instance a chef recipe configuration of a virtual host that wants a "Node
> Creation Policy" defined at startup.
> In response to a question on Qpid-users (reference
> [http://qpid.2158936.n2.nabble.com/Qpid-Broker-J-Configuring-nodeAutoCreationPolicies-for-an-BDB-HA-cluster-from-json-td7683530.html]
> )
> On 5/1/19, 3:09 PM, "Oleksandr Rudyy" wrote:
> Hi Tom,
> The node auto creation policies can be set on virtual host only, as it is
> an attribute of virtual host. Adding policies into virtual host node
> configuration does not have any effect. The settings are simply ignored
> and
> removed on configuration update.
> If you need to have the policies in broker initial configuration, you can
> add them into virtual host inital configuration. Though, at the moment,
> virtualHostInitialConfigurati can only have string values. Thus, you need
> to stringify your policy json.
> For example,
> ...
> "virtualHostInitialConfiguration":
>
> "\{\"type\":\"BDB_HA\",\"context\":{},\"name\":\"$parent.name\",\"nodeAutoCreationPolicies\":
> [\{\"pattern\":\"*\",\"nodeType\":\"Queue\" ... }]}"
> ...
> Kind Regards,
> Alex
--
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] (QPID-8306) [Broker-J] Add ability to update TLS transport on AMQP port after changing keystore, trustores or other TLS related attributes
[ https://issues.apache.org/jira/browse/QPID-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835864#comment-16835864 ] ASF GitHub Bot commented on QPID-8306: -- asfgit commented on pull request #31: QPID-8306: [Broker-J] Add operation to update AmqpPort TLS support after changes to TLS related attributes URL: https://github.com/apache/qpid-broker-j/pull/31 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 > [Broker-J] Add ability to update TLS transport on AMQP port after changing > keystore, trustores or other TLS related attributes > -- > > Key: QPID-8306 > URL: https://issues.apache.org/jira/browse/QPID-8306 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > Broker restart is required after changes to AMQP port TLS attributes, > keystore and trust stores. It should be possible to update TLS transport > without affecting existing AMQP connections. -- 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-broker-j] asfgit closed pull request #31: QPID-8306: [Broker-J] Add operation to update AmqpPort TLS support after changes to TLS related attributes
asfgit closed pull request #31: QPID-8306: [Broker-J] Add operation to update AmqpPort TLS support after changes to TLS related attributes URL: https://github.com/apache/qpid-broker-j/pull/31 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] [Commented] (QPID-8306) [Broker-J] Add ability to update TLS transport on AMQP port after changing keystore, trustores or other TLS related attributes
[ https://issues.apache.org/jira/browse/QPID-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835865#comment-16835865 ] ASF subversion and git services commented on QPID-8306: --- Commit ce1cb00c795a70ed33f8717250f0ab61838d23f5 in qpid-broker-j's branch refs/heads/master from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=ce1cb00 ] QPID-8306: [Broker-J] Add operation to update port TLS support This closes #31 > [Broker-J] Add ability to update TLS transport on AMQP port after changing > keystore, trustores or other TLS related attributes > -- > > Key: QPID-8306 > URL: https://issues.apache.org/jira/browse/QPID-8306 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.3 > > > Broker restart is required after changes to AMQP port TLS attributes, > keystore and trust stores. It should be possible to update TLS transport > without affecting existing AMQP connections. -- 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] (PROTON-2040) [cpp] Allow connection options to be updated for automatic reconnect.
[ https://issues.apache.org/jira/browse/PROTON-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835816#comment-16835816 ] ASF GitHub Bot commented on PROTON-2040: alanconway commented on issue #182: PROTON-2040: Alternative suggestion for updating connection options: URL: https://github.com/apache/qpid-proton/pull/182#issuecomment-490608572 This looks good to me. On initial URL I noticed that also. We could make URL a connection_option and provide a connect() that takes only options - I think we do that in some other bindings like ruby. If you use a connect(url, opts) call, then I would say the URL from connect() should over-write any URL in the options to avoid confusion. 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 > [cpp] Allow connection options to be updated for automatic reconnect. > - > > Key: PROTON-2040 > URL: https://issues.apache.org/jira/browse/PROTON-2040 > Project: Qpid Proton > Issue Type: New Feature > Components: cpp-binding >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Major > Fix For: proton-c-0.29.0 > > > Allow modification of connection options prior to an automatic re-connect. > Requested on mailing list: > > [https://lists.apache.org/thread.html/1fcd524de1e0d896a6f025470e0d774e051b8449dba0b9ddb3d0439e@%3Cusers.qpid.apache.org%3E] > > -- 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-proton] alanconway commented on issue #182: PROTON-2040: Alternative suggestion for updating connection options:
alanconway commented on issue #182: PROTON-2040: Alternative suggestion for updating connection options: URL: https://github.com/apache/qpid-proton/pull/182#issuecomment-490608572 This looks good to me. On initial URL I noticed that also. We could make URL a connection_option and provide a connect() that takes only options - I think we do that in some other bindings like ruby. If you use a connect(url, opts) call, then I would say the URL from connect() should over-write any URL in the options to avoid confusion. 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
[GitHub] [qpid-proton] alanconway edited a comment on issue #182: PROTON-2040: Alternative suggestion for updating connection options:
alanconway edited a comment on issue #182: PROTON-2040: Alternative suggestion for updating connection options: URL: https://github.com/apache/qpid-proton/pull/182#issuecomment-490608572 This looks good to me. On initial URL I noticed that also. We could make URL a connection_option and provide a connect() that takes only options - I think we do that in some other bindings like ruby. If you use a connect(url, opts) call, then I would say the URL from connect() should over-write any URL in the options to avoid confusion. Either that or it would be an error to have a URL in the options when calling connect(url, opts) 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] [Commented] (PROTON-2040) [cpp] Allow connection options to be updated for automatic reconnect.
[ https://issues.apache.org/jira/browse/PROTON-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835817#comment-16835817 ] ASF GitHub Bot commented on PROTON-2040: alanconway commented on issue #182: PROTON-2040: Alternative suggestion for updating connection options: URL: https://github.com/apache/qpid-proton/pull/182#issuecomment-490608572 This looks good to me. On initial URL I noticed that also. We could make URL a connection_option and provide a connect() that takes only options - I think we do that in some other bindings like ruby. If you use a connect(url, opts) call, then I would say the URL from connect() should over-write any URL in the options to avoid confusion. Either that or it would be an error to have a URL in the options when calling connect(url, opts) 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 > [cpp] Allow connection options to be updated for automatic reconnect. > - > > Key: PROTON-2040 > URL: https://issues.apache.org/jira/browse/PROTON-2040 > Project: Qpid Proton > Issue Type: New Feature > Components: cpp-binding >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Major > Fix For: proton-c-0.29.0 > > > Allow modification of connection options prior to an automatic re-connect. > Requested on mailing list: > > [https://lists.apache.org/thread.html/1fcd524de1e0d896a6f025470e0d774e051b8449dba0b9ddb3d0439e@%3Cusers.qpid.apache.org%3E] > > -- 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-974) Getting connections via the router management protocol causes AMQP framing errors
[
https://issues.apache.org/jira/browse/DISPATCH-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835793#comment-16835793
]
ASF GitHub Bot commented on DISPATCH-974:
-
ChugR commented on issue #503: DISPATCH-974 - Added code to qdstat and qdmanage
clients to repeatedl…
URL: https://github.com/apache/qpid-dispatch/pull/503#issuecomment-490593232
+1 the implementation looks OK and the tests pass.
The technique used here, pulling successive slices on repeated calls, leaves
room for the underlying list in proton to change between calls. This could lead
to duplicate or missing entries. Is there a place to put doc text explaining
this so that users' expectations are properly framed when the lists are longer
than the 700 entries?
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
> Getting connections via the router management protocol causes AMQP framing
> errors
> -
>
> Key: DISPATCH-974
> URL: https://issues.apache.org/jira/browse/DISPATCH-974
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
>Affects Versions: 1.0.1
>Reporter: Marcel Meulemans
>Assignee: Ganesh Murthy
>Priority: Major
> Attachments: qdrouter-frame-errors.pcapng.gz
>
>
> I am running a standalone router with 5000 clients connected. When I try to
> get all connections via qdstat (qdstat --limit 5000 -c) something goes wrong
> (seems to be a framing error). The output from qdstat is:
> {{ MessageException: [-10]: data error: (null)}}
> The problems seems to somehow be related to result size because when I set
> the limit to less I get the list of connections as expected. In my situation
> the critical limit is 3447 (i.e. 3447 result in the expected list of
> connections, 3448 result in the error above). It does not seem to be frame
> size related because getting 3447 connection is already spread over transfer
> frames (256182, 256512 and 159399 bytes).
> The error is not qdstat related because using some plain proton code to
> create a management query results in the same problem. Ultimately the call to
> pn_message_decode with data receive from the router fails (also wireshark can
> not decode the final frame).
> I have attached a wireshark dump to the qdstat session with the router
> ([^qdrouter-frame-errors.pcapng.gz]). The logs of the router (at info level)
> contain no further information.
>
--
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] ChugR commented on issue #503: DISPATCH-974 - Added code to qdstat and qdmanage clients to repeatedl…
ChugR commented on issue #503: DISPATCH-974 - Added code to qdstat and qdmanage clients to repeatedl… URL: https://github.com/apache/qpid-dispatch/pull/503#issuecomment-490593232 +1 the implementation looks OK and the tests pass. The technique used here, pulling successive slices on repeated calls, leaves room for the underlying list in proton to change between calls. This could lead to duplicate or missing entries. Is there a place to put doc text explaining this so that users' expectations are properly framed when the lists are longer than the 700 entries? 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] [Updated] (PROTON-2044) Azure IoT Hub local-idle-timeout expired
[
https://issues.apache.org/jira/browse/PROTON-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Fendt updated PROTON-2044:
--
Description:
I'm using following python code to send messages to the devices
(*/messages/devicebound*) which are connected to the *azure iot hub*:
{code}
import json
from base64 import b64encode, b64decode
from hashlib import sha256
from hmac import HMAC
from time import time
from urllib.parse import quote_plus, urlencode
from proton import ProtonException, Message
from proton.utils import BlockingConnection
class IotHub:
def __init__(self):
self._hostname = f"example-hub.azure-devices.net"
self._username = f"iothubow...@sas.root.example-hub.azure-devices.net"
self._blocking_connection = None
self._sender = None
self.connect()
@staticmethod
def generate_sas_token(uri: str, policy: str, key: str, expiry: float =
None):
if not expiry:
expiry = time() + 3600 # Default to 1 hour.
encoded_uri = quote_plus(uri)
ttl = int(expiry)
sign_key = f"{encoded_uri}\n{ttl}"
signature = b64encode(HMAC(b64decode(key), sign_key.encode(),
sha256).digest())
result = {"sr": uri, "sig": signature, "se": str(ttl)}
if policy:
result["skn"] = policy
return f"SharedAccessSignature {urlencode(result)}"
def connect(self):
# create credentials
password = self.generate_sas_token(self._hostname,
"iothubowner", "key",
time() + 31557600) # ttl = 1 Year
# establish connection
self._blocking_connection =
BlockingConnection(f"amqps://{self._hostname}", allowed_mechs="PLAIN",
user=self._username,
password=password,
heartbeat=30)
self._sender =
self._blocking_connection.create_sender("/messages/devicebound")
def send(self, message: dict, serial_number: str):
message =
Message(address="/devices/{serial_number}/messages/devicebound".format(serial_number=serial_number),
body=bytes(json.dumps(message, separators=(",",
":")), "utf-8"))
message.inferred = True # disable message encoding
self._sender.send(message, timeout=20)
{code}
The problem is now that when I don't send any message for some seconds I get
following exepction while sending a message:
{code:java}
Connection amqps://example-hub.azure-devices.net:amqps disconnected:
Condition('amqp:resource-limit-exceeded', 'local-idle-timeout expired')
{code}
Whats the reason for that? How can I solve that?
Thank you for help.
was:
I'm using following python code to send messages to the devices which are
connected to the azure iot hub:
{code:python}
import json
from base64 import b64encode, b64decode
from hashlib import sha256
from hmac import HMAC
from time import time
from urllib.parse import quote_plus, urlencode
from proton import ProtonException, Message
from proton.utils import BlockingConnection
class IotHub:
def __init__(self):
self._hostname = f"example-hub.azure-devices.net"
self._username = f"iothubow...@sas.root.example-hub.azure-devices.net"
self._blocking_connection = None
self._sender = None
self.connect()
@staticmethod
def generate_sas_token(uri: str, policy: str, key: str, expiry: float =
None):
if not expiry:
expiry = time() + 3600 # Default to 1 hour.
encoded_uri = quote_plus(uri)
ttl = int(expiry)
sign_key = f"{encoded_uri}\n{ttl}"
signature = b64encode(HMAC(b64decode(key), sign_key.encode(),
sha256).digest())
result = {"sr": uri, "sig": signature, "se": str(ttl)}
if policy:
result["skn"] = policy
return f"SharedAccessSignature {urlencode(result)}"
def connect(self):
# create credentials
password = self.generate_sas_token(self._hostname,
"iothubowner", "key",
time() + 31557600) # ttl = 1 Year
# establish connection
self._blocking_connection =
BlockingConnection(f"amqps://{self._hostname}", allowed_mechs="PLAIN",
user=self._username,
password=password,
heartbeat=30)
self._sender =
self._blocking_connection.create_sender("/messages/devicebound")
def send(self, message: dict, serial_number: str):
message =
Message(address="/devices/{serial_number}/messages/devicebound".format(serial_number=serial_number),
body=bytes(json.dumps(message, separators=(",",
":")), "utf-8"))
message.inferred = True
[jira] [Updated] (PROTON-2044) Azure IoT Hub local-idle-timeout expired
[
https://issues.apache.org/jira/browse/PROTON-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Fendt updated PROTON-2044:
--
Description:
I'm using following python code to send messages to the devices which are
connected to the azure iot hub:
{code:python}
import json
from base64 import b64encode, b64decode
from hashlib import sha256
from hmac import HMAC
from time import time
from urllib.parse import quote_plus, urlencode
from proton import ProtonException, Message
from proton.utils import BlockingConnection
class IotHub:
def __init__(self):
self._hostname = f"example-hub.azure-devices.net"
self._username = f"iothubow...@sas.root.example-hub.azure-devices.net"
self._blocking_connection = None
self._sender = None
self.connect()
@staticmethod
def generate_sas_token(uri: str, policy: str, key: str, expiry: float =
None):
if not expiry:
expiry = time() + 3600 # Default to 1 hour.
encoded_uri = quote_plus(uri)
ttl = int(expiry)
sign_key = f"{encoded_uri}\n{ttl}"
signature = b64encode(HMAC(b64decode(key), sign_key.encode(),
sha256).digest())
result = {"sr": uri, "sig": signature, "se": str(ttl)}
if policy:
result["skn"] = policy
return f"SharedAccessSignature {urlencode(result)}"
def connect(self):
# create credentials
password = self.generate_sas_token(self._hostname,
"iothubowner", "key",
time() + 31557600) # ttl = 1 Year
# establish connection
self._blocking_connection =
BlockingConnection(f"amqps://{self._hostname}", allowed_mechs="PLAIN",
user=self._username,
password=password,
heartbeat=30)
self._sender =
self._blocking_connection.create_sender("/messages/devicebound")
def send(self, message: dict, serial_number: str):
message =
Message(address="/devices/{serial_number}/messages/devicebound".format(serial_number=serial_number),
body=bytes(json.dumps(message, separators=(",",
":")), "utf-8"))
message.inferred = True # disable message encoding
self._sender.send(message, timeout=20)
{code}
The problem is now that when I don't send any message for some seconds I get
following exepction while sending a message:
{code:java}
Connection amqps://example-hub.azure-devices.net:amqps disconnected:
Condition('amqp:resource-limit-exceeded', 'local-idle-timeout expired')
{code}
Whats the reason for that? How can I solve that?
was:
I'm using following python code to send messages to the devices which are
connected to the azure iot hub:
{code:java}
import json
from base64 import b64encode, b64decode
from hashlib import sha256
from hmac import HMAC
from time import time
from urllib.parse import quote_plus, urlencode
from proton import ProtonException, Message
from proton.utils import BlockingConnection
class IotHub:
def __init__(self):
self._hostname = f"example-hub.azure-devices.net"
self._username = f"iothubow...@sas.root.example-hub.azure-devices.net"
self._blocking_connection = None
self._sender = None
self.connect()
@staticmethod
def generate_sas_token(uri: str, policy: str, key: str, expiry: float =
None):
if not expiry:
expiry = time() + 3600 # Default to 1 hour.
encoded_uri = quote_plus(uri)
ttl = int(expiry)
sign_key = f"{encoded_uri}\n{ttl}"
signature = b64encode(HMAC(b64decode(key), sign_key.encode(),
sha256).digest())
result = {"sr": uri, "sig": signature, "se": str(ttl)}
if policy:
result["skn"] = policy
return f"SharedAccessSignature {urlencode(result)}"
def connect(self):
# create credentials
password = self.generate_sas_token(self._hostname,
"iothubowner", "key",
time() + 31557600) # ttl = 1 Year
# establish connection
self._blocking_connection =
BlockingConnection(f"amqps://{self._hostname}", allowed_mechs="PLAIN",
user=self._username,
password=password,
heartbeat=30)
self._sender =
self._blocking_connection.create_sender("/messages/devicebound")
def send(self, message: dict, serial_number: str):
"""
Send proton Message to AMQP queue
"""
message =
Message(address="/devices/{serial_number}/messages/devicebound".format(serial_number=serial_number),
body=bytes(json.dumps(message, separators=(",",
":")), "utf-8"))
[jira] [Created] (PROTON-2044) Azure IoT Hub local-idle-timeout expired
Andreas Fendt created PROTON-2044:
-
Summary: Azure IoT Hub local-idle-timeout expired
Key: PROTON-2044
URL: https://issues.apache.org/jira/browse/PROTON-2044
Project: Qpid Proton
Issue Type: Bug
Components: python-binding
Affects Versions: proton-c-0.24.0
Environment: Operating System: Windows
Python: 3.6.4
qpid-proton: 0.24.0
Reporter: Andreas Fendt
Fix For: proton-c-0.24.0
I'm using following python code to send messages to the devices which are
connected to the azure iot hub:
{code:java}
import json
from base64 import b64encode, b64decode
from hashlib import sha256
from hmac import HMAC
from time import time
from urllib.parse import quote_plus, urlencode
from proton import ProtonException, Message
from proton.utils import BlockingConnection
class IotHub:
def __init__(self):
self._hostname = f"example-hub.azure-devices.net"
self._username = f"iothubow...@sas.root.example-hub.azure-devices.net"
self._blocking_connection = None
self._sender = None
self.connect()
@staticmethod
def generate_sas_token(uri: str, policy: str, key: str, expiry: float =
None):
if not expiry:
expiry = time() + 3600 # Default to 1 hour.
encoded_uri = quote_plus(uri)
ttl = int(expiry)
sign_key = f"{encoded_uri}\n{ttl}"
signature = b64encode(HMAC(b64decode(key), sign_key.encode(),
sha256).digest())
result = {"sr": uri, "sig": signature, "se": str(ttl)}
if policy:
result["skn"] = policy
return f"SharedAccessSignature {urlencode(result)}"
def connect(self):
# create credentials
password = self.generate_sas_token(self._hostname,
"iothubowner", "key",
time() + 31557600) # ttl = 1 Year
# establish connection
self._blocking_connection =
BlockingConnection(f"amqps://{self._hostname}", allowed_mechs="PLAIN",
user=self._username,
password=password,
heartbeat=30)
self._sender =
self._blocking_connection.create_sender("/messages/devicebound")
def send(self, message: dict, serial_number: str):
"""
Send proton Message to AMQP queue
"""
message =
Message(address="/devices/{serial_number}/messages/devicebound".format(serial_number=serial_number),
body=bytes(json.dumps(message, separators=(",",
":")), "utf-8"))
message.inferred = True # disable message encoding
self._sender.send(message, timeout=20)
{code}
The problem is now that when I don't send any message for some seconds I get
following exepction while sending a message:
{code:java}
Connection amqps://example-hub.azure-devices.net:amqps disconnected:
Condition('amqp:resource-limit-exceeded', 'local-idle-timeout expired')
{code}
Whats the reason for that? How can I solve that?
--
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] (PROTON-1870) better logging for ssl
[ https://issues.apache.org/jira/browse/PROTON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835743#comment-16835743 ] Gordon Sim commented on PROTON-1870: A specific example is where the certificate is not valid for the intended use, e.g. its only valid for server not for client. The error you get just says the client certificate verification failed, would be nicer to get more details if possible. > better logging for ssl > -- > > Key: PROTON-1870 > URL: https://issues.apache.org/jira/browse/PROTON-1870 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Gordon Sim >Priority: Major > Labels: logging > > Would be nice to have better logging for ssl connections, particularly where > they fail, e.g. the sni used, the ca the peer cert is signed with etc -- This message was sent by Atlassian JIRA (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-974) Getting connections via the router management protocol causes AMQP framing errors
[
https://issues.apache.org/jira/browse/DISPATCH-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835737#comment-16835737
]
ASF GitHub Bot commented on DISPATCH-974:
-
ganeshmurthy commented on pull request #503: DISPATCH-974 - Added code to
qdstat and qdmanage clients to repeatedl…
URL: https://github.com/apache/qpid-dispatch/pull/503
…y get rows to overcome the limitations imposed by PROTON-1846
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
> Getting connections via the router management protocol causes AMQP framing
> errors
> -
>
> Key: DISPATCH-974
> URL: https://issues.apache.org/jira/browse/DISPATCH-974
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
>Affects Versions: 1.0.1
>Reporter: Marcel Meulemans
>Assignee: Ganesh Murthy
>Priority: Major
> Attachments: qdrouter-frame-errors.pcapng.gz
>
>
> I am running a standalone router with 5000 clients connected. When I try to
> get all connections via qdstat (qdstat --limit 5000 -c) something goes wrong
> (seems to be a framing error). The output from qdstat is:
> {{ MessageException: [-10]: data error: (null)}}
> The problems seems to somehow be related to result size because when I set
> the limit to less I get the list of connections as expected. In my situation
> the critical limit is 3447 (i.e. 3447 result in the expected list of
> connections, 3448 result in the error above). It does not seem to be frame
> size related because getting 3447 connection is already spread over transfer
> frames (256182, 256512 and 159399 bytes).
> The error is not qdstat related because using some plain proton code to
> create a management query results in the same problem. Ultimately the call to
> pn_message_decode with data receive from the router fails (also wireshark can
> not decode the final frame).
> I have attached a wireshark dump to the qdstat session with the router
> ([^qdrouter-frame-errors.pcapng.gz]). The logs of the router (at info level)
> contain no further information.
>
--
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] ganeshmurthy opened a new pull request #503: DISPATCH-974 - Added code to qdstat and qdmanage clients to repeatedl…
ganeshmurthy opened a new pull request #503: DISPATCH-974 - Added code to qdstat and qdmanage clients to repeatedl… URL: https://github.com/apache/qpid-dispatch/pull/503 …y get rows to overcome the limitations imposed by PROTON-1846 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] [Updated] (PROTON-2024) [cpp] [Windows] Json connect config test fails connecting to TLS connections
[ https://issues.apache.org/jira/browse/PROTON-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2024: --- Issue Type: Test (was: Bug) > [cpp] [Windows] Json connect config test fails connecting to TLS connections > > > Key: PROTON-2024 > URL: https://issues.apache.org/jira/browse/PROTON-2024 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Andrew Stitcher >Priority: Major > > This is because the certificate files used in the test aren't varied between > the Unix/Windows test runs. -- 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] (PROTON-2038) [Python] ubyte (and other unsigned types) can hold negative value
[
https://issues.apache.org/jira/browse/PROTON-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-2038:
---
Affects Version/s: proton-c-0.27.1
> [Python] ubyte (and other unsigned types) can hold negative value
> -
>
> Key: PROTON-2038
> URL: https://issues.apache.org/jira/browse/PROTON-2038
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
>Affects Versions: proton-c-0.27.1
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>Priority: Major
> Fix For: proton-c-0.28.0
>
>
> Python representations of:
> proton.ubyte
> proton.ushort
> proton.uint
> proton.ulong
> can hold a negative value, even though they should be unsigned.
> {{import proton}}
> {{print proton.ubyte(-1)}}
> {{print proton.ushort(-1)}}
> {{print proton.uint(-1)}}
> {{print proton.ulong(-1)}}
> results in
> {{-1}}
> {{-1}}
> {{-1}}
> {{-1}}
> If an unsigned type containing a negative value is used in a message in any
> context, it can cause an Overflow exception to be thrown within 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] (PROTON-2028) [c++] Json config connect test gets port too early
[ https://issues.apache.org/jira/browse/PROTON-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2028: --- Issue Type: Test (was: Bug) > [c++] Json config connect test gets port too early > -- > > Key: PROTON-2028 > URL: https://issues.apache.org/jira/browse/PROTON-2028 > Project: Qpid Proton > Issue Type: Test > Components: cpp-binding >Reporter: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.28.0 > > > Instead of waiting for the bind to finish it tries to get the port > immediately. This works using the epoll/iocp proactors, but not the libuv > proactor. -- 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] (DISPATCH-1265) Delivery_abort test causes inter-router session error
[ https://issues.apache.org/jira/browse/DISPATCH-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated DISPATCH-1265: - Fix Version/s: (was: 1.7.0) 1.8.0 > Delivery_abort test causes inter-router session error > - > > Key: DISPATCH-1265 > URL: https://issues.apache.org/jira/browse/DISPATCH-1265 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.5.0 > Environment: Fedora 29, Python 3. > branch DISPATCH-1264#a5aab9 > ctest -VV -R system_tests_delivery_abort >Reporter: Chuck Rolke >Assignee: Ganesh Murthy >Priority: Critical > Fix For: 1.8.0 > > Attachments: DISPATCH-1265_ctest-log.txt, > DISPATCH-1265_scraped-logs-timeout.html > > > Inter-router connection closes with: > error :"amqp:session:invalid-field" "sequencing error, expected delivery-id > 24, got 23" -- 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] (DISPATCH-1333) Console test fails printing to file with python 3
[
https://issues.apache.org/jira/browse/DISPATCH-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated DISPATCH-1333:
--
Attachment: run_console_test.out.txt
> Console test fails printing to file with python 3
> -
>
> Key: DISPATCH-1333
> URL: https://issues.apache.org/jira/browse/DISPATCH-1333
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.7.0
> Environment: Fedora 29, Python 3, proton and dispatch master branches
>Reporter: Chuck Rolke
>Priority: Major
> Attachments: console-test.patch, run_console_test.out.txt
>
>
> {code:java}
> test 53
> Start 53: system_tests_console
> 53: Test command: /bin/python
> "/home/chug/git/qpid-dispatch/build/tests/run.py" "unit2" "-v"
> "system_tests_console"
> 53: Test timeout computed to be: 1500
> 53: test_console (system_tests_console.ConsoleTest) ... ERROR
> 53:
> 53: ==
> 53: ERROR: test_console (system_tests_console.ConsoleTest)
> 53: --
> 53: Traceback (most recent call last):
> 53: File "/home/chug/git/qpid-dispatch/tests/system_test.py", line 706, in
> wrap
> 53: return f(*args, **kwargs)
> 53: File "/home/chug/git/qpid-dispatch/tests/system_tests_console.py", line
> 132, in test_console
> 53: self.run_console_test()
> 53: File "/home/chug/git/qpid-dispatch/tests/system_tests_console.py", line
> 116, in run_console_test
> 53: popenfile.writelines(out)
> 53: TypeError: write() argument must be str, not int
> 53:
> 53: --
> 53: Ran 1 test in 0.959s
> 53:
> 53: FAILED (errors=1)
> 1/1 Test #53: system_tests_console .***Failed 1.63 sec
> 0% tests passed, 1 tests failed out of 1
> {code}
> The test passes with the attached patch.
> The content of the failed printout is attached.
>
>
--
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] (DISPATCH-1333) Console test fails printing to file with python 3
[
https://issues.apache.org/jira/browse/DISPATCH-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated DISPATCH-1333:
--
Attachment: (was: run_console_test.out)
> Console test fails printing to file with python 3
> -
>
> Key: DISPATCH-1333
> URL: https://issues.apache.org/jira/browse/DISPATCH-1333
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.7.0
> Environment: Fedora 29, Python 3, proton and dispatch master branches
>Reporter: Chuck Rolke
>Priority: Major
> Attachments: console-test.patch, run_console_test.out.txt
>
>
> {code:java}
> test 53
> Start 53: system_tests_console
> 53: Test command: /bin/python
> "/home/chug/git/qpid-dispatch/build/tests/run.py" "unit2" "-v"
> "system_tests_console"
> 53: Test timeout computed to be: 1500
> 53: test_console (system_tests_console.ConsoleTest) ... ERROR
> 53:
> 53: ==
> 53: ERROR: test_console (system_tests_console.ConsoleTest)
> 53: --
> 53: Traceback (most recent call last):
> 53: File "/home/chug/git/qpid-dispatch/tests/system_test.py", line 706, in
> wrap
> 53: return f(*args, **kwargs)
> 53: File "/home/chug/git/qpid-dispatch/tests/system_tests_console.py", line
> 132, in test_console
> 53: self.run_console_test()
> 53: File "/home/chug/git/qpid-dispatch/tests/system_tests_console.py", line
> 116, in run_console_test
> 53: popenfile.writelines(out)
> 53: TypeError: write() argument must be str, not int
> 53:
> 53: --
> 53: Ran 1 test in 0.959s
> 53:
> 53: FAILED (errors=1)
> 1/1 Test #53: system_tests_console .***Failed 1.63 sec
> 0% tests passed, 1 tests failed out of 1
> {code}
> The test passes with the attached patch.
> The content of the failed printout is attached.
>
>
--
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] (DISPATCH-1333) Console test fails printing to file with python 3
[
https://issues.apache.org/jira/browse/DISPATCH-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated DISPATCH-1333:
--
Attachment: run_console_test.out
> Console test fails printing to file with python 3
> -
>
> Key: DISPATCH-1333
> URL: https://issues.apache.org/jira/browse/DISPATCH-1333
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.7.0
> Environment: Fedora 29, Python 3, proton and dispatch master branches
>Reporter: Chuck Rolke
>Priority: Major
> Attachments: console-test.patch, run_console_test.out
>
>
> {code:java}
> test 53
> Start 53: system_tests_console
> 53: Test command: /bin/python
> "/home/chug/git/qpid-dispatch/build/tests/run.py" "unit2" "-v"
> "system_tests_console"
> 53: Test timeout computed to be: 1500
> 53: test_console (system_tests_console.ConsoleTest) ... ERROR
> 53:
> 53: ==
> 53: ERROR: test_console (system_tests_console.ConsoleTest)
> 53: --
> 53: Traceback (most recent call last):
> 53: File "/home/chug/git/qpid-dispatch/tests/system_test.py", line 706, in
> wrap
> 53: return f(*args, **kwargs)
> 53: File "/home/chug/git/qpid-dispatch/tests/system_tests_console.py", line
> 132, in test_console
> 53: self.run_console_test()
> 53: File "/home/chug/git/qpid-dispatch/tests/system_tests_console.py", line
> 116, in run_console_test
> 53: popenfile.writelines(out)
> 53: TypeError: write() argument must be str, not int
> 53:
> 53: --
> 53: Ran 1 test in 0.959s
> 53:
> 53: FAILED (errors=1)
> 1/1 Test #53: system_tests_console .***Failed 1.63 sec
> 0% tests passed, 1 tests failed out of 1
> {code}
> The test passes with the attached patch.
> The content of the failed printout is attached.
>
>
--
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] (DISPATCH-1333) Console test fails printing to file with python 3
[
https://issues.apache.org/jira/browse/DISPATCH-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke updated DISPATCH-1333:
--
Attachment: console-test.patch
> Console test fails printing to file with python 3
> -
>
> Key: DISPATCH-1333
> URL: https://issues.apache.org/jira/browse/DISPATCH-1333
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.7.0
> Environment: Fedora 29, Python 3, proton and dispatch master branches
>Reporter: Chuck Rolke
>Priority: Major
> Attachments: console-test.patch
>
>
> {code:java}
> test 53
> Start 53: system_tests_console
> 53: Test command: /bin/python
> "/home/chug/git/qpid-dispatch/build/tests/run.py" "unit2" "-v"
> "system_tests_console"
> 53: Test timeout computed to be: 1500
> 53: test_console (system_tests_console.ConsoleTest) ... ERROR
> 53:
> 53: ==
> 53: ERROR: test_console (system_tests_console.ConsoleTest)
> 53: --
> 53: Traceback (most recent call last):
> 53: File "/home/chug/git/qpid-dispatch/tests/system_test.py", line 706, in
> wrap
> 53: return f(*args, **kwargs)
> 53: File "/home/chug/git/qpid-dispatch/tests/system_tests_console.py", line
> 132, in test_console
> 53: self.run_console_test()
> 53: File "/home/chug/git/qpid-dispatch/tests/system_tests_console.py", line
> 116, in run_console_test
> 53: popenfile.writelines(out)
> 53: TypeError: write() argument must be str, not int
> 53:
> 53: --
> 53: Ran 1 test in 0.959s
> 53:
> 53: FAILED (errors=1)
> 1/1 Test #53: system_tests_console .***Failed 1.63 sec
> 0% tests passed, 1 tests failed out of 1
> {code}
> The test passes with the attached patch.
> The content of the failed printout is attached.
>
>
--
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-1333) Console test fails printing to file with python 3
Chuck Rolke created DISPATCH-1333:
-
Summary: Console test fails printing to file with python 3
Key: DISPATCH-1333
URL: https://issues.apache.org/jira/browse/DISPATCH-1333
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.7.0
Environment: Fedora 29, Python 3, proton and dispatch master branches
Reporter: Chuck Rolke
Attachments: console-test.patch
{code:java}
test 53
Start 53: system_tests_console
53: Test command: /bin/python "/home/chug/git/qpid-dispatch/build/tests/run.py"
"unit2" "-v" "system_tests_console"
53: Test timeout computed to be: 1500
53: test_console (system_tests_console.ConsoleTest) ... ERROR
53:
53: ==
53: ERROR: test_console (system_tests_console.ConsoleTest)
53: --
53: Traceback (most recent call last):
53: File "/home/chug/git/qpid-dispatch/tests/system_test.py", line 706, in
wrap
53: return f(*args, **kwargs)
53: File "/home/chug/git/qpid-dispatch/tests/system_tests_console.py", line
132, in test_console
53: self.run_console_test()
53: File "/home/chug/git/qpid-dispatch/tests/system_tests_console.py", line
116, in run_console_test
53: popenfile.writelines(out)
53: TypeError: write() argument must be str, not int
53:
53: --
53: Ran 1 test in 0.959s
53:
53: FAILED (errors=1)
1/1 Test #53: system_tests_console .***Failed 1.63 sec
0% tests passed, 1 tests failed out of 1
{code}
The test passes with the attached patch.
The content of the failed printout is attached.
--
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] (PROTON-2043) update to apache parent pom v21
[ https://issues.apache.org/jira/browse/PROTON-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2043: --- Priority: Minor (was: Major) > update to apache parent pom v21 > --- > > Key: PROTON-2043 > URL: https://issues.apache.org/jira/browse/PROTON-2043 > Project: Qpid Proton > Issue Type: Task > Components: proton-j >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: proton-j-0.34.0 > > > update to apache parent pom v21 -- 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] [Resolved] (PROTON-2043) update to apache parent pom v21
[ https://issues.apache.org/jira/browse/PROTON-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-2043. Resolution: Fixed > update to apache parent pom v21 > --- > > Key: PROTON-2043 > URL: https://issues.apache.org/jira/browse/PROTON-2043 > Project: Qpid Proton > Issue Type: Task > Components: proton-j >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Minor > Fix For: proton-j-0.34.0 > > > update to apache parent pom v21 -- 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-1326) Anonymous messages are released by edge router even if there is a receiver for the messages
[
https://issues.apache.org/jira/browse/DISPATCH-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835624#comment-16835624
]
ASF subversion and git services commented on DISPATCH-1326:
---
Commit 9dbb4c5de6ff2c73ef84b2126e1f7aaf7a2272f8 in qpid-dispatch's branch
refs/heads/master from Ganesh Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=9dbb4c5 ]
DISPATCH-1326 - Additional fix to initialize the temp_link object. This caused
a crash
> Anonymous messages are released by edge router even if there is a receiver
> for the messages
> ---
>
> Key: DISPATCH-1326
> URL: https://issues.apache.org/jira/browse/DISPATCH-1326
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.5.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.8.0
>
> Attachments: E1.conf, I1.conf, simple_send_anon.py
>
>
> Steps to reproduce
> # Start one interior router and one edge router using the attached config
> files
> # Start a receiver using simple_recv.py and connect it to the interior router
> ##
> {noformat}
> python simple_recv.py -m1 --address 0.0.0.0:8/examples{noformat}
> # Use the attached sender to send an anonymous message to the edge router
> ##
> {noformat}
> python simple_send_anon.py --address 0.0.0.0:5672 -m1{noformat}
> # The message must travel from the edge router to the interior router which
> in turn must forward it to the receiver. Instead the message is released as
> seen in the below frame trace.
>
> {noformat}
> [0x5603df87eb20]: -> SASL
> [0x5603df87eb20]: <- SASL
> [0x5603df87eb20]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x5603df87eb20]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"anonymous@localhost.localdomain"]
> [0x5603df87eb20]:0 <- @sasl-outcome(68) [code=0]
> [0x5603df87eb20]: -> AMQP
> [0x5603df87eb20]:0 -> @open(16)
> [container-id="c99c4867-447c-424a-8b4f-e8a406c71a57", hostname="0.0.0.0",
> channel-max=32767]
> [0x5603df87eb20]:0 -> @begin(17) [next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x5603df87eb20]:0 -> @attach(18)
> [name="c99c4867-447c-424a-8b4f-e8a406c71a57-8db0b3b7-ffde-4c99-9d99-ee8f3c0d9efd",
> handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [durable=0, timeout=0, dynamic=false], target=@target(41)
> [durable=0, timeout=0, dynamic=false], initial-delivery-count=0,
> max-message-size=0]
> [0x5603df87eb20]: <- AMQP
> [0x5603df87eb20]:0 <- @open(16) [container-id="Edge_66t2+y4DnWql1Vx",
> max-frame-size=16384, channel-max=32767, idle-time-out=8000,
> offered-capabilities=:"ANONYMOUS-RELAY",
> properties={:product="qpid-dispatch-router", :version="1.8.0-SNAPSHOT",
> :"qd.conn-id"=7}]
> [0x5603df87eb20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x5603df87eb20]:0 <- @attach(18)
> [name="c99c4867-447c-424a-8b4f-e8a406c71a57-8db0b3b7-ffde-4c99-9d99-ee8f3c0d9efd",
> handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [durable=0, expiry-policy=:"session-end", timeout=0,
> dynamic=false], target=@target(41) [durable=0, expiry-policy=:"session-end",
> timeout=0, dynamic=false], initial-delivery-count=0, max-message-size=0]
> [0x5603df87eb20]:0 <- @flow(19) [next-incoming-id=0,
> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
> handle=0, delivery-count=0, link-credit=250, drain=false]
> [0x5603df87eb20]:0 -> @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"1", message-format=0] (53)
> "\x00SpE\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x03S\x01@\xa1\x08examples\x00Sw\xd1\x00\x00\x00\x10\x00\x00\x00\x02\xa1\x08sequenceT\x01"
> [0x5603df87eb20]:0 <- @flow(19) [next-incoming-id=1,
> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
> handle=0, delivery-count=1, link-credit=250, drain=false]
> [0x5603df87eb20]:0 <- @disposition(21) [role=true, first=0, settled=true,
> state=@released(38) []]
> [0x5603df87eb20]:0 -> (EMPTY FRAME)
> [0x5603df87eb20]:0 -> (EMPTY FRAME)
> ^C[gmurthy@localhost examples]$
> {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] (PROTON-2043) update to apache parent pom v21
[ https://issues.apache.org/jira/browse/PROTON-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835619#comment-16835619 ] ASF subversion and git services commented on PROTON-2043: - Commit 1ef7bbda567bf30be47678660aaf9efee021feb5 in qpid-proton-j's branch refs/heads/master from Robert Gemmell [ https://gitbox.apache.org/repos/asf?p=qpid-proton-j.git;h=1ef7bbd ] PROTON-2043: update to apache parent pom v21 > update to apache parent pom v21 > --- > > Key: PROTON-2043 > URL: https://issues.apache.org/jira/browse/PROTON-2043 > Project: Qpid Proton > Issue Type: Task > Components: proton-j >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-j-0.34.0 > > > update to apache parent pom v21 -- 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] (PROTON-2043) update to apache parent pom v21
[ https://issues.apache.org/jira/browse/PROTON-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2043: --- Description: update to apache parent pom v21 (was: h1. update to apache parent pom v21) > update to apache parent pom v21 > --- > > Key: PROTON-2043 > URL: https://issues.apache.org/jira/browse/PROTON-2043 > Project: Qpid Proton > Issue Type: Task > Components: proton-j >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-j-0.34.0 > > > update to apache parent pom v21 -- 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] (PROTON-2043) update to apache parent pom v21
Robbie Gemmell created PROTON-2043: -- Summary: update to apache parent pom v21 Key: PROTON-2043 URL: https://issues.apache.org/jira/browse/PROTON-2043 Project: Qpid Proton Issue Type: Task Components: proton-j Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: proton-j-0.34.0 h1. update to apache parent pom v21 -- 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] [Resolved] (DISPATCH-1326) Anonymous messages are released by edge router even if there is a receiver for the messages
[
https://issues.apache.org/jira/browse/DISPATCH-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1326.
-
Resolution: Fixed
Fix Version/s: 1.8.0
> Anonymous messages are released by edge router even if there is a receiver
> for the messages
> ---
>
> Key: DISPATCH-1326
> URL: https://issues.apache.org/jira/browse/DISPATCH-1326
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.5.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.8.0
>
> Attachments: E1.conf, I1.conf, simple_send_anon.py
>
>
> Steps to reproduce
> # Start one interior router and one edge router using the attached config
> files
> # Start a receiver using simple_recv.py and connect it to the interior router
> ##
> {noformat}
> python simple_recv.py -m1 --address 0.0.0.0:8/examples{noformat}
> # Use the attached sender to send an anonymous message to the edge router
> ##
> {noformat}
> python simple_send_anon.py --address 0.0.0.0:5672 -m1{noformat}
> # The message must travel from the edge router to the interior router which
> in turn must forward it to the receiver. Instead the message is released as
> seen in the below frame trace.
>
> {noformat}
> [0x5603df87eb20]: -> SASL
> [0x5603df87eb20]: <- SASL
> [0x5603df87eb20]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x5603df87eb20]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"anonymous@localhost.localdomain"]
> [0x5603df87eb20]:0 <- @sasl-outcome(68) [code=0]
> [0x5603df87eb20]: -> AMQP
> [0x5603df87eb20]:0 -> @open(16)
> [container-id="c99c4867-447c-424a-8b4f-e8a406c71a57", hostname="0.0.0.0",
> channel-max=32767]
> [0x5603df87eb20]:0 -> @begin(17) [next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x5603df87eb20]:0 -> @attach(18)
> [name="c99c4867-447c-424a-8b4f-e8a406c71a57-8db0b3b7-ffde-4c99-9d99-ee8f3c0d9efd",
> handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [durable=0, timeout=0, dynamic=false], target=@target(41)
> [durable=0, timeout=0, dynamic=false], initial-delivery-count=0,
> max-message-size=0]
> [0x5603df87eb20]: <- AMQP
> [0x5603df87eb20]:0 <- @open(16) [container-id="Edge_66t2+y4DnWql1Vx",
> max-frame-size=16384, channel-max=32767, idle-time-out=8000,
> offered-capabilities=:"ANONYMOUS-RELAY",
> properties={:product="qpid-dispatch-router", :version="1.8.0-SNAPSHOT",
> :"qd.conn-id"=7}]
> [0x5603df87eb20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x5603df87eb20]:0 <- @attach(18)
> [name="c99c4867-447c-424a-8b4f-e8a406c71a57-8db0b3b7-ffde-4c99-9d99-ee8f3c0d9efd",
> handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [durable=0, expiry-policy=:"session-end", timeout=0,
> dynamic=false], target=@target(41) [durable=0, expiry-policy=:"session-end",
> timeout=0, dynamic=false], initial-delivery-count=0, max-message-size=0]
> [0x5603df87eb20]:0 <- @flow(19) [next-incoming-id=0,
> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
> handle=0, delivery-count=0, link-credit=250, drain=false]
> [0x5603df87eb20]:0 -> @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"1", message-format=0] (53)
> "\x00SpE\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x03S\x01@\xa1\x08examples\x00Sw\xd1\x00\x00\x00\x10\x00\x00\x00\x02\xa1\x08sequenceT\x01"
> [0x5603df87eb20]:0 <- @flow(19) [next-incoming-id=1,
> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
> handle=0, delivery-count=1, link-credit=250, drain=false]
> [0x5603df87eb20]:0 <- @disposition(21) [role=true, first=0, settled=true,
> state=@released(38) []]
> [0x5603df87eb20]:0 -> (EMPTY FRAME)
> [0x5603df87eb20]:0 -> (EMPTY FRAME)
> ^C[gmurthy@localhost examples]$
> {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] (DISPATCH-1326) Anonymous messages are released by edge router even if there is a receiver for the messages
[
https://issues.apache.org/jira/browse/DISPATCH-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835593#comment-16835593
]
ASF GitHub Bot commented on DISPATCH-1326:
--
asfgit commented on pull request #502: DISPATCH-1326 - Handling of anonymous
messages sent to edge routers. …
URL: https://github.com/apache/qpid-dispatch/pull/502
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
> Anonymous messages are released by edge router even if there is a receiver
> for the messages
> ---
>
> Key: DISPATCH-1326
> URL: https://issues.apache.org/jira/browse/DISPATCH-1326
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.5.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Attachments: E1.conf, I1.conf, simple_send_anon.py
>
>
> Steps to reproduce
> # Start one interior router and one edge router using the attached config
> files
> # Start a receiver using simple_recv.py and connect it to the interior router
> ##
> {noformat}
> python simple_recv.py -m1 --address 0.0.0.0:8/examples{noformat}
> # Use the attached sender to send an anonymous message to the edge router
> ##
> {noformat}
> python simple_send_anon.py --address 0.0.0.0:5672 -m1{noformat}
> # The message must travel from the edge router to the interior router which
> in turn must forward it to the receiver. Instead the message is released as
> seen in the below frame trace.
>
> {noformat}
> [0x5603df87eb20]: -> SASL
> [0x5603df87eb20]: <- SASL
> [0x5603df87eb20]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x5603df87eb20]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"anonymous@localhost.localdomain"]
> [0x5603df87eb20]:0 <- @sasl-outcome(68) [code=0]
> [0x5603df87eb20]: -> AMQP
> [0x5603df87eb20]:0 -> @open(16)
> [container-id="c99c4867-447c-424a-8b4f-e8a406c71a57", hostname="0.0.0.0",
> channel-max=32767]
> [0x5603df87eb20]:0 -> @begin(17) [next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x5603df87eb20]:0 -> @attach(18)
> [name="c99c4867-447c-424a-8b4f-e8a406c71a57-8db0b3b7-ffde-4c99-9d99-ee8f3c0d9efd",
> handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [durable=0, timeout=0, dynamic=false], target=@target(41)
> [durable=0, timeout=0, dynamic=false], initial-delivery-count=0,
> max-message-size=0]
> [0x5603df87eb20]: <- AMQP
> [0x5603df87eb20]:0 <- @open(16) [container-id="Edge_66t2+y4DnWql1Vx",
> max-frame-size=16384, channel-max=32767, idle-time-out=8000,
> offered-capabilities=:"ANONYMOUS-RELAY",
> properties={:product="qpid-dispatch-router", :version="1.8.0-SNAPSHOT",
> :"qd.conn-id"=7}]
> [0x5603df87eb20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x5603df87eb20]:0 <- @attach(18)
> [name="c99c4867-447c-424a-8b4f-e8a406c71a57-8db0b3b7-ffde-4c99-9d99-ee8f3c0d9efd",
> handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [durable=0, expiry-policy=:"session-end", timeout=0,
> dynamic=false], target=@target(41) [durable=0, expiry-policy=:"session-end",
> timeout=0, dynamic=false], initial-delivery-count=0, max-message-size=0]
> [0x5603df87eb20]:0 <- @flow(19) [next-incoming-id=0,
> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
> handle=0, delivery-count=0, link-credit=250, drain=false]
> [0x5603df87eb20]:0 -> @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"1", message-format=0] (53)
> "\x00SpE\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x03S\x01@\xa1\x08examples\x00Sw\xd1\x00\x00\x00\x10\x00\x00\x00\x02\xa1\x08sequenceT\x01"
> [0x5603df87eb20]:0 <- @flow(19) [next-incoming-id=1,
> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
> handle=0, delivery-count=1, link-credit=250, drain=false]
> [0x5603df87eb20]:0 <- @disposition(21) [role=true, first=0, settled=true,
> state=@released(38) []]
> [0x5603df87eb20]:0 -> (EMPTY FRAME)
> [0x5603df87eb20]:0 -> (EMPTY FRAME)
> ^C[gmurthy@localhost examples]$
> {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] (DISPATCH-1326) Anonymous messages are released by edge router even if there is a receiver for the messages
[
https://issues.apache.org/jira/browse/DISPATCH-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835592#comment-16835592
]
ASF subversion and git services commented on DISPATCH-1326:
---
Commit fa1b167dcf1e77a40f9fcb5bba3074a698b6a6ab in qpid-dispatch's branch
refs/heads/master from Ganesh Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=fa1b167 ]
DISPATCH-1326 - Handling of anonymous messages sent to edge routers. Added
small message and large message tests. This closes #502
> Anonymous messages are released by edge router even if there is a receiver
> for the messages
> ---
>
> Key: DISPATCH-1326
> URL: https://issues.apache.org/jira/browse/DISPATCH-1326
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 1.5.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Attachments: E1.conf, I1.conf, simple_send_anon.py
>
>
> Steps to reproduce
> # Start one interior router and one edge router using the attached config
> files
> # Start a receiver using simple_recv.py and connect it to the interior router
> ##
> {noformat}
> python simple_recv.py -m1 --address 0.0.0.0:8/examples{noformat}
> # Use the attached sender to send an anonymous message to the edge router
> ##
> {noformat}
> python simple_send_anon.py --address 0.0.0.0:5672 -m1{noformat}
> # The message must travel from the edge router to the interior router which
> in turn must forward it to the receiver. Instead the message is released as
> seen in the below frame trace.
>
> {noformat}
> [0x5603df87eb20]: -> SASL
> [0x5603df87eb20]: <- SASL
> [0x5603df87eb20]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x5603df87eb20]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
> initial-response=b"anonymous@localhost.localdomain"]
> [0x5603df87eb20]:0 <- @sasl-outcome(68) [code=0]
> [0x5603df87eb20]: -> AMQP
> [0x5603df87eb20]:0 -> @open(16)
> [container-id="c99c4867-447c-424a-8b4f-e8a406c71a57", hostname="0.0.0.0",
> channel-max=32767]
> [0x5603df87eb20]:0 -> @begin(17) [next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x5603df87eb20]:0 -> @attach(18)
> [name="c99c4867-447c-424a-8b4f-e8a406c71a57-8db0b3b7-ffde-4c99-9d99-ee8f3c0d9efd",
> handle=0, role=false, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [durable=0, timeout=0, dynamic=false], target=@target(41)
> [durable=0, timeout=0, dynamic=false], initial-delivery-count=0,
> max-message-size=0]
> [0x5603df87eb20]: <- AMQP
> [0x5603df87eb20]:0 <- @open(16) [container-id="Edge_66t2+y4DnWql1Vx",
> max-frame-size=16384, channel-max=32767, idle-time-out=8000,
> offered-capabilities=:"ANONYMOUS-RELAY",
> properties={:product="qpid-dispatch-router", :version="1.8.0-SNAPSHOT",
> :"qd.conn-id"=7}]
> [0x5603df87eb20]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x5603df87eb20]:0 <- @attach(18)
> [name="c99c4867-447c-424a-8b4f-e8a406c71a57-8db0b3b7-ffde-4c99-9d99-ee8f3c0d9efd",
> handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0,
> source=@source(40) [durable=0, expiry-policy=:"session-end", timeout=0,
> dynamic=false], target=@target(41) [durable=0, expiry-policy=:"session-end",
> timeout=0, dynamic=false], initial-delivery-count=0, max-message-size=0]
> [0x5603df87eb20]:0 <- @flow(19) [next-incoming-id=0,
> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
> handle=0, delivery-count=0, link-credit=250, drain=false]
> [0x5603df87eb20]:0 -> @transfer(20) [handle=0, delivery-id=0,
> delivery-tag=b"1", message-format=0] (53)
> "\x00SpE\x00Ss\xd0\x00\x00\x00\x11\x00\x00\x00\x03S\x01@\xa1\x08examples\x00Sw\xd1\x00\x00\x00\x10\x00\x00\x00\x02\xa1\x08sequenceT\x01"
> [0x5603df87eb20]:0 <- @flow(19) [next-incoming-id=1,
> incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
> handle=0, delivery-count=1, link-credit=250, drain=false]
> [0x5603df87eb20]:0 <- @disposition(21) [role=true, first=0, settled=true,
> state=@released(38) []]
> [0x5603df87eb20]:0 -> (EMPTY FRAME)
> [0x5603df87eb20]:0 -> (EMPTY FRAME)
> ^C[gmurthy@localhost examples]$
> {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
[GitHub] [qpid-dispatch] asfgit closed pull request #502: DISPATCH-1326 - Handling of anonymous messages sent to edge routers. …
asfgit closed pull request #502: DISPATCH-1326 - Handling of anonymous messages sent to edge routers. … URL: https://github.com/apache/qpid-dispatch/pull/502 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] [Assigned] (DISPATCH-974) Getting connections via the router management protocol causes AMQP framing errors
[
https://issues.apache.org/jira/browse/DISPATCH-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-974:
--
Assignee: Ganesh Murthy
> Getting connections via the router management protocol causes AMQP framing
> errors
> -
>
> Key: DISPATCH-974
> URL: https://issues.apache.org/jira/browse/DISPATCH-974
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
>Affects Versions: 1.0.1
>Reporter: Marcel Meulemans
>Assignee: Ganesh Murthy
>Priority: Major
> Attachments: qdrouter-frame-errors.pcapng.gz
>
>
> I am running a standalone router with 5000 clients connected. When I try to
> get all connections via qdstat (qdstat --limit 5000 -c) something goes wrong
> (seems to be a framing error). The output from qdstat is:
> {{ MessageException: [-10]: data error: (null)}}
> The problems seems to somehow be related to result size because when I set
> the limit to less I get the list of connections as expected. In my situation
> the critical limit is 3447 (i.e. 3447 result in the expected list of
> connections, 3448 result in the error above). It does not seem to be frame
> size related because getting 3447 connection is already spread over transfer
> frames (256182, 256512 and 159399 bytes).
> The error is not qdstat related because using some plain proton code to
> create a management query results in the same problem. Ultimately the call to
> pn_message_decode with data receive from the router fails (also wireshark can
> not decode the final frame).
> I have attached a wireshark dump to the qdstat session with the router
> ([^qdrouter-frame-errors.pcapng.gz]). The logs of the router (at info level)
> contain no further information.
>
--
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] (DISPATCH-999) error querying large number of addresses with qdmanage
[ https://issues.apache.org/jira/browse/DISPATCH-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-999: -- Assignee: Ganesh Murthy > error querying large number of addresses with qdmanage > -- > > Key: DISPATCH-999 > URL: https://issues.apache.org/jira/browse/DISPATCH-999 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Gordon Sim >Assignee: Ganesh Murthy >Priority: Major > > Create 1 addresses on a router then try and run: > qdmanage QUERY --type=address > against it. Get following error: > MessageException: [-10]: data error: (null) > This appears to be a decode error in proton-c. The message is received in > several transfer fragments. -- 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] [Resolved] (QPIDJMS-456) update to apache parent pom v21
[ https://issues.apache.org/jira/browse/QPIDJMS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPIDJMS-456. Resolution: Fixed > update to apache parent pom v21 > --- > > Key: QPIDJMS-456 > URL: https://issues.apache.org/jira/browse/QPIDJMS-456 > Project: Qpid JMS > Issue Type: Task > Components: qpid-jms-client >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 0.43.0 > > > update to apache parent pom v21 -- 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] (QPIDJMS-456) update to apache parent pom v21
[ https://issues.apache.org/jira/browse/QPIDJMS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835537#comment-16835537 ] ASF subversion and git services commented on QPIDJMS-456: - Commit 055865320eadb189c562ba02cd6d582e8e22e4bd in qpid-jms's branch refs/heads/master from Robert Gemmell [ https://gitbox.apache.org/repos/asf?p=qpid-jms.git;h=0558653 ] QPIDJMS-456: update to apache parent pom v21 > update to apache parent pom v21 > --- > > Key: QPIDJMS-456 > URL: https://issues.apache.org/jira/browse/QPIDJMS-456 > Project: Qpid JMS > Issue Type: Task > Components: qpid-jms-client >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: 0.43.0 > > > update to apache parent pom v21 -- 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
