Hi All, I'm using JMeter (2.3.2) to simulate a traffic model for our application (server) based on the traffic that our client generates. I used the JMeter proxy to sniff the traffic and then to make it more realistic I re-organised the captured samples into a series or Random and Throughput controllers. This works fine until the point in the test plan where the random/throuput controller come into play nad the the following happens, halting the test:
2009/05/25 16:07:54 ERROR - jmeter.threads.JMeterThread: Test failed! java.lang.StackOverflowError at java.util.HashMap.getEntry(HashMap.java:344) at java.util.LinkedHashMap.get(LinkedHashMap.java:280) at java.util.Collections$SynchronizedMap.get(Collections.java:1975) at org.apache.jmeter.testelement.AbstractTestElement.getProperty(AbstractTestElement.java:140) at org.apache.jmeter.testelement.AbstractTestElement.getPropertyAsInt(AbstractTestElement.java:183) at org.apache.jmeter.control.ThroughputController.getStyle(ThroughputController.java:109) at org.apache.jmeter.control.ThroughputController.isDone(ThroughputController.java:207) at org.apache.jmeter.control.InterleaveControl.currentReturnedNull(InterleaveControl.java:153) at org.apache.jmeter.control.InterleaveControl.nextIsAController(InterleaveControl.java:94) at org.apache.jmeter.control.GenericController.next(GenericController.java:146) at org.apache.jmeter.control.InterleaveControl.next(InterleaveControl.java:83) at org.apache.jmeter.control.InterleaveControl.nextIsAController(InterleaveControl.java:95) at org.apache.jmeter.control.GenericController.next(GenericController.java:146) at org.apache.jmeter.control.InterleaveControl.next(InterleaveControl.java:83) at org.apache.jmeter.control.InterleaveControl.nextIsAController(InterleaveControl.java:95) at org.apache.jmeter.control.GenericController.next(GenericController.java:146) at org.apache.jmeter.control.InterleaveControl.next(InterleaveControl.java:83) at org.apache.jmeter.control.InterleaveControl.nextIsAController(InterleaveControl.java:95) Has anyone seen this before? If so what's causing it and is thete a way to work around it? I've tries the test plan with 2.3.3 also, but the same thing happens -- Regards, Noel
