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? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
