netscape server 404 question ..

[someone_4]

Ok here is what I found I am just needing to know if i am on the right track here.
on the server web console I do Monitor Current Activity.
And the thing that sticks out is
4xx 75% 606.
Now 4xx are 404 errors. as in my report says
Not Founds (404's): 2607
So would it be safe to say that if i look at the error and access log that the link or url that is giving me the problem would look something like this in the access log:

/batchmast/BatchMastResource_en_US.class HTTP/1.0" 404 207

and like this in the errors log:

GET /batchmast/BatchMastResource_en_US.class, send-file reports: can't find /usr/netscape/server4/std_root/english/applets/com/simpletel/jcss/clients/tablemaintenance/batchmast/BatchMastResource_en_US.class (File not found)

So these would be the files that cant be found and sending out the errors right? And would i be right by saying this could be the cause of performance issues?

Thanks
Richard

[Bill Hassell]

The 4040 error that is reported as above is very simple: the file is not there so the web page that referred to it is broken and needs to be rewritten. Or the file needs to be created.

Performance issues are generally not associated with 404 unless there are (ughhhhh) timing-dependent processes that start something and then 'assume' the needed file will be present (without checking first).

You'll have to characterize the performance issues first. Is the web server getting 5,000 requests per second? Then you probably need a much bigger box or a load balancer and multiple boxes.

If the request rate is low (less than 5 per second) then you'll have to instrument your system to track down the paths of slow web pages. While you can do this with classic Unix tools like top, sar, vmstat, etc it will be very painful. Load a copy of Glance and first determine if your system is compute-bound or disk-bound or LAN-bound.

Then find the busy modules to see what needs fixing. You may have a bunch of broken processes tying up the LAN.

[Christopher Caldwell]

I agree with Bill -

404 shouldn't cause performance problems.

Netscape cache's files by default, so you'd get the initial 404 (at the cost of a file stat-very low overhead), subsequent accesses will probably be memory hits (even lower memory hits).

Give us more info on your performance problem.