One of the first aspects of troubleshooting problems with the sample applications is to check the web server and application server log files. See the log section in the Samples Getting Started Guide for details on viewing logs.
Review the following conditions and explanations when troubleshooting the sample applications:
ERROR: Could not connect to the requested serveice.
Check if has been started.
This message as displayed in the web browser results from an error being encountered by the application server's web server plugin. The plugin was unable to communicate with the Executive Service (kxs) of the application server. The web server error log includes a message similar to the following:
[10/Jan/2001:14:02:06] warning (18744): for host 192.18.116.165 trying to GET /NASApp/fortune/fortune, gxrequest reports: cannot connect to iPlanet Executive Server at 0xc01274a5:10818
The cause is usually an application server that has not yet been started. Ensure that the application server is started. See the Samples Getting Started Guide for details on viewing the web server logs.
A "GX Error" displayed in the web browser results from an error being
encountered by the application server's web server plugin. The cause is usually
an invalid URL or misconfiguration of the application. To determine the exact
cause, review the web server's error log. See Samples
Getting Started Guide for details on viewing the web server logs.
A "Server 500 Error" displayed in the web browser results
from an error being encountered by the application server's Java Engine (kjs)
process. A wide variety of configuration and application issues can cause an
exception to occur in the Java Engine. To determine the exact cause, review
the kjs log file. See the Samples Getting
Started Guide for details on viewing the application server logs.
Copyright
(c) 2001 Sun Microsystems, Inc.