[jira] [Updated] (QPID-5641) [legacystore] Valgrind reports memory leaks on older store tests
[ https://issues.apache.org/jira/browse/QPID-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5641: -- Fix Version/s: 0.28 > [legacystore] Valgrind reports memory leaks on older store tests > > > Key: QPID-5641 > URL: https://issues.apache.org/jira/browse/QPID-5641 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Kim van der Riet >Assignee: Kim van der Riet > Fix For: 0.28 > > > When running cmake test, between one and four of the older tests fail with > memory leaks reported by Valgrind: > SimpleTest > OrderingTest > TransactionalTest > TwoPhaseCommitTest > These are early tests which use broker components in unconventional ways to > test store functionality. Stack trace analysis suggests that the leaks > originate in the handling and destruction of static objects and are tied in > with the boost test framework which is used in these cases. -- 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-5641) [legacystore] Valgrind reports memory leaks on older store tests
[ https://issues.apache.org/jira/browse/QPID-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954676#comment-13954676 ] Justin Ross commented on QPID-5641: --- Kim, it's important you set the fix version. Otherwise, the fix will not be reported with the release. > [legacystore] Valgrind reports memory leaks on older store tests > > > Key: QPID-5641 > URL: https://issues.apache.org/jira/browse/QPID-5641 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Kim van der Riet >Assignee: Kim van der Riet > Fix For: 0.28 > > > When running cmake test, between one and four of the older tests fail with > memory leaks reported by Valgrind: > SimpleTest > OrderingTest > TransactionalTest > TwoPhaseCommitTest > These are early tests which use broker components in unconventional ways to > test store functionality. Stack trace analysis suggests that the leaks > originate in the handling and destruction of static objects and are tied in > with the boost test framework which is used in these cases. -- 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-5641) [legacystore] Valgrind reports memory leaks on older store tests
[ https://issues.apache.org/jira/browse/QPID-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet resolved QPID-5641. Resolution: Fixed Resolved in r.1582324 > [legacystore] Valgrind reports memory leaks on older store tests > > > Key: QPID-5641 > URL: https://issues.apache.org/jira/browse/QPID-5641 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > When running cmake test, between one and four of the older tests fail with > memory leaks reported by Valgrind: > SimpleTest > OrderingTest > TransactionalTest > TwoPhaseCommitTest > These are early tests which use broker components in unconventional ways to > test store functionality. Stack trace analysis suggests that the leaks > originate in the handling and destruction of static objects and are tied in > with the boost test framework which is used in these cases. -- 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-5641) [legacystore] Valgrind reports memory leaks on older store tests
[ https://issues.apache.org/jira/browse/QPID-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949390#comment-13949390 ] ASF subversion and git services commented on QPID-5641: --- Commit 1582324 from [~kpvdr] in branch 'qpid/branches/0.28' [ https://svn.apache.org/r1582324 ] QPID-5641: [legacystore] Valgrind reports memory leaks on older store tests > [legacystore] Valgrind reports memory leaks on older store tests > > > Key: QPID-5641 > URL: https://issues.apache.org/jira/browse/QPID-5641 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > When running cmake test, between one and four of the older tests fail with > memory leaks reported by Valgrind: > SimpleTest > OrderingTest > TransactionalTest > TwoPhaseCommitTest > These are early tests which use broker components in unconventional ways to > test store functionality. Stack trace analysis suggests that the leaks > originate in the handling and destruction of static objects and are tied in > with the boost test framework which is used in these cases. -- 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-5641) [legacystore] Valgrind reports memory leaks on older store tests
[ https://issues.apache.org/jira/browse/QPID-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948186#comment-13948186 ] Justin Ross commented on QPID-5641: --- Reviewed by Andrew. Approved for 0.28. > [legacystore] Valgrind reports memory leaks on older store tests > > > Key: QPID-5641 > URL: https://issues.apache.org/jira/browse/QPID-5641 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > When running cmake test, between one and four of the older tests fail with > memory leaks reported by Valgrind: > SimpleTest > OrderingTest > TransactionalTest > TwoPhaseCommitTest > These are early tests which use broker components in unconventional ways to > test store functionality. Stack trace analysis suggests that the leaks > originate in the handling and destruction of static objects and are tied in > with the boost test framework which is used in these cases. -- 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-5641) [legacystore] Valgrind reports memory leaks on older store tests
[ https://issues.apache.org/jira/browse/QPID-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948122#comment-13948122 ] Andrew Stitcher commented on QPID-5641: --- Approved for 0.28 > [legacystore] Valgrind reports memory leaks on older store tests > > > Key: QPID-5641 > URL: https://issues.apache.org/jira/browse/QPID-5641 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > When running cmake test, between one and four of the older tests fail with > memory leaks reported by Valgrind: > SimpleTest > OrderingTest > TransactionalTest > TwoPhaseCommitTest > These are early tests which use broker components in unconventional ways to > test store functionality. Stack trace analysis suggests that the leaks > originate in the handling and destruction of static objects and are tied in > with the boost test framework which is used in these cases. -- 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-5641) [legacystore] Valgrind reports memory leaks on older store tests
[ https://issues.apache.org/jira/browse/QPID-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943172#comment-13943172 ] ASF subversion and git services commented on QPID-5641: --- Commit 1579963 from [~kpvdr] in branch 'qpid/trunk' [ https://svn.apache.org/r1579963 ] QPID-5641: [legacystore] Valgrind reports memory leaks on older store tests > [legacystore] Valgrind reports memory leaks on older store tests > > > Key: QPID-5641 > URL: https://issues.apache.org/jira/browse/QPID-5641 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > When running cmake test, between one and four of the older tests fail with > memory leaks reported by Valgrind: > SimpleTest > OrderingTest > TransactionalTest > TwoPhaseCommitTest > These are early tests which use broker components in unconventional ways to > test store functionality. Stack trace analysis suggests that the leaks > originate in the handling and destruction of static objects and are tied in > with the boost test framework which is used in these cases. -- 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-5641) [legacystore] Valgrind reports memory leaks on older store tests
[ https://issues.apache.org/jira/browse/QPID-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943164#comment-13943164 ] Kim van der Riet commented on QPID-5641: Given the limited value of these older tests and the unconventional techniques used in them, the simplest approach to solving this is to eliminate them altogether. With other more recent tests in place, this would not result in any significant coverage loss. https://reviews.apache.org/r/19533/ > [legacystore] Valgrind reports memory leaks on older store tests > > > Key: QPID-5641 > URL: https://issues.apache.org/jira/browse/QPID-5641 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Reporter: Kim van der Riet >Assignee: Kim van der Riet > > When running cmake test, between one and four of the older tests fail with > memory leaks reported by Valgrind: > SimpleTest > OrderingTest > TransactionalTest > TwoPhaseCommitTest > These are early tests which use broker components in unconventional ways to > test store functionality. Stack trace analysis suggests that the leaks > originate in the handling and destruction of static objects and are tied in > with the boost test framework which is used in these cases. -- 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-5641) [legacystore] Valgrind reports memory leaks on older store tests
Kim van der Riet created QPID-5641: -- Summary: [legacystore] Valgrind reports memory leaks on older store tests Key: QPID-5641 URL: https://issues.apache.org/jira/browse/QPID-5641 Project: Qpid Issue Type: Bug Components: C++ Broker Reporter: Kim van der Riet Assignee: Kim van der Riet When running cmake test, between one and four of the older tests fail with memory leaks reported by Valgrind: SimpleTest OrderingTest TransactionalTest TwoPhaseCommitTest These are early tests which use broker components in unconventional ways to test store functionality. Stack trace analysis suggests that the leaks originate in the handling and destruction of static objects and are tied in with the boost test framework which is used in these cases. -- 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-5511) Valgrind reports memory leaks in store tests
[ https://issues.apache.org/jira/browse/QPID-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935097#comment-13935097 ] Sébastien GALLET commented on QPID-5511: This bug should be merged with #5317 Don't know if that could help but here is the result of test when compiling 0.26 package on an Ubuntu saucy. > Valgrind reports memory leaks in store tests > > > Key: QPID-5511 > URL: https://issues.apache.org/jira/browse/QPID-5511 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.26, 0.27 >Reporter: Justin Ross >Assignee: Kim van der Riet >Priority: Blocker > Fix For: 0.26 > > Attachments: valgrind.txt > > > The legacystore tests on trunk and the 0.26 release branch report leaks under > valgrind. We need to know if they are real, and if so, what is their > severity. -- 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-5511) Valgrind reports memory leaks in store tests
[ https://issues.apache.org/jira/browse/QPID-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sébastien GALLET updated QPID-5511: --- Attachment: tests_qpid.txt This bug should be merged with #5317 Don't know if that could help but here is the result of test when compiling 0.26 package on an Ubuntu saucy. > Valgrind reports memory leaks in store tests > > > Key: QPID-5511 > URL: https://issues.apache.org/jira/browse/QPID-5511 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.26, 0.27 >Reporter: Justin Ross >Assignee: Kim van der Riet >Priority: Blocker > Fix For: 0.26 > > Attachments: tests_qpid.txt, valgrind.txt > > > The legacystore tests on trunk and the 0.26 release branch report leaks under > valgrind. We need to know if they are real, and if so, what is their > severity. -- 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] [Issue Comment Deleted] (QPID-5511) Valgrind reports memory leaks in store tests
[ https://issues.apache.org/jira/browse/QPID-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sébastien GALLET updated QPID-5511: --- Comment: was deleted (was: This bug should be merged with #5317 Don't know if that could help but here is the result of test when compiling 0.26 package on an Ubuntu saucy. ) > Valgrind reports memory leaks in store tests > > > Key: QPID-5511 > URL: https://issues.apache.org/jira/browse/QPID-5511 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.26, 0.27 >Reporter: Justin Ross >Assignee: Kim van der Riet >Priority: Blocker > Fix For: 0.26 > > Attachments: valgrind.txt > > > The legacystore tests on trunk and the 0.26 release branch report leaks under > valgrind. We need to know if they are real, and if so, what is their > severity. -- 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] [Closed] (QPID-5511) Valgrind reports memory leaks in store tests
[ https://issues.apache.org/jira/browse/QPID-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross closed QPID-5511. - Resolution: Duplicate Fix Version/s: (was: 0.26) > Valgrind reports memory leaks in store tests > > > Key: QPID-5511 > URL: https://issues.apache.org/jira/browse/QPID-5511 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.26, 0.27 >Reporter: Justin Ross >Assignee: Kim van der Riet >Priority: Blocker > Attachments: tests_qpid.txt, valgrind.txt > > > The legacystore tests on trunk and the 0.26 release branch report leaks under > valgrind. We need to know if they are real, and if so, what is their > severity. -- 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-5511) Valgrind reports memory leaks in store tests
[ https://issues.apache.org/jira/browse/QPID-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-5511: -- Attachment: valgrind.txt > Valgrind reports memory leaks in store tests > > > Key: QPID-5511 > URL: https://issues.apache.org/jira/browse/QPID-5511 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.26, 0.27 >Reporter: Justin Ross >Assignee: Kim van der Riet >Priority: Blocker > Fix For: 0.26 > > Attachments: valgrind.txt > > > The legacystore tests on trunk and the 0.26 release branch report leaks under > valgrind. We need to know if they are real, and if so, what is their > severity. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5511) Valgrind reports memory leaks in store tests
Justin Ross created QPID-5511: - Summary: Valgrind reports memory leaks in store tests Key: QPID-5511 URL: https://issues.apache.org/jira/browse/QPID-5511 Project: Qpid Issue Type: Bug Components: C++ Broker, C++ Client Affects Versions: 0.26, 0.27 Reporter: Justin Ross Assignee: Kim van der Riet Priority: Blocker Fix For: 0.26 Attachments: valgrind.txt The legacystore tests on trunk and the 0.26 release branch report leaks under valgrind. We need to know if they are real, and if so, what is their severity. -- This message was sent by Atlassian JIRA (v6.1.5#6160) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201230#comment-13201230 ] Robbie Gemmell commented on QPID-3775: -- Looks good to me. > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Robbie Gemmell > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201229#comment-13201229 ] Keith Wall commented on QPID-3775: -- I've changed the two BDB scripts to avoid use of readlink. Robbie, could you review please? > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-3775: Assignee: Robbie Gemmell (was: Keith Wall) > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Robbie Gemmell > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-3775: Assignee: Keith Wall (was: Alex Rudyy) > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Resolved] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-3775. -- Resolution: Fixed The changes in BDB scripts seem reasonable for me. I have only one comment about backup.sh changes: We do not need to add bdb jars into classpath because backup.sh does not use bdb API to copy data. Instead files are copied using standard java io API. > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195467#comment-13195467 ] Keith Wall commented on QPID-3775: -- Committed patch to correct the argument/QPID_HOME handling. Also changed the scripts so that BDB library version is no longer explicit and the scripts behave in the same manner as qpid-server etc. > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-3775: Assignee: Alex Rudyy (was: Keith Wall) Alex, can you review the script changes please? > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3775: - Status: Ready To Review (was: In Progress) > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Reopened] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reopened QPID-3775: -- Tests failed on Jenkins as the Qpid-Matrix paths contain spaces. This was caused by a preexisting defect in the path/argument handling of backup.sh (and storeUpgrade.sh). > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3775: - Fix Version/s: 0.15 > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Closed] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall closed QPID-3775. > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -15. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3775: - Description: The Java broker currently has a suite of manual persistent store tests. These tests should be automated as part of the System Test suite. BDB-Qpid-1Verifies that committed messages survive clean broker shutdown, after fully completing a number of transactions. BDB-Qpid-2Verifies that committed messages survive immediate (kill -9) broker shutdown, after fully completing a number of transactions. BDB-Qpid-5Verifies that committed messages survive clean broker shutdown, when broker is shutdown mid-transaction. BDB-Qpid-6Verifies that committed messages survive immediate (kill -9) broker shutdown, when broker is shutdown mid-transaction. BDB-Qpid-7Verifies that committed messages survive client connection termination, when clients connection is closed mid-transaction. BDB-Qpid-8Verifies that committed messages survive message store backup and restore, when broker is restarted on a restored backup. The non-store implementation specific tests should be incorporated into the PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a should be implemented as in BDB specific system test. QBTC will need to be extended to permit the shutting down the Broker down ungracefully (using kill -9). Currently the framework uses java.lang.Process#destroy() which is implemented as kill -15. was: The Java broker currently has a suite of manual persistent store tests. These tests should be automated as part of the System Test suite. BDB-Qpid-1Verifies that committed messages survive clean broker shutdown, after fully completing a number of transactions. BDB-Qpid-2Verifies that committed messages survive immediate (kill -9) broker shutdown, after fully completing a number of transactions. BDB-Qpid-5Verifies that committed messages survive clean broker shutdown, when broker is shutdown mid-transaction. BDB-Qpid-6Verifies that committed messages survive immediate (kill -9) broker shutdown, when broker is shutdown mid-transaction. BDB-Qpid-7Verifies that committed messages survive client connection termination, when clients connection is closed mid-transaction. BDB-Qpid-8Verifies that committed messages survive message store backup and restore, when broker is restarted on a restored backup. The non-store implementation specific tests should be incorporated into the PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a should be implemented as in BDB specific system test. QBTC will need to be extended to permit the shutting down the Broker down gracefully (using kill -15). Currently the framework uses java.lang.Process#destroy() which is implemented as kill -9. > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Fix For: 0.15 > > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > ungracefully (using kill -9). Currently the framework uses > java.lang.Process#destr
[jira] [Resolved] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-3775. -- Resolution: Fixed > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > gracefully (using kill -15). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Commented] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195261#comment-13195261 ] Keith Wall commented on QPID-3775: -- Patch applied. > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > gracefully (using kill -15). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-3775: Assignee: Keith Wall (was: Alex Rudyy) Hi Keith, Could you please have a look and commit an updated patch? > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > gracefully (using kill -15). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-3775: - Status: Ready To Review (was: In Progress) > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > gracefully (using kill -15). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-3775: - Attachment: 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch Hi Keith, I and Andrew reviewed your patch and found some tiny issues which we fixed in a new patch attached (0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch): 1) changed BDBBackupTest to be able to run it on Windows 2) fixed SpawnedBrokerHolder#kill() to use kill -KILL to kill the broker process, fixed SpawnedBrokerHolder#shutdown() to utilize process.destroy() to destroy broker gracefully 3) reverted back some changes in FailoverBaseCase in order not to stop broker abruptly as failover tests require some additional changes (IMHO, we need to change FailoverBaseCase to utilize BrokerHolder#kill() in a separate review ) > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests-updated.patch, > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > gracefully (using kill -15). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-3775: Assignee: Alex Rudyy (was: Keith Wall) > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Alex Rudyy > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > gracefully (using kill -15). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3775: - Attachment: 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > gracefully (using kill -15). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3775: - Attachment: (was: 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch) > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > gracefully (using kill -15). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Updated] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3775: - Description: The Java broker currently has a suite of manual persistent store tests. These tests should be automated as part of the System Test suite. BDB-Qpid-1Verifies that committed messages survive clean broker shutdown, after fully completing a number of transactions. BDB-Qpid-2Verifies that committed messages survive immediate (kill -9) broker shutdown, after fully completing a number of transactions. BDB-Qpid-5Verifies that committed messages survive clean broker shutdown, when broker is shutdown mid-transaction. BDB-Qpid-6Verifies that committed messages survive immediate (kill -9) broker shutdown, when broker is shutdown mid-transaction. BDB-Qpid-7Verifies that committed messages survive client connection termination, when clients connection is closed mid-transaction. BDB-Qpid-8Verifies that committed messages survive message store backup and restore, when broker is restarted on a restored backup. The non-store implementation specific tests should be incorporated into the PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a should be implemented as in BDB specific system test. QBTC will need to be extended to permit the shutting down the Broker down gracefully (using kill -15). Currently the framework uses java.lang.Process#destroy() which is implemented as kill -9. was: The Java broker currently has a suite of manual test. These tests should be automated as part of the System Test suite. BDB-Qpid-1Verifies that committed messages survive clean broker shutdown, after fully completing a number of transactions. BDB-Qpid-2Verifies that committed messages survive immediate (kill -9) broker shutdown, after fully completing a number of transactions. BDB-Qpid-5Verifies that committed messages survive clean broker shutdown, when broker is shutdown mid-transaction. BDB-Qpid-6Verifies that committed messages survive immediate (kill -9) broker shutdown, when broker is shutdown mid-transaction. BDB-Qpid-7Verifies that committed messages survive client connection termination, when clients connection is closed mid-transaction. BDB-Qpid-8Verifies that committed messages survive message store backup and restore, when broker is restarted on a restored backup. The non-store implementation specific tests should be incorporated into the PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a should be implemented as in BDB specific system test. QBTC will need to be extended to shut the Broker down gracefully (using kill -15). Currently the framework uses java.lang.Process#destroy() which is implemented as kill -9. > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual persistent store tests. These > tests should be automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to permit the shutting down the Broker down > gracefully (using kill -15). Currently the framework uses > java.lang.Process#destroy() which is implemented as kill -9. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your J
[jira] [Updated] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-3775: - Attachment: 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch Finally testing in progress, uploaded for safe keeping. > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > Attachments: > 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch > > > The Java broker currently has a suite of manual test. These tests should be > automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to shut the Broker down gracefully (using kill > -15). Currently the framework uses java.lang.Process#destroy() which is > implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Created] (QPID-3775) Automate the manual persistent store tests
Automate the manual persistent store tests -- Key: QPID-3775 URL: https://issues.apache.org/jira/browse/QPID-3775 Project: Qpid Issue Type: Task Components: Java Tests Reporter: Keith Wall The Java broker currently has a suite of manual test. These tests should be automated as part of the System Test suite. BDB-Qpid-1Verifies that committed messages survive clean broker shutdown, after fully completing a number of transactions. BDB-Qpid-2Verifies that committed messages survive immediate (kill -9) broker shutdown, after fully completing a number of transactions. BDB-Qpid-5Verifies that committed messages survive clean broker shutdown, when broker is shutdown mid-transaction. BDB-Qpid-6Verifies that committed messages survive immediate (kill -9) broker shutdown, when broker is shutdown mid-transaction. BDB-Qpid-7Verifies that committed messages survive client connection termination, when clients connection is closed mid-transaction. BDB-Qpid-8Verifies that committed messages survive message store backup and restore, when broker is restarted on a restored backup. The non-store implementation specific tests should be incorporated into the PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a should be implemented as in BDB specific system test. QBTC will need to be extended to shut the Broker down gracefully (using kill -15). Currently the framework uses java.lang.Process#destroy() which is implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] [Assigned] (QPID-3775) Automate the manual persistent store tests
[ https://issues.apache.org/jira/browse/QPID-3775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-3775: Assignee: Keith Wall > Automate the manual persistent store tests > -- > > Key: QPID-3775 > URL: https://issues.apache.org/jira/browse/QPID-3775 > Project: Qpid > Issue Type: Task > Components: Java Tests >Reporter: Keith Wall >Assignee: Keith Wall > > The Java broker currently has a suite of manual test. These tests should be > automated as part of the System Test suite. > BDB-Qpid-1Verifies that committed messages survive clean broker > shutdown, after fully completing a number of transactions. > BDB-Qpid-2Verifies that committed messages survive immediate (kill > -9) broker shutdown, after fully completing a number of transactions. > BDB-Qpid-5Verifies that committed messages survive clean broker > shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-6Verifies that committed messages survive immediate (kill > -9) broker shutdown, when broker is shutdown mid-transaction. > BDB-Qpid-7Verifies that committed messages survive client connection > termination, when clients connection is closed mid-transaction. > BDB-Qpid-8Verifies that committed messages survive message store > backup and restore, when broker is restarted on a restored backup. > The non-store implementation specific tests should be incorporated into the > PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a > should be implemented as in BDB specific system test. > QBTC will need to be extended to shut the Broker down gracefully (using kill > -15). Currently the framework uses java.lang.Process#destroy() which is > implemented as kill -9. -- 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 - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Store tests
2009/11/11 Ján Sáreník : > Hello! > > On Wed, Nov 11, 2009 at 02:45:25AM +, James Birdsall wrote: >> + clicking on the "Qpid Testing" link gets me a login page, then after >> I log in I get "You cannot view this page", "Page level restrictions >> have been applied that limit access to this page." >> > > I am experiencing all the same. > Thank you, James, for pointing this out! > > Best regards, Jasan Should be fixed now. The IBM JMS Testing page is still restricted to qpid-comitters. IIRC this is because we have results from the IBM JMS Toolkit there and the license says not to publish results. > -- > Red Hat Czech, MRG Quality Assurance Associate > > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > > -- Martin Ritchie - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Store tests
Hello! On Wed, Nov 11, 2009 at 02:45:25AM +, James Birdsall wrote: > + clicking on the "Qpid Testing" link gets me a login page, then after > I log in I get "You cannot view this page", "Page level restrictions > have been applied that limit access to this page." > I am experiencing all the same. Thank you, James, for pointing this out! Best regards, Jasan -- Red Hat Czech, MRG Quality Assurance Associate - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
RE: Store tests
On Tuesday, November 10, 2009 5:42 AM, Aidan Skinner
[mailto:aidan.skin...@gmail.com] wrote:
>On Tue, Nov 10, 2009 at 3:33 AM, James Birdsall wrote:
>> The mailing list strips attachments and I don't have permissions to add a
>> page to the wiki (I can't even LOOK at most of the testing pages!), so I
>> will send the PDF to Kim directly. If anyone else would like to see it,
>> please let me know!
>
>Which pages are you getting permission denied on? There shouldn't be
>anything on the wiki that isn't publically readable... (both as a
>bland statement of fact and, y'know, general policy)
Well, if I go to "Developer Pages":
+ clicking on the "Qpid Testing" link gets me a login page, then after I log in
I get "You cannot view this page", "Page level restrictions have been applied
that limit access to this page."
+ clicking on any of the three links beneath that ("Qpid JMX Management Console
Testing Guide", "Interop Testing Specification", and "Performance Reliability
and Scaling") gets a login and then a different message: "You cannot view this
page due to inherited restrictions", "Page level restrictions have been applied
to a parent of the current page. These restrictions limit access to only
certain certain user(s) or group(s) and apply to all pages in the hierarchy
underneath the parent."
+ by way of variety, the "Distributed Testing" link higher up the page actually
works
--James Birdsall
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Store tests
On Tue, Nov 10, 2009 at 3:33 AM, James Birdsall wrote: > The mailing list strips attachments and I don't have permissions to add a > page to the wiki (I can't even LOOK at most of the testing pages!), so I will > send the PDF to Kim directly. If anyone else would like to see it, please let > me know! Which pages are you getting permission denied on? There shouldn't be anything on the wiki that isn't publically readable... (both as a bland statement of fact and, y'know, general policy) - Aidan -- Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org "A witty saying proves nothing" - Voltaire - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Store tests
James Birdsall wrote: On Monday, November 09, 2009 12:41 PM, Alan Conway wrote: On 11/09/2009 11:45 AM, Kim van der Riet wrote: It would be a good idea to standardize store tests if we can. If we can agree that no matter what store is used, the end-result from a client perspective would be the same, then tests would be fairly universal and can be run against any store module. All tests outlined below (which are based on some of the current async store tests) assume a clean broker start with the store module loaded (with no store content on disk) and stopping broker on conclusion for each test (which may or may not leave messages in the store) - so there needs to be some mechanism to clean up store artifacts between tests. However, if tests are carefully constructed, it may be possible to avoid a disk cleanup between tests by ensuring exchange and queue names do not overlap between tests. No test should leave the store in an unrecoverable state. The python broker tests framework I've been working on creates a separate working directory for each test, all under a common directory so its easy to clean up between test runs so there's no need to worry about conflicts between tests. Tests marked (SERVER-SIDE) may need to be run from the broker itself or on the same machine as the broker in order to gain access to store artifacts. And they'd be easy enough to write in python. Suggestions welcome. The set below looks good. In particular I think the idea of having the tests be based on user-observable outcomes is the right way to go. Tests for persistence providers came up a while back; I'm in the middle of writing some for the SQL-based provider that Steve Huston is working on. My test plan is more basic, since I'm new to AMQP and Qpid and don't have the detailed understanding of it yet, but even so my tests have shaken out a number of bugs. The test plan is 99% not specific to the provider; at some point I would like to try it against other providers, just to see what happens. The mailing list strips attachments and I don't have permissions to add a page to the wiki (I can't even LOOK at most of the testing pages!), so I will send the PDF to Kim directly. If anyone else would like to see it, please let me know! --James B. James, You can create a Jira, and attach it. This is a good way as then it can be used as the project. It also serves as a way to interact with the project and is weighed into decision to nominate and vote people onto the project as committers. i.e. if you want to work to committership it helps to provide details of what you are doing on the list as a form of updates so people can comment and understand the work stream. regards Carl.
Re: Store tests
On Tue, 2009-11-10 at 04:41 +0100, Robert Godfrey wrote: > 2009/11/10 James Birdsall > > > > Tests for persistence providers came up a while back; I'm in the middle of > > writing some for the SQL-based provider that Steve Huston is working on. My > > test plan is more basic, since I'm new to AMQP and Qpid and don't have the > > detailed understanding of it yet, but even so my tests have shaken out a > > number of bugs. The test plan is 99% not specific to the provider; at some > > point I would like to try it against other providers, just to see what > > happens. > > > > The mailing list strips attachments and I don't have permissions to add a > > page to the wiki (I can't even LOOK at most of the testing pages!), so I > > will send the PDF to Kim directly. If anyone else would like to see it, > > please let me know! > > > > > Can you create a JIRA and attach the PDF to that? > I have created a JIRA: https://issues.apache.org/jira/browse/QPID-2194 in which the original proposal has been pasted. I suggest that we transfer the conversation there. It should be possible to add attachments and files here, please feel free to do so. Kim - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Store tests
2009/11/10 James Birdsall > On Monday, November 09, 2009 12:41 PM, Alan Conway wrote: > > >On 11/09/2009 11:45 AM, Kim van der Riet wrote: > >> It would be a good idea to standardize store tests if we can. If we can > >> agree that no matter what store is used, the end-result from a client > >> perspective would be the same, then tests would be fairly universal and > >> can be run against any store module. > >> > >> All tests outlined below (which are based on some of the current async > >> store tests) assume a clean broker start with the store module loaded > >> (with no store content on disk) and stopping broker on conclusion for > >> each test (which may or may not leave messages in the store) - so there > >> needs to be some mechanism to clean up store artifacts between tests. > >> However, if tests are carefully constructed, it may be possible to avoid > >> a disk cleanup between tests by ensuring exchange and queue names do not > >> overlap between tests. No test should leave the store in an > >> unrecoverable state. > > > >The python broker tests framework I've been working on creates a separate > >working directory for each test, all under a common directory so its easy > to > >clean up between test runs so there's no need to worry about conflicts > between > >tests. > > > >> Tests marked (SERVER-SIDE) may need to be run from the broker itself or > >> on the same machine as the broker in order to gain access to store > >> artifacts. > >And they'd be easy enough to write in python. > > > >> Suggestions welcome. > >The set below looks good. In particular I think the idea of having the > tests be > >based on user-observable outcomes is the right way to go. > > Tests for persistence providers came up a while back; I'm in the middle of > writing some for the SQL-based provider that Steve Huston is working on. My > test plan is more basic, since I'm new to AMQP and Qpid and don't have the > detailed understanding of it yet, but even so my tests have shaken out a > number of bugs. The test plan is 99% not specific to the provider; at some > point I would like to try it against other providers, just to see what > happens. > > The mailing list strips attachments and I don't have permissions to add a > page to the wiki (I can't even LOOK at most of the testing pages!), so I > will send the PDF to Kim directly. If anyone else would like to see it, > please let me know! > > Can you create a JIRA and attach the PDF to that? Cheers, Rob > - > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > >
RE: Store tests
On Monday, November 09, 2009 12:41 PM, Alan Conway wrote: >On 11/09/2009 11:45 AM, Kim van der Riet wrote: >> It would be a good idea to standardize store tests if we can. If we can >> agree that no matter what store is used, the end-result from a client >> perspective would be the same, then tests would be fairly universal and >> can be run against any store module. >> >> All tests outlined below (which are based on some of the current async >> store tests) assume a clean broker start with the store module loaded >> (with no store content on disk) and stopping broker on conclusion for >> each test (which may or may not leave messages in the store) - so there >> needs to be some mechanism to clean up store artifacts between tests. >> However, if tests are carefully constructed, it may be possible to avoid >> a disk cleanup between tests by ensuring exchange and queue names do not >> overlap between tests. No test should leave the store in an >> unrecoverable state. > >The python broker tests framework I've been working on creates a separate >working directory for each test, all under a common directory so its easy to >clean up between test runs so there's no need to worry about conflicts between >tests. > >> Tests marked (SERVER-SIDE) may need to be run from the broker itself or >> on the same machine as the broker in order to gain access to store >> artifacts. >And they'd be easy enough to write in python. > >> Suggestions welcome. >The set below looks good. In particular I think the idea of having the tests >be >based on user-observable outcomes is the right way to go. Tests for persistence providers came up a while back; I'm in the middle of writing some for the SQL-based provider that Steve Huston is working on. My test plan is more basic, since I'm new to AMQP and Qpid and don't have the detailed understanding of it yet, but even so my tests have shaken out a number of bugs. The test plan is 99% not specific to the provider; at some point I would like to try it against other providers, just to see what happens. The mailing list strips attachments and I don't have permissions to add a page to the wiki (I can't even LOOK at most of the testing pages!), so I will send the PDF to Kim directly. If anyone else would like to see it, please let me know! --James B. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
Re: Store tests
On 11/09/2009 11:45 AM, Kim van der Riet wrote: It would be a good idea to standardize store tests if we can. If we can agree that no matter what store is used, the end-result from a client perspective would be the same, then tests would be fairly universal and can be run against any store module. All tests outlined below (which are based on some of the current async store tests) assume a clean broker start with the store module loaded (with no store content on disk) and stopping broker on conclusion for each test (which may or may not leave messages in the store) - so there needs to be some mechanism to clean up store artifacts between tests. However, if tests are carefully constructed, it may be possible to avoid a disk cleanup between tests by ensuring exchange and queue names do not overlap between tests. No test should leave the store in an unrecoverable state. The python broker tests framework I've been working on creates a separate working directory for each test, all under a common directory so its easy to clean up between test runs so there's no need to worry about conflicts between tests. Tests marked (SERVER-SIDE) may need to be run from the broker itself or on the same machine as the broker in order to gain access to store artifacts. And they'd be easy enough to write in python. Suggestions welcome. The set below looks good. In particular I think the idea of having the tests be based on user-observable outcomes is the right way to go. SimpleTest.CreateDelete: (SERVER-SIDE) Create a persistent queue and delete it again, making sure that the disk artifacts (db tables, files) are created and destroyed as appropriate to the implementation. SimpleTest.EmptyRecover: Start stop and restart broker without creating any queues. SimpleTest.QueueCreate: Create a persistent queue. Stop broker and restart it. Make sure queue exists after recovery, and that its persistence ID is unchanged. SimpleTest.QueueCreateWithSettings: Create a persistent queue with a content policy. Stop and restart broker. Make sure queue exists after recovery, and that its policy is still set with the correct limits. SimpleTest.QueueDestroy: Create a persistent queue, then destroy it. Stop broker, then restart. Make sure the queue does not exist. SimpleTest.Enqueue: Create a persistent queue. Send three messages to the queue. Stop and restart the broker. Deqeueue the messages, checking the content. Make sure no extra messages exist in the queue. SimpleTest.Dequeue: Create a persistent queue. Send three messages to the queue, then consume them. Stop the broker. Restart the broker. Make sure no messages exist in the queue. SimpleTest.Staging: Set the frame size to a small value - this will ensure that the message will arrive in parts over the wire. Create a persistent queue with a size policy. Send both a transient and a persistent message which is larger than the size policy and the frame size. This will force the broker to release the content of the message to disk in parts. Now browse the messages, making sure that they are correctly read from the store. Check that the messages are still on the queue. Now stop the broker, then restart. First browse, then consume the messages, making sure the content is as expected. Make sure no other messages remain. SimpleTest.DestroyStagedMessage: Create a persistent queue with a size policy. Send both a transient and a persistent message which is larger than the size policy. This will force the broker to release the content of the message to disk. Now consume the messages, making sure that it is correctly read from the store. Now stop the broker, then restart. Make sure no messages are present. SimpleTest.ExchangeCreateAndDestroy: Create a persistent exchange. Stop and restart broker. Check exchange still exists. Destroy exchange. Stop and restart broker. Make sure exchange does not exist. SimpleTest.ExchangeBindAndUnbind: Create a persistent exchange, a persistent queue and bind them. Stop and restart the broker. Unbind the exchange and the queue. Stop and restart the broker. Check that the exchange and queue are unbound. SimpleTest.ExchangeBindAndUnbindWithArgs: Create a persistent exchange with args, a persistent queue and bind them. Stop and restart the broker. Check that the args are still set on the exchange. Unbind the exchange and the queue. Stop and restart the broker. Check that the args are still set on the exchange. Check that the exchange and queue are unbound. SimpleTest.ExchangeImplicitUnbind: Create persistent exchange and two persistent queues. Bind both queues to exchange. Destroy one of the queues. Stop and restart broker. Ensure that only one queue remains, and is still bound to the exchange. Delete the exchange. Stop and restart broker. Make sure remaining queue still exists, but is not bound. Delete remaining queue. OrderingTest.Basic: Create a persistent queue. Produce 10 messages to the queue. Stop and restart the broker.
Store tests
It would be a good idea to standardize store tests if we can. If we can agree that no matter what store is used, the end-result from a client perspective would be the same, then tests would be fairly universal and can be run against any store module. All tests outlined below (which are based on some of the current async store tests) assume a clean broker start with the store module loaded (with no store content on disk) and stopping broker on conclusion for each test (which may or may not leave messages in the store) - so there needs to be some mechanism to clean up store artifacts between tests. However, if tests are carefully constructed, it may be possible to avoid a disk cleanup between tests by ensuring exchange and queue names do not overlap between tests. No test should leave the store in an unrecoverable state. Tests marked (SERVER-SIDE) may need to be run from the broker itself or on the same machine as the broker in order to gain access to store artifacts. Suggestions welcome. Kim -- SimpleTest.CreateDelete: (SERVER-SIDE) Create a persistent queue and delete it again, making sure that the disk artifacts (db tables, files) are created and destroyed as appropriate to the implementation. SimpleTest.EmptyRecover: Start stop and restart broker without creating any queues. SimpleTest.QueueCreate: Create a persistent queue. Stop broker and restart it. Make sure queue exists after recovery, and that its persistence ID is unchanged. SimpleTest.QueueCreateWithSettings: Create a persistent queue with a content policy. Stop and restart broker. Make sure queue exists after recovery, and that its policy is still set with the correct limits. SimpleTest.QueueDestroy: Create a persistent queue, then destroy it. Stop broker, then restart. Make sure the queue does not exist. SimpleTest.Enqueue: Create a persistent queue. Send three messages to the queue. Stop and restart the broker. Deqeueue the messages, checking the content. Make sure no extra messages exist in the queue. SimpleTest.Dequeue: Create a persistent queue. Send three messages to the queue, then consume them. Stop the broker. Restart the broker. Make sure no messages exist in the queue. SimpleTest.Staging: Set the frame size to a small value - this will ensure that the message will arrive in parts over the wire. Create a persistent queue with a size policy. Send both a transient and a persistent message which is larger than the size policy and the frame size. This will force the broker to release the content of the message to disk in parts. Now browse the messages, making sure that they are correctly read from the store. Check that the messages are still on the queue. Now stop the broker, then restart. First browse, then consume the messages, making sure the content is as expected. Make sure no other messages remain. SimpleTest.DestroyStagedMessage: Create a persistent queue with a size policy. Send both a transient and a persistent message which is larger than the size policy. This will force the broker to release the content of the message to disk. Now consume the messages, making sure that it is correctly read from the store. Now stop the broker, then restart. Make sure no messages are present. SimpleTest.ExchangeCreateAndDestroy: Create a persistent exchange. Stop and restart broker. Check exchange still exists. Destroy exchange. Stop and restart broker. Make sure exchange does not exist. SimpleTest.ExchangeBindAndUnbind: Create a persistent exchange, a persistent queue and bind them. Stop and restart the broker. Unbind the exchange and the queue. Stop and restart the broker. Check that the exchange and queue are unbound. SimpleTest.ExchangeBindAndUnbindWithArgs: Create a persistent exchange with args, a persistent queue and bind them. Stop and restart the broker. Check that the args are still set on the exchange. Unbind the exchange and the queue. Stop and restart the broker. Check that the args are still set on the exchange. Check that the exchange and queue are unbound. SimpleTest.ExchangeImplicitUnbind: Create persistent exchange and two persistent queues. Bind both queues to exchange. Destroy one of the queues. Stop and restart broker. Ensure that only one queue remains, and is still bound to the exchange. Delete the exchange. Stop and restart broker. Make sure remaining queue still exists, but is not bound. Delete remaining queue. OrderingTest.Basic: Create a persistent queue. Produce 10 messages to the queue. Stop and restart the broker. Consume the 10 messages, making sure that the order is correct. OrderingTest.Cycle: Create a persistent queue. Send 10 messages to the queue. Consume 5 messages from the queue, then send another 5 messages to the queue. Stop and restart the broker. Consume the 10 messages, making sure that the order is correct. TransactionalTest.Commit: Create two queues. Send a message to queue 1. Opening a transaction, consume the message from queue 1, then send it to
