Performance Testing issues

[rmunamar]

We are executing a load test using Mercury's load runner and are encountering an issue

wherein after a few new virtual users log in we get a java exception

javax.naming.NamingException: Disconnected: user change

We spaced out the rate at which new virtual users began to execute and are seeing less errors, however the rate at which virtual users start is extremely slow and may not be realistic (one every 30 seconds up from one every 15 seconds).

When looking at the log, the OTM home page comes up, but we encounter the error when a virtual user does logs in by typing in his/her user id and password and then hits the Login button. We are seeing 30% failure rate which is not good and by spacing out to 30 seconds interval we are seeing a 10% failure rate.

It leads me to think we may be limited in the connections to the database or app server, or that using the same user id multiple times could be causing problems. Are there any property settings we should be looking at to increase this. We did create multiple users and still get the same issue.

Appreciate your assistance

Ramesh

[nick.polites]

Re: Performance Testing issues

Are you running this through a LB and if so be sure to have cookie persistence otherwise you will be bouncing across web servers and continuously getting the login page.

Please provide us with the specs and your environment.

Finally how many users are you simulating on your hardware?

[rmunamar]

Re: Performance Testing issues

We don't have a LB in our configuration. We tested for 100 users and want to ramp it up to 400 users. We seemed to have fixed the issue by increasing the value of glog.cache.RMIConnections.capacity in glog.common.properties.

Please let me know if you see any downside with having a high value for this property. We increased it to 500 since we need at least 400 concurrent users.

[nick.polites]

Re: Performance Testing issues

What kind of hardware/OS are you running? This plays a key in how many users a server can handle. Also your change that you made needs to be placed in the glog.properties file otherwise when you apply a CU patch, it will be overwritten.