CordaRPCClientReconnectionTest appears to leak some threads that are then detected in the RPCStabilityTests, resulting in integration test failures. A fix was identified for this particular problem (see here), but this appears to have introduced a more serious instability into the RpcReconnectTests, resulting in it being reverted here. To work around the original issue, the CordaRPCClientReconnectionTest was moved out into a new package.
This ticket covers fixing the original test problem by moving the CordaRPCClientReconnectionTest back to its original package (net.corda.client.rpc) and resolving the leaking thread issue, while ensuring that the RpcReconnectTests remain stable.
It's unclear whether these problems represent a genuine bug or a problem with the tests at this time.