[jira] [Commented] (DISPATCH-371) qdstat and all other clients stopped connecting to interior router

[ https://issues.apache.org/jira/browse/DISPATCH-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320787#comment-15320787 ] Vishal Sharda commented on DISPATCH-371: Hi Ganesh, Can I share the same port between

[jira] [Commented] (DISPATCH-371) qdstat and all other clients stopped connecting to interior router

[ https://issues.apache.org/jira/browse/DISPATCH-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320776#comment-15320776 ] Ganesh Murthy commented on DISPATCH-371: Hi Vishal, Your clients are forbidden from

[jira] [Updated] (DISPATCH-366) When delivery fails the router sends the RELEASED disposition, not MODIFIED

[ https://issues.apache.org/jira/browse/DISPATCH-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated DISPATCH-366: Fix Version/s: (was: 0.6.0) 0.7.0 0.6.1 > When delivery

[jira] [Created] (DISPATCH-370) qdmanage tool hangs if --type option is "linkRoute"

Paolo Patierno created DISPATCH-370: --- Summary: qdmanage tool hangs if --type option is "linkRoute" Key: DISPATCH-370 URL: https://issues.apache.org/jira/browse/DISPATCH-370 Project: Qpid Dispatch

[jira] [Created] (DISPATCH-371) qdstat and all other clients stopped connecting to interior router

Vishal Sharda created DISPATCH-371: -- Summary: qdstat and all other clients stopped connecting to interior router Key: DISPATCH-371 URL: https://issues.apache.org/jira/browse/DISPATCH-371 Project:

[jira] [Assigned] (DISPATCH-370) qdmanage tool hangs if --type option is "linkRoute" or "address"

[ https://issues.apache.org/jira/browse/DISPATCH-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-370: -- Assignee: Ganesh Murthy > qdmanage tool hangs if --type option is "linkRoute" or

Re: Review Request 48362: PROTON-1221: c++ container::schedule() support.

> On June 7, 2016, 9:40 p.m., Andrew Stitcher wrote: > > You need to compile this code with C++03 and fix up the places that end up > > needing a feature macro to avoid breakage. > > Alan Conway wrote: > Yep, known limitation. I need to add C++03 callback support. This is a > first cut in

[jira] [Resolved] (DISPATCH-317) Show tooltip for long values on left panel on topology page

[ https://issues.apache.org/jira/browse/DISPATCH-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-317. --- Resolution: Fixed Fix Version/s: 0.7.0 > Show tooltip for long values on left panel

[jira] [Commented] (DISPATCH-317) Show tooltip for long values on left panel on topology page

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

[jira] [Updated] (DISPATCH-370) qdmanage tool hangs if --type option is "linkRoute" or "address"

[ https://issues.apache.org/jira/browse/DISPATCH-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno updated DISPATCH-370: Description: Using qdmanage tool in the following way : qdmanage read --type linkRoute

[jira] [Commented] (DISPATCH-371) qdstat and all other clients stopped connecting to interior router

[ https://issues.apache.org/jira/browse/DISPATCH-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320795#comment-15320795 ] Ganesh Murthy commented on DISPATCH-371: Please use different ports. > qdstat and all other

[jira] [Commented] (PROTON-1227) Go Client cannot send message in fire-and-forget mode

[ https://issues.apache.org/jira/browse/PROTON-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321035#comment-15321035 ] Alan Conway commented on PROTON-1227: - I can reproduce it. An interesting one. All the Send methods

[jira] [Created] (DISPATCH-372) qdstat should have a timeout command line argument

michael goulish created DISPATCH-372: Summary: qdstat should have a timeout command line argument Key: DISPATCH-372 URL: https://issues.apache.org/jira/browse/DISPATCH-372 Project: Qpid Dispatch

[jira] [Closed] (DISPATCH-372) qdstat should have a timeout command line argument

[ https://issues.apache.org/jira/browse/DISPATCH-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy closed DISPATCH-372. -- Resolution: Not A Bug Assignee: Ganesh Murthy Fix Version/s: 0.6.0 > qdstat

[jira] [Resolved] (DISPATCH-370) qdmanage tool hangs if --type option is "linkRoute" or "address"

[ https://issues.apache.org/jira/browse/DISPATCH-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-370. Resolution: Fixed Fix Version/s: 0.7.0 > qdmanage tool hangs if --type option is

[jira] [Commented] (DISPATCH-369) investigate excursions in memory usage

[ https://issues.apache.org/jira/browse/DISPATCH-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321448#comment-15321448 ] michael goulish commented on DISPATCH-369: -- I rebuilt dispatch without the memory pooling

[jira] [Commented] (DISPATCH-369) investigate excursions in memory usage

[ https://issues.apache.org/jira/browse/DISPATCH-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321466#comment-15321466 ] michael goulish commented on DISPATCH-369: -- ...and without anything interesting showing up in

[jira] [Assigned] (QPID-7247) Implement preferences model and REST API

[ https://issues.apache.org/jira/browse/QPID-7247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-7247: Assignee: Keith Wall > Implement preferences model and REST API >

Re: Review Request 48362: PROTON-1221: c++ container::schedule() support.

On Tue, 2016-06-07 at 20:15 -0400, Michael Goulish wrote: > > > > > > > > In other words, are we trying for a fixed frequency or an "at > > least" > > delay? > > > What I need this feature for is to be able to send messages at a > fixed frequency. OK that's 2 votes, I'll redo the

Re: Review Request 48362: PROTON-1221: c++ container::schedule() support.

> On June 7, 2016, 9:40 p.m., Andrew Stitcher wrote: > > You need to compile this code with C++03 and fix up the places that end up > > needing a feature macro to avoid breakage. Yep, known limitation. I need to add C++03 callback support. This is a first cut in C++11 without worrying about

[jira] [Commented] (QPID-7274) [Java Client] Asynchronous client acknowledgements

[ https://issues.apache.org/jira/browse/QPID-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320200#comment-15320200 ] Jakub Scholz commented on QPID-7274: Hi Keith, I tested this with AMQP 0-10 and it works perfectly.

[jira] [Resolved] (QPID-7116) Ability to utilise group information from a LDAP compatible directory

[ https://issues.apache.org/jira/browse/QPID-7116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-7116. -- Resolution: Fixed Documentation looks reasonable too. > Ability to utilise group information from a

[jira] [Updated] (QPID-6988) Define an anonymous Broker initial profile and make this the default

[ https://issues.apache.org/jira/browse/QPID-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6988: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Define an anonymous Broker

[jira] [Updated] (QPID-6987) Define an initial profile which uses an OTP authentication provider

[ https://issues.apache.org/jira/browse/QPID-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6987: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Define an initial profile which

[jira] [Updated] (QPID-7287) Query parser fails silently with expression such as a + b

[ https://issues.apache.org/jira/browse/QPID-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7287: - Priority: Minor (was: Major) > Query parser fails silently with expression such as a + b >

[jira] [Updated] (QPID-7104) [Java Broker] Creating multiple state transition methods on a ConfiguredObject should cause an error

[ https://issues.apache.org/jira/browse/QPID-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7104: - Fix Version/s: (was: qpid-java-6.1) qpid-java-7.0.0 > [Java Broker] Creating

[jira] [Updated] (QPID-7125) [Java Broker] REST API return code when deleting a resource which does not exist

[ https://issues.apache.org/jira/browse/QPID-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7125: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > [Java Broker] REST API return

[jira] [Updated] (QPID-7138) [Java Broker] Broker should detect duplicate IDs in configured objects

[ https://issues.apache.org/jira/browse/QPID-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7138: - Fix Version/s: (was: qpid-java-6.1) qpid-java-7.0.0 > [Java Broker] Broker should

[jira] [Updated] (QPID-7272) [Java Broker] Direct memory QpidByteBuffer created in message conversion modules should be disposed as soon as possible after becoming unused

[ https://issues.apache.org/jira/browse/QPID-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7272: - Fix Version/s: (was: qpid-java-6.1) qpid-java-7.0.0 > [Java Broker] Direct memory

[jira] [Updated] (QPID-6989) Define an initial profile that defines a fixed password

[ https://issues.apache.org/jira/browse/QPID-6989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6989: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Define an initial profile that

[jira] [Updated] (QPID-6986) Management: Users should not be able to view an object to which they have no access

[ https://issues.apache.org/jira/browse/QPID-6986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6986: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Management: Users should not be

[jira] [Updated] (QPID-7293) Rationalise broker logging levels

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

[jira] [Updated] (QPID-6981) SSLSender does not send the close_notify bytes during client initiated connection close

[ https://issues.apache.org/jira/browse/QPID-6981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6981: - Fix Version/s: qpid-java-6.2 > SSLSender does not send the close_notify bytes during client initiated >

[jira] [Updated] (QPID-7296) Use connection property to determine if message delay (notValidBefore) is supported or not

[ https://issues.apache.org/jira/browse/QPID-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7296: - Component/s: Java Client > Use connection property to determine if message delay (notValidBefore) is >

[jira] [Updated] (QPID-7296) Use connection property to determine if message delay (notValidBefore) is supported or not

[ https://issues.apache.org/jira/browse/QPID-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7296: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Use connection property to

[jira] [Updated] (QPID-7296) Use connection property to determine if message delay (notValidBefore) is supported or not

[ https://issues.apache.org/jira/browse/QPID-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7296: - Summary: Use connection property to determine if message delay (notValidBefore) is supported or not (was:

[jira] [Updated] (QPID-7296) Use connection property to show determine if message delay is supported or not

[ https://issues.apache.org/jira/browse/QPID-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7296: - Description: QPID-7255 introduced support of message delays. Make the Broker provide a connection

[jira] [Updated] (QPID-7296) Use connection property to determine if message delay (notValidBefore )is supported or not

[ https://issues.apache.org/jira/browse/QPID-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7296: - Summary: Use connection property to determine if message delay (notValidBefore )is supported or not (was:

[jira] [Updated] (QPID-7168) Allow authentication providers to resolve a realm qualified user identity into a displayable name

[ https://issues.apache.org/jira/browse/QPID-7168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7168: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Allow authentication providers

[jira] [Updated] (QPID-7123) [Java Client] Closing an SSL connection may timeout

[ https://issues.apache.org/jira/browse/QPID-7123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7123: - Fix Version/s: qpid-java-6.2 > [Java Client] Closing an SSL connection may timeout >

[jira] [Updated] (QPID-7198) LDAP and OAUTH2 Authentication Providers should cache authentication results for a short period

[ https://issues.apache.org/jira/browse/QPID-7198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7198: - Fix Version/s: qpid-java-6.1 > LDAP and OAUTH2 Authentication Providers should cache authentication

[jira] [Created] (QPID-7296) Use connection property to show determine if message delay is supported or not

Keith Wall created QPID-7296: Summary: Use connection property to show determine if message delay is supported or not Key: QPID-7296 URL: https://issues.apache.org/jira/browse/QPID-7296 Project: Qpid

[jira] [Updated] (QPID-7289) [Java Broker] SASL challenges and response should be masked in the log file

[ https://issues.apache.org/jira/browse/QPID-7289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7289: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > [Java Broker] SASL challenges

[jira] [Updated] (QPID-6990) [Java Broker] Support password expiry

[ https://issues.apache.org/jira/browse/QPID-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6990: - Fix Version/s: (was: Future) qpid-java-6.2 > [Java Broker] Support password expiry

[jira] [Updated] (QPID-6907) Add ability to restrict read in ACLs

[ https://issues.apache.org/jira/browse/QPID-6907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6907: - Fix Version/s: (was: Future) qpid-java-6.2 > Add ability to restrict read in ACLs >

[jira] [Updated] (QPID-6991) NonBlockingConnection does not gracefully close TLS connections

[ https://issues.apache.org/jira/browse/QPID-6991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6991: - Fix Version/s: (was: Future) qpid-java-6.2 > NonBlockingConnection does not

[jira] [Updated] (QPID-7276) Message delay improvements

[ https://issues.apache.org/jira/browse/QPID-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7276: - Description: QPID-7255 introduced support of message delays. To make the feature more useful/usable, the

[jira] [Updated] (QPID-7197) Prevent deletion of objects that are in use

[ https://issues.apache.org/jira/browse/QPID-7197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7197: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Prevent deletion of objects

[jira] [Updated] (QPID-7194) Give client an ordered preferences to drive AMQP protocol selection

[ https://issues.apache.org/jira/browse/QPID-7194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7194: - Fix Version/s: (was: qpid-java-6.1) qpid-java-7.0.0 > Give client an ordered

[jira] [Updated] (QPID-7279) [Java Broker] with config encryption creating a JDBC VirtualHost fails

[ https://issues.apache.org/jira/browse/QPID-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7279: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > [Java Broker] with config

[jira] [Updated] (QPID-7093) Make the display of createdBy/lastUpdatedBy user information human readable

[ https://issues.apache.org/jira/browse/QPID-7093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7093: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Make the display of

[jira] [Updated] (QPID-7246) Make ACL module realm aware

[ https://issues.apache.org/jira/browse/QPID-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7246: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Make ACL module realm aware >

[jira] [Updated] (QPID-7167) Make user/group names produced by LDAP authentication and group provider be realm qualified

[ https://issues.apache.org/jira/browse/QPID-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7167: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Make user/group names produced

[jira] [Updated] (QPID-7092) User identity must be unique

[ https://issues.apache.org/jira/browse/QPID-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7092: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > User identity must be unique >

[jira] [Updated] (QPID-7166) Make user/group names produced by authentication and group providers realm qualified

[ https://issues.apache.org/jira/browse/QPID-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7166: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Make user/group names produced

[jira] [Updated] (QPID-7243) Make legacy JMS client publish messages with domain qualified userid

[ https://issues.apache.org/jira/browse/QPID-7243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7243: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Make legacy JMS client publish

[jira] [Updated] (QPID-7242) Make existing authentication/group providers produce realm qualified principals

[ https://issues.apache.org/jira/browse/QPID-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7242: - Fix Version/s: (was: qpid-java-6.1) qpid-java-6.2 > Make existing

[jira] [Updated] (QPID-7283) [Java Broker] Simplify SASL authentication functionality accros broker AMQP layers

[ https://issues.apache.org/jira/browse/QPID-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7283: - Fix Version/s: qpid-java-6.2 > [Java Broker] Simplify SASL authentication functionality accros broker AMQP

[jira] [Updated] (QPID-7293) Rationalise broker logging levels

[ https://issues.apache.org/jira/browse/QPID-7293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7293: - Fix Version/s: (was: qpid-java-7.0.0) qpid-java-6.2 > Rationalise broker logging

[jira] [Updated] (QPID-7245) Configuration upgrader for realm qualified identities

[ https://issues.apache.org/jira/browse/QPID-7245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7245: - Fix Version/s: qpid-java-6.2 > Configuration upgrader for realm qualified identities >

[jira] [Updated] (QPID-7244) Expose realm qualified authenticate name to messaging clients

[ https://issues.apache.org/jira/browse/QPID-7244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7244: - Fix Version/s: qpid-java-6.2 > Expose realm qualified authenticate name to messaging clients >

[jira] [Updated] (QPID-7292) Qpid clients should verify the server-final message when using SCRAM-* authentication

[ https://issues.apache.org/jira/browse/QPID-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7292: - Fix Version/s: qpid-java-6.2 > Qpid clients should verify the server-final message when using SCRAM-* >

[jira] [Updated] (QPID-7296) Use connection property to determine if message delay (notValidBefore) is supported or not

[ https://issues.apache.org/jira/browse/QPID-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7296: - Fix Version/s: (was: qpid-java-6.2) qpid-java-7.0.0 > Use connection property to

[jira] [Assigned] (DISPATCH-368) Router in bad state in two inter-connected routers

[ https://issues.apache.org/jira/browse/DISPATCH-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-368: - Assignee: Ted Ross > Router in bad state in two inter-connected routers >

[jira] [Commented] (DISPATCH-368) Router in bad state in two inter-connected routers

[ https://issues.apache.org/jira/browse/DISPATCH-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320460#comment-15320460 ] Ted Ross commented on DISPATCH-368: --- The fix for DISPATCH-364 should also fix this issue. > Router in

[jira] [Commented] (DISPATCH-364) Inter-router listeners should not permit normal endpoint traffic

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

[jira] [Resolved] (DISPATCH-364) Inter-router listeners should not permit normal endpoint traffic

[ https://issues.apache.org/jira/browse/DISPATCH-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-364. --- Resolution: Fixed > Inter-router listeners should not permit normal endpoint traffic >

[jira] [Resolved] (DISPATCH-365) Standalone router crashes if an interior router attempts to connect to it

[ https://issues.apache.org/jira/browse/DISPATCH-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-365. --- Resolution: Fixed Fix Version/s: 0.6.0 > Standalone router crashes if an interior router

[jira] [Commented] (DISPATCH-364) Inter-router listeners should not permit normal endpoint traffic

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

[jira] [Commented] (DISPATCH-365) Standalone router crashes if an interior router attempts to connect to it

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

[jira] [Resolved] (DISPATCH-368) Router in bad state in two inter-connected routers

[ https://issues.apache.org/jira/browse/DISPATCH-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-368. --- Resolution: Fixed Fix Version/s: 0.6.0 > Router in bad state in two inter-connected routers

[jira] [Commented] (DISPATCH-368) Router in bad state in two inter-connected routers

[ https://issues.apache.org/jira/browse/DISPATCH-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15320464#comment-15320464 ] Ted Ross commented on DISPATCH-368: --- DISPATCH-364 fixes two issues: First, it prevents normal clients

[jira] [Commented] (DISPATCH-370) qdmanage tool hangs if --type option is "linkRoute" or "address"

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

[jira] [Assigned] (DISPATCH-366) When delivery fails the router sends the RELEASED disposition, not MODIFIED

[ https://issues.apache.org/jira/browse/DISPATCH-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-366: - Assignee: Ted Ross > When delivery fails the router sends the RELEASED disposition, not

[jira] [Closed] (DISPATCH-371) qdstat and all other clients stopped connecting to interior router

[ https://issues.apache.org/jira/browse/DISPATCH-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy closed DISPATCH-371. -- Resolution: Not A Bug Assignee: Ganesh Murthy Fix Version/s: 0.6.0 > qdstat

Re: Review Request 48362: PROTON-1221: c++ container::schedule() support.

> On June 7, 2016, 9:40 p.m., Andrew Stitcher wrote: > > You need to compile this code with C++03 and fix up the places that end up > > needing a feature macro to avoid breakage. > > Alan Conway wrote: > Yep, known limitation. I need to add C++03 callback support. This is a > first cut in

[jira] [Assigned] (DISPATCH-367) balanced distribution needs to be more... balanced.

[ https://issues.apache.org/jira/browse/DISPATCH-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-367: -- Assignee: Ganesh Murthy > balanced distribution needs to be more... balanced. >

[jira] [Commented] (DISPATCH-372) qdstat should have a timeout command line argument

[ https://issues.apache.org/jira/browse/DISPATCH-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321482#comment-15321482 ] Ganesh Murthy commented on DISPATCH-372: Hi Mick, qdstat and qdmanage both have a --timeout

[jira] [Updated] (DISPATCH-358) Intermittent crashes in qdrouterd under load from parallel senders

[ https://issues.apache.org/jira/browse/DISPATCH-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Sharda updated DISPATCH-358: --- Attachment: Crash_EXTERNAL.png I started testing again with latest trunk code that has

[jira] [Created] (PROTON-1228) Windows schannel needs default peer_hostname to match OpenSSL

Cliff Jansen created PROTON-1228: Summary: Windows schannel needs default peer_hostname to match OpenSSL Key: PROTON-1228 URL: https://issues.apache.org/jira/browse/PROTON-1228 Project: Qpid Proton