Project: springxd
Issue XD-1379: Avoid false negative test failures related to HSQLDB
When executing tests and failures occur (should be easy to simulate with a forced failure), several other side-effect failures occur with the following error: {code} Caused by: java.lang.IllegalArgumentException: HSQLDB could not be started. Maybe another instance is already running on 0.0.0.0:13583 ? {code} It seems that the failing tests are not properly cleaning up, so the HSQLDB instance they started is still running thereby causing the other failures. In the case I last witnessed this on a dev branch, I had a valid failure in LocalControlRedisDataInitializationTests (the environmentMatchesTransport method, specifically) and TypeConvertingStreamTests. So, perhaps a good way to start exploring this issue is to simulate a failure in one or both of those classes. The false negatives I'm seeing are in the following: {code} LocalSingleNodeInitializationTests.environmentMatchesTransport RabbitSingleNodeInitializationTests.environmentMatchesTransport RedisSingleNodeInitializationTests.environmentMatchesTransport FileSourceModuleTests.classMethod LocalSingleNodeStreamDeploymentIntegrationTests.classMethod RabbitSingleNodeStreamDeploymentIntegrationTests.classMethod RabbitSingleNodeStreamDeploymentIntegrationTests.classMethod {code} They all seem to be tests that start the SingleNodeApplication.
Story points: 4