[jira] [Updated] (DISPATCH-557) High connection rates cause problems in the Python management agent

[ https://issues.apache.org/jira/browse/DISPATCH-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-557: -- Fix Version/s: 0.8.0 > High connection rates cause problems in the Python management agent >

[jira] [Resolved] (DISPATCH-533) Router crash in the 6-node example

[ https://issues.apache.org/jira/browse/DISPATCH-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-533. --- Resolution: Fixed > Router crash in the 6-node example > -- > >

[jira] [Resolved] (DISPATCH-550) Assertion failure in router in larger scale networks

[ https://issues.apache.org/jira/browse/DISPATCH-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-550. --- Resolution: Fixed > Assertion failure in router in larger scale networks >

[jira] [Resolved] (DISPATCH-558) Remove assertions in the core agent that fail due to malformed requests

[ https://issues.apache.org/jira/browse/DISPATCH-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-558. --- Resolution: Fixed > Remove assertions in the core agent that fail due to malformed requests >

[jira] [Resolved] (DISPATCH-535) Use correct lifecycle management for Proton objects

[ https://issues.apache.org/jira/browse/DISPATCH-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-535. --- Resolution: Fixed > Use correct lifecycle management for Proton objects >

[jira] [Created] (DISPATCH-559) qdstat - Request only the columns that will be used in the display

Ted Ross created DISPATCH-559: - Summary: qdstat - Request only the columns that will be used in the display Key: DISPATCH-559 URL: https://issues.apache.org/jira/browse/DISPATCH-559 Project: Qpid

[jira] [Created] (DISPATCH-558) Remove assertions in the core agent that fail due to malformed requests

Ted Ross created DISPATCH-558: - Summary: Remove assertions in the core agent that fail due to malformed requests Key: DISPATCH-558 URL: https://issues.apache.org/jira/browse/DISPATCH-558 Project: Qpid

[jira] [Updated] (DISPATCH-209) Three+ router test is needed in the system test suite.

[ https://issues.apache.org/jira/browse/DISPATCH-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-209: -- Assignee: michael goulish > Three+ router test is needed in the system test suite. >

[jira] [Updated] (DISPATCH-113) expose NodeTracker::last_topology_change in management

[ https://issues.apache.org/jira/browse/DISPATCH-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-113: -- Assignee: michael goulish > expose NodeTracker::last_topology_change in management >

[jira] [Updated] (DISPATCH-535) Use correct lifecycle management for Proton objects

[ https://issues.apache.org/jira/browse/DISPATCH-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-535: -- Summary: Use correct lifecycle management for Proton objects (was: Dispatch memory increases on long

[jira] [Created] (DISPATCH-557) High connection rates cause problems in the Python management agent

Ted Ross created DISPATCH-557: - Summary: High connection rates cause problems in the Python management agent Key: DISPATCH-557 URL: https://issues.apache.org/jira/browse/DISPATCH-557 Project: Qpid

[jira] [Created] (DISPATCH-556) qdstat fails at high scale

Ted Ross created DISPATCH-556: - Summary: qdstat fails at high scale Key: DISPATCH-556 URL: https://issues.apache.org/jira/browse/DISPATCH-556 Project: Qpid Dispatch Issue Type: Bug

[jira] [Updated] (DISPATCH-535) Dispatch memory increases on long lived link routed connections

[ https://issues.apache.org/jira/browse/DISPATCH-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-535: -- Fix Version/s: 0.7.0 > Dispatch memory increases on long lived link routed connections >

[jira] [Created] (DISPATCH-553) Add statistic counter to the "log" entity to count log events per severity

Ted Ross created DISPATCH-553: - Summary: Add statistic counter to the "log" entity to count log events per severity Key: DISPATCH-553 URL: https://issues.apache.org/jira/browse/DISPATCH-553 Project: Qpid

[jira] [Updated] (DISPATCH-551) disconnect connections that do not complete initial protocol handshake within a given time

[ https://issues.apache.org/jira/browse/DISPATCH-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-551: -- Fix Version/s: 0.8.0 > disconnect connections that do not complete initial protocol handshake within

[jira] [Created] (DISPATCH-550) Assertion failure in router in larger scale networks

Ted Ross created DISPATCH-550: - Summary: Assertion failure in router in larger scale networks Key: DISPATCH-550 URL: https://issues.apache.org/jira/browse/DISPATCH-550 Project: Qpid Dispatch

[jira] [Commented] (DISPATCH-533) Router crash in the 6-node example

[ https://issues.apache.org/jira/browse/DISPATCH-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15595057#comment-15595057 ] Ted Ross commented on DISPATCH-533: --- git bisect has identified that the commit for DISPATCH-160 caused

[jira] [Created] (DISPATCH-533) Router crash in the 6-node example

Ted Ross created DISPATCH-533: - Summary: Router crash in the 6-node example Key: DISPATCH-533 URL: https://issues.apache.org/jira/browse/DISPATCH-533 Project: Qpid Dispatch Issue Type: Bug

[jira] [Created] (DISPATCH-529) Address annotation for Multi-Tenancy

Ted Ross created DISPATCH-529: - Summary: Address annotation for Multi-Tenancy Key: DISPATCH-529 URL: https://issues.apache.org/jira/browse/DISPATCH-529 Project: Qpid Dispatch Issue Type: New

[jira] [Resolved] (DISPATCH-467) Terminus renaming for autoLinks

[ https://issues.apache.org/jira/browse/DISPATCH-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-467. --- Resolution: Fixed > Terminus renaming for autoLinks > --- > >

[jira] [Assigned] (DISPATCH-467) Terminus renaming for autoLinks

[ https://issues.apache.org/jira/browse/DISPATCH-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-467: - Assignee: Ted Ross > Terminus renaming for autoLinks > --- > >

[jira] [Commented] (DISPATCH-337) Huge memory leaks in Qpid Dispatch router

[ https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556229#comment-15556229 ] Ted Ross commented on DISPATCH-337: --- I believe that the qdstat program is timing out waiting for a

[jira] [Commented] (DISPATCH-337) Huge memory leaks in Qpid Dispatch router

[ https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556214#comment-15556214 ] Ted Ross commented on DISPATCH-337: --- Did you build your executable without debug symbols? Without

[jira] [Commented] (DISPATCH-337) Huge memory leaks in Qpid Dispatch router

[ https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556161#comment-15556161 ] Ted Ross commented on DISPATCH-337: --- It appears that the router is isolated and unreachable via AMQP.

[jira] [Comment Edited] (DISPATCH-337) Huge memory leaks in Qpid Dispatch router

[ https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556024#comment-15556024 ] Ted Ross edited comment on DISPATCH-337 at 10/7/16 7:24 PM: A couple of

[jira] [Commented] (DISPATCH-337) Huge memory leaks in Qpid Dispatch router

[ https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15556024#comment-15556024 ] Ted Ross commented on DISPATCH-337: --- A couple of questions: # In what way is the bad router rejecting

[jira] [Commented] (DISPATCH-525) What are proper names and units for protocol configuration settings?

[ https://issues.apache.org/jira/browse/DISPATCH-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15549843#comment-15549843 ] Ted Ross commented on DISPATCH-525: --- +1 on all of your proposed changes. > What are proper names and

[jira] [Updated] (DISPATCH-525) What are proper names and units for protocol configuration settings?

[ https://issues.apache.org/jira/browse/DISPATCH-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-525: -- Fix Version/s: 0.8.0 > What are proper names and units for protocol configuration settings? >

[jira] [Updated] (DISPATCH-471) server.c needs refactoring around qd_connection_t allocation

[ https://issues.apache.org/jira/browse/DISPATCH-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-471: -- Assignee: Chuck Rolke > server.c needs refactoring around qd_connection_t allocation >

[jira] [Resolved] (DISPATCH-224) Tools fail with no useful error in some SASL configurations

[ https://issues.apache.org/jira/browse/DISPATCH-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-224. --- Resolution: Fixed > Tools fail with no useful error in some SASL configurations >

[jira] [Commented] (DISPATCH-224) Tools fail with no useful error in some SASL configurations

[ https://issues.apache.org/jira/browse/DISPATCH-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15546047#comment-15546047 ] Ted Ross commented on DISPATCH-224: --- The issue here is that even though authenticatePeer is set to

[jira] [Updated] (DISPATCH-433) Navigating to console from bookmark displays empty page with just toolbars

[ https://issues.apache.org/jira/browse/DISPATCH-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-433: -- Fix Version/s: (was: 0.7.0) 0.8.0 > Navigating to console from bookmark

[jira] [Comment Edited] (DISPATCH-451) [AMQP] Hard coded session capacity should be configurable

[ https://issues.apache.org/jira/browse/DISPATCH-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15542646#comment-15542646 ] Ted Ross edited comment on DISPATCH-451 at 10/3/16 3:23 PM: The issue is in

[jira] [Updated] (DISPATCH-492) Add a way to request logs for a specific module

[ https://issues.apache.org/jira/browse/DISPATCH-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-492: -- Fix Version/s: (was: 0.7.0) > Add a way to request logs for a specific module >

[jira] [Updated] (DISPATCH-500) name in conf file is not sent in response to management query

[ https://issues.apache.org/jira/browse/DISPATCH-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-500: -- Fix Version/s: 0.6.2 > name in conf file is not sent in response to management query >

[jira] [Updated] (DISPATCH-523) Topology changes can cause in-flight deliveries to be stuck in the ingress router

[ https://issues.apache.org/jira/browse/DISPATCH-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-523: -- Fix Version/s: 0.6.2 > Topology changes can cause in-flight deliveries to be stuck in the ingress >

[jira] [Updated] (DISPATCH-505) Eventual loss of credit on inter-router control links when the topology changes

[ https://issues.apache.org/jira/browse/DISPATCH-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-505: -- Fix Version/s: 0.6.2 > Eventual loss of credit on inter-router control links when the topology >

[jira] [Updated] (DISPATCH-496) Activation of an autolink does not result in issuing credit to a blocked sender

[ https://issues.apache.org/jira/browse/DISPATCH-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-496: -- Fix Version/s: 0.6.2 > Activation of an autolink does not result in issuing credit to a blocked >

[jira] [Resolved] (DISPATCH-160) Dispatch router does not propagate custom message annotations

[ https://issues.apache.org/jira/browse/DISPATCH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-160. --- Resolution: Fixed > Dispatch router does not propagate custom message annotations >

[jira] [Updated] (DISPATCH-357) Address field is empty for link routed links in the qdstat "links" output

[ https://issues.apache.org/jira/browse/DISPATCH-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-357: -- Fix Version/s: (was: 0.7.0) 0.8.0 > Address field is empty for link routed

[jira] [Resolved] (DISPATCH-524) Unfair handling of multiple connections to the router

[ https://issues.apache.org/jira/browse/DISPATCH-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-524. --- Resolution: Fixed > Unfair handling of multiple connections to the router >

[jira] [Created] (DISPATCH-524) Unfair handling of multiple connections to the router

Ted Ross created DISPATCH-524: - Summary: Unfair handling of multiple connections to the router Key: DISPATCH-524 URL: https://issues.apache.org/jira/browse/DISPATCH-524 Project: Qpid Dispatch

[jira] [Resolved] (DISPATCH-521) Switch to verify qdrouterd installation

[ https://issues.apache.org/jira/browse/DISPATCH-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-521. --- Resolution: Fixed Fix Version/s: 0.7.0 > Switch to verify qdrouterd installation >

[jira] [Updated] (DISPATCH-521) Switch to verify qdrouterd installation

[ https://issues.apache.org/jira/browse/DISPATCH-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-521: -- Assignee: Ganesh Murthy > Switch to verify qdrouterd installation >

[jira] [Updated] (DISPATCH-466) Orderly Quiescence of Links

[ https://issues.apache.org/jira/browse/DISPATCH-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-466: -- Fix Version/s: (was: 0.7.0) 0.8.0 > Orderly Quiescence of Links >

[jira] [Updated] (DISPATCH-467) Terminus renaming for autoLinks

[ https://issues.apache.org/jira/browse/DISPATCH-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-467: -- Fix Version/s: (was: 0.7.0) 0.8.0 > Terminus renaming for autoLinks >

[jira] [Resolved] (DISPATCH-523) Topology changes can cause in-flight deliveries to be stuck in the ingress router

[ https://issues.apache.org/jira/browse/DISPATCH-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-523. --- Resolution: Fixed > Topology changes can cause in-flight deliveries to be stuck in the ingress >

[jira] [Created] (DISPATCH-523) Topology changes can cause in-flight deliveries to be stuck in the ingress router

Ted Ross created DISPATCH-523: - Summary: Topology changes can cause in-flight deliveries to be stuck in the ingress router Key: DISPATCH-523 URL: https://issues.apache.org/jira/browse/DISPATCH-523

[jira] [Commented] (DISPATCH-521) Switch to verify qdrouterd installation

[ https://issues.apache.org/jira/browse/DISPATCH-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15516417#comment-15516417 ] Ted Ross commented on DISPATCH-521: --- >>Running just qdrouterd is not sufficient, because port 5672 may

[jira] [Commented] (DISPATCH-337) Huge memory leaks in Qpid Dispatch router

[ https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514296#comment-15514296 ] Ted Ross commented on DISPATCH-337: --- There appear to be a lot of message deliveries in memory. Using

[jira] [Commented] (DISPATCH-337) Huge memory leaks in Qpid Dispatch router

[ https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15514110#comment-15514110 ] Ted Ross commented on DISPATCH-337: --- Vishal, It looks like the memory usage jumps up very suddenly.

[jira] [Commented] (DISPATCH-337) Huge memory leaks in Qpid Dispatch router

[ https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15513991#comment-15513991 ] Ted Ross commented on DISPATCH-337: --- Hi Vishal, Are you using SSL? If so, do you see the same memory

[jira] [Resolved] (DISPATCH-522) Performance: Defer activation and driver-awakening

[ https://issues.apache.org/jira/browse/DISPATCH-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-522. --- Resolution: Fixed > Performance: Defer activation and driver-awakening >

[jira] [Created] (DISPATCH-522) Performance: Defer activation and driver-awakening

Ted Ross created DISPATCH-522: - Summary: Performance: Defer activation and driver-awakening Key: DISPATCH-522 URL: https://issues.apache.org/jira/browse/DISPATCH-522 Project: Qpid Dispatch Issue

[jira] [Resolved] (DISPATCH-518) Use eventfd instead of a pipe for poll wakeup.

[ https://issues.apache.org/jira/browse/DISPATCH-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-518. --- Resolution: Fixed > Use eventfd instead of a pipe for poll wakeup. >

[jira] [Created] (DISPATCH-518) Use eventfd instead of a pipe for poll wakeup.

Ted Ross created DISPATCH-518: - Summary: Use eventfd instead of a pipe for poll wakeup. Key: DISPATCH-518 URL: https://issues.apache.org/jira/browse/DISPATCH-518 Project: Qpid Dispatch Issue

[jira] [Updated] (DISPATCH-103) Websocket Listeners

[ https://issues.apache.org/jira/browse/DISPATCH-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-103: -- Fix Version/s: (was: 0.7.0) > Websocket Listeners > --- > > Key:

[jira] [Resolved] (DISPATCH-514) Add link statistics for different dispositions

[ https://issues.apache.org/jira/browse/DISPATCH-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-514. --- Resolution: Fixed > Add link statistics for different dispositions >

[jira] [Created] (DISPATCH-514) Add link statistics for different dispositions

Ted Ross created DISPATCH-514: - Summary: Add link statistics for different dispositions Key: DISPATCH-514 URL: https://issues.apache.org/jira/browse/DISPATCH-514 Project: Qpid Dispatch Issue

[jira] [Resolved] (DISPATCH-479) Use atomic operations for ref counts

[ https://issues.apache.org/jira/browse/DISPATCH-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-479. --- Resolution: Fixed > Use atomic operations for ref counts > > >

[jira] [Resolved] (DISPATCH-513) Add a typed iterator to parsed field (qd_parsed_field_t)

[ https://issues.apache.org/jira/browse/DISPATCH-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-513. --- Resolution: Fixed > Add a typed iterator to parsed field (qd_parsed_field_t) >

[jira] [Updated] (DISPATCH-513) Add a typed iterator to parsed field (qd_parsed_field_t)

[ https://issues.apache.org/jira/browse/DISPATCH-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-513: -- Fix Version/s: 0.7.0 > Add a typed iterator to parsed field (qd_parsed_field_t) >

[jira] [Resolved] (DISPATCH-499) in propagating link detach the info field is dropped

[ https://issues.apache.org/jira/browse/DISPATCH-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-499. --- Resolution: Fixed > in propagating link detach the info field is dropped >

[jira] [Assigned] (DISPATCH-499) in propagating link detach the info field is dropped

[ https://issues.apache.org/jira/browse/DISPATCH-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-499: - Assignee: Ted Ross > in propagating link detach the info field is dropped >

[jira] [Resolved] (DISPATCH-505) Eventual loss of credit on inter-router control links when the topology changes

[ https://issues.apache.org/jira/browse/DISPATCH-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-505. --- Resolution: Fixed The underlying problem was that credit was not replenished for unroutable

[jira] [Resolved] (DISPATCH-511) Remove performance problems from locks and memory allocation

[ https://issues.apache.org/jira/browse/DISPATCH-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-511. --- Resolution: Fixed > Remove performance problems from locks and memory allocation >

[jira] [Commented] (DISPATCH-511) Remove performance problems from locks and memory allocation

[ https://issues.apache.org/jira/browse/DISPATCH-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494517#comment-15494517 ] Ted Ross commented on DISPATCH-511: --- Memory pool statistics are enabled by default. If you wish to

[jira] [Created] (DISPATCH-511) Remove performance problems from locks and memory allocation

Ted Ross created DISPATCH-511: - Summary: Remove performance problems from locks and memory allocation Key: DISPATCH-511 URL: https://issues.apache.org/jira/browse/DISPATCH-511 Project: Qpid Dispatch

[jira] [Assigned] (DISPATCH-479) Use atomic operations for ref counts

[ https://issues.apache.org/jira/browse/DISPATCH-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-479: - Assignee: Ted Ross (was: Ulf Lilleengen) > Use atomic operations for ref counts >

[jira] [Updated] (DISPATCH-160) Dispatch router does not propagate custom message annotations

[ https://issues.apache.org/jira/browse/DISPATCH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-160: -- Fix Version/s: 0.7.0 > Dispatch router does not propagate custom message annotations >

[jira] [Updated] (DISPATCH-160) Dispatch router does not propagate custom message annotations

[ https://issues.apache.org/jira/browse/DISPATCH-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-160: -- Priority: Critical (was: Minor) > Dispatch router does not propagate custom message annotations >

[jira] [Commented] (DISPATCH-8) Message:user-id must be authenticated on ingress

[ https://issues.apache.org/jira/browse/DISPATCH-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491244#comment-15491244 ] Ted Ross commented on DISPATCH-8: - The user_id is in the Properties, which is part of the bare message

[jira] [Updated] (DISPATCH-502) Seeing unexpected values in management query response

[ https://issues.apache.org/jira/browse/DISPATCH-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-502: -- Fix Version/s: 0.7.0 > Seeing unexpected values in management query response >

[jira] [Updated] (DISPATCH-500) name in conf file is not sent in response to management query

[ https://issues.apache.org/jira/browse/DISPATCH-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-500: -- Assignee: Ganesh Murthy > name in conf file is not sent in response to management query >

[jira] [Updated] (DISPATCH-501) router segfaults if you sent a management query with an empty body

[ https://issues.apache.org/jira/browse/DISPATCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-501: -- Assignee: Ganesh Murthy > router segfaults if you sent a management query with an empty body >

[jira] [Updated] (DISPATCH-500) name in conf file is not sent in response to management query

[ https://issues.apache.org/jira/browse/DISPATCH-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-500: -- Fix Version/s: 0.7.0 > name in conf file is not sent in response to management query >

[jira] [Updated] (DISPATCH-501) router segfaults if you sent a management query with an empty body

[ https://issues.apache.org/jira/browse/DISPATCH-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-501: -- Fix Version/s: 0.7.0 > router segfaults if you sent a management query with an empty body >

[jira] [Updated] (DISPATCH-499) in propagating link detach the info field is dropped

[ https://issues.apache.org/jira/browse/DISPATCH-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-499: -- Fix Version/s: 0.7.0 > in propagating link detach the info field is dropped >

[jira] [Updated] (DISPATCH-498) memory leak in _configure_ssl_profile error path

[ https://issues.apache.org/jira/browse/DISPATCH-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-498: -- Assignee: Ganesh Murthy > memory leak in _configure_ssl_profile error path >

[jira] [Updated] (DISPATCH-498) memory leak in _configure_ssl_profile error path

[ https://issues.apache.org/jira/browse/DISPATCH-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-498: -- Fix Version/s: 0.7.0 > memory leak in _configure_ssl_profile error path >

[jira] [Updated] (DISPATCH-8) Message:user-id must be authenticated on ingress

[ https://issues.apache.org/jira/browse/DISPATCH-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-8: Assignee: Chuck Rolke > Message:user-id must be authenticated on ingress >

[jira] [Updated] (DISPATCH-505) Eventual loss of credit on inter-router control links when the topology changes

[ https://issues.apache.org/jira/browse/DISPATCH-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-505: -- Description: It was observed that in a network of routers, connectivity would be lost on some of the

[jira] [Created] (DISPATCH-505) Eventual loss of credit on inter-router control links when the topology changes

Ted Ross created DISPATCH-505: - Summary: Eventual loss of credit on inter-router control links when the topology changes Key: DISPATCH-505 URL: https://issues.apache.org/jira/browse/DISPATCH-505 Project:

[jira] [Resolved] (DISPATCH-495) Autolinks to non-existent nodes cause problems in the router

[ https://issues.apache.org/jira/browse/DISPATCH-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-495. --- Resolution: Fixed > Autolinks to non-existent nodes cause problems in the router >

[jira] [Resolved] (DISPATCH-496) Activation of an autolink does not result in issuing credit to a blocked sender

[ https://issues.apache.org/jira/browse/DISPATCH-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-496. --- Resolution: Fixed > Activation of an autolink does not result in issuing credit to a blocked >

[jira] [Closed] (DISPATCH-497) Activation of an autolink does not result in issuing credit to a blocked sender

[ https://issues.apache.org/jira/browse/DISPATCH-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross closed DISPATCH-497. - Resolution: Duplicate > Activation of an autolink does not result in issuing credit to a blocked >

[jira] [Created] (DISPATCH-497) Activation of an autolink does not result in issuing credit to a blocked sender

Ted Ross created DISPATCH-497: - Summary: Activation of an autolink does not result in issuing credit to a blocked sender Key: DISPATCH-497 URL: https://issues.apache.org/jira/browse/DISPATCH-497 Project:

[jira] [Created] (DISPATCH-496) Activation of an autolink does not result in issuing credit to a blocked sender

Ted Ross created DISPATCH-496: - Summary: Activation of an autolink does not result in issuing credit to a blocked sender Key: DISPATCH-496 URL: https://issues.apache.org/jira/browse/DISPATCH-496 Project:

[jira] [Created] (DISPATCH-495) Autolinks to non-existent nodes cause problems in the router

Ted Ross created DISPATCH-495: - Summary: Autolinks to non-existent nodes cause problems in the router Key: DISPATCH-495 URL: https://issues.apache.org/jira/browse/DISPATCH-495 Project: Qpid Dispatch

[jira] [Updated] (DISPATCH-468) Display-name for identity in x.509 certificates

[ https://issues.apache.org/jira/browse/DISPATCH-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-468: -- Assignee: Chuck Rolke > Display-name for identity in x.509 certificates >

[jira] [Resolved] (DISPATCH-491) Frequent skipped HELLO message from route engine

[ https://issues.apache.org/jira/browse/DISPATCH-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-491. --- Resolution: Fixed > Frequent skipped HELLO message from route engine >

[jira] [Created] (DISPATCH-491) Frequent skipped HELLO message from route engine

Ted Ross created DISPATCH-491: - Summary: Frequent skipped HELLO message from route engine Key: DISPATCH-491 URL: https://issues.apache.org/jira/browse/DISPATCH-491 Project: Qpid Dispatch Issue

[jira] [Updated] (DISPATCH-479) Use atomic operations for ref counts

[ https://issues.apache.org/jira/browse/DISPATCH-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-479: -- Fix Version/s: 0.7.0 > Use atomic operations for ref counts > >

[jira] [Updated] (DISPATCH-479) Use atomic operations for ref counts

[ https://issues.apache.org/jira/browse/DISPATCH-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-479: -- Assignee: Ulf Lilleengen > Use atomic operations for ref counts >

[jira] [Updated] (DISPATCH-244) SASL library generates un-necessary DNS and LDAP requests

[ https://issues.apache.org/jira/browse/DISPATCH-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-244: -- Fix Version/s: (was: 0.7.0) > SASL library generates un-necessary DNS and LDAP requests >

[jira] [Updated] (DISPATCH-205) Schema.validate() called many times

[ https://issues.apache.org/jira/browse/DISPATCH-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-205: -- Fix Version/s: (was: 0.7.0) 0.8.0 > Schema.validate() called many times >

[jira] [Resolved] (DISPATCH-177) Valgrind finds leaks when running dispatch w/SSL

[ https://issues.apache.org/jira/browse/DISPATCH-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-177. --- Resolution: Fixed Fix Version/s: (was: 0.7.0) 0.6.0 I'm resolving

[jira] [Resolved] (DISPATCH-336) Very high latency for fire-and-forget sender

[ https://issues.apache.org/jira/browse/DISPATCH-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-336. --- Resolution: Fixed > Very high latency for fire-and-forget sender >

[jira] [Resolved] (DISPATCH-477) Drop pre-settled under congestion

[ https://issues.apache.org/jira/browse/DISPATCH-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-477. --- Resolution: Fixed > Drop pre-settled under congestion > - > >

[jira] [Commented] (DISPATCH-336) Very high latency for fire-and-forget sender

[ https://issues.apache.org/jira/browse/DISPATCH-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424994#comment-15424994 ] Ted Ross commented on DISPATCH-336: --- Dropping pre-settled deliveries under congestion will resolve

<    2   3   4   5   6   7   8   9   10   11   >