[jira] [Commented] (QPID-4047) IoNetworkTransport doesn't use timeout on socket connect

[ https://issues.apache.org/jira/browse/QPID-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292061#comment-13292061 ] Praveen Murugesan commented on QPID-4047: - Rob, Thanks for getting to this immediat

[jira] [Commented] (QPID-2960) Broker Windows SSL implementation prevent broker to run as a windows service under a service account user (local service, network service)

[ https://issues.apache.org/jira/browse/QPID-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292024#comment-13292024 ] Steve Huston commented on QPID-2960: This should be re-tested with 0.17. QPID-4013 may

[jira] [Created] (QPID-4049) Linux C++ broker crashes when Windows client connects SSL with expired certificate

Steve Huston created QPID-4049: -- Summary: Linux C++ broker crashes when Windows client connects SSL with expired certificate Key: QPID-4049 URL: https://issues.apache.org/jira/browse/QPID-4049 Project: Q

[jira] [Resolved] (QPID-4048) Refactor TopicExchange to separate the topic-key lookup engine from the exchange

[ https://issues.apache.org/jira/browse/QPID-4048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-4048. Resolution: Fixed > Refactor TopicExchange to separate the topic-key lookup engine from the > exchange

[jira] [Created] (QPID-4048) Refactor TopicExchange to separate the topic-key lookup engine from the exchange

Ted Ross created QPID-4048: -- Summary: Refactor TopicExchange to separate the topic-key lookup engine from the exchange Key: QPID-4048 URL: https://issues.apache.org/jira/browse/QPID-4048 Project: Qpid

[jira] [Resolved] (QPID-4047) IoNetworkTransport doesn't use timeout on socket connect

[ https://issues.apache.org/jira/browse/QPID-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved QPID-4047. --- Resolution: Fixed I've made an equivalent change (since the value of _timeout is fixed and cannot be

[jira] [Commented] (QPID-4047) IoNetworkTransport doesn't use timeout on socket connect

[ https://issues.apache.org/jira/browse/QPID-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291941#comment-13291941 ] Rob Godfrey commented on QPID-4047: --- Seems like a reasonable enhancement. Ideally we shou

[jira] [Assigned] (QPID-4047) IoNetworkTransport doesn't use timeout on socket connect

[ https://issues.apache.org/jira/browse/QPID-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-4047: - Assignee: Rob Godfrey > IoNetworkTransport doesn't use timeout on socket connect > ---

[jira] [Updated] (QPID-4047) IoNetworkTransport doesn't use timeout on socket connect

[ https://issues.apache.org/jira/browse/QPID-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Murugesan updated QPID-4047: Attachment: addTimeOutOnSocketConnect.patch Patch. > IoNetworkTransport doe

[jira] [Created] (QPID-4047) IoNetworkTransport doesn't use timeout on socket connect

Praveen Murugesan created QPID-4047: --- Summary: IoNetworkTransport doesn't use timeout on socket connect Key: QPID-4047 URL: https://issues.apache.org/jira/browse/QPID-4047 Project: Qpid Iss

[jira] [Commented] (QPID-4012) [Java Broker] PriorityQueue entries may attempt to access message metadata in the store after it is no longer available

[ https://issues.apache.org/jira/browse/QPID-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291893#comment-13291893 ] Praveen Murugesan commented on QPID-4012: - Hi Robbie, I tested the change. It work

[jira] [Commented] (QPID-4022) C++ Broker connection limits by host ip and by user name can get confused

[ https://issues.apache.org/jira/browse/QPID-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291848#comment-13291848 ] Andrew Stitcher commented on QPID-4022: --- This patch looks good. Just one thing: It

[jira] [Resolved] (QPID-4046) Improve broker's performance by rate limiting queue cleanup.

[ https://issues.apache.org/jira/browse/QPID-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved QPID-4046. -- Resolution: Fixed > Improve broker's performance by rate limiting queue cleanup. > -

Re: Federation Problem

Hi Nitin, I was able to get everything working, at least against the latest build from Subversion. I haven't tried this against 0.16, however. qpid-route dynamic add localhost:5672 localhost:5673 amq.topic qpid-route dynamic add localhost:5673 localhost:5672 amq.topic qpid-route dynamic add loc

[jira] [Updated] (QPID-4022) C++ Broker connection limits by host ip and by user name can get confused

[ https://issues.apache.org/jira/browse/QPID-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated QPID-4022: -- Attachment: QPID-4022-conn-limits-rev2-10-with-tests.patch I put the last patch up for review a week ago

[jira] [Resolved] (QPID-4045) [Java broker] remove the 'extras' plugin as it isnt used

[ https://issues.apache.org/jira/browse/QPID-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved QPID-4045. -- Resolution: Fixed > [Java broker] remove the 'extras' plugin as it isnt used > -