|
From: Christian M. <chr...@ta...> - 2012-08-29 09:15:10
|
Hello Jim, If your monitoring tool needs a pid of the Wrapper (and Java) process, you could also use the wrapper.pidfile and wrapper.java.pidfile. With this properties set, the Wrapper, which runs as service will write the PID of itself and the JVM to the specified files. http://wrapper.tanukisoftware.com/doc/english/prop-pidfile.html Another option on querying the Wrapper would be using the '--query' call of the Wrapper binary: bin\wrapper -q ../conf/wrapper.conf http://wrapper.tanukisoftware.com/doc/english/launch-win.html#standalone-status Please let me know if you need any further information. Thank you, Christian On Wed, Aug 29, 2012 at 2:01 PM, Christian Mueller < chr...@ta...> wrote: > Hi Jim, > > thank you for your message. > After the Wrapper has been installed as Windows Service, the Wrapper will > be not directly started but from the Service Control Manager (SCM) and its > context. > > So when you run the command line to start the service, the Wrapper is > starting and connecting to the SCM and requesting it to start the Wrapper > installed as service, this Wrapper process is then eventually starting your > application. Once the SCM returns the confirmation it has successfully > started to the initial Wrapper, it also exits. > > So your monitoring tool should rather monitor the wrapper.exe process, > running as service. > > Hope this information helps you out. > > Cheers, > > Christian Mueller > Tanuki Software, Ltd. > > On Tue, Aug 28, 2012 at 10:05 PM, Jim Burns <Jim...@ge...>wrote: > >> Hello.**** >> >> ** ** >> >> I am trying to monitor the status of a running Wrapper.exe, and the 3rdparty application that starts and monitors the Wrapper.exe process starts >> the process with a command line and command line parameters, then monitors >> for the initial process id to determine the runtime status.**** >> >> ** ** >> >> Problem is that Wrapper.exe starts up, then spawns other processes and >> stops the initial process.**** >> >> Te monitoring tool sees the initial process stop and think the overall >> process has stopped.**** >> >> ** ** >> >> Is there any way to force this initial process to stay running or for *** >> * >> >> ** ** >> >> Command Line used:**** >> >> c:\gcticustom\genesys-ali-adapter\bin\wrapper.exe -t >> c:\gcticustom\genesys-ali-adapter\conf\wrapper.conf**** >> >> ** ** >> >> Jim Burns**** >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Wrapper-user mailing list >> Wra...@li... >> https://lists.sourceforge.net/lists/listinfo/wrapper-user >> >> > |