Jmeter can only be used to simulate concurrent load, which can tell you a problem exists, but can't really tell you where or what the problem is . If you want resource consumption (CPU memory) you will have to use a OS/app server specific tool. There is a monitor results Listener in jmeter but it is specific to tomcat (but you could implement it for your web container). thread deadlock etc would be indicated to Jmeter as the sample does not return (or takes increasingly longer times with loads) but you would have to profile your application while jmeter is running to diagnose the cause
regards deepak For threads deadlock etc On Mon, Nov 2, 2009 at 11:27 AM, Maria Alejandra Trozzi <[email protected]>wrote: > Hi > I'm starting using Jmeter and it's great! but I can't find reports on > resource consumption tests (CPU, memory...) and threads (deadlocks, > contention, etc.) Can I do it with jmeter? If not, is there any other > stress > tool to acomplish this ? > > Thanks ! >
