|
From: Leif M. <le...@ta...> - 2010-04-13 02:17:50
|
Tomer, The PID file that you are seeing is that of the Wrapper process. It is the "service" that is running so this is correct. It sounds like you are wanting to monitor the status of the Java process as well on your own. You can do so using the following Java PID property: http://wrapper.tanukisoftware.org/doc/english/prop-java-pidfile.html You will also most likely also find the following properties useful. They will contain a token which describes the current status of the Wrapper and Java processes respectively. http://wrapper.tanukisoftware.org/doc/english/prop-statusfile.html http://wrapper.tanukisoftware.org/doc/english/prop-java-statusfile.html Please let me know if you have any questions about these properties and how they work for you. Cheers, Leif On Tue, Apr 13, 2010 at 12:21 AM, Tomer B <tom...@gm...> wrote: > Hi, > > The pid that the java service wrapper stores in file seems to be the pid of > the wrapper service, so I killed my java process and performed status > command the java service wrapper returned that the process is up and printed > on console the pid of the wrapper, a couple of seconds afterwards the > wrapper started my own java process automatically, this time the status is > correct that my service is up but the pid presented is the pid of the > wrapper, is that the correct behaviour? (showing that my service is up while > only the wrapper service was up and showing the pid of the service wrapper > and not of my process?) > > Thanks > |