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.

Sign up for GitHub

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

Jump to bottom

Fail fast if the daemon can not be started #162

Closed
gnodet opened this issue Oct 27, 2020 · 0 comments
Closed

Fail fast if the daemon can not be started #162

gnodet opened this issue Oct 27, 2020 · 0 comments
Assignees
@gnodet
Labels
enhancement New feature or request
Milestone
0.0.12

Comments

@gnodet
Copy link
Contributor

gnodet commented Oct 27, 2020

If the JVM exits early (or is not started at all), the client will wait for 30s before failing. We should check early if the daemon is not alive using its PID so that we don't have to wait for 30s.
@gnodet gnodet added the enhancement New feature or request label Oct 29, 2020
@gnodet gnodet self-assigned this Nov 2, 2020
gnodet added a commit to gnodet/mvnd that referenced this issue Nov 2, 2020
@gnodet
Fail fast if the daemon can not be started, fixes apache#162
ed23329
@gnodet gnodet closed this as completed in a95ac9e Nov 2, 2020
@ppalaga ppalaga added this to the 0.0.12 milestone Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gnodet gnodet

Labels
enhancement New feature or request
Projects
None yet
Milestone
0.0.12
Development

No branches or pull requests
2 participants
@gnodet @ppalaga