[jira] [Commented] (DISPATCH-334) Proton sequence error during backpressure with balanced distribution

[ https://issues.apache.org/jira/browse/DISPATCH-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15282039#comment-15282039 ] Ted Ross commented on DISPATCH-334: --- Of possible interest: This test case involves out-of-order

[jira] [Created] (DISPATCH-334) Proton sequence error during backpressure with balanced distribution

Ted Ross created DISPATCH-334: - Summary: Proton sequence error during backpressure with balanced distribution Key: DISPATCH-334 URL: https://issues.apache.org/jira/browse/DISPATCH-334 Project: Qpid

[jira] [Commented] (DISPATCH-332) Heavy message loss happening with 2 interconnected routers

[ https://issues.apache.org/jira/browse/DISPATCH-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15280552#comment-15280552 ] Ted Ross commented on DISPATCH-332: --- I tried to reproduce your symptom and didn't see any problem. If

[jira] [Resolved] (DISPATCH-319) Discrepancy between origin router's path and other routers' valid-origins

[ https://issues.apache.org/jira/browse/DISPATCH-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-319. --- Resolution: Fixed > Discrepancy between origin router's path and other routers' valid-origins >

[jira] [Commented] (DISPATCH-332) Heavy message loss happening with 2 interconnected routers

[ https://issues.apache.org/jira/browse/DISPATCH-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15280288#comment-15280288 ] Ted Ross commented on DISPATCH-332: --- Can you provide information about what distribution settings you

[jira] [Updated] (DISPATCH-332) Heavy message loss happening with 2 interconnected routers

[ https://issues.apache.org/jira/browse/DISPATCH-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-332: -- Fix Version/s: 0.6.0 > Heavy message loss happening with 2 interconnected routers >

[jira] [Assigned] (DISPATCH-332) Heavy message loss happening with 2 interconnected routers

[ https://issues.apache.org/jira/browse/DISPATCH-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-332: - Assignee: Ted Ross > Heavy message loss happening with 2 interconnected routers >

[jira] [Commented] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15279005#comment-15279005 ] Ted Ross commented on DISPATCH-290: --- Sure. I interpreted your comment from the 25th as a request to

[jira] [Assigned] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-290: - Assignee: Ted Ross > Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on

[jira] [Resolved] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-290. --- Resolution: Fixed > Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[jira] [Updated] (DISPATCH-330) Access control policy should return more suitable errors

[ https://issues.apache.org/jira/browse/DISPATCH-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-330: -- Assignee: Chuck Rolke > Access control policy should return more suitable errors >

[jira] [Updated] (DISPATCH-211) Expose connection properties in management response

[ https://issues.apache.org/jira/browse/DISPATCH-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-211: -- Fix Version/s: 0.7.0 > Expose connection properties in management response >

[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: -- Assignee: (was: Ted Ross) > Websocket Listeners > --- > > Key:

[jira] [Created] (DISPATCH-331) Allow for a default policy to apply when open.hostname doesn't match an existing policy

Ted Ross created DISPATCH-331: - Summary: Allow for a default policy to apply when open.hostname doesn't match an existing policy Key: DISPATCH-331 URL: https://issues.apache.org/jira/browse/DISPATCH-331

[jira] [Resolved] (DISPATCH-47) qdrouterd doesn't know where its libraries are

[ https://issues.apache.org/jira/browse/DISPATCH-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-47. -- Resolution: Fixed Assignee: Ted Ross Fix Version/s: 0.6.0 > qdrouterd doesn't know

[jira] [Resolved] (DISPATCH-53) waypoints are not robust if targets not set up in advance.

[ https://issues.apache.org/jira/browse/DISPATCH-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-53. -- Resolution: Fixed Assignee: Ted Ross Fix Version/s: 0.6.0 > waypoints are not robust

[jira] [Resolved] (DISPATCH-58) Router/Broker interaction - Unroutable/released messages are continually resent

[ https://issues.apache.org/jira/browse/DISPATCH-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-58. -- Resolution: Fixed Fix Version/s: 0.6.0 > Router/Broker interaction - Unroutable/released

[jira] [Resolved] (DISPATCH-175) Router continues to forward messages to the broker even when the broker is not available

[ https://issues.apache.org/jira/browse/DISPATCH-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-175. --- Resolution: Fixed Assignee: Ted Ross Fix Version/s: 0.6.0 > Router continues to

[jira] [Resolved] (DISPATCH-176) Messages sent got lost when one of the brokers went down

[ https://issues.apache.org/jira/browse/DISPATCH-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-176. --- Resolution: Fixed Assignee: Ted Ross Fix Version/s: 0.6.0 > Messages sent got lost

[jira] [Resolved] (DISPATCH-207) When a message body of [ ] is sent from rhea it is rejected as an invalid body

[ https://issues.apache.org/jira/browse/DISPATCH-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-207. --- Resolution: Fixed Assignee: Ganesh Murthy Fix Version/s: 0.6.0 > When a message

[jira] [Resolved] (DISPATCH-234) undeliverable-here set to true for messages from waypoints if there is no receiver

[ https://issues.apache.org/jira/browse/DISPATCH-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-234. --- Resolution: Fixed Fix Version/s: 0.6.0 The 0.6.0 architecture update removes this behavior.

[jira] [Updated] (DISPATCH-306) Deprecate addr and routerId attributes in qdrouter schema and replace them with host and id respectively

[ https://issues.apache.org/jira/browse/DISPATCH-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-306: -- Fix Version/s: 0.6.0 > Deprecate addr and routerId attributes in qdrouter schema and replace them >

[jira] [Updated] (DISPATCH-310) Use router.id instead of container.containerName

[ https://issues.apache.org/jira/browse/DISPATCH-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-310: -- Fix Version/s: 0.6.0 > Use router.id instead of container.containerName >

[jira] [Updated] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-290: -- Fix Version/s: 0.6.0 > Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[jira] [Updated] (DISPATCH-320) SSL enabled connector does not do hostname verification

[ https://issues.apache.org/jira/browse/DISPATCH-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-320: -- Fix Version/s: 0.6.0 > SSL enabled connector does not do hostname verification >

[jira] [Created] (DISPATCH-319) Discrepancy between origin router's path and other routers' valid-origins

Ted Ross created DISPATCH-319: - Summary: Discrepancy between origin router's path and other routers' valid-origins Key: DISPATCH-319 URL: https://issues.apache.org/jira/browse/DISPATCH-319 Project: Qpid

[jira] [Resolved] (DISPATCH-309) Mobile addresses get the wrong distribution when mapped to remote routers

[ https://issues.apache.org/jira/browse/DISPATCH-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-309. --- Resolution: Fixed > Mobile addresses get the wrong distribution when mapped to remote routers >

[jira] [Created] (DISPATCH-312) Closest distribution fails to react to loss of a remote destination

Ted Ross created DISPATCH-312: - Summary: Closest distribution fails to react to loss of a remote destination Key: DISPATCH-312 URL: https://issues.apache.org/jira/browse/DISPATCH-312 Project: Qpid

[jira] [Created] (DISPATCH-309) Mobile addresses get the wrong distribution when mapped to remote routers

Ted Ross created DISPATCH-309: - Summary: Mobile addresses get the wrong distribution when mapped to remote routers Key: DISPATCH-309 URL: https://issues.apache.org/jira/browse/DISPATCH-309 Project: Qpid

[jira] [Resolved] (DISPATCH-194) Move libqpid-dispatch.so out of /lib

[ https://issues.apache.org/jira/browse/DISPATCH-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-194. --- Resolution: Fixed > Move libqpid-dispatch.so out of /lib > > >

[jira] [Resolved] (DISPATCH-305) Don't tie inter-router flow credit to unsettled deliveries

[ https://issues.apache.org/jira/browse/DISPATCH-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-305. --- Resolution: Fixed > Don't tie inter-router flow credit to unsettled deliveries >

[jira] [Created] (DISPATCH-305) Don't tie inter-router flow credit to unsettled deliveries

Ted Ross created DISPATCH-305: - Summary: Don't tie inter-router flow credit to unsettled deliveries Key: DISPATCH-305 URL: https://issues.apache.org/jira/browse/DISPATCH-305 Project: Qpid Dispatch

[jira] [Resolved] (DISPATCH-238) Need more documentation for qdstat output

[ https://issues.apache.org/jira/browse/DISPATCH-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-238. --- Resolution: Fixed > Need more documentation for qdstat output >

[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.6) 0.7 > SASL library generates un-necessary DNS and

[jira] [Resolved] (DISPATCH-32) Undeliverable messages should get released.

[ https://issues.apache.org/jira/browse/DISPATCH-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-32. -- Resolution: Fixed I claim that this issue is resolved in 0.6.0. It would be good to retest this

[jira] [Updated] (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 updated DISPATCH-177: -- Fix Version/s: (was: 0.6) 0.7 > Valgrind finds leaks when running dispatch

[jira] [Commented] (DISPATCH-197) Provide list of current link routing

[ https://issues.apache.org/jira/browse/DISPATCH-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15270576#comment-15270576 ] Ted Ross commented on DISPATCH-197: --- A new attribute "peer" has been added to the link entity. Peer

[jira] [Resolved] (DISPATCH-197) Provide list of current link routing

[ https://issues.apache.org/jira/browse/DISPATCH-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-197. --- Resolution: Fixed > Provide list of current link routing > > >

[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.6) 0.7 > Schema.validate() called many times >

[jira] [Updated] (DISPATCH-224) Default installed configuration fails without error message.

[ https://issues.apache.org/jira/browse/DISPATCH-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-224: -- Fix Version/s: (was: 0.6) 0.7 > Default installed configuration fails without

[jira] [Updated] (DISPATCH-265) Improvements to Detecting Routers with Duplicate IDs

[ https://issues.apache.org/jira/browse/DISPATCH-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-265: -- Summary: Improvements to Detecting Routers with Duplicate IDs (was: Improvements to Monitoring) >

[jira] [Resolved] (DISPATCH-265) Improvements to Detecting Routers with Duplicate IDs

[ https://issues.apache.org/jira/browse/DISPATCH-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-265. --- Resolution: Fixed > Improvements to Detecting Routers with Duplicate IDs >

[jira] [Updated] (DISPATCH-265) Improvements to Monitoring

[ https://issues.apache.org/jira/browse/DISPATCH-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-265: -- Description: The router module should provide logs when it detects a duplicate neighbor. Also, an

[jira] [Resolved] (DISPATCH-300) Deprecate the ContainerEntity and move its attributes to RouterEntity

[ https://issues.apache.org/jira/browse/DISPATCH-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-300. --- Resolution: Fixed > Deprecate the ContainerEntity and move its attributes to RouterEntity >

[jira] [Updated] (DISPATCH-300) Deprecate the ContainerEntity and move its attributes to RouterEntity

[ https://issues.apache.org/jira/browse/DISPATCH-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-300: -- Fix Version/s: 0.6 > Deprecate the ContainerEntity and move its attributes to RouterEntity >

[jira] [Assigned] (DISPATCH-194) Move libqpid-dispatch.so out of /lib

[ https://issues.apache.org/jira/browse/DISPATCH-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-194: - Assignee: Ted Ross (was: Chuck Rolke) > Move libqpid-dispatch.so out of /lib >

[jira] [Updated] (DISPATCH-57) Balance deliveries adaptively across all competing consumers in the network

[ https://issues.apache.org/jira/browse/DISPATCH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-57: - Description: When there are multiple competing consumers on an address across a network, the network

[jira] [Resolved] (DISPATCH-303) Block all remote access to the "console" entity

[ https://issues.apache.org/jira/browse/DISPATCH-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-303. --- Resolution: Fixed > Block all remote access to the "console" entity >

[jira] [Assigned] (DISPATCH-303) Block all remote access to the "console" entity

[ https://issues.apache.org/jira/browse/DISPATCH-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-303: - Assignee: Ted Ross > Block all remote access to the "console" entity >

[jira] [Created] (DISPATCH-303) Block all remote access to the "console" entity

Ted Ross created DISPATCH-303: - Summary: Block all remote access to the "console" entity Key: DISPATCH-303 URL: https://issues.apache.org/jira/browse/DISPATCH-303 Project: Qpid Dispatch Issue

[jira] [Updated] (DISPATCH-199) Add Dockerfiles that launches the dispatch router inside a container for RHEL and Debian based systems

[ https://issues.apache.org/jira/browse/DISPATCH-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-199: -- Assignee: Ganesh Murthy > Add Dockerfiles that launches the dispatch router inside a container for

[jira] [Assigned] (DISPATCH-203) Improve loop-prevention to drop messages before they are improperly forwarded

[ https://issues.apache.org/jira/browse/DISPATCH-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-203: - Assignee: Ted Ross > Improve loop-prevention to drop messages before they are improperly

[jira] [Updated] (DISPATCH-222) For Dispatch 0.6 release move up the minimum required version of qpid proton to 0.12.0

[ https://issues.apache.org/jira/browse/DISPATCH-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-222: -- Assignee: Ganesh Murthy > For Dispatch 0.6 release move up the minimum required version of qpid

[jira] [Assigned] (DISPATCH-288) Driver - Wakeup pipe was seen to block on read, deadlocking the driver.

[ https://issues.apache.org/jira/browse/DISPATCH-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-288: - Assignee: Ted Ross > Driver - Wakeup pipe was seen to block on read, deadlocking the driver. >

[jira] [Updated] (DISPATCH-299) After policy rejects a connection queued Begin causes a crash

[ https://issues.apache.org/jira/browse/DISPATCH-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-299: -- Assignee: Chuck Rolke > After policy rejects a connection queued Begin causes a crash >

[jira] [Assigned] (DISPATCH-295) Router aborted on assertion failed after socker closing by client

[ https://issues.apache.org/jira/browse/DISPATCH-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-295: - Assignee: Ted Ross > Router aborted on assertion failed after socker closing by client >

[jira] [Resolved] (DISPATCH-295) Router aborted on assertion failed after socker closing by client

[ https://issues.apache.org/jira/browse/DISPATCH-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-295. --- Resolution: Fixed > Router aborted on assertion failed after socker closing by client >

[jira] [Updated] (DISPATCH-295) Router aborted on assertion failed after socker closing by client

[ https://issues.apache.org/jira/browse/DISPATCH-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-295: -- Fix Version/s: 0.6 > Router aborted on assertion failed after socker closing by client >

[jira] [Resolved] (DISPATCH-298) router spinning on shutdown (in qdr_del_connection_ref)

[ https://issues.apache.org/jira/browse/DISPATCH-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-298. --- Resolution: Fixed > router spinning on shutdown (in qdr_del_connection_ref) >

[jira] [Assigned] (DISPATCH-298) router spinning on shutdown (in qdr_del_connection_ref)

[ https://issues.apache.org/jira/browse/DISPATCH-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-298: - Assignee: Ted Ross > router spinning on shutdown (in qdr_del_connection_ref) >

[jira] [Updated] (DISPATCH-298) router spinning on shutdown (in qdr_del_connection_ref)

[ https://issues.apache.org/jira/browse/DISPATCH-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-298: -- Fix Version/s: 0.6 > router spinning on shutdown (in qdr_del_connection_ref) >

[jira] [Commented] (DISPATCH-295) Router aborted on assertion failed after socker closing by client

[ https://issues.apache.org/jira/browse/DISPATCH-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257935#comment-15257935 ] Ted Ross commented on DISPATCH-295: --- I'm wondering if this is related to DISPATCH-294. Did the router

[jira] [Resolved] (DISPATCH-294) Crash in the core-thread due to an address referencing a link on a closed connection

[ https://issues.apache.org/jira/browse/DISPATCH-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-294. --- Resolution: Fixed > Crash in the core-thread due to an address referencing a link on a closed >

[jira] [Created] (DISPATCH-294) Crash in the core-thread due to an address referencing a link on a closed connection

Ted Ross created DISPATCH-294: - Summary: Crash in the core-thread due to an address referencing a link on a closed connection Key: DISPATCH-294 URL: https://issues.apache.org/jira/browse/DISPATCH-294

[jira] [Resolved] (DISPATCH-10) Add link-cost for route computation

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

[jira] [Resolved] (DISPATCH-208) Closest semantics forwards improperly in multi-router network

[ https://issues.apache.org/jira/browse/DISPATCH-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-208. --- Resolution: Fixed > Closest semantics forwards improperly in multi-router network >

[jira] [Updated] (DISPATCH-10) Add link-cost for route computation

[ https://issues.apache.org/jira/browse/DISPATCH-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-10: - Description: The route computation algorithm has the ability to take link cost into consideration when

[jira] [Updated] (DISPATCH-10) Add link-cost for route computation

[ https://issues.apache.org/jira/browse/DISPATCH-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-10: - Description: The route computation algorithm has the ability to take link cost into consideration when

[jira] [Updated] (DISPATCH-10) Add link-cost for route computation

[ https://issues.apache.org/jira/browse/DISPATCH-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-10: - Fix Version/s: 0.6 > Add link-cost for route computation > --- > >

[jira] [Updated] (DISPATCH-10) Add link-cost for route computation

[ https://issues.apache.org/jira/browse/DISPATCH-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-10: - Issue Type: New Feature (was: Improvement) > Add link-cost for route computation >

[jira] [Commented] (DISPATCH-208) Closest semantics forwards improperly in multi-router network

[ https://issues.apache.org/jira/browse/DISPATCH-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15254580#comment-15254580 ] Ted Ross commented on DISPATCH-208: --- In order to properly choose the lowest-cost remote router, it

[jira] [Assigned] (DISPATCH-10) Add link-cost for route computation

[ https://issues.apache.org/jira/browse/DISPATCH-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-10: Assignee: Ted Ross > Add link-cost for route computation > --- >

[jira] [Updated] (DISPATCH-290) Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-290: -- Attachment: dispatch-290.patch Here's a slightly modified version of your patch. The differences are

[jira] [Resolved] (DISPATCH-289) Unit tests failing on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-289. --- Resolution: Fixed > Unit tests failing on Solaris > - > >

[jira] [Resolved] (DISPATCH-288) Driver - Wakeup pipe was seen to block on read, deadlocking the driver.

[ https://issues.apache.org/jira/browse/DISPATCH-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-288. --- Resolution: Fixed > Driver - Wakeup pipe was seen to block on read, deadlocking the driver. >

[jira] [Assigned] (DISPATCH-289) Unit tests failing on Solaris

[ https://issues.apache.org/jira/browse/DISPATCH-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-289: - Assignee: Ted Ross > Unit tests failing on Solaris > - > >

[jira] [Commented] (DISPATCH-288) Driver - Wakeup pipe was seen to block on read, deadlocking the driver.

[ https://issues.apache.org/jira/browse/DISPATCH-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250734#comment-15250734 ] Ted Ross commented on DISPATCH-288: --- The pipe established in the driver for waking up the poll loop is

[jira] [Created] (DISPATCH-288) Driver - Wakeup pipe was seen to block on read, deadlocking the driver.

Ted Ross created DISPATCH-288: - Summary: Driver - Wakeup pipe was seen to block on read, deadlocking the driver. Key: DISPATCH-288 URL: https://issues.apache.org/jira/browse/DISPATCH-288 Project: Qpid

[jira] [Resolved] (DISPATCH-286) Prefix delimiters: allow slashes as well as periods

[ https://issues.apache.org/jira/browse/DISPATCH-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-286. --- Resolution: Fixed > Prefix delimiters: allow slashes as well as periods >

[jira] [Commented] (DISPATCH-286) Prefix delimiters: allow slashes as well as periods

[ https://issues.apache.org/jira/browse/DISPATCH-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15250030#comment-15250030 ] Ted Ross commented on DISPATCH-286: --- This is not so much a pattern-matching problem as it is a

[jira] [Created] (DISPATCH-286) Prefix delimiters: allow slashes as well as periods

Ted Ross created DISPATCH-286: - Summary: Prefix delimiters: allow slashes as well as periods Key: DISPATCH-286 URL: https://issues.apache.org/jira/browse/DISPATCH-286 Project: Qpid Dispatch

[jira] [Updated] (DISPATCH-285) qdmanage returns an empty list when you QUERY for certain entities

[ https://issues.apache.org/jira/browse/DISPATCH-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-285: -- Fix Version/s: 0.6 > qdmanage returns an empty list when you QUERY for certain entities >

[jira] [Updated] (DISPATCH-261) Bind error on one port causes bind error on other ports

[ https://issues.apache.org/jira/browse/DISPATCH-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-261: -- Fix Version/s: 0.6 > Bind error on one port causes bind error on other ports >

[jira] [Updated] (DISPATCH-275) Prevent javascript alert errors when navigating to console from a bookmark

[ https://issues.apache.org/jira/browse/DISPATCH-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-275: -- Fix Version/s: 0.6 > Prevent javascript alert errors when navigating to console from a bookmark >

[jira] [Updated] (DISPATCH-281) Hostname not sent in open frame on connectors

[ https://issues.apache.org/jira/browse/DISPATCH-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-281: -- Fix Version/s: 0.6 > Hostname not sent in open frame on connectors >

[jira] [Resolved] (DISPATCH-277) Improve defaults for router configuration

[ https://issues.apache.org/jira/browse/DISPATCH-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-277. --- Resolution: Fixed > Improve defaults for router configuration >

[jira] [Resolved] (DISPATCH-278) Deleting amqp listener using qdmanage crashes the router

[ https://issues.apache.org/jira/browse/DISPATCH-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-278. --- Resolution: Fixed Fix Version/s: 0.6 > Deleting amqp listener using qdmanage crashes the

[jira] [Assigned] (DISPATCH-278) Deleting amqp listener using qdmanage crashes the router

[ https://issues.apache.org/jira/browse/DISPATCH-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-278: - Assignee: Ted Ross > Deleting amqp listener using qdmanage crashes the router >

[jira] [Created] (DISPATCH-277) Improve defaults for router configuration

Ted Ross created DISPATCH-277: - Summary: Improve defaults for router configuration Key: DISPATCH-277 URL: https://issues.apache.org/jira/browse/DISPATCH-277 Project: Qpid Dispatch Issue Type:

[jira] [Resolved] (DISPATCH-237) Dispatch Router overwrites delivery tag for link-routed deliveries

[ https://issues.apache.org/jira/browse/DISPATCH-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-237. --- Resolution: Fixed > Dispatch Router overwrites delivery tag for link-routed deliveries >

[jira] [Updated] (DISPATCH-171) SSL Domain objects are leaked.

[ https://issues.apache.org/jira/browse/DISPATCH-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-171: -- Affects Version/s: (was: 0.6) > SSL Domain objects are leaked. > -- >

[jira] [Resolved] (DISPATCH-263) Router crash when requesting log

[ https://issues.apache.org/jira/browse/DISPATCH-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-263. --- Resolution: Fixed > Router crash when requesting log > > >

[jira] [Resolved] (DISPATCH-263) Router crash when requesting log

[ https://issues.apache.org/jira/browse/DISPATCH-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-263. --- Resolution: Fixed Good work, Ganesh and Ernie. > Router crash when requesting log >

[jira] [Commented] (DISPATCH-263) Router crash when requesting log

[ https://issues.apache.org/jira/browse/DISPATCH-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15239143#comment-15239143 ] Ted Ross commented on DISPATCH-263: --- This is a really good find... This can be reproduced by sending a

[jira] [Updated] (DISPATCH-263) Router crash when requesting log

[ https://issues.apache.org/jira/browse/DISPATCH-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-263: -- Priority: Blocker (was: Major) > Router crash when requesting log >

[jira] [Updated] (DISPATCH-263) Router crash when requesting log

[ https://issues.apache.org/jira/browse/DISPATCH-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-263: -- Fix Version/s: 0.6 > Router crash when requesting log > > >

[jira] [Resolved] (DISPATCH-268) Delivery from waypoint queue can stall when messages are released

[ https://issues.apache.org/jira/browse/DISPATCH-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-268. --- Resolution: Fixed > Delivery from waypoint queue can stall when messages are released >

[jira] [Created] (DISPATCH-265) Improvements to Monitoring

Ted Ross created DISPATCH-265: - Summary: Improvements to Monitoring Key: DISPATCH-265 URL: https://issues.apache.org/jira/browse/DISPATCH-265 Project: Qpid Dispatch Issue Type: Improvement

[jira] [Resolved] (DISPATCH-264) printf formats for 64-bit quantities need to be 64/32-bit safe

[ https://issues.apache.org/jira/browse/DISPATCH-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-264. --- Resolution: Fixed > printf formats for 64-bit quantities need to be 64/32-bit safe >

[jira] [Resolved] (DISPATCH-262) oslo.messaging RPC fanout crashes qdrouterd

[ https://issues.apache.org/jira/browse/DISPATCH-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved DISPATCH-262. --- Resolution: Fixed > oslo.messaging RPC fanout crashes qdrouterd >

<    4   5   6   7   8   9   10   11   12   13   >