-
Notifications
You must be signed in to change notification settings - Fork 87
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
Address already in use - starting up Zookeeper #114
Comments
I've seen this issue on multiple Mac's and running this project's Travis build. |
Sorry to reply to this just now. Are you allowing parallel execution of your tests? |
Rerunning the latest version of the project, I still get the same "Address already in use error" whilst running The only references to parallel execution I can see are in
|
I'm sorry about this - I haven't been able to reproduce. What's the frequency of this failure? Could you share some of the test code you're talking about? |
I wonder if this could actually be related to #150. Any chance you can try with the current |
Unfortunately I still do. I'll spend some time looking further into why. The fact that this issue didn't resolve it gives me something to go on. |
java.net.BindException: Address already in use: bind My error when starting zookeeper, any solution for this ?? |
This error is also happening to me when I use withRunningKafka on different test files. Ex:
And I have other testSpec:
And it fails with
I'm on macOS Catalina. If I just move all the tests to the same file everything is fine and working. |
I started working PRs for #109 and #92 but have run into a problem running tests.
I'm posting here in hopes of getting some help in resolving the issue.
So far I've tried:
EmbeddedKafkaObjectSpec
I came across ZOOKEEPER-1441 which outlines my issue but has been left open.
I am able to run tests individually but multiple tests, even using separate ports, result in the second test and onwards failing for the following reason.
Any thoughts would be appreicated.
The text was updated successfully, but these errors were encountered: