I have this situation, I want to test an application which was released to the client, the client has reported that the application is crashed after couple of hours of live use.
We believe there is memory leak, so to monitor the server/memory I set the following testing environment:
1-I set my testing tools (which happened to be eLoad from empirix) in a controller machine
2-two separates machines as agents
And I access the site through the internet, the application is installed in the client site server.
My question is, if I want to test the memory leak or server status, which machine I should monitor? Obviously not the agents machines..right?
Should we set the memory leak/server status check on the controller machine or the server machine? The problem is I donít have access to the client machine where the application is installed, but currently I am monitoring the controller machine..but I am not if I am doing the right way ..any elaboration?
U have a setup look like : two load generators & and a controller machine on which ur load driver is installed to monitor the server session.In this scenerio,u never check the agents for leaks.Memory leaks occurs in the server due to the application.To be precise,if u know the memory leaks,use JProbe4.0,Code performance Tool to analyse the application for memory leaks,provided u should know what use case is causing this problem.JProbe,profiler tool
gives the precise report of no. of objects created by methods use in the app.,allocation of memory for each object,
count of short lived and over allocated objects.