[jira] [Created] (QPID-3430) Cannot exclude protocol from SSL ports on command line
Cannot exclude protocol from SSL ports on command line -- Key: QPID-3430 URL: https://issues.apache.org/jira/browse/QPID-3430 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Andrew MacBean Assignee: Robbie Gemmell Fix For: 0.13 Cannot exclude protocol from specific SSL ports on command line. Change required to allow exclusion of specified ports based on protocol. Port excludes specified as per NonSSL using: 'connector.non010port','connector.non091port','connector.non09port' and 'connector.non08port' SSL port(s) specific using '-s' option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3430) Cannot exclude protocol from SSL ports on command line
[ https://issues.apache.org/jira/browse/QPID-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3430: - Attachment: QPID-3430_SSLportexclude.patch Created utility method and used to process excludes for both SSL and non SSL ports. > Cannot exclude protocol from SSL ports on command line > -- > > Key: QPID-3430 > URL: https://issues.apache.org/jira/browse/QPID-3430 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Robbie Gemmell > Fix For: 0.13 > > Attachments: QPID-3430_SSLportexclude.patch > > > Cannot exclude protocol from specific SSL ports on command line. Change > required to allow exclusion of specified ports based on protocol. > Port excludes specified as per NonSSL using: > 'connector.non010port','connector.non091port','connector.non09port' and > 'connector.non08port' > SSL port(s) specific using '-s' option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3430) Cannot exclude protocol from SSL ports on command line
[ https://issues.apache.org/jira/browse/QPID-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-3430: Assignee: Andrew MacBean (was: Robbie Gemmell) > Cannot exclude protocol from SSL ports on command line > -- > > Key: QPID-3430 > URL: https://issues.apache.org/jira/browse/QPID-3430 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > Fix For: 0.13 > > Attachments: QPID-3430_SSLportexclude.patch > > > Cannot exclude protocol from specific SSL ports on command line. Change > required to allow exclusion of specified ports based on protocol. > Port excludes specified as per NonSSL using: > 'connector.non010port','connector.non091port','connector.non09port' and > 'connector.non08port' > SSL port(s) specific using '-s' option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3430) Cannot exclude protocol from SSL ports on command line
[ https://issues.apache.org/jira/browse/QPID-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-3430: Assignee: Robbie Gemmell (was: Andrew MacBean) Please review > Cannot exclude protocol from SSL ports on command line > -- > > Key: QPID-3430 > URL: https://issues.apache.org/jira/browse/QPID-3430 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Robbie Gemmell > Fix For: 0.13 > > Attachments: QPID-3430_SSLportexclude.patch > > > Cannot exclude protocol from specific SSL ports on command line. Change > required to allow exclusion of specified ports based on protocol. > Port excludes specified as per NonSSL using: > 'connector.non010port','connector.non091port','connector.non09port' and > 'connector.non08port' > SSL port(s) specific using '-s' option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3430) Cannot exclude protocol from SSL ports on command line
[ https://issues.apache.org/jira/browse/QPID-3430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3430: - Status: Ready To Review (was: In Progress) > Cannot exclude protocol from SSL ports on command line > -- > > Key: QPID-3430 > URL: https://issues.apache.org/jira/browse/QPID-3430 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > Fix For: 0.13 > > Attachments: QPID-3430_SSLportexclude.patch > > > Cannot exclude protocol from specific SSL ports on command line. Change > required to allow exclusion of specified ports based on protocol. > Port excludes specified as per NonSSL using: > 'connector.non010port','connector.non091port','connector.non09port' and > 'connector.non08port' > SSL port(s) specific using '-s' option. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-3428) Verifification of unique client ID does not work in Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095213#comment-13095213 ] Andrew MacBean commented on QPID-3428: -- Based on test case and implementation in Java client and C++ broker for (QPID-3269) the broker has been changed to validate that the client id used is unique when creating a new session and attaching. If the client id is null or is unique then the session is attached as before, otherwise it invokes session detached and sets the session detach code to SESSION_BUSY and calls session.closed(). A patch has been attached for review. The patch also includes some minor client changes to fix a small bug found during development in the Session.awaitOpen() method which was throwing a SessionException even if the state was OPEN as expected. This was "swallowed" later so had no real knock on effect anyway. > Verifification of unique client ID does not work in Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Robbie Gemmell >Priority: Minor > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3428) Verifification of unique client ID does not work in Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3428: - Attachment: [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch > Verifification of unique client ID does not work in Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Robbie Gemmell >Priority: Minor > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Resolved] (QPID-3428) Verifification of unique client ID does not work in Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-3428. -- Resolution: Fixed Robbie, could you please review the attached patch and apply if suitable. Thanks Andrew > Verifification of unique client ID does not work in Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Robbie Gemmell >Priority: Minor > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3428) Verifification of unique client ID does not work in Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-3428: Assignee: Andrew MacBean (was: Robbie Gemmell) > Verifification of unique client ID does not work in Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Andrew MacBean >Priority: Minor > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Reopened] (QPID-3428) Verifification of unique client ID does not work in Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reopened QPID-3428: -- > Verifification of unique client ID does not work in Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Robbie Gemmell >Priority: Minor > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3428) Verifification of unique client ID does not work in Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-3428: Assignee: Robbie Gemmell (was: Andrew MacBean) > Verifification of unique client ID does not work in Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Robbie Gemmell >Priority: Minor > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3428) Verifification of unique client ID does not work in Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3428: - Status: Ready To Review (was: In Progress) > Verifification of unique client ID does not work in Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Andrew MacBean >Priority: Minor > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Created] (QPID-3477) Java Broker does not handle a rejection/acknowledgemnt with invalid code correctly
Java Broker does not handle a rejection/acknowledgemnt with invalid code correctly -- Key: QPID-3477 URL: https://issues.apache.org/jira/browse/QPID-3477 Project: Qpid Issue Type: Bug Components: Java Broker Affects Versions: 0.12 Reporter: Andrew MacBean Priority: Minor When running the Python client 0-10 tests against the Java broker it was noticed that the following test would cause test run to hang/time out: qpid.tests.messaging.endpoints.SessionTests.testReject It appears that this is because the Java broker does not handle the following call correctly: self.ssn.acknowledge(echos[2], Disposition(REJECTED, code=3, text="test-reject")) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3477) Java Broker does not handle a rejection/acknowledgemnt with invalid code correctly
[ https://issues.apache.org/jira/browse/QPID-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3477: - Attachment: QPID-3477-java-broker-not-handling-reject-code-correctly.txt > Java Broker does not handle a rejection/acknowledgemnt with invalid code > correctly > -- > > Key: QPID-3477 > URL: https://issues.apache.org/jira/browse/QPID-3477 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.12 >Reporter: Andrew MacBean >Priority: Minor > Attachments: > QPID-3477-java-broker-not-handling-reject-code-correctly.txt > > > When running the Python client 0-10 tests against the Java broker it was > noticed that the following test would cause test run to hang/time out: > qpid.tests.messaging.endpoints.SessionTests.testReject > It appears that this is because the Java broker does not handle the following > call correctly: > self.ssn.acknowledge(echos[2], Disposition(REJECTED, code=3, > text="test-reject")) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-3477) Java Broker does not handle a rejection/acknowledgemnt with invalid code correctly
[ https://issues.apache.org/jira/browse/QPID-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100210#comment-13100210 ] Andrew MacBean commented on QPID-3477: -- Patch attached to add Java010Excludes file to prevent test running and allow for CI runs of Python tests. > Java Broker does not handle a rejection/acknowledgemnt with invalid code > correctly > -- > > Key: QPID-3477 > URL: https://issues.apache.org/jira/browse/QPID-3477 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.12 >Reporter: Andrew MacBean >Priority: Minor > Attachments: > QPID-3477-java-broker-not-handling-reject-code-correctly.txt > > > When running the Python client 0-10 tests against the Java broker it was > noticed that the following test would cause test run to hang/time out: > qpid.tests.messaging.endpoints.SessionTests.testReject > It appears that this is because the Java broker does not handle the following > call correctly: > self.ssn.acknowledge(echos[2], Disposition(REJECTED, code=3, > text="test-reject")) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3477) Java Broker does not handle a rejection/acknowledgemnt with invalid code correctly
[ https://issues.apache.org/jira/browse/QPID-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-3477: Assignee: Robbie Gemmell Can you please reveiew. > Java Broker does not handle a rejection/acknowledgemnt with invalid code > correctly > -- > > Key: QPID-3477 > URL: https://issues.apache.org/jira/browse/QPID-3477 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.12 >Reporter: Andrew MacBean >Assignee: Robbie Gemmell >Priority: Minor > Attachments: > QPID-3477-java-broker-not-handling-reject-code-correctly.txt > > > When running the Python client 0-10 tests against the Java broker it was > noticed that the following test would cause test run to hang/time out: > qpid.tests.messaging.endpoints.SessionTests.testReject > It appears that this is because the Java broker does not handle the following > call correctly: > self.ssn.acknowledge(echos[2], Disposition(REJECTED, code=3, > text="test-reject")) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3428) Verification of unique client ID does not work with Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-3428: Assignee: Robbie Gemmell (was: Andrew MacBean) > Verification of unique client ID does not work with Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 0.13 > > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch, > > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker2.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3428) Verification of unique client ID does not work with Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3428: - Attachment: [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker2.patch Review comments actioned, please review. > Verification of unique client ID does not work with Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Andrew MacBean >Priority: Minor > Fix For: 0.13 > > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch, > > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker2.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3428) Verification of unique client ID does not work with Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-3428: Assignee: Robbie Gemmell (was: Andrew MacBean) > Verification of unique client ID does not work with Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Robbie Gemmell >Priority: Minor > Fix For: 0.13 > > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch, > > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker2.patch, > > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker3.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3428) Verification of unique client ID does not work with Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3428: - Status: Ready To Review (was: In Progress) > Verification of unique client ID does not work with Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Andrew MacBean >Priority: Minor > Fix For: 0.13 > > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch, > > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker2.patch, > > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker3.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3428) Verification of unique client ID does not work with Java Broker
[ https://issues.apache.org/jira/browse/QPID-3428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3428: - Attachment: [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker3.patch Checked this vs the C++ broker and you were right, modified the patch and added a new test to highlight the difference. > Verification of unique client ID does not work with Java Broker > --- > > Key: QPID-3428 > URL: https://issues.apache.org/jira/browse/QPID-3428 > Project: Qpid > Issue Type: Bug > Components: Java Broker, Java Client >Affects Versions: 0.10 >Reporter: Alex Rudyy >Assignee: Andrew MacBean >Priority: Minor > Fix For: 0.13 > > Attachments: > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker.patch, > > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker2.patch, > > [QPID-3428]-verifification-of-unique-client-ID-does-not-work-in-Java-Broker3.patch > > > On settings client JVM property "qpid.verify_client_id" to "true" Qpid broker > should not allow creation of connections with the same client id. However, > this functionality does not work at the moment. > JUnit test > org.apache.qpid.test.unit.client.connection.ConnectionTest#testClientIDVerification > fails with the following message: > "The client should throw a ConnectionException stating the client ID is not > unique" > junit.framework.AssertionFailedError: The client should throw a > ConnectionException stating the client ID is not unique > at > org.apache.qpid.test.unit.client.connection.ConnectionTest.testClientIDVerification(ConnectionTest.java:307) > at > org.apache.qpid.test.utils.QpidBrokerTestCase.runBare(QpidBrokerTestCase.java:243) > at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:125) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3486) Make connector server port used for JMX configurable
[ https://issues.apache.org/jira/browse/QPID-3486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3486: - Attachment: 0001-QPID-3486-Make-connector-server-port-used-for-JMX-co.patch Here is a patch that resolves this. > Make connector server port used for JMX configurable > > > Key: QPID-3486 > URL: https://issues.apache.org/jira/browse/QPID-3486 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.13 > > Attachments: > 0001-QPID-3486-Make-connector-server-port-used-for-JMX-co.patch > > > Make the connector server port used for JMX configurable. Currently the > second port (used for the JMXConnectorServer itself) is chosen using a fixed > offset of 100 from the first port (the 'management' port, used for the > RMIRegistry). This can continue to be the default behavior, but the ability > to specify the second port explicitly should be added. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Resolved] (QPID-3903) Session#close() should not wait forever if broker fails to respond to channel close (0-8..0-9-1 protocols)
[
https://issues.apache.org/jira/browse/QPID-3903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew MacBean resolved QPID-3903.
--
Resolution: Fixed
> Session#close() should not wait forever if broker fails to respond to channel
> close (0-8..0-9-1 protocols)
> --
>
> Key: QPID-3903
> URL: https://issues.apache.org/jira/browse/QPID-3903
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
>Affects Versions: 0.6, 0.8, 0.10, 0.12, 0.14, 0.16
>Reporter: Keith Wall
>Assignee: Andrew MacBean
> Fix For: 0.17
>
>
> For the 0-8..0-9-1 protocols, if the broker fails to respond to a channel
> close command (for whatever reason), the client thread hangs forever. This
> is because AMQSession#close() uses a timeout value of -1, which is
> interpreted by BlockingWaiter as a indefinite wait.
> Users of the 0-10 protocol are unaffected by this defect.
> {code}
> - parking to wait for <1f004f3> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925)
> at
> org.apache.qpid.client.util.BlockingWaiter.block(BlockingWaiter.java:168)
> at
> org.apache.qpid.client.protocol.BlockingMethodFrameListener.blockForFrame(BlockingMethodFrameListener.java:127)
> at
> org.apache.qpid.client.protocol.AMQProtocolHandler.writeCommandFrameAndWaitForReply(AMQProtocolHandler.java:686)
> at
> org.apache.qpid.client.protocol.AMQProtocolHandler.syncWrite(AMQProtocolHandler.java:707)
> at
> org.apache.qpid.client.AMQSession_0_8.sendClose(AMQSession_0_8.java:162)
> at org.apache.qpid.client.AMQSession.close(AMQSession.java:723)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-3184) Amend ant build to produce cobertura coverage.xml
Amend ant build to produce cobertura coverage.xml - Key: QPID-3184 URL: https://issues.apache.org/jira/browse/QPID-3184 Project: Qpid Issue Type: Task Components: Ant Build System Reporter: Andrew MacBean Priority: Minor Fix For: 0.11 Amend ant build to produce cobertura coverage.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3184) Amend ant build to produce cobertura coverage.xml
[ https://issues.apache.org/jira/browse/QPID-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3184: - Attachment: 0001-QPID-3184-Amend-ant-build-to-produce-cobertura-cover-trunk.patch > Amend ant build to produce cobertura coverage.xml > - > > Key: QPID-3184 > URL: https://issues.apache.org/jira/browse/QPID-3184 > Project: Qpid > Issue Type: Task > Components: Ant Build System >Reporter: Andrew MacBean >Priority: Minor > Fix For: 0.11 > > Attachments: > 0001-QPID-3184-Amend-ant-build-to-produce-cobertura-cover-trunk.patch, > 0001-QPID-3184-amend-ant-build-to-produce-coverage.xml.patch > > > Amend ant build to produce cobertura coverage.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3184) Amend ant build to produce cobertura coverage.xml
[ https://issues.apache.org/jira/browse/QPID-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-3184: - Attachment: 0001-QPID-3184-amend-ant-build-to-produce-coverage.xml.patch > Amend ant build to produce cobertura coverage.xml > - > > Key: QPID-3184 > URL: https://issues.apache.org/jira/browse/QPID-3184 > Project: Qpid > Issue Type: Task > Components: Ant Build System >Reporter: Andrew MacBean >Priority: Minor > Fix For: 0.11 > > Attachments: > 0001-QPID-3184-Amend-ant-build-to-produce-cobertura-cover-trunk.patch, > 0001-QPID-3184-amend-ant-build-to-produce-coverage.xml.patch > > > Amend ant build to produce cobertura coverage.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-5822) Replace low-level JDBC/BDB attributes with context variables
[ https://issues.apache.org/jira/browse/QPID-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058887#comment-14058887 ] Andrew MacBean commented on QPID-5822: -- Found a weakness in the logic for determining which JE parameters are used when building the configuiration Map. Calls to EnvironmentParams.SUPPORTED_PARAMS do not always return the full list and so this needs modified to work around this by using the prefixes of the paramater names. > Replace low-level JDBC/BDB attributes with context variables > > > Key: QPID-5822 > URL: https://issues.apache.org/jira/browse/QPID-5822 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > Attachments: > 0001-QPID-5822-Java-Broker-Eliminate-low-level-BDB-JDBC-a.patch > > > We have identified some VH attributes that are deemed too low level to > warrant attribute status and are to be demoted to context variable. > * JDBC types > * JE envConfig > * JE repConfig > For the JE configs, Rob suggested we iterate the supported JE config names > (EnvironmentParams#SUPPORTED_PARAMS) check the context for each one and set > as necessary. > This task should include any upgrader work. > Include writing a system test that uses Derby as an external database. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5891) Add BDB HA operational logging
Andrew MacBean created QPID-5891: Summary: Add BDB HA operational logging Key: QPID-5891 URL: https://issues.apache.org/jira/browse/QPID-5891 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Andrew MacBean Assignee: Andrew MacBean -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5891) Add BDB HA operational logging
[ https://issues.apache.org/jira/browse/QPID-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-5891: - Description: BDB HA Replicated environments currently have no specific operational logging, an initial set of relevant messages should be defined and logged at the relevant points in the code, as per the other operation logs. > Add BDB HA operational logging > -- > > Key: QPID-5891 > URL: https://issues.apache.org/jira/browse/QPID-5891 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > > BDB HA Replicated environments currently have no specific operational > logging, an initial set of relevant messages should be defined and logged at > the relevant points in the code, as per the other operation logs. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPID-5822) Replace low-level JDBC/BDB attributes with context variables
[ https://issues.apache.org/jira/browse/QPID-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reopened QPID-5822: -- > Replace low-level JDBC/BDB attributes with context variables > > > Key: QPID-5822 > URL: https://issues.apache.org/jira/browse/QPID-5822 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > Attachments: > 0001-QPID-5822-Java-Broker-Eliminate-low-level-BDB-JDBC-a.patch > > > We have identified some VH attributes that are deemed too low level to > warrant attribute status and are to be demoted to context variable. > * JDBC types > * JE envConfig > * JE repConfig > For the JE configs, Rob suggested we iterate the supported JE config names > (EnvironmentParams#SUPPORTED_PARAMS) check the context for each one and set > as necessary. > This task should include any upgrader work. > Include writing a system test that uses Derby as an external database. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5891) Add BDB HA operational logging
[ https://issues.apache.org/jira/browse/QPID-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5891. -- Resolution: Fixed Assignee: Alex Rudyy (was: Andrew MacBean) > Add BDB HA operational logging > -- > > Key: QPID-5891 > URL: https://issues.apache.org/jira/browse/QPID-5891 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > BDB HA Replicated environments currently have no specific operational > logging, an initial set of relevant messages should be defined and logged at > the relevant points in the code, as per the other operation logs. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5822) Replace low-level JDBC/BDB attributes with context variables
[ https://issues.apache.org/jira/browse/QPID-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-5822: - Status: Reviewable (was: In Progress) > Replace low-level JDBC/BDB attributes with context variables > > > Key: QPID-5822 > URL: https://issues.apache.org/jira/browse/QPID-5822 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > Attachments: > 0001-QPID-5822-Java-Broker-Eliminate-low-level-BDB-JDBC-a.patch > > > We have identified some VH attributes that are deemed too low level to > warrant attribute status and are to be demoted to context variable. > * JDBC types > * JE envConfig > * JE repConfig > For the JE configs, Rob suggested we iterate the supported JE config names > (EnvironmentParams#SUPPORTED_PARAMS) check the context for each one and set > as necessary. > This task should include any upgrader work. > Include writing a system test that uses Derby as an external database. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5891) Add BDB HA operational logging
[ https://issues.apache.org/jira/browse/QPID-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-5891: - Status: Reviewable (was: In Progress) > Add BDB HA operational logging > -- > > Key: QPID-5891 > URL: https://issues.apache.org/jira/browse/QPID-5891 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > > BDB HA Replicated environments currently have no specific operational > logging, an initial set of relevant messages should be defined and logged at > the relevant points in the code, as per the other operation logs. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5891) Add BDB HA operational logging
[ https://issues.apache.org/jira/browse/QPID-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-5891: Assignee: Alex Rudyy (was: Andrew MacBean) > Add BDB HA operational logging > -- > > Key: QPID-5891 > URL: https://issues.apache.org/jira/browse/QPID-5891 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > BDB HA Replicated environments currently have no specific operational > logging, an initial set of relevant messages should be defined and logged at > the relevant points in the code, as per the other operation logs. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (QPID-5891) Add BDB HA operational logging
[ https://issues.apache.org/jira/browse/QPID-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reopened QPID-5891: -- > Add BDB HA operational logging > -- > > Key: QPID-5891 > URL: https://issues.apache.org/jira/browse/QPID-5891 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > BDB HA Replicated environments currently have no specific operational > logging, an initial set of relevant messages should be defined and logged at > the relevant points in the code, as per the other operation logs. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5822) Replace low-level JDBC/BDB attributes with context variables
[ https://issues.apache.org/jira/browse/QPID-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-5822: Assignee: Keith Wall (was: Andrew MacBean) Keith, could you please review the additional commit I made for the JE supported params work around please? Andrew > Replace low-level JDBC/BDB attributes with context variables > > > Key: QPID-5822 > URL: https://issues.apache.org/jira/browse/QPID-5822 > Project: Qpid > Issue Type: Task > Components: Java Broker >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.29 > > Attachments: > 0001-QPID-5822-Java-Broker-Eliminate-low-level-BDB-JDBC-a.patch > > > We have identified some VH attributes that are deemed too low level to > warrant attribute status and are to be demoted to context variable. > * JDBC types > * JE envConfig > * JE repConfig > For the JE configs, Rob suggested we iterate the supported JE config names > (EnvironmentParams#SUPPORTED_PARAMS) check the context for each one and set > as necessary. > This task should include any upgrader work. > Include writing a system test that uses Derby as an external database. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5891) Add BDB HA operational logging
[ https://issues.apache.org/jira/browse/QPID-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-5891: Assignee: Andrew MacBean (was: Alex Rudyy) > Add BDB HA operational logging > -- > > Key: QPID-5891 > URL: https://issues.apache.org/jira/browse/QPID-5891 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > > BDB HA Replicated environments currently have no specific operational > logging, an initial set of relevant messages should be defined and logged at > the relevant points in the code, as per the other operation logs. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5851) [Java Broker] Add new test profiles for JSON config store and Persistent Message Store
[ https://issues.apache.org/jira/browse/QPID-5851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5851. -- Resolution: Fixed > [Java Broker] Add new test profiles for JSON config store and Persistent > Message Store > -- > > Key: QPID-5851 > URL: https://issues.apache.org/jira/browse/QPID-5851 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Alex Rudyy >Assignee: Andrew MacBean > Fix For: 0.29 > > > We have had a few defects come to light through manual testing owing to our > decision to switch to a split store. We need a json + persistent store > profile in order to make sure we catch defects that come out through more > complex usage scenarios. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5885) Virtualhostnode to replace real virtualhost with replica virtualhost in the event that the BDB HA goes into detached state
[ https://issues.apache.org/jira/browse/QPID-5885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5885. -- Resolution: Fixed > Virtualhostnode to replace real virtualhost with replica virtualhost in the > event that the BDB HA goes into detached state > -- > > Key: QPID-5885 > URL: https://issues.apache.org/jira/browse/QPID-5885 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > > Currently, if the BDB HA node goes into a detached state (as it does when it > restarts itself when it detects that quorum has gone), the virtualhost > remains available. > If a client attempts a virtualhost operation whilst the node is in this > state, the operation appears hangs with timeouts appearing on the client. > This hang is owing to the ReplicaConsistencyPolicy - which defaults to 1h. > The virtualhostnode should replace the real virtualhost with the 'replica' > virtualhost when the node is in detached state. This will cause existing > client connections to be disconnected and new connections will be disallowed. > -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5909) [Java Broker] Activation of BDB HA virtual host fails when changing node role from Master to Replica and back to Master because message store durability is already set
[
https://issues.apache.org/jira/browse/QPID-5909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew MacBean resolved QPID-5909.
--
Resolution: Fixed
> [Java Broker] Activation of BDB HA virtual host fails when changing node
> role from Master to Replica and back to Master because message store
> durability is already set
>
>
> Key: QPID-5909
> URL: https://issues.apache.org/jira/browse/QPID-5909
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.29
>Reporter: Alex Rudyy
>Assignee: Andrew MacBean
> Fix For: 0.29
>
>
> On flipping node role from MASTER to REPLICA and back (for example, using UI
> transfer master functionality) IllegalStateException is thrown:
> {noformat}
> java.lang.IllegalStateException: Message store durability is already set to
> SYNC,NO_SYNC,SIMPLE_MAJORITY
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.setMessageStoreDurability(ReplicatedEnvironmentFacade.java:1122)
> at
> org.apache.qpid.server.virtualhost.berkeleydb.BDBHAVirtualHostImpl.onOpen(BDBHAVirtualHostImpl.java:110)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doOpening(AbstractConfiguredObject.java:503)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.open(AbstractConfiguredObject.java:395)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl$1.run(BDBHAVirtualHostNodeImpl.java:470)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.onMaster(BDBHAVirtualHostNodeImpl.java:465)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl.access$300(BDBHAVirtualHostNodeImpl.java:74)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl$EnvironmentStateChangeListener.stateChange(BDBHAVirtualHostNodeImpl.java:539)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.stateChanged(ReplicatedEnvironmentFacade.java:510)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade.access$300(ReplicatedEnvironmentFacade.java:95)
> at
> org.apache.qpid.server.store.berkeleydb.replication.ReplicatedEnvironmentFacade$3.run(ReplicatedEnvironmentFacade.java:474)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5811) FailoverBehaviourTest.testTransactionRolledBackExceptionThrownOnCommitAfterFailoverOnMessageReceiving failed with unexpected message order
[ https://issues.apache.org/jira/browse/QPID-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-5811: - Status: Reviewable (was: In Progress) > FailoverBehaviourTest.testTransactionRolledBackExceptionThrownOnCommitAfterFailoverOnMessageReceiving > failed with unexpected message order > -- > > Key: QPID-5811 > URL: https://issues.apache.org/jira/browse/QPID-5811 > Project: Qpid > Issue Type: Bug > Components: Java Tests >Affects Versions: 0.28 >Reporter: Andrew MacBean >Assignee: Andrew MacBean >Priority: Minor > > FailoverBehaviourTest.testTransactionRolledBackExceptionThrownOnCommitAfterFailoverOnMessageReceiving > failed with unexpected message order, the test appears to consume messages > in wrong order after a successful failover. > --- > Test set: org.apache.qpid.client.failover.FailoverBehaviourTest > --- > Tests run: 33, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 156.508 sec > <<< FAILURE! - in org.apache.qpid.client.failover.FailoverBehaviourTest > testTransactionRolledBackExceptionThrownOnCommitAfterFailoverOnMessageReceiving(org.apache.qpid.client.failover.FailoverBehaviourTest) > Time elapsed: 3.206 sec <<< FAILURE! > junit.framework.ComparisonFailure: Failover is broken! Expected [test message > 37] but got [test message 38] expected: but was: message 3[8]> > at junit.framework.Assert.assertEquals(Assert.java:100) > at junit.framework.TestCase.assertEquals(TestCase.java:261) > at > org.apache.qpid.client.failover.FailoverBehaviourTest.assertReceivedMessage(FailoverBehaviourTest.java:1150) > at > org.apache.qpid.client.failover.FailoverBehaviourTest.consumeMessages(FailoverBehaviourTest.java:1120) > at > org.apache.qpid.client.failover.FailoverBehaviourTest.consumeMessages(FailoverBehaviourTest.java:1062) > at > org.apache.qpid.client.failover.FailoverBehaviourTest.testTransactionRolledBackExceptionThrownOnCommitAfterFailoverOnMessageReceiving(FailoverBehaviourTest.java:256) -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5811) FailoverBehaviourTest.testTransactionRolledBackExceptionThrownOnCommitAfterFailoverOnMessageReceiving failed with unexpected message order
[ https://issues.apache.org/jira/browse/QPID-5811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5811. -- Resolution: Fixed > FailoverBehaviourTest.testTransactionRolledBackExceptionThrownOnCommitAfterFailoverOnMessageReceiving > failed with unexpected message order > -- > > Key: QPID-5811 > URL: https://issues.apache.org/jira/browse/QPID-5811 > Project: Qpid > Issue Type: Bug > Components: Java Tests >Affects Versions: 0.28 >Reporter: Andrew MacBean >Assignee: Andrew MacBean >Priority: Minor > > FailoverBehaviourTest.testTransactionRolledBackExceptionThrownOnCommitAfterFailoverOnMessageReceiving > failed with unexpected message order, the test appears to consume messages > in wrong order after a successful failover. > --- > Test set: org.apache.qpid.client.failover.FailoverBehaviourTest > --- > Tests run: 33, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 156.508 sec > <<< FAILURE! - in org.apache.qpid.client.failover.FailoverBehaviourTest > testTransactionRolledBackExceptionThrownOnCommitAfterFailoverOnMessageReceiving(org.apache.qpid.client.failover.FailoverBehaviourTest) > Time elapsed: 3.206 sec <<< FAILURE! > junit.framework.ComparisonFailure: Failover is broken! Expected [test message > 37] but got [test message 38] expected: but was: message 3[8]> > at junit.framework.Assert.assertEquals(Assert.java:100) > at junit.framework.TestCase.assertEquals(TestCase.java:261) > at > org.apache.qpid.client.failover.FailoverBehaviourTest.assertReceivedMessage(FailoverBehaviourTest.java:1150) > at > org.apache.qpid.client.failover.FailoverBehaviourTest.consumeMessages(FailoverBehaviourTest.java:1120) > at > org.apache.qpid.client.failover.FailoverBehaviourTest.consumeMessages(FailoverBehaviourTest.java:1062) > at > org.apache.qpid.client.failover.FailoverBehaviourTest.testTransactionRolledBackExceptionThrownOnCommitAfterFailoverOnMessageReceiving(FailoverBehaviourTest.java:256) -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5721) [Java Broker] Allow configured object attributes of collection types (e.g. maps, lists, sets) to be set using JSON strings
[ https://issues.apache.org/jira/browse/QPID-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5721. -- Resolution: Fixed > [Java Broker] Allow configured object attributes of collection types (e.g. > maps, lists, sets) to be set using JSON strings > -- > > Key: QPID-5721 > URL: https://issues.apache.org/jira/browse/QPID-5721 > Project: Qpid > Issue Type: Sub-task > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.29 > > > Allow for defaulting and setting of configured object attributes of > collection types using JSON string representation -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5928) UI: Implement or update virtualhostnode & virtualhost view and edit dialogs
Andrew MacBean created QPID-5928: Summary: UI: Implement or update virtualhostnode & virtualhost view and edit dialogs Key: QPID-5928 URL: https://issues.apache.org/jira/browse/QPID-5928 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Andrew MacBean Assignee: Andrew MacBean Implement or modify the VHN/VH view and edit dialogs to be up to date with tyoe specific and common/derived attributes.. implementation should be sensibly shared to avoid duplication of UI code. if virtualhost is not active, then panels for queues, exchanges, connections etc should be hidden -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5911) Increase default maximum heap size from 1g to 2g
[ https://issues.apache.org/jira/browse/QPID-5911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5911. -- Resolution: Fixed > Increase default maximum heap size from 1g to 2g > > > Key: QPID-5911 > URL: https://issues.apache.org/jira/browse/QPID-5911 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > > The Java Broker has shipped with a default maximum heap size (-Xmx) of 1GB > for many years. It has been decided the with the availability of memory in > modern machines, now is the time to increase the default maximum heap size > from 1g to 2g. > The user is still free to use the QPID_JAVA_MEM to override the this value if > the new default does not suit. > http://qpid.apache.org/releases/qpid-trunk/java-broker/book/Java-Broker-Appendix-Environment-Variables.html -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5935) Web Management UI style refactor to remove html inline styles and standardise via css
Andrew MacBean created QPID-5935: Summary: Web Management UI style refactor to remove html inline styles and standardise via css Key: QPID-5935 URL: https://issues.apache.org/jira/browse/QPID-5935 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Andrew MacBean Assignee: Andrew MacBean Priority: Minor The web UI HTML markup contains many uses of inline css style which in many cases is actually redundant. Much of it can be refactored into the CSS for .formLabel-labelCell and .tableContainer-labelCell and the others simply removed. In order to do this a standard label width has been set as 300px. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5935) Web Management UI style refactor to remove html inline styles and standardise via css
[ https://issues.apache.org/jira/browse/QPID-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-5935: - Description: The web UI HTML markup contains many uses of inline css style which in many cases is actually redundant. Much of it can be refactored into the CSS for .formLabel-labelCell and .tableContainer-labelCell and the others simply removed. In order to do this a standard label width has been set as 300px but purely based on the majority currently set inline. This change will not change the JS generated html markup or the tables based to use CSS, this is something to consider to make everything consistent. was: The web UI HTML markup contains many uses of inline css style which in many cases is actually redundant. Much of it can be refactored into the CSS for .formLabel-labelCell and .tableContainer-labelCell and the others simply removed. In order to do this a standard label width has been set as 300px. > Web Management UI style refactor to remove html inline styles and standardise > via css > - > > Key: QPID-5935 > URL: https://issues.apache.org/jira/browse/QPID-5935 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean >Priority: Minor > > The web UI HTML markup contains many uses of inline css style which in many > cases is actually redundant. > Much of it can be refactored into the CSS for .formLabel-labelCell and > .tableContainer-labelCell and the others simply removed. > In order to do this a standard label width has been set as 300px but purely > based on the majority currently set inline. > This change will not change the JS generated html markup or the tables based > to use CSS, this is something to consider to make everything consistent. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5935) Web Management UI style refactor to remove html inline styles and standardise via css
[ https://issues.apache.org/jira/browse/QPID-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-5935: - Status: Reviewable (was: In Progress) > Web Management UI style refactor to remove html inline styles and standardise > via css > - > > Key: QPID-5935 > URL: https://issues.apache.org/jira/browse/QPID-5935 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean >Priority: Minor > > The web UI HTML markup contains many uses of inline css style which in many > cases is actually redundant. > Much of it can be refactored into the CSS for .formLabel-labelCell and > .tableContainer-labelCell and the others simply removed. > In order to do this a standard label width has been set as 300px but purely > based on the majority currently set inline. > This change will not change the JS generated html markup or the tables based > to use CSS, this is something to consider to make everything consistent. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5935) Web Management UI style refactor to remove html inline styles and standardise via css
[ https://issues.apache.org/jira/browse/QPID-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-5935: Assignee: Keith Wall (was: Andrew MacBean) Could you please review this commit for me. It's an attempt at trying to standardise some of the UI elements and make better use of the common.css rather than inline style in HTML. > Web Management UI style refactor to remove html inline styles and standardise > via css > - > > Key: QPID-5935 > URL: https://issues.apache.org/jira/browse/QPID-5935 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Keith Wall >Priority: Minor > > The web UI HTML markup contains many uses of inline css style which in many > cases is actually redundant. > Much of it can be refactored into the CSS for .formLabel-labelCell and > .tableContainer-labelCell and the others simply removed. > In order to do this a standard label width has been set as 300px but purely > based on the majority currently set inline. > This change will not change the JS generated html markup or the tables based > to use CSS, this is something to consider to make everything consistent. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5936) Tests from suite VirtualHostMessageStoreTest are failing on json test profiles when BDB VH is used
[ https://issues.apache.org/jira/browse/QPID-5936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5936. -- Resolution: Fixed > Tests from suite VirtualHostMessageStoreTest are failing on json test > profiles when BDB VH is used > -- > > Key: QPID-5936 > URL: https://issues.apache.org/jira/browse/QPID-5936 > Project: Qpid > Issue Type: Bug > Components: Java Tests >Reporter: Alex Rudyy >Assignee: Alex Rudyy > Fix For: 0.29 > > > In the test suite VirtualHostMessageStoreTest VH configuration store is > created in the same location as a message store. BDB message store requires a > sub-folder. JSON configuration store is stored in a file now. As result, > sub-folder for BDB message store cannot be created in JSON configuration > store location -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5943) [Java Broker] Test BDBHAVirtualHostNodeOperationalLoggingTest.testSetPriority fails sporadically
[ https://issues.apache.org/jira/browse/QPID-5943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5943. -- Resolution: Fixed > [Java Broker] Test BDBHAVirtualHostNodeOperationalLoggingTest.testSetPriority > fails sporadically > > > Key: QPID-5943 > URL: https://issues.apache.org/jira/browse/QPID-5943 > Project: Qpid > Issue Type: Bug > Components: Java Tests >Reporter: Alex Rudyy >Assignee: Andrew MacBean > Fix For: 0.29 > > > Failed > org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeOperationalLoggingTest.testSetPriority > Failing for the past 3 builds (Since #194 ) > Took 1.1 sec. > Error Message > Wanted but not invoked: > eventLogger.message(, ); > -> at > org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeOperationalLoggingTest.testSetPriority(BDBHAVirtualHostNodeOperationalLoggingTest.java:184) > Actually, there were zero interactions with this mock. > Stacktrace > org.mockito.exceptions.verification.WantedButNotInvoked: > Wanted but not invoked: > eventLogger.message(, ); > -> at > org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeOperationalLoggingTest.testSetPriority(BDBHAVirtualHostNodeOperationalLoggingTest.java:184) > Actually, there were zero interactions with this mock. > at > org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeOperationalLoggingTest.testSetPriority(BDBHAVirtualHostNodeOperationalLoggingTest.java:184) -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5944) Expose queue clear management operation to the REST API and Web Management Console
[ https://issues.apache.org/jira/browse/QPID-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-5944: Assignee: Andrew MacBean > Expose queue clear management operation to the REST API and Web Management > Console > -- > > Key: QPID-5944 > URL: https://issues.apache.org/jira/browse/QPID-5944 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > > A number of users have requested that clear queue function is made available > through the REST API and Web Management UI. > This change will implement a servlet, exposing the operation and integrate > into the UI. ACLs controls will be imposed on the operation, giving the user > the ability to restrict access to the operation if required. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5944) Expose queue clear management operation to the REST API and Web Management Console
[ https://issues.apache.org/jira/browse/QPID-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5944. -- Resolution: Fixed > Expose queue clear management operation to the REST API and Web Management > Console > -- > > Key: QPID-5944 > URL: https://issues.apache.org/jira/browse/QPID-5944 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > > A number of users have requested that clear queue function is made available > through the REST API and Web Management UI. > This change will implement a servlet, exposing the operation and integrate > into the UI. ACLs controls will be imposed on the operation, giving the user > the ability to restrict access to the operation if required. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5944) Expose queue clear management operation to the REST API and Web Management Console
[ https://issues.apache.org/jira/browse/QPID-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-5944: - Status: Reviewable (was: In Progress) > Expose queue clear management operation to the REST API and Web Management > Console > -- > > Key: QPID-5944 > URL: https://issues.apache.org/jira/browse/QPID-5944 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > > A number of users have requested that clear queue function is made available > through the REST API and Web Management UI. > This change will implement a servlet, exposing the operation and integrate > into the UI. ACLs controls will be imposed on the operation, giving the user > the ability to restrict access to the operation if required. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5958) Wire up the Connection#remoteProcessPid attribute to the client's pid obtained during 0-8..0-10 connection negotiation
[ https://issues.apache.org/jira/browse/QPID-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084440#comment-14084440 ] Andrew MacBean commented on QPID-5958: -- Keith, I notice that you changes have introduced some more inline style into the HTML, namely in broker-plugins/management-http/src/main/java/resources/showConnection.html. The inline style setting float to be left on the atrribute value divs is something we should avoid anyway but as far as I can tell its also unecessary? The JIRA I raised for QPID-5935 was to try and remove inline HTML style and make use of the common.css and so I am keen to avoid us adding more? > Wire up the Connection#remoteProcessPid attribute to the client's pid > obtained during 0-8..0-10 connection negotiation > -- > > Key: QPID-5958 > URL: https://issues.apache.org/jira/browse/QPID-5958 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall > Fix For: 0.29 > > > In order to allow an operators of complex systems to more effectively manage > systems with many messaging clients, the process identifiers (pids) of the > remote client processes should be made available from the Web Management UI. > This change will wire up the currently unused Connection model attribute > remoteProcessPid to the pid yielded at part of the 0-8..0-10 connection > negotiation. It will also make the same field visible through the UI. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5953) Web UI: queue, exchange and connection tables have stopped refreshing automatically
[ https://issues.apache.org/jira/browse/QPID-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5953. -- Resolution: Fixed > Web UI: queue, exchange and connection tables have stopped refreshing > automatically > --- > > Key: QPID-5953 > URL: https://issues.apache.org/jira/browse/QPID-5953 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.29 >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > > The exchanges, queues and connection tables on the virtual host used to > automatically refresh periodically giving a useful live view of the state of > the Broker (displaying current queue depths, rates of flow etc). > This functionality has been lost some where during the course of the work on > 0.29. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5957) Session model object to expose transaction start and update information
[ https://issues.apache.org/jira/browse/QPID-5957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5957. -- Resolution: Fixed > Session model object to expose transaction start and update information > --- > > Key: QPID-5957 > URL: https://issues.apache.org/jira/browse/QPID-5957 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > > The Java Broker currently keeps track of store transaction start and > transaction update times which it uses the long running transaction > detection.It would be helpful to users if this information was made > available through the Session model object. > This change will make transactionStartTime and transactionUpdateTime > available as attributes of the Session model object. It will also make this > fields available via the Connection tab within the Management UI. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5958) Wire up the Connection#remoteProcessPid attribute to the client's pid obtained during 0-8..0-10 connection negotiation
[ https://issues.apache.org/jira/browse/QPID-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5958. -- Resolution: Fixed > Wire up the Connection#remoteProcessPid attribute to the client's pid > obtained during 0-8..0-10 connection negotiation > -- > > Key: QPID-5958 > URL: https://issues.apache.org/jira/browse/QPID-5958 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > > In order to allow an operators of complex systems to more effectively manage > systems with many messaging clients, the process identifiers (pids) of the > remote client processes should be made available from the Web Management UI. > This change will wire up the currently unused Connection model attribute > remoteProcessPid to the pid yielded at part of the 0-8..0-10 connection > negotiation. It will also make the same field visible through the UI. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5928) UI: Implement or update virtualhostnode & virtualhost view and edit dialogs
[ https://issues.apache.org/jira/browse/QPID-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-5928: - Status: Reviewable (was: In Progress) > UI: Implement or update virtualhostnode & virtualhost view and edit dialogs > --- > > Key: QPID-5928 > URL: https://issues.apache.org/jira/browse/QPID-5928 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > > Implement or modify the VHN/VH view and edit dialogs to be up to date with > tyoe specific and common/derived attributes.. > implementation should be sensibly shared to avoid duplication of UI code. > if virtualhost is not active, then panels for queues, exchanges, connections > etc should be hidden -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5928) UI: Implement or update virtualhostnode & virtualhost view and edit dialogs
[ https://issues.apache.org/jira/browse/QPID-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5928. -- Resolution: Fixed Work done as a pair > UI: Implement or update virtualhostnode & virtualhost view and edit dialogs > --- > > Key: QPID-5928 > URL: https://issues.apache.org/jira/browse/QPID-5928 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > > Implement or modify the VHN/VH view and edit dialogs to be up to date with > tyoe specific and common/derived attributes.. > implementation should be sensibly shared to avoid duplication of UI code. > if virtualhost is not active, then panels for queues, exchanges, connections > etc should be hidden -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5962) Prevent two or more BDB virtual host or virtual hosts nodes sharing the same JE environment path
[ https://issues.apache.org/jira/browse/QPID-5962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5962. -- Resolution: Fixed > Prevent two or more BDB virtual host or virtual hosts nodes sharing the same > JE environment path > > > Key: QPID-5962 > URL: https://issues.apache.org/jira/browse/QPID-5962 > Project: Qpid > Issue Type: Improvement >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.29 > > > BDB JE permits the same environment path to be opened many times from within > a single JVM process. The second environment basically becomes a handle for > the first. > This use case does not fit with the Java Broker's model which expects stores > underlying each virtual host (VH) or virtual host node (VHN) to be > independent. > This change will introduce a simple registry which will serve to prevent the > same JE store being attached to more than one VH or VHN. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5972) Web UI to edit actual attribute values rather than effective values
[
https://issues.apache.org/jira/browse/QPID-5972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew MacBean resolved QPID-5972.
--
Resolution: Fixed
> Web UI to edit actual attribute values rather than effective values
> ---
>
> Key: QPID-5972
> URL: https://issues.apache.org/jira/browse/QPID-5972
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: 0.29
>
>
> The model underlying the Java Broker now makes a distinction between actual
> attribute values and effective attribute values. For instance a virtual host
> might have an effective storePath attribute of:
> {noformat}
> virtualHost.storePath=/Users/keith/work/mytrades
> {noformat}
> but an actual value of:
> {noformat}
> virtualHost.storePath=${qpid.work_dir}/mytrades
> {noformat}
> When editing an object through the UI, the 'show' tab should show me an
> object's effective values, whereas when editing, the dialogue should offer me
> the actual value for edit.
> This change will alter the UI so that actual values are offer on all edit
> dialogues.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5984) Queue tab improvements
[ https://issues.apache.org/jira/browse/QPID-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5984. -- Resolution: Fixed > Queue tab improvements > -- > > Key: QPID-5984 > URL: https://issues.apache.org/jira/browse/QPID-5984 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Keith Wall > > The queue tabs needs the following extra attributes to be useful to an > operator of a Java Broker: > * queueFlowResumeSizeBytes > * queueFlowControlSizeBytes > * maximumDeliveryAttempts > Also the attributes pane should be reformatted to use two columns. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5981) [Java Broker] Add ability to set binding arguments in web management console
[ https://issues.apache.org/jira/browse/QPID-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5981. -- Resolution: Fixed > [Java Broker] Add ability to set binding arguments in web management console > > > Key: QPID-5981 > URL: https://issues.apache.org/jira/browse/QPID-5981 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Affects Versions: 0.30 >Reporter: Alex Rudyy >Assignee: Andrew MacBean > > In binding creation dialogue add ability to set binding arguments. UI should > allow the user to select only arguments that are suitable for the exchange > (how will it know?). Which arguments do we want to support (jms selector, > x-match etc)??? > Scope: > create a table > allow the user to add key / value pairs (value is String) > no extra UI side validation > x-match etc out of scope -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5986) Second column atrributes on virtual host, virtual host node and queue tabs not aligned correctly in IE
Andrew MacBean created QPID-5986: Summary: Second column atrributes on virtual host, virtual host node and queue tabs not aligned correctly in IE Key: QPID-5986 URL: https://issues.apache.org/jira/browse/QPID-5986 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Andrew MacBean Assignee: Andrew MacBean The wrapped divs in the right hand aligned container on the queue, virtualhost and connection tabs need to be cleared to appear correctly in some IE versions and also for consistency. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5986) Second column atrributes on virtual host, virtual host node and queue tabs not aligned correctly in IE
[ https://issues.apache.org/jira/browse/QPID-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-5986: Assignee: Keith Wall (was: Andrew MacBean) > Second column atrributes on virtual host, virtual host node and queue tabs > not aligned correctly in IE > -- > > Key: QPID-5986 > URL: https://issues.apache.org/jira/browse/QPID-5986 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Keith Wall > Time Spent: 0.5h > Remaining Estimate: 1h > > The wrapped divs in the right hand aligned container on the queue, > virtualhost and connection tabs need to be cleared to appear correctly in > some IE versions and also for consistency. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5986) Second column atrributes on virtual host, virtual host node and queue tabs not aligned correctly in IE
[ https://issues.apache.org/jira/browse/QPID-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-5986: - Status: Reviewable (was: In Progress) > Second column atrributes on virtual host, virtual host node and queue tabs > not aligned correctly in IE > -- > > Key: QPID-5986 > URL: https://issues.apache.org/jira/browse/QPID-5986 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > Time Spent: 0.5h > Remaining Estimate: 1h > > The wrapped divs in the right hand aligned container on the queue, > virtualhost and connection tabs need to be cleared to appear correctly in > some IE versions and also for consistency. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5988) Usefully default VHN/VH store paths to path location based on QPID_WORK
[
https://issues.apache.org/jira/browse/QPID-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew MacBean resolved QPID-5988.
--
Resolution: Fixed
> Usefully default VHN/VH store paths to path location based on QPID_WORK
> ---
>
> Key: QPID-5988
> URL: https://issues.apache.org/jira/browse/QPID-5988
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: 0.31
>
>
> In order to reduce the amount of typing the user needs to perform when
> creating Virtualhost nodes (VHNs) or Virtualhosts (VHs), the model should
> default the storePath attribute of BDB, BDB-HA, Derby and Json VHN impls and
> BDB and Derby VH impls in the following manner:
> {noformat}
> ${qpid.workdir}/${this:name}/[config|messages]
> {noformat}
> The UI should change to indicate that these fields are no longer mandatory.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5987) [Java Broker] Make VHN/VH grid consistent with other grids on broker tab in web management console
[ https://issues.apache.org/jira/browse/QPID-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5987. -- Resolution: Fixed > [Java Broker] Make VHN/VH grid consistent with other grids on broker tab in > web management console > -- > > Key: QPID-5987 > URL: https://issues.apache.org/jira/browse/QPID-5987 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30 >Reporter: Alex Rudyy >Assignee: Andrew MacBean > Fix For: 0.31 > > > Radio buttons are used as a selection elements in the VHN/VH grid. > The rest of the grids on the broker tab uses check boxes as selection element. > 'default' virtualhost column has been lost. It needs to be restored. > the connections/queues/exchanges columns should show N/A if the virtualhost > is not ACTIVE -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5994) [Java Broker]Test BDBHAVirtualHostNodeOperationalLoggingTest.testRemoteNodeReAttached fails sporadically
[
https://issues.apache.org/jira/browse/QPID-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew MacBean resolved QPID-5994.
--
Resolution: Fixed
> [Java Broker]Test
> BDBHAVirtualHostNodeOperationalLoggingTest.testRemoteNodeReAttached fails
> sporadically
>
>
> Key: QPID-5994
> URL: https://issues.apache.org/jira/browse/QPID-5994
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Alex Rudyy
>Assignee: Andrew MacBean
> Fix For: 0.30
>
>
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeOperationalLoggingTest.testRemoteNodeReAttached
> Failing for the past 1 build (Since Failed#167 )
> Took 16 sec.
> Error Message
> eventLogger.message(
> ,
>
> );
> Wanted 2 times:
> -> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeOperationalLoggingTest.testRemoteNodeReAttached(BDBHAVirtualHostNodeOperationalLoggingTest.java:369)
> But was 1 time:
> -> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl$RemoteNodesDiscoverer.onNodeState(BDBHAVirtualHostNodeImpl.java:799)
> Stacktrace
> {noformat}
> org.mockito.exceptions.verification.TooLittleActualInvocations:
> eventLogger.message(
> ,
>
> );
> Wanted 2 times:
> -> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeOperationalLoggingTest.testRemoteNodeReAttached(BDBHAVirtualHostNodeOperationalLoggingTest.java:369)
> But was 1 time:
> -> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl$RemoteNodesDiscoverer.onNodeState(BDBHAVirtualHostNodeImpl.java:799)
> at
> org.apache.qpid.server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeOperationalLoggingTest.testRemoteNodeReAttached(BDBHAVirtualHostNodeOperationalLoggingTest.java:369)
> {noformat}
> Standard Output
> {noformat}
> main 2014-08-11 14:14:33,876 INFO [qpid.test.utils.QpidTestCase] ==
> start BDBHAVirtualHostNodeOperationalLoggingTest.testRemoteNodeReAttached
> ==
> main 2014-08-11 14:14:33,879 DEBUG [qpid.server.plugin.QpidServiceLoader]
> Found 42 implementations of interface
> org.apache.qpid.server.plugin.ConfiguredObjectTypeFactory
> main 2014-08-11 14:14:33,882 DEBUG
> [server.configuration.updater.TaskExecutorImpl] Starting task executor
> main 2014-08-11 14:14:33,883 DEBUG
> [server.configuration.updater.TaskExecutorImpl] Task executor is started
> main 2014-08-11 14:14:33,899 DEBUG
> [server.virtualhostnode.berkeleydb.BDBHAVirtualHostNodeImpl] Activating
> virtualhost node BDBHAVirtualHostNodeImpl
> [id=1af44e76-4cb2-43bb-83d7-053586beb749, name=node1,
> storePath=/tmp/BDBHAVirtualHostNodeOperationalLoggingTest.testRemoteNodeReAttached.1407780873883/node1,
> groupName=group, address=localhost:1, state=UNINITIALIZED, priority=1,
> designatedPrimary=true, quorumOverride=0]
> main 2014-08-11 14:14:33,899 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Creating
> environment
> main 2014-08-11 14:14:33,899 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Environment path
> /tmp/BDBHAVirtualHostNodeOperationalLoggingTest.testRemoteNodeReAttached.1407780873883/node1
> main 2014-08-11 14:14:33,900 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Group name group
> main 2014-08-11 14:14:33,900 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Node name node1
> main 2014-08-11 14:14:33,900 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Node host port
> localhost:1
> main 2014-08-11 14:14:33,900 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Helper host port
> localhost:1
> main 2014-08-11 14:14:33,900 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Helper node name
> node1
> main 2014-08-11 14:14:33,900 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Durability
> SYNC,NO_SYNC,SIMPLE_MAJORITY
> main 2014-08-11 14:14:33,900 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Designated primary
> (applicable to 2 node case only) true
> main 2014-08-11 14:14:33,900 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Node priority 1
> main 2014-08-11 14:14:33,900 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Quorum override 0
> main 2014-08-11 14:14:33,900 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Permitted node
> list []
> main 2014-08-11 14:14:33,902 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Setting
> ReplicationConfig key je.rep.repStreamTimeout to '1 h'
> main 2014-08-11 14:14:33,902 INFO
> [store.berkeleydb.replication.ReplicatedEnvironmentFacade] Setting
> Replicati
[jira] [Updated] (QPID-6006) UI to expose attribute defaults during create and edit workflows
[ https://issues.apache.org/jira/browse/QPID-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-6006: - Status: Reviewable (was: In Progress) > UI to expose attribute defaults during create and edit workflows > > > Key: QPID-6006 > URL: https://issues.apache.org/jira/browse/QPID-6006 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.31 > > > The model underlying the Java Broker has provision for Configured Object > attributes to have default values. The defaults take effect unless the user > overrides them be specifying a value. > These default value need to be revealed to the user in create and edit > workflow so the user can understand how the system will behave, if they > choose to leave an optional field blank. > The decision has been made to utilise Dojo's widget promptMessage to reveal > the default to the user during create and edit workflows. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6006) UI to expose attribute defaults during create and edit workflows
[ https://issues.apache.org/jira/browse/QPID-6006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-6006. -- Resolution: Fixed > UI to expose attribute defaults during create and edit workflows > > > Key: QPID-6006 > URL: https://issues.apache.org/jira/browse/QPID-6006 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.31 > > > The model underlying the Java Broker has provision for Configured Object > attributes to have default values. The defaults take effect unless the user > overrides them be specifying a value. > These default value need to be revealed to the user in create and edit > workflow so the user can understand how the system will behave, if they > choose to leave an optional field blank. > The decision has been made to utilise Dojo's widget promptMessage to reveal > the default to the user during create and edit workflows. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5976) File Keystores or truststores created with the incorrect path/password cannot be deleted
[
https://issues.apache.org/jira/browse/QPID-5976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew MacBean resolved QPID-5976.
--
Resolution: Fixed
> File Keystores or truststores created with the incorrect path/password cannot
> be deleted
>
>
> Key: QPID-5976
> URL: https://issues.apache.org/jira/browse/QPID-5976
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.29
>Reporter: Keith Wall
>Assignee: Andrew MacBean
>Priority: Minor
> Fix For: 0.31
>
>
> If I create a keystore or truststore using the Web Management UI but mistype
> the file path or password, the keystore/truststore object is created anyway.
> If I then try delete the keystore/truststore, I receive an error message and
> the object remains.
> {noformat}
> Error:RequestError: Unable to load
> api/latest/keystore?id=f6c298f6-3735-49b7-bf26-d138273d561e status: 409
> {noformat}
> The problem is that even on delete, the keystore/trustore tries to validate
> itself, this validation fails and prevents the deletion from proceeding.
> {noformat}
> org.apache.qpid.server.configuration.IllegalConfigurationException: Cannot
> instantiate key store at
> /Users/keith/src/qpid/qpid/java/test-profiles/test_resources/ssl/java_broker_keystore.jks
> at
> org.apache.qpid.server.security.FileKeyStoreImpl.validateKeyStoreAttributes(FileKeyStoreImpl.java:173)
> at
> org.apache.qpid.server.security.FileKeyStoreImpl.validateChange(FileKeyStoreImpl.java:158)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.changeAttributes(AbstractConfiguredObject.java:1295)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$11.execute(AbstractConfiguredObject.java:1282)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$2.execute(TaskExecutorImpl.java:149)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$2.execute(TaskExecutorImpl.java:145)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.executeTask(TaskExecutorImpl.java:299)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submit(TaskExecutorImpl.java:131)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.run(TaskExecutorImpl.java:251)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.run(TaskExecutorImpl.java:144)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.runTask(AbstractConfiguredObject.java:1259)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.setAttributes(AbstractConfiguredObject.java:1276)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$7.execute(AbstractConfiguredObject.java:814)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$7.execute(AbstractConfiguredObject.java:799)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.executeTask(TaskExecutorImpl.java:299)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.access$400(TaskExecutorImpl.java:43)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:327)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:322)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: java.io.IOException: Keystore was tampered with, or password was
> incorrect
> at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:772)
> at
> sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55)
> at java.security.KeyStore.load(KeyStore.java:1214)
> at
> org.apache.qpid.transport.network.security.ssl.SSLUtil.getInitializedKeyStore(SSLUtil.java:172)
> at
> org.apache.qpid.server.security.FileKeyStoreImpl.validateKeyStoreAttributes(FileKeyStoreImpl.java:169)
> ... 23 more
> Caused by: java.security.UnrecoverableKeyException: Password verification
> failed
> at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:770)
> ... 27 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail:
[jira] [Resolved] (QPID-5991) Improve BDB HA system tests
[ https://issues.apache.org/jira/browse/QPID-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5991. -- Resolution: Fixed > Improve BDB HA system tests > --- > > Key: QPID-5991 > URL: https://issues.apache.org/jira/browse/QPID-5991 > Project: Qpid > Issue Type: Test > Components: Java Tests >Reporter: Keith Wall >Assignee: Andrew MacBean >Priority: Minor > Fix For: 0.31 > > > Eliminate some duplication from the BDB HA system test suite and reduce the > time taken for their execution. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5918) Prevent file system paths with mixed file separator conventions when running on Windows
[
https://issues.apache.org/jira/browse/QPID-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew MacBean resolved QPID-5918.
--
Resolution: Fixed
> Prevent file system paths with mixed file separator conventions when running
> on Windows
> ---
>
> Key: QPID-5918
> URL: https://issues.apache.org/jira/browse/QPID-5918
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Environment: Windows
>Reporter: Keith Wall
>Assignee: Andrew MacBean
>Priority: Minor
> Fix For: 0.29
>
>
> On Windows if I choose a QPID_WORK such as
> {code}
> set QPID_WORK=c:\work
> {code}
> when I start the Broker and look at the Management console, I see file system
> paths (store paths, auth providers etc) with mixed file separator conventions
> (i.e. paths containing a mixture of unix / and windows \ ).
> {noformat}
> c:\work/default/config
> {noformat}
> Whilst this is functional, it looks ugly and will confuse those accustomed to
> Windows file separator conventions.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6014) [Java] Declare variables as ConcurrentMap not ConcurrentHashMap to avoid issues afetr compiling on Java 8
[ https://issues.apache.org/jira/browse/QPID-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-6014. -- Resolution: Fixed > [Java] Declare variables as ConcurrentMap not ConcurrentHashMap to avoid > issues afetr compiling on Java 8 > - > > Key: QPID-6014 > URL: https://issues.apache.org/jira/browse/QPID-6014 > Project: Qpid > Issue Type: Improvement > Components: Java Broker, Java Client, Java Common >Reporter: Rob Godfrey >Assignee: Andrew MacBean > Fix For: 0.31 > > > Java 8 redefines the method keySet() on ConcurrentHashMap to return a > narrower type than the standard return type given in the Map interface. If > the code is compiled in Java 8 and then run under Java 7 this causes linking > issues. > Avoid these issues by always declaring variables in terms of the interface > ConcurrentMap -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6002) Server crash with Rabbit MQ C# client
[ https://issues.apache.org/jira/browse/QPID-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-6002. -- Resolution: Fixed > Server crash with Rabbit MQ C# client > - > > Key: QPID-6002 > URL: https://issues.apache.org/jira/browse/QPID-6002 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.28 > Environment: JVM : Oracle Corporation version: 1.7.0_45-b18 OS : > Windows 8 version: 6.2 arch: amd64 >Reporter: Antti Pirilä >Assignee: Andrew MacBean > Fix For: 0.31 > > > When I send a message using RabbitMQ C# client a get this exception to the > log. The server doesn't technically crash, but it becames unusable. > java.lang.NullPointerException > at > org.apache.qpid.server.protocol.v0_8.AMQChannel.handleUnroutableMessage(AMQChannel.java:467) > at > org.apache.qpid.server.protocol.v0_8.AMQChannel.deliverCurrentMessageIfComplete(AMQChannel.java:403) > at > org.apache.qpid.server.protocol.v0_8.AMQChannel.publishContentBody(AMQChannel.java:508) > at > org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.contentBodyReceived(AMQProtocolEngine.java:655) > at org.apache.qpid.framing.ContentBody.handle(ContentBody.java:72) > at > org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.frameReceived(AMQProtocolEngine.java:451) > at > org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.dataBlockReceived(AMQProtocolEngine.java:386) > at > org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.access$700(AMQProtocolEngine.java:88) > at > org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:290) > at > org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine$2.run(AMQProtocolEngine.java:273) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Unknown Source) > at > org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:272) > at > org.apache.qpid.server.protocol.v0_8.AMQProtocolEngine.received(AMQProtocolEngine.java:88) > at > org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:132) > at > org.apache.qpid.server.protocol.MultiVersionProtocolEngine.received(MultiVersionProtocolEngine.java:48) > at > org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:161) > at java.lang.Thread.run(Unknown Source) -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5891) Add BDB HA operational logging
[ https://issues.apache.org/jira/browse/QPID-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5891. -- Resolution: Fixed > Add BDB HA operational logging > -- > > Key: QPID-5891 > URL: https://issues.apache.org/jira/browse/QPID-5891 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > Fix For: 0.29 > > > BDB HA Replicated environments currently have no specific operational > logging, an initial set of relevant messages should be defined and logged at > the relevant points in the code, as per the other operation logs. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5989) Maven build generates duplicate system test class files
[ https://issues.apache.org/jira/browse/QPID-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-5989. -- Resolution: Fixed > Maven build generates duplicate system test class files > --- > > Key: QPID-5989 > URL: https://issues.apache.org/jira/browse/QPID-5989 > Project: Qpid > Issue Type: Bug > Components: Java Tests >Affects Versions: 0.29 >Reporter: Keith Wall >Assignee: Andrew MacBean > Fix For: 0.31 > > > Running the test-comple shows that some classes with systest directories are > being compiled twice. This is causing problems for tools such as Sonar. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6005) [Java Broker] Restoring durable AMQP 1.0 messages leads to IndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/QPID-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew MacBean resolved QPID-6005.
--
Resolution: Fixed
> [Java Broker] Restoring durable AMQP 1.0 messages leads to
> IndexOutOfBoundsException
> -
>
> Key: QPID-6005
> URL: https://issues.apache.org/jira/browse/QPID-6005
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: 0.29
>Reporter: Rob Godfrey
>Assignee: Andrew MacBean
>Priority: Blocker
> Fix For: 0.31
>
>
> {noformat}
> java.lang.IndexOutOfBoundsException
> at java.nio.ByteBuffer.wrap(ByteBuffer.java:371)
> at
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore$StoredBDBMessage.getContent(AbstractBDBMessageStore.java:1337)
> at
> org.apache.qpid.server.protocol.v1_0.Message_1_0.restoreFragments(Message_1_0.java:52)
> at
> org.apache.qpid.server.protocol.v1_0.Message_1_0.(Message_1_0.java:40)
> at
> org.apache.qpid.server.protocol.v1_0.MessageMetaDataType_1_0.createMessage(MessageMetaDataType_1_0.java:52)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.getRecoveredMessage(AsynchronousMessageStoreRecoverer.java:192)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.access$600(AsynchronousMessageStoreRecoverer.java:68)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer$MessageInstanceVisitor.handle(AsynchronousMessageStoreRecoverer.java:388)
> at
> org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.visitMessageInstances(AbstractBDBMessageStore.java:232)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.recoverQueue(AsynchronousMessageStoreRecoverer.java:131)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer.access$800(AsynchronousMessageStoreRecoverer.java:68)
> at
> org.apache.qpid.server.virtualhost.AsynchronousMessageStoreRecoverer$AsynchronousRecoverer$QueueRecoveringTask.run(AsynchronousMessageStoreRecoverer.java:367)
> at java.lang.Thread.run(Thread.java:724)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5984) Queue tab improvements
[ https://issues.apache.org/jira/browse/QPID-5984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103860#comment-14103860 ] Andrew MacBean commented on QPID-5984: -- I think this should be in 0.30 > Queue tab improvements > -- > > Key: QPID-5984 > URL: https://issues.apache.org/jira/browse/QPID-5984 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Keith Wall > Fix For: 0.31 > > > The queue tabs needs the following extra attributes to be useful to an > operator of a Java Broker: > * queueFlowResumeSizeBytes > * queueFlowControlSizeBytes > * maximumDeliveryAttempts > Also the attributes pane should be reformatted to use two columns. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5981) [Java Broker] Add ability to set binding arguments in web management console
[ https://issues.apache.org/jira/browse/QPID-5981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103864#comment-14103864 ] Andrew MacBean commented on QPID-5981: -- I think this should be in 0.30 > [Java Broker] Add ability to set binding arguments in web management console > > > Key: QPID-5981 > URL: https://issues.apache.org/jira/browse/QPID-5981 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Affects Versions: 0.30 >Reporter: Alex Rudyy >Assignee: Andrew MacBean > Fix For: 0.31 > > > In binding creation dialogue add ability to set binding arguments. UI should > allow the user to select only arguments that are suitable for the exchange > (how will it know?). Which arguments do we want to support (jms selector, > x-match etc)??? > Scope: > create a table > allow the user to add key / value pairs (value is String) > no extra UI side validation > x-match etc out of scope -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5987) [Java Broker] Make VHN/VH grid consistent with other grids on broker tab in web management console
[ https://issues.apache.org/jira/browse/QPID-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103869#comment-14103869 ] Andrew MacBean commented on QPID-5987: -- I think this should be in 0.30 > [Java Broker] Make VHN/VH grid consistent with other grids on broker tab in > web management console > -- > > Key: QPID-5987 > URL: https://issues.apache.org/jira/browse/QPID-5987 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30 >Reporter: Alex Rudyy >Assignee: Andrew MacBean > Fix For: 0.31 > > > Radio buttons are used as a selection elements in the VHN/VH grid. > The rest of the grids on the broker tab uses check boxes as selection element. > 'default' virtualhost column has been lost. It needs to be restored. > the connections/queues/exchanges columns should show N/A if the virtualhost > is not ACTIVE -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5988) Default VHN/VH store paths to path location based on QPID_WORK
[
https://issues.apache.org/jira/browse/QPID-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103870#comment-14103870
]
Andrew MacBean commented on QPID-5988:
--
I think this should be in 0.30
> Default VHN/VH store paths to path location based on QPID_WORK
> --
>
> Key: QPID-5988
> URL: https://issues.apache.org/jira/browse/QPID-5988
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Keith Wall
>Assignee: Keith Wall
> Fix For: 0.31
>
>
> In order to reduce the amount of typing the user needs to perform when
> creating Virtualhost nodes (VHNs) or Virtualhosts (VHs), the model should
> default the storePath attribute of BDB, BDB-HA, Derby and Json VHN impls and
> BDB and Derby VH impls in the following manner:
> {noformat}
> ${qpid.work_dir}/${this:name}/[config|messages]
> {noformat}
> The UI should change to indicate that these fields are no longer mandatory.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5991) Improve BDB HA system tests
[ https://issues.apache.org/jira/browse/QPID-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103871#comment-14103871 ] Andrew MacBean commented on QPID-5991: -- I think this should be in 0.30 > Improve BDB HA system tests > --- > > Key: QPID-5991 > URL: https://issues.apache.org/jira/browse/QPID-5991 > Project: Qpid > Issue Type: Test > Components: Java Tests >Reporter: Keith Wall >Assignee: Andrew MacBean >Priority: Minor > Fix For: 0.31 > > > Eliminate some duplication from the BDB HA system test suite and reduce the > time taken for their execution. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-6034) Refactor Port UI to use metadata service rather than hard-coding a list of protocols/transports etc
Andrew MacBean created QPID-6034: Summary: Refactor Port UI to use metadata service rather than hard-coding a list of protocols/transports etc Key: QPID-6034 URL: https://issues.apache.org/jira/browse/QPID-6034 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Andrew MacBean Assignee: Andrew MacBean Refactor the Port UI to use the metadata service (QPID-6009) to determine the list of protocols and transports suitable for each type. Remove want client auth/need client auth attributes from the JMXPort configured object and move the bindingAddress attribute from parent to AMQP and HTTP ports only. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-6034) Refactor Port UI to use metadata service rather than hard-coding a list of protocols/transports etc
[ https://issues.apache.org/jira/browse/QPID-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-6034: Assignee: Alex Rudyy (was: Andrew MacBean) Could you please review this change please? > Refactor Port UI to use metadata service rather than hard-coding a list of > protocols/transports etc > --- > > Key: QPID-6034 > URL: https://issues.apache.org/jira/browse/QPID-6034 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > Refactor the Port UI to use the metadata service (QPID-6009) to determine the > list of protocols and transports suitable for each type. > Remove want client auth/need client auth attributes from the JMXPort > configured object and move the bindingAddress attribute from parent to AMQP > and HTTP ports only. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6034) Refactor Port UI to use metadata service rather than hard-coding a list of protocols/transports etc
[ https://issues.apache.org/jira/browse/QPID-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-6034: - Status: Reviewable (was: In Progress) > Refactor Port UI to use metadata service rather than hard-coding a list of > protocols/transports etc > --- > > Key: QPID-6034 > URL: https://issues.apache.org/jira/browse/QPID-6034 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > > Refactor the Port UI to use the metadata service (QPID-6009) to determine the > list of protocols and transports suitable for each type. > Remove want client auth/need client auth attributes from the JMXPort > configured object and move the bindingAddress attribute from parent to AMQP > and HTTP ports only. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6048) [Java Broker] BDB HA intruder protection allows cluster to restart with an intruder
[ https://issues.apache.org/jira/browse/QPID-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-6048: - Status: Reviewable (was: In Progress) > [Java Broker] BDB HA intruder protection allows cluster to restart with an > intruder > --- > > Key: QPID-6048 > URL: https://issues.apache.org/jira/browse/QPID-6048 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30 >Reporter: Alex Rudyy >Assignee: Alex Rudyy > Fix For: 0.31 > > > When an intruder node joins the BDB HA group the intruder protection shuts > down all nodes in the group. However, it does not shut down nodes on group > restart. Thus, an intruder can become a master. The intruder protection > should be fixed to disallow nodes start-up with an intruder in the group -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6048) [Java Broker] BDB HA intruder protection allows cluster to restart with an intruder
[ https://issues.apache.org/jira/browse/QPID-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-6048. -- Resolution: Fixed > [Java Broker] BDB HA intruder protection allows cluster to restart with an > intruder > --- > > Key: QPID-6048 > URL: https://issues.apache.org/jira/browse/QPID-6048 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30 >Reporter: Alex Rudyy >Assignee: Alex Rudyy > Fix For: 0.31 > > > When an intruder node joins the BDB HA group the intruder protection shuts > down all nodes in the group. However, it does not shut down nodes on group > restart. Thus, an intruder can become a master. The intruder protection > should be fixed to disallow nodes start-up with an intruder in the group -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6048) [Java Broker] BDB HA intruder protection allows cluster to restart with an intruder
[ https://issues.apache.org/jira/browse/QPID-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112251#comment-14112251 ] Andrew MacBean commented on QPID-6048: -- Looks good to me Alex. I think this should be included in 0.30 if possible? > [Java Broker] BDB HA intruder protection allows cluster to restart with an > intruder > --- > > Key: QPID-6048 > URL: https://issues.apache.org/jira/browse/QPID-6048 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30 >Reporter: Alex Rudyy >Assignee: Alex Rudyy > Fix For: 0.31 > > > When an intruder node joins the BDB HA group the intruder protection shuts > down all nodes in the group. However, it does not shut down nodes on group > restart. Thus, an intruder can become a master. The intruder protection > should be fixed to disallow nodes start-up with an intruder in the group -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6057) Test MultiNodeTest.testClusterCannotStartWithIntruder fails sporadically
[ https://issues.apache.org/jira/browse/QPID-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean resolved QPID-6057. -- Resolution: Fixed Looks good to me Alex > Test MultiNodeTest.testClusterCannotStartWithIntruder fails sporadically > > > Key: QPID-6057 > URL: https://issues.apache.org/jira/browse/QPID-6057 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30 >Reporter: Alex Rudyy >Assignee: Andrew MacBean > Fix For: 0.31 > > > Test MultiNodeTest.testClusterCannotStartWithIntruder fails occasionally. -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-6090) Disallow a removal of permitted node entry from BDB HA VHN attribute "permittedNodes", if that node is already a member of a group
Andrew MacBean created QPID-6090: Summary: Disallow a removal of permitted node entry from BDB HA VHN attribute "permittedNodes", if that node is already a member of a group Key: QPID-6090 URL: https://issues.apache.org/jira/browse/QPID-6090 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Andrew MacBean Assignee: Andrew MacBean New validation needs to be enforced so that on removal of node entry from "permittedNodes", if removing node entry is already a member of the group, the new "permittedNodes" nodes entry should not be stored in the configuration store and an exception should be thrown. We need to change UI to disallow a removal of permitted node entry from BDB HA VH attribute "permittedNodes", if that node is already a member of a group -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6090) Disallow a removal of permitted node entry from BDB HA VHN attribute "permittedNodes", if that node is already a member of a group
[ https://issues.apache.org/jira/browse/QPID-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-6090: - Status: Reviewable (was: In Progress) > Disallow a removal of permitted node entry from BDB HA VHN attribute > "permittedNodes", if that node is already a member of a group > -- > > Key: QPID-6090 > URL: https://issues.apache.org/jira/browse/QPID-6090 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > > New validation needs to be enforced so that on removal of node entry from > "permittedNodes", if removing node entry is already a member of the group, > the new "permittedNodes" nodes entry should not be stored in the > configuration store and an exception should be thrown. > We need to change UI to disallow a removal of permitted node entry from BDB > HA VH attribute "permittedNodes", if that node is already a member of a group -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6090) Disallow a removal of permitted node entry from BDB HA VHN attribute "permittedNodes", if that node is already a member of a group
[ https://issues.apache.org/jira/browse/QPID-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean updated QPID-6090: - Assignee: Alex Rudyy (was: Andrew MacBean) > Disallow a removal of permitted node entry from BDB HA VHN attribute > "permittedNodes", if that node is already a member of a group > -- > > Key: QPID-6090 > URL: https://issues.apache.org/jira/browse/QPID-6090 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > New validation needs to be enforced so that on removal of node entry from > "permittedNodes", if removing node entry is already a member of the group, > the new "permittedNodes" nodes entry should not be stored in the > configuration store and an exception should be thrown. > We need to change UI to disallow a removal of permitted node entry from BDB > HA VH attribute "permittedNodes", if that node is already a member of a group -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6090) Disallow a removal of permitted node entry from BDB HA VHN attribute "permittedNodes", if that node is already a member of a group
[ https://issues.apache.org/jira/browse/QPID-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14129818#comment-14129818 ] Andrew MacBean commented on QPID-6090: -- Alex, good question and valid point. I will make changes to the if guards to ensure that the node is part of the current set permitted nodes too so that it works around this scenario. Thanks, Andrew > Disallow a removal of permitted node entry from BDB HA VHN attribute > "permittedNodes", if that node is already a member of a group > -- > > Key: QPID-6090 > URL: https://issues.apache.org/jira/browse/QPID-6090 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > New validation needs to be enforced so that on removal of node entry from > "permittedNodes", if removing node entry is already a member of the group, > the new "permittedNodes" nodes entry should not be stored in the > configuration store and an exception should be thrown. > We need to change UI to disallow a removal of permitted node entry from BDB > HA VH attribute "permittedNodes", if that node is already a member of a group -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-6092) Editing permitted node list to be allowed when VHN is master or in STOPPED/ERRORed state
Andrew MacBean created QPID-6092: Summary: Editing permitted node list to be allowed when VHN is master or in STOPPED/ERRORed state Key: QPID-6092 URL: https://issues.apache.org/jira/browse/QPID-6092 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Andrew MacBean Assignee: Andrew MacBean The permitted node list should be editable only when the node is master, or the node is in error/stopped state. Validation to be enforced both client and server side. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6090) Disallow a removal of permitted node entry from BDB HA VHN attribute "permittedNodes", if that node is already a member of a group
[ https://issues.apache.org/jira/browse/QPID-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130077#comment-14130077 ] Andrew MacBean commented on QPID-6090: -- Alex please review again thanks > Disallow a removal of permitted node entry from BDB HA VHN attribute > "permittedNodes", if that node is already a member of a group > -- > > Key: QPID-6090 > URL: https://issues.apache.org/jira/browse/QPID-6090 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Alex Rudyy > > New validation needs to be enforced so that on removal of node entry from > "permittedNodes", if removing node entry is already a member of the group, > the new "permittedNodes" nodes entry should not be stored in the > configuration store and an exception should be thrown. > We need to change UI to disallow a removal of permitted node entry from BDB > HA VH attribute "permittedNodes", if that node is already a member of a group -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6092) Editing permitted node list to be allowed when VHN is master or in STOPPED/ERRORed state
[ https://issues.apache.org/jira/browse/QPID-6092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130085#comment-14130085 ] Andrew MacBean commented on QPID-6092: -- UI commit to follow > Editing permitted node list to be allowed when VHN is master or in > STOPPED/ERRORed state > > > Key: QPID-6092 > URL: https://issues.apache.org/jira/browse/QPID-6092 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Andrew MacBean >Assignee: Andrew MacBean > > The permitted node list should be editable only when the node is master, or > the node is in error/stopped state. > Validation to be enforced both client and server side. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-6075) Deleting VHN fails to delete underlying store files if VHN has not been started
[ https://issues.apache.org/jira/browse/QPID-6075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew MacBean reassigned QPID-6075: Assignee: Andrew MacBean > Deleting VHN fails to delete underlying store files if VHN has not been > started > --- > > Key: QPID-6075 > URL: https://issues.apache.org/jira/browse/QPID-6075 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.30, 0.31 >Reporter: Keith Wall >Assignee: Andrew MacBean > > Deleting a VHN should delete any files owned by the underlying store. There > is a circumstance where this fails to happen. > # Create a Derby VHN with Provided VH > # Stop the VHN > # Restart the Broker > # Delete the VHN > # VHN removed successfully from the list of VHNs, however, it underlying > store files are still present on disk (DEFECT) > The issue is that ConfigurationStore implementations don't learn their > storeLocation until they are opened. If the store is not opened (as is the > case in the sequence above, or in the case of BDB HA, if a node never becomes > MASTER), the the ConfigurationStore has no knowledge of the store location > when #onDelete is called. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
