You are right.  My apologies, I was thinking of a 304 message.  

I think I have seen this before as well.  You are using the server and the
application, and all of a sudden it seems like JRun is not responding to
requests.  When you go to look at the web server logs, you see a bunch of
servlet request calls with Status of 304.  You restart JRun, and the
application is suddenly working again.  This will continue to work for some
time.

I have worked on this issue with Allaire support for several years, in
several different versions on two different Operating Systems.

My 2 cents is that the plugin that is installed in the web server is loosing
connectivity with the JRun server.  This can be potentially be cause by
several reasons, but we seem to notice it when there is extreme activity in
the JRun server process.  This results in the server not responding to the
plugin in a timely manner, which would effect new requests coming in.

Here is what iPlanet has in their online documentation about the status
codes:

Status Code 
 When a client makes a request, one item the server sends back
 is a status code, which is a three-digit numeric code. There are
 four categories of status codes: 

     Status codes in the 100-199 range indicate a provisional
     response.

     Status codes in the 200-299 range indicate a successful
     transaction. 

     Status codes in the 300-399 range are returned when the
     URL can't be retrieved because the requested document
     has moved. 

     Status codes in the 400-499 range indicate the client has
     an error. 

     Status codes of 500 and higher indicate that the server
     can't perform the request, or an error has occurred. 

 Table A.2 contains some common status codes. 

 Table A.2 Common HTTP status codes 
  Status code 
             Meaning 
  200 
             OK; successful transmission. This is not an
             error. 
  302 
             Found. Redirection to a new URL. The original
             URL has moved. This is not an error; most
             browsers will get the new page. 
  304 
             Use a local copy. If a browser already has a
             page in its cache, and the page is requested
             again, some browsers (such as Netscape
             Navigator) relay to the web server the
             "last-modified" timestamp on the browser's
             cached copy. If the copy on the server is not
             newer than the browser's copy, the server
             returns a 304 code instead of returning the
             page, reducing unnecessary network traffic.
             This is not an error. 
  401 
             Unauthorized. The user requested a
             document but didn't provide a valid username
             or password. 
  403 
             Forbidden. Access to this URL is forbidden. 
  404 
             Not found. The document requested isn't on
             the server. This code can also be sent if the
             server has been told to protect the document
             by telling unauthorized people that it doesn't
             exist. 
  500 
             Server error. A server-related error occurred.
             The server administrator should check the
             server's error log to see what happened. 

             - Ben

-----Original Message-----
From: Christopher B. Hamlin [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 07, 2002 2:18 PM
To: JRun-Talk
Subject: Re: Unexpected 302 return code?


"Garfield, Ben" wrote:
> 
> The 302 code in iPlanet means that the web server used a cached version of
> the file instead of reading it off of the hard drive on the server.
> 
> 

  By 302 I meant the http return code, from the server
to the browser, but also logged in the http log. 
It is used to redirect the browser to another URL.
This is defined in the http spec and it's hard to
believe iPlanet would do something that dumb, though
I guess I could be convinced . . . does iplanet actually say 
something about this in their documentation? It seems like
a mistake somehow, not something you would do on purpose.
And we've had similar (header) problems with JRun before.

  Also, our problems with the 302 are mainly on dynamic content
from JRun---stuff that isn't cached and most times isn't
even coming off a disk (it's in a database). 


  Regards,


______________________________________________________________________
Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. http://www.fusionauthority.com/ads.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to