5.3 Servlet Does Not Load
When set to a logging level of verbose or debug, the Agent log reports each servlet as it loads. For example, the log entry below loads the helloworld context but cannot load the servlet:
INFO|2010-06-03T09:45:51,133-07:00| Loading context: /helloworld/ ERROR|2010-06-03T09:45:51,149-07:00| /helloworld: Unable to load servlet: createWebServiceServlet |
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. 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 Agent 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 Agent cannot find the library containing the servlet, or if that library does not contain the function specified in the servlet-class element within web.xml. The Agent 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 Agent (see Section 3.6 and Appendix C).
Make sure the library base name matches the name of the actual library file, as described in Section 4.8.1, "Defining the Servlet Instance."
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo are registered trademarks of Rogue Wave Software, and HydraExpress is a trademark of Rogue Wave Software. All other trademarks are the property of their respective owners.
Contact Rogue Wave about documentation or support issues.