InfoCenter Home > 8.4.1.1: Plugin ProblemsHTTP Servers are legacy Web products, created at a time when they were the only conduit between Browsers and HTML or CGI files. With the evolution of Web technology, users now require servers to handle servlets, JSP files and EJBs. WebSphere Application Server supports this technology but to provide these functions, it must intercept requests sent to the HTTP Server. The plugin component extends the function of the HTTP Server. It intercepts requests and passes them to either WebSphere Application Server or the HTTP Server. The following three files in the <WAS_root>temp directory allow the plugin to determine the request's destination:
This is the high level view of the plugin process flow: Browser --> WebSphere plugin --> HTTP Server or WebSphere Application Server Typical plugin problemsGenerally plugin failures are caused by missing files or an incorrectly configured HTTP Server. To diagnose plugin problems, verify the data in the files is consistent with both the HTTP request and the active configuration in the Servlet Engine. The plugin configuration files are generated periodically so a delay can occur between the time a change is made in the system and the time the change is reflected in the configuration files. The following error descriptions are symptomatic of plugin problems:
How to debug plugin problemsCheck for errors in the following logs, and in the tracefile:
If there are no entries in the logs or tracefile. comment out the WebSphere Application Server plugin in the httpd.conf file. This will help you determine if the failure originates with WebSphere Application Server or the HTTP Server. The WebSphere plugin property in httpd.conf is:
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|