[jira] Resolved: (QPID-2048) Client can hang on close() if broker is simultaenously killed

[ https://issues.apache.org/jira/browse/QPID-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-2048. -- Resolution: Fixed > Client can hang on close() if broker is simultaenously killed >

[jira] Updated: (QPID-2045) crash when destroying a federation link with a dynamic bridge

[ https://issues.apache.org/jira/browse/QPID-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated QPID-2045: - Attachment: QPID-2045.diff Proposed fix: call bridge's closed() method when removing it from the active v

[jira] Resolved: (QPID-1971) bind in fedOpReorigen mode is not threadsafe for TopicExchange

[ https://issues.apache.org/jira/browse/QPID-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-1971. Resolution: Fixed > bind in fedOpReorigen mode is not threadsafe for TopicExchange > ---

[jira] Resolved: (QPID-2046) Closing of a federation link done on management thread, not links own io thread

[ https://issues.apache.org/jira/browse/QPID-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross resolved QPID-2046. Resolution: Fixed > Closing of a federation link done on management thread, not links own io > thread > ---

[Java] Java6 JVM, AttachAPI and local JMX connections to the broker

Java6 supports the Attach API, which allows local injection of an Agent into a running Java6 capable JVM. The main drive behind it was the ability to attach monitoring utilities to applications on-the-fly, regardless of whether they were started with support. JConsole uses this API to start a local

Re: Timer woken up late?

On 08/12/2009 10:19 AM, Andrew Stitcher wrote: On Wed, 2009-08-12 at 08:56 -0400, Alan Conway wrote: On 08/12/2009 07:25 AM, Gordon Sim wrote: The output from make check-long is now showing lots of warnings of the following form: soak-1: 2009-08-12 06:40:56 warning Timer woken up 3ms late Is

[Java] Log4J configuration process and broker startup behaviour

The Log4J configuration sequence and its usage within the broker is in a bit of a pickle(described below). I am wondering what people think about how it should actually behave at startup? Looking at the Main class from the broker suggests what it thinks is going on is: At startup, it checks if et

Re: test failures

Sorry Rafi, My fault. Will exclude them 2009/8/13 Rafael Schloming : > A number of the java tests are now failing under the cpp profile with the > following exception. It looks to be as of robbie's change at r802819. > > --Rafael > > > Testcase: testBindingCreateOnFanoutViaManagementConsole took

[jira] Commented: (QPID-2048) Client can hang on close() if broker is simultaenously killed

[ https://issues.apache.org/jira/browse/QPID-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742753#action_12742753 ] Gordon Sim commented on QPID-2048: -- I've checked in a fix that checks the state is still OP

[jira] Assigned: (QPID-2048) Client can hang on close() if broker is simultaenously killed

[ https://issues.apache.org/jira/browse/QPID-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned QPID-2048: Assignee: Alan Conway (was: Gordon Sim) > Client can hang on close() if broker is simultaenously ki

[jira] Updated: (QPID-2048) Client can hang on close() if broker is simultaenously killed

[ https://issues.apache.org/jira/browse/QPID-2048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-2048: - Status: Ready To Review (was: In Progress) > Client can hang on close() if broker is simultaenously kille

[jira] Created: (QPID-2048) Client can hang on close() if broker is simultaenously killed

Client can hang on close() if broker is simultaenously killed - Key: QPID-2048 URL: https://issues.apache.org/jira/browse/QPID-2048 Project: Qpid Issue Type: Bug Component