New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different failures in TestAutoServer #2249
Comments
|
This problem is weird, it looks like the previous connection does not release correctly. |
I've seen that last exception quite a few times, long before #2236 was introduced. |
I also think that its real cause isn't related with that recent change, the change only increased size of the test and issue became more visible. |
|
This means that there is some kind of leftover copy of H2 running. Perhaps we should be doing a global thread dump when this happens to see why the other copy is hangin around. |
With cycled test the failure appears very quickly.
|
|
Without both |
Possibly our test infrastructure should do a quick scan of the current threads after every test to verify that things have shutdown properly, this is not the first time we've had trouble with H2 not shutting down properly. |
In |
It looks like a problem with auto-server mode, |
They are possibly caused by #2236.
But the whole class looks suspicious. Perhaps it shouldn't extend the
TestDb
, but should extendTestBase
, be launched only once, and its logic should be reviewed.The text was updated successfully, but these errors were encountered: