The URL was passed into the Local Redirector Plug-in by
matching a properly coded Service statement in the httpd.conf file, but
once in the plug-in no match was found on the "virtual host + rooturi"
pair. Having no way to resolve the request down to a Web application
definition, the plug-in issues this error.
Diagnosing this error is best handled with first knowing where the Web
application is supposed to run: in the Local Redirector Plug-in or in the
Web container. In either case, the plug-in is involved; as stated before,
this message will not occur if you're routing your URL through the HTTP
Transport Handler.
If Web application runs in the
plug-in:
- Note the exact structure of the URL sent
in.
- If the plug-in is acting as a router to the Web
container, check the "Application Dispatching" portion of the
/webapp/examples utility provided, and see if the "virtual host + context
root" pairs there will match against the URL received.
- If the "virtual host + context root" pair is
not in "Application Dispatching, then validate that the J2EE server in
which the Web application is deployed has been started, and that the Web
application has successfully "bound" to a virtual host (check SYSPRINT of
server region).
Note: The plug-in’s "ncf" trace is of little value for this
problem. It will simply say that the URL received didn’t match a known Web
application definition, but it does not tell you why. Therefore,
diagnosing this problem involves visual inspection of the pieces of the
system. |
The problem is either in the structure of the URL or in the definitions
found in the was.conf or in the Web application's deployment descriptor
and the webcontainer.conf file. If the Web application definitions appear
correct, then check to make certain the URL structure is exactly
correct.
Related information
White paper WP100295 in www.ibm.com/support/techdocs
|