Hi -
I have a few servlets which handle POST requests via the doPost
handler. Usually, the system is fine. I can POST and get back
the responses I expect.
Sometimes - usually after a few hours of inactivity - clients
requesting to execute that POST are returned HTTP 500 errors. This
happens for the next 4 or so attempted connections, all of those
connections finishing after 300 ms from the first attempted connection.
To be more clear, I have an automated client program which issues
several POSTs in succession. Usually, the client and Apache+JServ work
fine, but after a few hours of inactivity, the next batch of client
requests will have at least 4 of those requests recieve HTTP 500 errors
from Apache. The rest of the connections after that are fine - almost
like Apache (or JServ) "warmed up".
Has anyone else seen this?
So, I'm not sure if the problem is with:
* Apache
or
* JServ availability (and Apache not being able to find it
results in HTTP 500s)
I noticed that there was an earlier bug report having to do with
lockups with concurrent requests on Apache 1.3.4, but that was the
closest thing I saw.
I am running:
- Apache 1.3.4,
- JServ 1.0b2
- WinNT 4.0 Wkstn Svc Pk 4
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
