You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you kill a daemon process for whatever reason, it'll stick around in mvnd --status until mvnd is stopped.
$ mvnd --status
UUID PID Port Status RSS Last activity Java home
2d49934d-77b3-4d5b-b762-3bfc7b5ebcf1 1918441 43609 Idle 2g 2020-10-26T20:21:46.238 /home/doc/.jabba/jdk/amazon-corretto@1.8.252-09.1
$ kill 1918441
$ mvnd --status
[main] WARN org.jboss.fuse.mvnd.common.OsUtils - ps -o rss= -p 1918441 exited with 1:
[main] WARN org.jboss.fuse.mvnd.common.OsUtils - Unexpected output of ps -o rss= -p 1918441:
UUID PID Port Status RSS Last activity Java home
2d49934d-77b3-4d5b-b762-3bfc7b5ebcf1 1918441 43609 Idle -1k 2020-10-26T20:21:46.238 /home/doc/.jabba/jdk/amazon-corretto@1.8.252-09.1
$ mvnd --stop
Stopping 1 running daemons
$ mvnd --status
UUID PID Port Status RSS Last activity Java home
The text was updated successfully, but these errors were encountered:
uweschaefer
changed the title
Minor: mvnd does not recognize killed daemon process
Minor: mvnd does not recognize killed daemon process on linux
Oct 26, 2020
ppalaga
changed the title
Minor: mvnd does not recognize killed daemon process on linux
Killed or crashed daemon process kept in the registry until mvnd --stop is called
Oct 27, 2020
ppalaga
added a commit
to ppalaga/mvnd
that referenced
this issue
Oct 27, 2020
If you kill a daemon process for whatever reason, it'll stick around in
mvnd --status
until mvnd is stopped.The text was updated successfully, but these errors were encountered: