On 06/10/05, Bruno CHARLOUP <[EMAIL PROTECTED]> wrote: > Hi all, > I have some problems when playing a script with JMeter (2.1 or 2.1.1) : > > > The 1st one is about cookie management : > ================================ > First, I've recorded a scenario with a HTTP Cookie manager associated to my > test plan. > > When JMeter plays afterward the script, sometimes the cookie JSessionID > stays unchanged during all the script, and then my scenario is OK (normal), > but other time, the JSessionID is changed within the same scenario and my > scenario fails because the session seems to be not created (I play my test > plan with only 1 thread). > I saw the JSessionID value by using the tab "request" in a listener "View > results tree". > > Does anybody kwows or has already met this problem. > Do you know if the position of the HTTP Cookie manager has an influence on > its way of working (child of the test plan or child of the thread group > item) ?
It will only be used if it is in scope. > The 2nd one is about internal "browser" of JMeter : > ====================================== > do you know if its engine has a cache mechanism ? when I saw page result in > a view result tree, even if the JSessionID is OK, the content of the page is > not always correct, it seems that not all data are reloaded ... that is the > reason why I ask my question about cache mechanism ... > There is no caching by JMeter code - the listeners display the data retrieved by the sampler. However, if the retrieved data contains images etc, these will be loaded by the Listener *whenever the data is displayed as HTML*. This is done internally by the Java library code. I don't know if these items are cached. Deselect "Download embedded resources" and JMeter will try to stop these further downloads from occurring during HTML display. Show text will never download embedded resources. S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
