-------------------------------------------------- From: "sebb" <seb...@gmail.com> Sent: Friday, March 19, 2010 3:57 PM To: "Commons Developers List" <dev@commons.apache.org> Subject: [DAEMON] Procrun Java mode usage
I've got a sample "jvm" mode service running OK, and am now trying to understand how Procrun handles the "Java" mode. The "start" function works fine, but "stop" does not. I'm not sure if that's because of a bug in the service code (I'm using ProcrunService.java) or a feature / bug in prunsrv. Process explorer shows that the "start" function creates the procrun process with a java.exe process. OK so far. However "stop" takes a long time, and ends up with the prunsrv process disappearing, leaving the java.exe process still running. It has to be killed manually. How is Java "stop" supposed to work?
Java "stop" launches another instance of java.exe that is supposed to communicate with the running started service and tell it to stop. The example that you are running doesn't support any kind of RPC, so what you are seeing is expected.
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
