I set up my test plan locally to write the results tree data to a file,
copied it out to the remote box and invoked it using jmeter -n blah blah
blah. It does write the log file (I guess) but that log file doesnt show me
any information relating to cookies. Though when I run it locally and then
view results tree, it does.

Any thoughts?



Himanshu Ghai wrote:
> 
> I tried it here..if you have view results tree writing to a file and
> in any view results tree listener if you open that file(extension
> jtl)... it shows all the logged data in same form..
> if jmeter is run with -n option this is the only way I can think of..
> 
> Himanshu
> 
> 
> 
> On 8/26/08, gwatson <[EMAIL PROTECTED]> wrote:
>>
>>  Well, I have it in my test plan. I just dont know what options to start
>>  jmeter with in order to view the data written to the results tree.
>> Anyone
>>  know?
>>
>>
>>  Himanshu Ghai wrote:
>>  >
>>  > In my jmeter scripts that are launched using cron..I have given a
>> shared
>>  > location as the path for aggregate log...try it in your jmeter plan
>>  > itself..
>>  > to give a path for the view results tree jmx file...results tree could
>>  > be pretty resource intensive...use the configure option for view
>> results
>>  > tree to
>>  > minimize the logged data... may be request headers are sufficient...
>>  >
>>  > Thanks,
>>  > Himanshu
>>  >
>>  >
>>  > On 8/26/08, gwatson <[EMAIL PROTECTED]> wrote:
>>  >>
>>  >>  Hello, sorry if this is in the wrong place but I am new to this
>> forum.
>>  >>
>>  >>  Anywhoo, I am using jmeter from a remote server to test load
>> balancing
>>  >>  through a couple of new server iron GT's. I have the serverirons
>>  >> configured
>>  >>  to hand out cookies to cookie-able browsers in order to maintain
>> session
>>  >>  state. (our application is relies on session state)
>>  >>
>>  >>  I am using the following command to run a jmx test plan against said
>>  >> load
>>  >>  balancer: (from a wrapper script)
>>  >>
>>  >>  jmeter -n -DHost=$HOST -t $JMXDIR/$JMX -Dhttpclient.localaddress=$IP
>> -l
>>  >> $LOG
>>  >>
>>  >>  The tests appear to be working. However, I need to verify that I am
>>  >> getting
>>  >>  cookie'd appropriately. I dont see anything in the logfile that Im
>>  >> writing
>>  >>  to that lets me know what cookies Ive been issued. Locally Im able
>> to
>>  >> run a
>>  >>  jmx from jmeter gui and view the cookie information by adding a
>> "view
>>  >>  results tree" element to my thread group. Does anyone know how I
>> would
>>  >>  accomplish the same thing remotely? (Note that I have to run the
>> remote
>>  >>  tests through CLI)
>>  >>
>>  >>  TIA!
>>  >>
>>  >>
>>  >>  --
>>  >>  View this message in context:
>>  >>
>> http://www.nabble.com/remote-jmeter-logging-question-tp19167347p19167347.html
>>  >>  Sent from the JMeter - User mailing list archive at Nabble.com.
>>  >>
>>  >>
>>  >> 
>> ---------------------------------------------------------------------
>>  >>  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]
>>  >
>>  >
>>  >
>>
>>
>> --
>>  View this message in context:
>> http://www.nabble.com/remote-jmeter-logging-question-tp19167347p19167819.html
>>
>> Sent from the JMeter - User mailing list archive at Nabble.com.
>>
>>
>>  ---------------------------------------------------------------------
>>  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]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/remote-jmeter-logging-question-tp19167347p19181047.html
Sent from the JMeter - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to