C.19 Troubleshooting

It requires good skills to troubleshoot any anomaly or incident that may be caused by system configuration problems or an incomplete configuration. For example, a tested program deployed in war files that runs very well on a Windows platform may not run on a Unix platform. This may be due to incorrect configuration on the Unix platform ”for example, a misspelled file name , missing CLASSPATH entries, or empty UDDI Service Registry entries.

It is always a good habit to look at the log files under %JWSDP_HOME%\logs. Many of the debug messages about the run-time errors are informative and can help track down the errors. For example, if the file location for the sample_soap_keystore is misplaced, the JWSDP log file jwsdp_log.YYYY-MM-DD will indicate the error message "java.io.FileNotFoundException: \opt\myFX\requester\ sample_soap_keystore (The system cannot find the path specified)." Then you can verify the file locations in your source programs. If a SOAP client does not return any result from invoking a remote Web Service, you may wish to check the Web Container log file catalina.out . If the remote connection is down or the remote Web Service is offline, the catalina.out file will show "AxisFault faultCode: { http://xml.apache.org/axis/Server.NoService ." Then you can verify whether the remote Web Service is online.

It is outside the scope of this book to cover troubleshooting guidelines for developing and deploying Web Services. However, it is recommended that developers verify each installation step and validate the system configuration before development starts and keep a baseline configuration record of all system parameters (for example, CLASSPATH entries) used for future troubleshooting purposes.