Getting Information From Running Processes

Web server 7.0 provides several ways to get more information on the running process, if your web server seems to hang or be little non responsive.

Find the running web server process:

1. Linux — Run the /bin/ps -o "pid ppid comm args" | grep webservd | grep -v admin-server command. The output will look similar to the following text:

   424 1 webservd-wdog webservd-wdog -d /var/opt/SUNWwbsvr7/https-chilidev1.red.iplanet.com/config -r 425 424 webservd webservd -d /var/opt/SUNWwbsvr7/https-chilidev1.red.iplanet.com/config -r /opt/ 426 425 webservd webservd -d /var/opt/SUNWwbsvr7/https-chilidev1.red.iplanet.com/config -r /opt/

   pstack -p 426 (the last child PID) will return the web server stack information of the running process.

2. Solaris — Run the /usr/bin/ps -o "pid ppid cmd args" | grep webservd | grep -v admin-server command. The output will look similar to the following text:

   424 1 webservd-wdog webservd-wdog -d /var/opt/SUNWwbsvr7/https-chilidev1.red.iplanet.com/config -r 425 424 webservd webservd -d /var/opt/SUNWwbsvr7/https-chilidev1.red.iplanet.com/config -r /opt/ 426 425 webservd webservd -d /var/opt/SUNWwbsvr7/https-chilidev1.red.iplanet.com/config -r /opt/

   pstack -p 426 (the last child PID) will return the web server stack information of the running process.

If you are running dynamic applications that uses JSPs/Servlets and you find that Web Server is becoming unresponsive during their execution, you can get Web Server to print the stack information within the log (logs/errors) by running the command kill -s QUIT 426 (last child PID).