[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jmeter-user
Subject:    Re: load balance through port number
From:       <13651877684 () 163 ! com>
Date:       2013-10-24 2:58:51
Message-ID: 78ec15a0.1958c.141e8667772.Coremail.13651877684 () 163 ! com
[Download RAW message or body]


you're right. At the same time, It's things about your test purpose.

At 2013-10-23 23:16:49,"Deepak Shetty" shettyd@gmail.com> wrote:
>>Anyway, we should be able to deal with such test situation.
>sure - but test out production like scenarios first .
>The reason I asked is because the way you would test out a case like a load
>balancer in front which distributes load to multiple servers (if you wanted
>to verify that load is being distributed) is not the same as if you would
>directly hit the servers. For e.g. if I am using http + weblogic the
>session cookie contains information about which server is being hit so you
>could from the test response determine how your load is being distributed.
>In other cases you have no way out of looking at the logs after your test
>has run to determine that the load did indeed get split up (or if you
>wanted to check that all the servers are up and running)
>
>>btw, there is a front in production environment, but no in test
>environment.
>generally considered bad practice.


[prev in list] [next in list] [prev in thread] [next in thread]