Greg Barish wrote:
> 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)
Well, we started to get HTTP 500's after several hours of inactivity, due
to too many open file descriptors causing our program to generate
exceptionswhen it wanted to connect to a database. I would reccomend
checking your mod_jserv.log and jserv.log to see what exception was
generating the HTTP 500.
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
