There are three typical reasons for a servlet to fail to load.
A servlet may not load if the web.xml file contains an error. The servlet container logs the error and the position in the web.xml file where the error occurs. To correct this problem, you must correct the error in the web.xml file. For information on the web.xml file, see Chapter 4, "Configuring Objects in the Servlet Container."
The servlet may be immediately unloaded if the servlet throws an exception from the init() method. The container logs the servlet name and information on the exception. To correct this problem, you must investigate and correct the init() method.
A servlet will not load if the servlet container cannot find the library containing the servlet, or if that library does not contain the function specified in the servlet-class element. The container logs a message indicating that the servlet could not be loaded. To correct this problem:
Check to make sure that the library is in the dynamic library search path for the container (see Appendix C).
Make sure the library base name matches the name of the actual library file, as described in Chapter 4.7.1, "Defining the Servlet Instance."
©2004-2007 Copyright Quovadx, Inc. All Rights Reserved.
Quovadx and Rogue Wave are registered trademarks of Quovadx, Inc. in the United States and other countries. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.