[ https://issues.apache.org/activemq/browse/AMQCPP-28?page=comments#action_37714 ] Albert Strasheim commented on AMQCPP-28: ----------------------------------------
Using the default activemq.xml, I can reproduce the IllegalStateException quite reliabily: 1. Start a fresh copy of the broker (4.2 from yesterday's trunk) 2. Run the integration test under Valgrind 3. IllegalStateException happens at the end of integration::durable::DurableTester::test or at the start of integration::expiration::ExpirationTest::testExpired. Subsequent test runs don't yield the error, until the broker is restarted. I don't know if this issue could be time-dependent -- if it is, it could explain why I only see it when running under Valgrind. On Linux, I also just got the following test failure for the first time (not running under Valgrind): 1) test: integration::durable::DurableTester::test (E) uncaught exception of unknown type > Purify and Valgrind warnings when running integration tests > ----------------------------------------------------------- > > Key: AMQCPP-28 > URL: https://issues.apache.org/activemq/browse/AMQCPP-28 > Project: ActiveMQ C++ Client > Issue Type: Bug > Affects Versions: 1.1 > Reporter: Albert Strasheim > Assigned To: Nathan Mittler > Fix For: 1.1 > > Attachments: activemq-cpp-test-integration-valgrind.log, > vc2005-activemq-integration-tests-purify.txt, > vc2005-activemq-integration-tests-r487924.txt > > > Warnings from Purify when running the integration test (latest from trunk) > against latest trunk of the broker. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
