|
Problem |
Error 404: "Target Servlet: null" issued at
browser. This occurs when the request is made to the Local Redirector
Plug-in |
|
|
|
Solution |
The plug-in matched the URI with
a deployedwebapp rooturi value in the was.conf file, but when the plug-in
tried to match it against a servletmappingsetting
in the Web application, a mapping was not found.
Note: You will not see this error when the Web application is
running in the Web container in a J2EE server. This is a plugin-specific
error message. |
This error also indicates that the plug-in was not
able to find a matching jspmapping
or filemapping (If matches to
either of these settings had been found one fo the following messages
would have been issued:
Target Servlet: jsp
or
Target Servlet: file
Check the following:
- Note the exact structure of the URL
sent in.
- Check the servletmapping string
definition to make sure it matches against the URL, and that the
servletmapping=
definition is properly associated (or "bundled" via
the <webapp_name> portion of statement) with the rooturi= definition.
Note:
The plug-in's "ncf" trace or the Web container's trace are not much help
in debugging this error. The browser message is telling you what the
problem is. The question is-- why the URL did not match against the
servletmapping value
defined in the was.conf file. |
- Correct either the URL's structure to
match the servletmapping= value for the Web application, or
correct the servletmapping= value to match the URL.
Related information:
WebSphere Applications Server V4.0.1 for z/OS and
OS/390 Assembling JAVA™ 2 Platform Enterprise Edition (J2EE™)
Applications, SA22-7836. |
|
|
|
|
|
|
|