Hi
There, I am using JMeter for performance testing my DWR app. The way it is
done in the current implementation is that JMeter picks up the script session
key from engine.js using regular expression based pattern matching to
propagate it in further calls made to other URLs on the test plan. In DWR3 I
understand that engine.js is now a static asset which works well for taking
advantage of browser caching but, it has broken assumptions made on JMeter for
us. Has anyone encountered this!? Does anyone have a solution for this!?
Thanks in advance. Regards, Phani