• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

JMeter test run leaks Oracle Sessions

 
tim too
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I'm using JMeter v2.3.4 to load test a GWT based web application. The webserver used is Tomcat v6.0.20.

When I run a simple JMeter recording which queries database and displays some information on the browser, I see lot of sessions getting created in the Oracle. These sessions become INACTIVE and do not get terminated once the recording completes its execution. The next run of the same recording again creates the same number of sessions. Because of this behavior, once I run out of all the Oracle sessions available, my subsequent executions of the test start failing.

This problem is not seen when the test is run directly using the application (i.e. without using JMeter). Please throw some light on what is the actual problem and how to fix it.

Thanks & Regards,
Tim
 
David Newton
Author
Rancher
Posts: 12617
IntelliJ IDE Ruby
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
JMeter shouldn't do anything differently than a browser does (except not run JavaScript, which makes me wonder how you're using it to test a GWT app). It has no way of directly affecting server behavior--it cannot hold Oracle sessions open. I'd be suspicious that your tests aren't logging out or doing something similar that affects app behavior--but it can't be JMeter itself causing a server-side issue.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 34669
367
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
tim too wrote:This problem is not seen when the test is run directly using the application (i.e. without using JMeter). Please throw some light on what is the actual problem and how to fix it.

Sounds like a connection leak in the application itself. It wouldn't show up in manual testing because you don't put forth enough requests. I would look at the code and check you are always closing connections (and in a finally block.)
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic