Sun Java System Web Server 7.0 Update 4 Troubleshooting Guide

Identifying the Problem

Sun Java System Web Servers are typically deployed in complex and highly sophisticated operating environments. The Sun Java System Web Server covers a broad range of technologies, including Java, Java Servlets, XML, JSP, JDBC data sources, and more. Understanding and diagnosing complex issues involving so many disparate components requires thorough knowledge and a careful diagnostic process.

Gathering any or all of the following information will make it easier to classify a problem and search for solutions. Note that operating system utilities, such as pkginfo and showrev on Solaris and rpm on Linux, are helpful in gathering system information.

ProcedureVerifying Server Platform

  1. What are the exact version numbers of the operating system and products installed?

  2. Have any patches been applied? If so, specify product and operating system patch numbers.

  3. How is the system configured?

    1. What system resources does the system have (memory, disk, swap space, and so on)?

    2. How many web servers and directory servers are installed?

    3. How is the Web Server connected to the directory server?

    4. Are web servers in a cluster or not?

    5. Was any upgrade done? If so, what were source and target versions?

    6. Was a migration done? If so, what were source and target versions?

  4. Have any new web applications been deployed?

  5. Is SSL enabled or not?

  6. What database is being used?

  7. What JDBC driver is being used to access the database?

  8. What JDK version is being used?

  9. What are the JVM heap, stack, and garbage collection-related parameters set to?

  10. What are the JVM options?

  11. What third-party technologies are being used in the installation?

  12. Are the interoperating component versions in compliance with the compatibility matrix specified in the release notes?

    After gathering this information:

    • Collect web server error and access log data (web server instance-specific).

    • Collect any Web Server stack traces. Note that a fresh set of logs associated with the specific problem should be run. This avoids scanning gigabytes of irrelevant log information.

    • Determine the sequence of events that occurred when the problem first appeared, including any steps that may already have been taken to resolve the problem.

      Note –

      When you encounter a problem, do not panic. It is better to approach the problem more systematically by collecting the necessary system specific details.