Skip to content
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

Tests hangs on "process has not exited" on Windows 11 #47

Open
prondzyn opened this issue Mar 27, 2024 · 3 comments
Open

Tests hangs on "process has not exited" on Windows 11 #47

prondzyn opened this issue Mar 27, 2024 · 3 comments
Assignees

Comments

@prondzyn
Copy link

We are migrating our application from Spring Boot 2.x to 3.x. So we upgraded embed mongo from:

            <dependency>
                <groupId>de.flapdoodle.embed</groupId>
                <artifactId>de.flapdoodle.embed.mongo</artifactId>
                <version>3.2.6</version>
            </dependency>

to:

            <dependency>
                <groupId>de.flapdoodle.embed</groupId>
                <artifactId>de.flapdoodle.embed.mongo.spring30x</artifactId>
                <version>4.5.2</version>
                <scope>test</scope>
            </dependency>

Then we are running mvn clean test then.

Tests are running without any problems on Linux machines.

But Windows (tested on Windows 11) users have a problem. Running hands on:

d.f.e.process.runtime.ProcessControl     : stopOrDestroyProcess: process has not exited 

and does not move forward.

Workaround

I've found a workaround. I can run the mvn clean test as administrator, so then everything moves smoothly.

What is the real solution?

Workaround is good for a short term, but I do not understand why user which is creating process cannot exit them.
Did anyone faced similar issue working on Windows?

@michaelmosmann
Copy link
Member

@prondzyn do you have some more logging/stacktrace?

@prondzyn
Copy link
Author

prondzyn commented Apr 2, 2024

Unfortunately I do not have nothing particular.

Additionally, we tested the same on other Windows 11 machine and there the problem does not occur :/ Everything works correctly there.

So the problem is probably my machine-specific. So I think we can close the issue. But it is worth to be aware that is some (unknown) circumstances the problem can occur.

@michaelmosmann
Copy link
Member

@prondzyn .. stopping processes on windows is tricky.. thats why i try to avoid to kill the process but shutdown the mongodb instead.. but if this fails, than there will be some problems.. so if you have such a case and some more logging i would be glad to see these..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants