Monitoring Performance - HTTP 500

Question

Hi all,
I have a system load testing and have been getting more than a 2:1 ratio of
Error 500's:
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from
fulfilling the request.
I am watching my default execute queue and it appears fine (a large
percentage of idle threads).. My default execute queue has 50 threads with
60% dedicated to socket connections (I have been playing around with this
number) - My test environment has 40 simultaneous threads making HTTP
requests with a 1 second delay between requests..
Other than viewing the results of my test, how can I detect when WLS is
returning an error and not processing a request (through JMX)?
The monitoring behavior I expected when I saw this error was a huge
utilization of threads in the execute queue - equal to 60% * 50 threads =
30, but I consistently have 35 - 40 threads idle.. Any ideas?
Furthermore I don't see any other database errors being generated in my log
files (and I have my servlet entry-point coded to throw a ServletException
when that occurs - so I should see that).
One last note, in my tests I have a request that does not invoke any
Servlets or JSP (strictly HTTP) and it is not generating this error..
Thanks in advance for your help!
Steve

Answer 1

Look in the weblogic.log file for a stack trace. That should tell you exactly
what is going on.
Mike
"Steven Haines" <[email protected]> wrote:
Hi all,
I have a system load testing and have been getting more than a 2:1 ratio
of
Error 500's:
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented
it from
fulfilling the request.
I am watching my default execute queue and it appears fine (a large
percentage of idle threads).. My default execute queue has 50 threads
with
60% dedicated to socket connections (I have been playing around with
this
number) - My test environment has 40 simultaneous threads making HTTP
requests with a 1 second delay between requests..
Other than viewing the results of my test, how can I detect when WLS
is
returning an error and not processing a request (through JMX)?
The monitoring behavior I expected when I saw this error was a huge
utilization of threads in the execute queue - equal to 60% * 50 threads
=
30, but I consistently have 35 - 40 threads idle.. Any ideas?
Furthermore I don't see any other database errors being generated in
my log
files (and I have my servlet entry-point coded to throw a ServletException
when that occurs - so I should see that).
One last note, in my tests I have a request that does not invoke any
Servlets or JSP (strictly HTTP) and it is not generating this error..
Thanks in advance for your help!
Steve