|
Problem |
The following error message was issued from
the WebSphere Local Redirector Plug-in
Message: "File not found: //<file name> Target Servlet: File
The URL was being passed to the plug-in, but the URL did not resolve to a
defined servletmapping= string. It did map to a defined rooturi= string,
otherwise a different error message ("Virtual Host or Web Application Not
Found") would have been issued. |
|
Cause |
With no servletmapping= match, the plug-in or Web
Container falls back to checking jspmapping=, and then filemapping=.
Assuming that the match was on filemapping= (commonly coded with a
catch-all single slash / ), the URL that was intended to be a servlet
request is evaluated as if it is a file request, causing this error error
message to be issued when the "file" is not found in the HFS. |
|
Solution |
- Note the exact structure of the URL sent in, the question
is simply why the URL didn't match against the servletmapping value
defined.
- If the Web application runs in the plug-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 <appname> portion of statement) with the
rooturi = definition.
- If the Web application runs in the Web container, validate
that the servletmapping value provided in the web.xml file of the
WAR file matches the servletmapping portion of the URL.
- Correct either the URL's structure to match the
servletmapping=value for the Web application, or correct the
servletmapping=value (in was.conf for WAR files
web.xml) to match the URL.
|
|
|
|
|
|
|
|