[jira] [Updated] (PROTON-1507) 4 local-loopback connections happen which Proton reactor runs

[ https://issues.apache.org/jira/browse/PROTON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anil Hashia updated PROTON-1507: Description: Use Azure IoT Java client SDK sample which references proton library for AMQP. As

[jira] [Created] (PROTON-1507) 4 local-loopback connections happen which Proton reactor runs

Anil Hashia created PROTON-1507: --- Summary: 4 local-loopback connections happen which Proton reactor runs Key: PROTON-1507 URL: https://issues.apache.org/jira/browse/PROTON-1507 Project: Qpid Proton

[jira] [Updated] (PROTON-1507) 4 local-loopback connections happen when Proton reactor runs

[ https://issues.apache.org/jira/browse/PROTON-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anil Hashia updated PROTON-1507: Summary: 4 local-loopback connections happen when Proton reactor runs (was: 4 local-loopback

[jira] [Created] (DISPATCH-790) The right-mouse-click menu on Topology tab appears off-center in the stand-alone console

Jiri Danek created DISPATCH-790: --- Summary: The right-mouse-click menu on Topology tab appears off-center in the stand-alone console Key: DISPATCH-790 URL: https://issues.apache.org/jira/browse/DISPATCH-790

[jira] [Updated] (DISPATCH-791) The node representing Console in Topology tab is not displayed

[ https://issues.apache.org/jira/browse/DISPATCH-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-791: Description: Both hawtio and stand-alone versions are affected. Issue was observed in Chrome and

[jira] [Updated] (DISPATCH-789) Console breaks when quickly moving between tabs (both hawtio and stand-alone)

[ https://issues.apache.org/jira/browse/DISPATCH-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-789: Description: If I open Dispatch plugin, log in, and quickly switch between tabs in Dispatch

[jira] [Updated] (DISPATCH-790) The right-mouse-click menu on Topology tab appears off-center in the stand-alone console

[ https://issues.apache.org/jira/browse/DISPATCH-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-790: Description: The hawtio version of console is not affected. See

[jira] [Created] (DISPATCH-789) Console breaks when quickly moving between tabs (both hawtio and stand-alone)

Jiri Danek created DISPATCH-789: --- Summary: Console breaks when quickly moving between tabs (both hawtio and stand-alone) Key: DISPATCH-789 URL: https://issues.apache.org/jira/browse/DISPATCH-789

[jira] [Created] (DISPATCH-791) The node representing Console in Topology tab is not displayed

Jiri Danek created DISPATCH-791: --- Summary: The node representing Console in Topology tab is not displayed Key: DISPATCH-791 URL: https://issues.apache.org/jira/browse/DISPATCH-791 Project: Qpid

[jira] [Updated] (DISPATCH-791) The node representing Console in Topology tab is not displayed

[ https://issues.apache.org/jira/browse/DISPATCH-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-791: Description: Both hawtio and stand-alone versions are affected. Issue was observed in Chrome and

Re: Proposal to create Docker images for Qpid components.

It was talking about downloading the built Java broker binary release tar.gz, verifying it, and doing something with it. It wasn't saying anything in particular about the OS, except there is one and Java is available somehow. For example, some randomly selected 'docker official' images I looked

Re: Proposal to create Docker images for Qpid components.

Re: "it doesnt seem unusual to have a Dockerfile set up to pull the existing binary release archive, verify its sigs, and extract+configure it in an appropriate location." Yes, it's certainly not unusual, but my personal view is that it isn't great practice. As I said in my earlier reply to

Re: QPID 0.32 going out of memory

Akhil, You should be aware that the 0.32 version of the Qpid Java Broker was affected by a number of CVEs. See Apache Qpid's Security page for information. https://qpid.apache.org/components/java-broker/security.html You ought to be planning to upgrade to a newer version. You get get the

Re: Proposal to create Docker images for Qpid components.

On Mon, 2017-06-19 at 13:16 +0100, Robbie Gemmell wrote: > - To the comments around the Java broker, I don't think creating > packages for it is really necessary? From a quick look at some others > images it doesnt seem unusual to have a Dockerfile set up to pull the > existing binary release

[jira] [Closed] (DISPATCH-762) Hawtio console does not show details about a connection whereas stand-alone console does

[ https://issues.apache.org/jira/browse/DISPATCH-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek closed DISPATCH-762. --- Works for me in build from master, commit e22091b3 > Hawtio console does not show details about a

Re: Proposal to create Docker images for Qpid components.

So, stepping back for a second, which components do we think we should be releasing docker images for (and once we've agreed on this we can agree on the number/form of images for each component perhaps :-) )? -- Rob On 20 June 2017 at 14:06, Robbie Gemmell wrote: > It

[jira] [Commented] (PROTON-1500) Allow plugin SASL implementations

[ https://issues.apache.org/jira/browse/PROTON-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055737#comment-16055737 ] ASF GitHub Bot commented on PROTON-1500: Github user astitcher closed the pull request at:

[jira] [Commented] (QPID-7791) Recover metadata into direct memory

[ https://issues.apache.org/jira/browse/QPID-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055742#comment-16055742 ] ASF subversion and git services commented on QPID-7791: --- Commit

[jira] [Closed] (DISPATCH-753) Neither version of console is usable on Internet Explorer 10 or 11

[ https://issues.apache.org/jira/browse/DISPATCH-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek closed DISPATCH-753. --- works for me now > Neither version of console is usable on Internet Explorer 10 or 11 >

[jira] [Updated] (DISPATCH-793) Edge between nodes in Topology diagram missing on IE11

[ https://issues.apache.org/jira/browse/DISPATCH-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek updated DISPATCH-793: Attachment: no_edge_between_nodes.png > Edge between nodes in Topology diagram missing on IE11 >

[jira] [Created] (DISPATCH-793) Edge between nodes in Topology diagram missing on IE11

Jiri Danek created DISPATCH-793: --- Summary: Edge between nodes in Topology diagram missing on IE11 Key: DISPATCH-793 URL: https://issues.apache.org/jira/browse/DISPATCH-793 Project: Qpid Dispatch

[jira] [Commented] (QPID-7791) Recover metadata into direct memory

[ https://issues.apache.org/jira/browse/QPID-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055838#comment-16055838 ] ASF subversion and git services commented on QPID-7791: --- Commit

[jira] [Closed] (DISPATCH-772) Buttons to Create and Delete entity disappear after navigation in either version of console

[ https://issues.apache.org/jira/browse/DISPATCH-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Danek closed DISPATCH-772. --- Fixed in current master, commit e22091b3 > Buttons to Create and Delete entity disappear after

[jira] [Resolved] (QPID-7648) [Java Broker] Reject AMQP 1.0 durable messages if no persistent store is configured

[ https://issues.apache.org/jira/browse/QPID-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7648. -- Resolution: Fixed Change looks reasonable to me. > [Java Broker] Reject AMQP 1.0 durable messages if no

[jira] [Updated] (QPID-7831) Refactor AbstractJDBCMessageStore to use try-with-resources

[ https://issues.apache.org/jira/browse/QPID-7831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7831: - Fix Version/s: qpid-java-broker-7.0.0 > Refactor AbstractJDBCMessageStore to use try-with-resources >

[jira] [Assigned] (QPID-7831) Refactor AbstractJDBCMessageStore to use try-with-resources

[ https://issues.apache.org/jira/browse/QPID-7831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7831: Assignee: Keith Wall > Refactor AbstractJDBCMessageStore to use try-with-resources >

[jira] [Updated] (QPID-7831) Refactor AbstractJDBCMessageStore to use try-with-resources

[ https://issues.apache.org/jira/browse/QPID-7831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7831: - Status: Reviewable (was: In Progress) > Refactor AbstractJDBCMessageStore to use try-with-resources >

[jira] [Updated] (QPID-7831) Refactor AbstractJDBCMessageStore to use try-with-resources

[ https://issues.apache.org/jira/browse/QPID-7831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7831: - Priority: Minor (was: Major) > Refactor AbstractJDBCMessageStore to use try-with-resources >

[jira] [Created] (QPID-7832) Refactor store/protocol API using Collection

Keith Wall created QPID-7832: Summary: Refactor store/protocol API using Collection Key: QPID-7832 URL: https://issues.apache.org/jira/browse/QPID-7832 Project: Qpid Issue Type: Improvement

[jira] [Comment Edited] (DISPATCH-753) Neither version of console is usable on Internet Explorer 10 or 11

[ https://issues.apache.org/jira/browse/DISPATCH-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055791#comment-16055791 ] Jiri Danek edited comment on DISPATCH-753 at 6/20/17 2:11 PM: -- works for me

[jira] [Updated] (QPID-7827) Recoverers allocate separate queue UUID for each recovered message instance

[ https://issues.apache.org/jira/browse/QPID-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7827: - Fix Version/s: qpid-java-6.0.8 qpid-java-6.1.4 qpid-java-broker-7.0.0

[jira] [Updated] (QPID-7791) Recover metadata into direct memory

[ https://issues.apache.org/jira/browse/QPID-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7791: - Fix Version/s: qpid-java-6.0.8 qpid-java-6.1.4 > Recover metadata into direct memory >

[jira] [Created] (DISPATCH-792) Freezing and moving nodes is somewhat broken (in either version of console)

Jiri Danek created DISPATCH-792: --- Summary: Freezing and moving nodes is somewhat broken (in either version of console) Key: DISPATCH-792 URL: https://issues.apache.org/jira/browse/DISPATCH-792 Project:

[jira] [Commented] (PROTON-1209) CLONE - Proton's use of Cyrus SASL is not thread-safe - long term fix

[ https://issues.apache.org/jira/browse/PROTON-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055729#comment-16055729 ] ASF subversion and git services commented on PROTON-1209: - Commit

[jira] [Commented] (PROTON-1500) Allow plugin SASL implementations

[ https://issues.apache.org/jira/browse/PROTON-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055728#comment-16055728 ] ASF subversion and git services commented on PROTON-1500: - Commit

[GitHub] qpid-proton pull request #108: PROTON-1500: Implement plugin interface for S...

Github user astitcher closed the pull request at: https://github.com/apache/qpid-proton/pull/108 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Resolved] (PROTON-1500) Allow plugin SASL implementations

[ https://issues.apache.org/jira/browse/PROTON-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1500. - Resolution: Fixed > Allow plugin SASL implementations >

RE: Proposal to create Docker images for Qpid components.

I agree w/ Rob, Robbie... 2 brokers and dispatch. Clients don't make sense for docker images, IMO. -Steve > -Original Message- > From: Rob Godfrey [mailto:rob.j.godf...@gmail.com] > Sent: Tuesday, June 20, 2017 1:19 PM > To: qpid > Subject: Re: Proposal to create

[jira] [Commented] (QPID-7830) Heap dominated by duplicates of common routing values / header values etc

[ https://issues.apache.org/jira/browse/QPID-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055947#comment-16055947 ] Rob Godfrey commented on QPID-7830: --- {quote} On the AMQP 0-8..0-91, with things like contentType, path I

[jira] [Commented] (DISPATCH-788) Create peer linkage for presettled deliveries so we can use this to handle muticast dispositions

[ https://issues.apache.org/jira/browse/DISPATCH-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056011#comment-16056011 ] ASF GitHub Bot commented on DISPATCH-788: - Github user ted-ross commented on a diff in the pull

[jira] [Created] (QPIDJMS-296) JMS client does not assign unique deliveryTag for messages sent on the same link

Lorenz Quack created QPIDJMS-296: Summary: JMS client does not assign unique deliveryTag for messages sent on the same link Key: QPIDJMS-296 URL: https://issues.apache.org/jira/browse/QPIDJMS-296

[GitHub] qpid-dispatch pull request #167: DISPATCH-788 - First attempt at adding a co...

Github user ted-ross commented on a diff in the pull request: https://github.com/apache/qpid-dispatch/pull/167#discussion_r123020082 --- Diff: src/router_core/router_core_private.h --- @@ -693,6 +694,28 @@ void qdr_delivery_release_CT(qdr_core_t *core, qdr_delivery_t *delivery);

[jira] [Updated] (QPID-7830) Heap dominated by duplicates of common routing values / header values etc

[ https://issues.apache.org/jira/browse/QPID-7830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7830: - Description: When used for store and forwarding, in some use cases the Broker's heap can become dominated

[jira] [Updated] (QPID-7827) Recoverers allocate separate queue UUID for each recovered message instance

[ https://issues.apache.org/jira/browse/QPID-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7827: - Status: Reviewable (was: In Progress) > Recoverers allocate separate queue UUID for each recovered

[jira] [Assigned] (QPID-7827) Recoverers allocate separate queue UUID for each recovered message instance

[ https://issues.apache.org/jira/browse/QPID-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7827: Assignee: Keith Wall > Recoverers allocate separate queue UUID for each recovered message instance

Re: Proposal to create Docker images for Qpid components.

I think it makes sense for qpid-broker-j, qpid-cpp broker, and qpid-dispatch. I believe some folks might also like 'client' images, which is much less obvious to me..though I can see that for those needing compilation or with interdependencies on bits that do, perhaps it could make them slightly

[jira] [Resolved] (QPID-7661) [Java Broker] Stop creating 'dead letter queue' for a durable subscription queue

[ https://issues.apache.org/jira/browse/QPID-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7661. -- Resolution: Fixed > [Java Broker] Stop creating 'dead letter queue' for a durable subscription > queue

[jira] [Updated] (QPID-7812) [Java Broker] [AMQP1.0] Wire up unacknowledged message bytes/count statistics

[ https://issues.apache.org/jira/browse/QPID-7812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7812: - Status: Reviewable (was: In Progress) > [Java Broker] [AMQP1.0] Wire up unacknowledged message

[jira] [Assigned] (QPID-7791) Recover metadata into direct memory

[ https://issues.apache.org/jira/browse/QPID-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7791: Assignee: Keith Wall > Recover metadata into direct memory > --- >

[jira] [Updated] (QPID-7791) Recover metadata into direct memory

[ https://issues.apache.org/jira/browse/QPID-7791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7791: - Status: Reviewable (was: In Progress) > Recover metadata into direct memory >

[jira] [Commented] (QPID-7367) [JCA] QpidRASessionImpl#closeSession does not destroy the underlying connection

[ https://issues.apache.org/jira/browse/QPID-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056034#comment-16056034 ] Keith Wall commented on QPID-7367: -- Won't fix. Feature removed by QPID-7716. > [JCA]

[jira] [Updated] (QPID-7708) [Java Broker] [AMQP 1.0] Allow the incoming session credit window to be configured with a context value

[ https://issues.apache.org/jira/browse/QPID-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7708: - Status: Reviewable (was: In Progress) > [Java Broker] [AMQP 1.0] Allow the incoming session credit window

[jira] [Assigned] (QPID-7708) [Java Broker] [AMQP 1.0] Allow the incoming session credit window to be configured with a context value

[ https://issues.apache.org/jira/browse/QPID-7708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7708: Assignee: Keith Wall (was: Rob Godfrey) > [Java Broker] [AMQP 1.0] Allow the incoming session

[jira] [Commented] (QPID-7459) ProducerFlowControlTest#testSendTimeout test fails sprodically on 0-10 profiles

[ https://issues.apache.org/jira/browse/QPID-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056031#comment-16056031 ] Keith Wall commented on QPID-7459: -- commit bdb6338f3b5afb7648506dbe35a39cf5f5564374 Author: Keith Wall

[jira] [Closed] (QPID-7459) ProducerFlowControlTest#testSendTimeout test fails sprodically on 0-10 profiles

[ https://issues.apache.org/jira/browse/QPID-7459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-7459. Resolution: Fixed Fix Version/s: qpid-java-broker-7.0.0 > ProducerFlowControlTest#testSendTimeout

[jira] [Closed] (QPID-7367) [JCA] QpidRASessionImpl#closeSession does not destroy the underlying connection

[ https://issues.apache.org/jira/browse/QPID-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-7367. Resolution: Won't Fix > [JCA] QpidRASessionImpl#closeSession does not destroy the underlying > connection >

[jira] [Commented] (QPIDJMS-296) JMS client does not assign unique deliveryTag for messages sent on the same link

[ https://issues.apache.org/jira/browse/QPIDJMS-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055966#comment-16055966 ] Timothy Bish commented on QPIDJMS-296: -- In this case it doesn't actually seem to be doing anything

[jira] [Closed] (QPIDJMS-296) JMS client does not assign unique deliveryTag for messages sent on the same link

[ https://issues.apache.org/jira/browse/QPIDJMS-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lorenz Quack closed QPIDJMS-296. Resolution: Invalid 2.6.12 states that the deliveryTag is only unique as long as it can be

[jira] [Commented] (DISPATCH-788) Create peer linkage for presettled deliveries so we can use this to handle muticast dispositions

[ https://issues.apache.org/jira/browse/DISPATCH-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056137#comment-16056137 ] ASF subversion and git services commented on DISPATCH-788: -- Commit

[jira] [Resolved] (QPID-7749) [Java Broker] In AMQP 1.0 settle incoming messages when rcv-settle-mode is default

[ https://issues.apache.org/jira/browse/QPID-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-7749. -- Resolution: Fixed Lorenz and I worked worked in pair at the changes. The code is reviewed as part of

Re: Proposal to create Docker images for Qpid components.

On 20 June 2017 at 18:20, Robbie Gemmell wrote: > I think it makes sense for qpid-broker-j, qpid-cpp broker, and > qpid-dispatch. > +1 These are what I imagined would make sense > > I believe some folks might also like 'client' images, which is much > less obvious to

[jira] [Updated] (QPID-7827) Recoverers allocate separate queue UUID for each recovered message instance

[ https://issues.apache.org/jira/browse/QPID-7827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7827: - Status: Open (was: Reviewable) The changes look reasonable to me. Please port them into the branches >

[GitHub] qpid-dispatch pull request #168: crolke dev annotations - work in progress P...

GitHub user ChugR opened a pull request: https://github.com/apache/qpid-dispatch/pull/168 crolke dev annotations - work in progress PR for review **DO NOT COMMIT THIS PULL REQUEST** It is for review only. This work adds a new annotation scheme for inter-router annotations.

[GitHub] qpid-dispatch pull request #167: DISPATCH-788 - First attempt at adding a co...

Github user ganeshmurthy closed the pull request at: https://github.com/apache/qpid-dispatch/pull/167 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Commented] (DISPATCH-788) Create peer linkage for presettled deliveries so we can use this to handle muticast dispositions

[ https://issues.apache.org/jira/browse/DISPATCH-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056242#comment-16056242 ] ASF GitHub Bot commented on DISPATCH-788: - Github user ganeshmurthy closed the pull request at:

[jira] [Updated] (DISPATCH-781) Tie end-to-end flow control of message-routed deliveries to outgoing capacity

[ https://issues.apache.org/jira/browse/DISPATCH-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-781: -- Summary: Tie end-to-end flow control of message-routed deliveries to outgoing capacity (was:

[GitHub] qpid-dispatch pull request #169: DISPATCH-788 - Part 2 - Added a list of pee...

GitHub user ganeshmurthy opened a pull request: https://github.com/apache/qpid-dispatch/pull/169 DISPATCH-788 - Part 2 - Added a list of peer references in case there… … is more than one peer. This will help in the future when we introduce large message streaming You can merge

[jira] [Commented] (DISPATCH-788) Create peer linkage for presettled deliveries so we can use this to handle muticast dispositions

[ https://issues.apache.org/jira/browse/DISPATCH-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16056253#comment-16056253 ] ASF GitHub Bot commented on DISPATCH-788: - GitHub user ganeshmurthy opened a pull request: