PQ54164: ENGINE DOES NOT CORRECTLY HANDLE ALL NOTARGETFORURIEXCEPTIONS

APAR status
Closed as program error.

Error description
Getting No target servlet configured for uri. The problem is a
request is coming in for a srevlet and the webgroup is not start
ed yet. If the default_app is configured with a root URI of /,
when the request comes in and the webgroup is not started yet,
based on best match, the request gets set to the default_app and
the servlet will not be found. When the association is made, thi
s is out into the invocation cache and until it is flushed or th
e app is restarted, they will continue to get this error.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server customers   *
****************************************************************
* PROBLEM DESCRIPTION: NoTargetForURIExceptions thrown         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The problem was requests for some of the customer's web
applications were received before those applications had been
loaded by the server.  However, by this time "default_app"
(with a context root of "/") was loaded and active.
WebSphere mistakenly assumed "default_app" was the target of
requests intended for the still unloaded applications.  This
happened because all URIs would match  the root context "/"
if they didn't match any other webapp root URI.  Once the
servlet container associates a URL with a particular web
application, all new requests (to that thread) with the same
URL are also directed to that web app.  This is what
prevented the problem from correcting itself.
.
The NoTargetForURIExceptions are valid errors if the target
web app hasn't loaded yet.
Problem conclusion
The solution that requires no design change is to invalidate
the InvocationCache of a thread that throws this type of
exception (NoTargetForURIException).
Temporary fix Comments
APAR information
APAR number PQ54164
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-10-31
Closed date 2001-10-31
Last modified date 2001-10-31

APAR is sysrouted FROM one or more of the following:
PQ53356

APAR is sysrouted TO one or more of the following:

Modules/Macros
ENGINE          

Fix information
Fixed component name WEBSPHERE AE NT
Fixed component ID 5630A2201

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ54164
IBM Group: Software Group
Modified date: Oct 31, 2001