Something no one's pointed out yet is that "500 Internal Server Error" is among
the most generic error messages one can get. By itself it means nothing more
than that an error on the server prevented the request from being handled
successfully. If you work with any kind of dynamic server-side processing for
very long, be it PERL, JSP, ColdFusion, ASP, whatever, you soon learn that "500
Internal Server Error" is almost meaningless. All it should mean to a developer
is to go look in the server and/or app-server logs for more data.
So which error are we referring to at this point? The reason I ask and bring
this up is that Mark's message suggests the 500 error. A 500 error is like a
red flag signaling a problem on the server. The cause of the problem could be
anything. Mark sounds like he'd got a pretty good idea of what's causing his
problem, but I don't see the relationship to the problem Amy was talking about.
Scott
> -----Original Message-----
> From: Mark Mynatt [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 29, 2000 1:34 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Strange! 500 Internal Server Error
>
>
> Hi Amy,
>
> I'm getting this error as well, and I think it's my driver from NetDirect.
> I've noticed that the driver (using trace stacks) makes a call to get a
> connection, and then fails to get that connection.
>
> Also, I'm using synchronized on the methods where I want to make sure the
> threads are not getting corrupted because I am also using global class
> variables.
>
> Mark Mynatt
> [EMAIL PROTECTED]
>
> -----Original Message-----
> From: Amy Wan [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 29, 2000 4:31 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Strange! 500 Internal Server Error
>
>
> Hi
>
> I am not sure if it is a requirement to restart JRUN Default server after I
> make changes to any JSP page.
>
> I found that after I restart JRun A FEW TIMES, the 500 Internal Error gone
> and my JSP pages work fine.
>
> The other funny thing is if I access a JSP page which I have never accessed
> before, I will get
> EXCEPTION 1 (See below) once and EXCEPTION 2 when I reload the page.
> Then when I restarted JRun Default Server, the page works again.
>
> Therefore, I concluded that it is not my JSP page error.
>
> The third thing is I have this line in my JSP page
> response.setIntHeader("Expires", -1);
> I got Exception 3 (see below)
> The same line works in Resin1.1.3
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
