I am load testing an application that requires you to be authenticated before you can use the site using SSL. When I run my test with a low number of users everything seems to be fine. However, when I run the test with more users (50 to 75) I start receiving HTTP 500 - internal server error messages. I had a developer look at Apache and he has found many defunct processes that are running. Also, we have seen some defunct Oracle processes. Has anyone experienced something like this in the past? I am wondering if it could be related to my virtual users not closing connections to the database. This application does not have a logout link that the users can click on. They just close their browser when they are done. Is it safe to assume that the users close their browser when they have finished executing all of the trasactions? Any comments are appreciated!
Re: HTTP 500
hmm, i've seen something similar in IIS. What happens is that sometimes just because the browser is closed doesn't mean the web server kills the thread. IIS would keep working on the thread not knowing the browser was gone. This is most likely some issue with Apache or your code and the way it handles the destruction of threads.
Any thoughts from others? Mine may be a special case example.