No target servlet configured for uri: /myapp/index.shtml

Bill Hines

unread,

Jan 10, 2001, 11:25:04 AM1/10/01

to

We're converting an old app that used shtml pages over to a newer one
that uses JSP instead. We got rid of all of the shtml, except the home
page, index.shtml, because many bookmarks are set to that. We gutted that
and put a tag in like this:
<META HTTP-EQUIV="REFRESH" CONTENT="0;
URL=/myapp/servlet/com.myco.myapp.IndexServlet">

However, when we run it using the URL
http://myserver/myapp/index.shtml
under WAS Advanced 3.5.2, we get the 404 message:

No target servlet configured for uri: /myapp/index.shtml

This is a webapp and we can get to everything else under /myapp/ by
entering in URLs for the html, jsp, servlets, etc. It doesn't appear that
it is hitting the META tag, but has a problem with the request for
index.shtml itself. Can anyone tell me what this "No target servlet"
message means? We're using the JSP 1.0, auto-invoker and file serving
enabler. TIA

Paul Ilechko

unread,

Jan 10, 2001, 12:04:10 PM1/10/01

to

Is the index.shtml file in the doc root for the webapp ? It needs to be for
the file serving servlet to find it.

Art Smet

unread,

Jan 10, 2001, 1:26:27 PM1/10/01

to

I would suggest abandoning the META tag approach, and instead try to use WebSphere to configure your com.myco.myapp.IndexServlet directly. In your "myapp" web app for this servlet, define it's servlet web path to be "/index.shtml". That way, references to http://myserver/myapp/index.shtml get mapped to your IndexServlet which is what you want.

It is a bit unconventional (to reference a servlet using a .shtml file extension), but it may be worth a shot.

Bill Hines

unread,

Jan 10, 2001, 4:12:50 PM1/10/01

to

Yes, it's definitely there. In fact, I just tried the same URI with an
HTML file and I get the same error. They are both right there in the doc
root, as defined in the webapp from the admin console.

In article <3A5C960A...@bms.com>, paul.i...@bms.com says...

Paul Ilechko

unread,

Jan 10, 2001, 4:54:33 PM1/10/01

to

Take the autoinvoker out of the webapp and see if it works then.

Bill Hines

unread,

Jan 11, 2001, 11:11:59 AM1/11/01

to

It works now - I had tried various things including restarting the
webapp. I think there is a bug in WAS 3.5.2 - I don't have time to retest
this now, but what I did was to uncheck the enabled flag on the webapp,
then I think I changed the webapp web path, then re-enabled and restared
the webapp. I don't think the file serving enabler responded well to
that. I had to restart the whole app server to get it to work right.

In article <3A5CDA19...@bms.com>, paul.i...@bms.com says...

Darin

unread,

Jan 16, 2001, 1:16:26 PM1/16/01

to

I am getting this problem too, but my doc root is correct and the .jsp is
there. I have no idea what the autoinvoker is, how do I take it out ?
Also, what else could be causing this other than the doc root being
incorrect ?

"Bill Hines" <bhi...@hersheys.com> wrote in message
news:MPG.14c7a5584...@news.software.ibm.com...

Paul Ilechko

unread,

Jan 16, 2001, 1:55:46 PM1/16/01

to

The autoinvoker allows you to serve servlets by classname without them being
registered to websphere. You have to explicitly add it to your webapp.

Ken Hygh

unread,

Jan 17, 2001, 5:04:10 AM1/17/01

to

Darin,
This error message has nothing to do with docroot. It has everything to do with
the URI and webapp/servlet web paths. What WebSphere is trying to tell you is
that no servlet has a web path (URI fragment) of /myapp/*

Ken