Common Startup and Access Issues

                                                                                                                                                                                                                                                                                                                                      Back to [Book]     [Topic]

Common Startup and Access Issues

During startup, the Web Server encounters different issues which are discussed in this section along with troubleshooting information. This section also provides troubleshooting steps for access errors. The following topics are covered here:

• My Server Fails to Start
• File Descriptor Issues
• java.lang.StackOverflowError when accessing JSP and/or Servlet
• Performance Issues
• Getting Information From Running Processes

My Server Fails to Start

When your server fails to start, consider the following cases:

# su
# /usr/sbin/usermod -K defaultpriv=basic,net_privaddr webservd

• • Any of the configured 3rd party NSAPI plug-ins is either not following NSAPI specification.
  • Improper Server Configuration.
    Web Server requires at least 512 MB of memory to operate optimally. If your system is running low on swap space then you might get error shown below:

warning: CORE3283: stderr: Error occurred during initialization of VM
warning: CORE3283: stderr: Could not reserve enough space for object heap
catastrophe: CORE4005: Internal error: unable to create JVM
failure: server initialization failed

You will have to increase the swap space on your system. If you are running Web Server 7 under Solaris 10 zones, then you will need to increase the swap space within the global zone.

Note - Refer to your operating system document on how to add/increase swap space.

File Descriptor Issues

Under heavy load condition, Web Server may run out of file descriptors. In such cases you will get an error like the following:

[18/Dec/2005:20:01:03] failure ( 3014): HTTP3069: 
Error accepting connection (PR_PROC_DESC_TABLE_FULL_ERROR: file descriptor table full)

Increase the file descriptor limit either per process or per system and restart the system.

Linux limits the number of file descriptors that any one process may open; the default limits are 1024 per process. These limits can prevent optimum performance of Web Server. The open file limit is one of the limits that can be tuned with the ulimit command. The command ulimit -aS displays the current limit, and ulimit -aH displays the hard limit (above which the limit cannot be increased without tuning kernel parameters). For setting the limit to hard limit, execute the following command:

ulimit -n unlimited

java.lang.StackOverflowError when accessing JSP and/or Servlet

The default value for thread stack size is 128K for 32-bit server and 256K for 64-bit server. Depending on the web application, the server may require additional thread stack size to service a request. If you are seeing java.lang.StackOverflowError when servicing Java content, you should increase the thread stack size using the Administration Console or the wadm CLI utility. It is recommended that you increase the thread stack size in increments of 8K until the problem ceases to exist. For example, to set the thread stack size to the default +8K on a 64-bit server, execute the following command:

$wadm set-thread-pool-prop --user=admin --port=8989 --password-file=passwordfile --config=config-name stack-size=270336

Performance Issues

See [Sun Java System Web Server Performance Tuning, Sizing, and Scaling Guide].

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 a little non-responsive.

Find the running web server process:

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.

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).