Hi,
>>>>> On Mon, 12 Apr 1999 08:01:28 -0400, [EMAIL PROTECTED] (Adam Gifford) said:
Adam> 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.
I see exactly the same problems, that is on POST I see HTTP 500 errors.
Alas I either get a connection or never get a connection. Hit and miss.
This for a servlet which runs fine with "servletrunner". So the problem iss
definitely with Jserv and potentially the Zone configurations parameters
that are being handled. (see remarks below).
>>
>> 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 see this as a Jserv problem, though given that I get Servlet Exception
it could be more serious then that.
Adam> Well, we started to get HTTP 500's after several hours of
Adam> inactivity, due to too many open file descriptors causing our
Adam> program to generate exceptionswhen it wanted to connect to a
Adam> database. I would reccomend checking your mod_jserv.log and
Adam> jserv.log to see what exception was generating the HTTP 500.
I don't buy that its only due to "too many file descriptors".
I started seeing "500 Internal Server Error" for a servlet that had been
tested and working on Apache 1.3.4 with Jserv 1.04b & SSL. I spend a few days
trying to track what caused the failure. The error message I see in my
jserv.log file is :
[12/04/1999 15:49:38:303] (ERROR) ajp11: Servlet Error: javax.servlet.ServletException:
[12/04/1999 15:49:38:304] (ERROR) an error returned handling request via protocol
"ajpv11"
As I had tested this servlet on 2 different Platforms (Solaris,Irix) I was
miffed to say the least as to why this error out of the blue.
I can run the Servlet under JSDK2.0 "servletrunner" on Solaris and Irix with no
problems.
So the problem must be with Jserv. Aside this, it appears that Jserv freaks out if one
packages the the servlets, and has the .jar file on the "repository" for the zone.
This being a separate problem altogether too.
Any clues for such problem ?
I'd really appreciate feed back on this.
Tarang
----------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
