No if you dont really care about cookies , then keep it the way it.
Currently each thread makes the same request and you dont really need to
bother about it. If you needed to change so that a thread makes multiple
requests and you need the cookie to be the same then you'd have to change
this to use a single thread group.

On Wed, Sep 16, 2009 at 10:27 PM, Jatin Davey <[email protected]> wrote:

> Thats a good question. I am not much aware of the cookies.
> But when i tried to sniff the HTTP headers while i access my Web App , All
> the requests were using the same cookie. Or should i say that they were
> sharing the same cookie.
>
> If this is the case is it fine to put the Cookie manager in each of the
> individual threads as you had mentioned.
>
>
> Thanks
> Jatin
>
> Deepak Shetty wrote:
>
>> It depends on what you want to do , 8 parallel requests will each have
>> their
>> own set of cookies , it depends on whether you need the same cookie
>> between
>> requests in the same thread . For the request set you posted in your first
>> mail , whats the cookie behavior you want..
>>
>> regards
>> deepak
>>
>> On Wed, Sep 16, 2009 at 10:19 PM, Jatin Davey <[email protected]> wrote:
>>
>>
>>
>>> So should i add the cookie managers into each Thread groups. That should
>>> work right??
>>>
>>>
>>> Thanks
>>> Jatin
>>>
>>> Deepak Shetty wrote:
>>>
>>>
>>>
>>>> Hi
>>>> I should just add that cookies wont be shared between threads.
>>>> regards
>>>> deepak
>>>>
>>>> On Wed, Sep 16, 2009 at 10:04 PM, Jatin Davey <[email protected]>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Many Thanks.
>>>>>
>>>>> I tired with different thread groups and it worked. I appreciate your
>>>>> help.
>>>>>
>>>>>
>>>>> Thanks
>>>>> Jatin
>>>>>
>>>>> Deepak Shetty wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> hi
>>>>>> Yes
>>>>>> Test Plan
>>>>>>  Cookie Manager
>>>>>>  Request Defaults
>>>>>>  Thread Group 1
>>>>>>  Thread Group 2
>>>>>>
>>>>>> regards
>>>>>> deepak
>>>>>>
>>>>>> On Wed, Sep 16, 2009 at 9:51 PM, Jatin Davey <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> I have the following three things:
>>>>>>>
>>>>>>> HTTP Cookie Manager
>>>>>>> HTTP Request Defaults
>>>>>>> HTTP Authorization Manager
>>>>>>>
>>>>>>> Is it possible to share these things across multiple thread groups as
>>>>>>> you
>>>>>>> have mentioned below?
>>>>>>>
>>>>>>> Thanks
>>>>>>> Jatin
>>>>>>>
>>>>>>>
>>>>>>> Deepak Shetty wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hi
>>>>>>>> Your simplest solution is to use different thread groups
>>>>>>>>
>>>>>>>> Thread Group (1 thread, Loop Forever)
>>>>>>>>  One HTTP Sampler
>>>>>>>>     Timer (Delay = 15 secs)
>>>>>>>> Thread Group (6 thread , loop forever)
>>>>>>>>  Interleave controller  (6 in parallel but only one at any one time)
>>>>>>>>     Six HTTP Samplers
>>>>>>>>     Test Action Sampler (Pause , Delay = 20 secs)
>>>>>>>>  Thread Group Controller (1thread ,Loop Forever)
>>>>>>>>  One HTTP Sampler
>>>>>>>>     Timer (Delay = 60 secs)
>>>>>>>>
>>>>>>>> In your test,the first loop controller never quits (you have said
>>>>>>>> forever)
>>>>>>>>
>>>>>>>> Im think you could achieve what you want with a single thread group
>>>>>>>> ,
>>>>>>>> but
>>>>>>>> Im
>>>>>>>> not sure the delays would work as you want ...
>>>>>>>> Thread Group 8 threads, forever
>>>>>>>>  Interleave
>>>>>>>>   Simple Controller
>>>>>>>>      Req 1
>>>>>>>>      Delay 1
>>>>>>>>   Interleave
>>>>>>>>      Simple Controller
>>>>>>>>           Req 2
>>>>>>>>           Req 3
>>>>>>>>           ...
>>>>>>>>           Req 7
>>>>>>>>           Delay 2
>>>>>>>>  Simple Controller
>>>>>>>>          Req 8
>>>>>>>>          Delay 8
>>>>>>>>
>>>>>>>> regards
>>>>>>>> deepak
>>>>>>>> On Wed, Sep 16, 2009 at 9:19 PM, Jatin Davey <[email protected]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> I have a requirement as below:
>>>>>>>>>
>>>>>>>>> 1. One HTTP Get Sampler to execute every 15 secs
>>>>>>>>> 2. Six HTTP Get Samplers to execute every 20 secs
>>>>>>>>> 3. One HTTP Get Samplers to execute every 60 secs
>>>>>>>>>
>>>>>>>>> I had the controllers organization as below in JMeter:
>>>>>>>>>
>>>>>>>>> Thread Group
>>>>>>>>>  Loop Controller (Loop Forever)
>>>>>>>>>  One HTTP Sampler
>>>>>>>>>     Timer (Delay = 15 secs)
>>>>>>>>>  Loop Controller (Loop Forever)
>>>>>>>>>  Six HTTP Samplers
>>>>>>>>>     Test Action Sampler (Pause , Delay = 20 secs)
>>>>>>>>>  Loop Controller (Loop Forever)
>>>>>>>>>  One HTTP Sampler
>>>>>>>>>     Timer (Delay = 60 secs)
>>>>>>>>>
>>>>>>>>> When i execute i see that only the first sampler gets executed and
>>>>>>>>> the
>>>>>>>>> others do not get executed. I want my requests such that there are
>>>>>>>>> 8
>>>>>>>>> requests going to my Web App , the rate of individual samplers
>>>>>>>>> being
>>>>>>>>> as
>>>>>>>>> per
>>>>>>>>> the requirment mentioned above.
>>>>>>>>>
>>>>>>>>> I tried many different combinations such as simple controller ,
>>>>>>>>> Random
>>>>>>>>> Controller and Throughput controller. Throughput controller was
>>>>>>>>> near
>>>>>>>>> to
>>>>>>>>> my
>>>>>>>>> solution but it loaded my Web App way too much.
>>>>>>>>>
>>>>>>>>> Can someone please help me on this.
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Jatin
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> [email protected]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: [email protected]
>>>>>>> For additional commands, e-mail: [email protected]
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to