You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Andy Dawson <an...@iti.upv.es> on 2006/07/04 11:17:04 UTC

Monitor Results - Thread Count

Hi All,

I´m experimenting with JMeter 2.2, Java 1.5, running on Windows XP 
testing against a Tomcat server running NT.

I´ve set up a results monitor, but irrespective of the actual number of 
threads used, the thread % reports 0 (memory and load show variation, 
health is always 100% right up until I crash the sever and it stops 
responding..). Browsing "/manager/status?XML=true" manually I can see 
that the active thread count is not 0 and varies. I´ve done a quick 
search but can´t find a reason for this - anybody got any tips?

Cheers,

Andy Dawson
PS. Does anybody use the irc channel..?

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org


Re: Monitor Results - Thread Count

Posted by Andy Dawson <an...@iti.upv.es>.
Hi Peter,

Thanks again for the reply.

The application, and therefore the thread count that is relavent, is on 
port 8100.

In the previous example, there were 8 busy threads at the time  (5% 
busy/max) which is shown in the xml. Even with > 50% of the threads 
active, it still shows 0%. How is the thread count determined?

I do hope there is something parameterizable to allow the busy thread % 
to be correctly determined.

Thanks & Regards,

Andy Dawson

Peter Lin wrote:
> looking at the response from tomcat, I see the following
>
> <connect or name='http-8084'><threadInfo  maxThreads="150"
> minSpareThreads="25" maxSpareThreads="75" currentThreadCount="25"
> currentThreadsBusy="1" />
>
> current busy thread is 1, the current thread count is 25 and max is the
> default 150
>
> so that means busy/max is less than 1%, which gets rounded to 0%.
>
> what I generally do is hit tomcat with 20-50 threads and monitor the
> performance using the monitor results.
>
> hope that helps
>
> peter
>
>
> On 7/10/06, Andy Dawson <an...@iti.upv.es> wrote:
>>
>> Peter Lin wrote:
>> > can you post a sample of what your tomcat is returning?  you should be
>> > able
>> > to just copy paste the response from view result tree.
>> >
>> > peter
>> >
>> >
>> > On 7/10/06, Andy Dawson <an...@iti.upv.es> wrote:
>> >>
>> >> Peter Lin escribió:
>> >> > make sure you setup an account to view the tomcat's status servlet
>> and
>> >> > add
>> >> > an Auth manager to the test plan. You can see if the request is
>> >> > successful
>> >> > by adding a View Result Tree
>> >> >
>> >> > peter
>> >> >
>> >> > On 7/4/06, Andy Dawson <an...@iti.upv.es> wrote:
>> >> >>
>> >> >> Hi All,
>> >> >>
>> >> >> I´m experimenting with JMeter 2.2, Java 1.5, running on Windows XP
>> >> >> testing against a Tomcat server running NT.
>> >> >>
>> >> >> I´ve set up a results monitor, but irrespective of the actual
>> >> number of
>> >> >> threads used, the thread % reports 0 (memory and load show
>> variation,
>> >> >> health is always 100% right up until I crash the sever and it 
>> stops
>> >> >> responding..). Browsing "/manager/status?XML=true" manually I can
>> see
>> >> >> that the active thread count is not 0 and varies. I´ve done a 
>> quick
>> >> >> search but can´t find a reason for this - anybody got any tips?
>> >> >>
>> >> >> Cheers,
>> >> >>
>> >> >> Andy Dawson
>> >> >> PS. Does anybody use the irc channel..?
>> >> >>
>> >> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> >> >> For additional commands, e-mail: 
>> jmeter-user-help@jakarta.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> Hi Peter,
>> >>
>> >> Many  thanks for the reply.
>> >>
>> >> The auth manager is present and the results monitor is able to access
>> >> the manager url. A graphic is generated showing a none-dead server
>> >> status with memory and load fluctuations in line with what I would
>> >> expect - the only query is regarding the tread count which always
>> >> indicates 0.
>> >>
>> >> Perhaps the threads for one of the other open ports is being captured
>> >> (guess). How is the thread count used in the results monitor
>> determined?
>> >>
>> >> Cheers,
>> >>
>> >> Andy Dawson
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >>
>> >>
>> >
>> Hi Peter,
>>
>> Below is what tomcat is returning, the application, is running on port
>> 8100. In this example the server was running with approx 75% memory
>> usage and 40% load. Although the number of theads is low compared to the
>> max defined (not my configuration) it isn't 0 percent and makes no
>> difference if I ramp up to 100 threads.
>>
>> Anything that can be changed to see the thread count?
>>
>> Regards,
>>
>> Andy Dawson
>>
>> I hope the below isn't corrupted.
>>
>> <?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl"
>> href="/manager/xform.xsl" ?><status><jvm><memory free='7357544'
>> total='37093376' max='66650112'/></jvm><connector
>> name='http-8084'><threadInfo  maxThreads="150" minSpareThreads="25"
>> maxSpareThreads="75" currentThreadCount="25" currentThreadsBusy="1"
>> /><requestInfo  maxTime="0" processingTime="0" requestCount="0"
>> errorCount="0" bytesReceived="0" bytesSent="0" /><workers><worker  
>> stage="R"
>> requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0"
>> remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;"
>> currentQueryString="&#63;" protocol="&#63;"
>> /></workers></connector><connector
>> name='http-8100'><threadInfo  maxThreads="150" minSpareThreads="25"
>> maxSpareThreads="75" currentThreadCount="25" currentThreadsBusy="8"
>> /><requestInfo  maxTime="4813" processingTime="255614" 
>> requestCount="2569"
>> errorCount="1" bytesReceived="559008" bytesSent="40935221"
>> /><workers><worker  stage="K" requestProcessingTime="3406"
>> requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124"
>> virtualHost="?" method="&#63;" currentUri="&#63;" 
>> currentQueryString="&#63;"
>> protocol="&#63;" /><worker  stage="K" requestProcessingTime="2843"
>> requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124"
>> virtualHost="?" method="&#63;" currentUri="&#63;" 
>> currentQueryString="&#63;"
>> protocol="&#63;" /><worker  stage="R" requestProcessingTime="0"
>> requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;"
>> virtualHost="&#63;" method="&#63;" currentUri="&#63;"
>> currentQueryString="&#63;" protocol="&#63;" /><worker  stage="S"
>> requestProcessingTime="0" requestBytesSent="0" requestBytesReceived="0"
>> remoteAddr="192.168.1.124" virtualHost="mistral" method="GET"
>> currentUri="/manager/status" currentQueryString="XML=true"
>> protocol="HTTP/1.1" /><worker  stage="K" requestProcessingTime="2796"
>> requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124"
>> virtualHost="?" method="&#63;" currentUri="&#63;" 
>> currentQueryString="&#63;"
>> protocol="&#63;" /><worker  stage="R" requestProcessingTime="0"
>> requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;"
>> virtualHost="&#63;" method="&#63;" currentUri="&#63;"
>> currentQueryString="&#63;" protocol="&#63;" /><worker  stage="K"
>> requestProcessingTime="968" requestBytesSent="0" 
>> requestBytesReceived="0"
>> remoteAddr="192.168.1.124" virtualHost="?" method="&#63;"
>> currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;"
>> /><worker  stage="R" requestProcessingTime="0" requestBytesSent="0"
>> requestBytesRecieved="0" remoteAddr="&#63;" virtualHost="&#63;"
>> method="&#63;" currentUri="&#63;" currentQueryString="&#63;"
>> protocol="&#63;" /><worker  stage="R" requestProcessingTime="0"
>> requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;"
>> virtualHost="&#63;" method="&#63;" currentUri="&#63;"
>> currentQueryString="&#63;" protocol="&#63;" /><worker  stage="R"
>> requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0"
>> remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;"
>> currentQueryString="&#63;" protocol="&#63;" /><worker  stage="R"
>> requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0"
>> remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;"
>> currentQueryString="&#63;" protocol="&#63;" /><worker  stage="K"
>> requestProcessingTime="3031" requestBytesSent="0" 
>> requestBytesReceived="0"
>> remoteAddr="192.168.1.124" virtualHost="?" method="&#63;"
>> currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;"
>> /><worker  stage="K" requestProcessingTime="609" requestBytesSent="0"
>> requestBytesReceived="0" remoteAddr="192.168.1.124" virtualHost="?"
>> method="&#63;" currentUri="&#63;" currentQueryString="&#63;"
>> protocol="&#63;" /></workers></connector><connector
>> name='http-4443'><threadInfo  maxThreads="150" minSpareThreads="25"
>> maxSpareThreads="75" currentThreadCount="25" currentThreadsBusy="1"
>> /><requestInfo  maxTime="0" processingTime="0" requestCount="0"
>> errorCount="0" bytesReceived="0" bytesSent="0" /><workers><worker  
>> stage="R"
>> requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0"
>> remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;"
>> currentQueryString="&#63;" protocol="&#63;"
>> /></workers></connector><connector
>> name='jk-8009'><threadInfo  maxThreads="200" minSpareThreads="4"
>> maxSpareThreads="50" currentThreadCount="4" currentThreadsBusy="1"
>> /><requestInfo  maxTime="0" processingTime="0" requestCount="0"
>> errorCount="0" bytesReceived="0" bytesSent="0"
>> /><workers></workers></connector></status>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org


Re: Monitor Results - Thread Count

Posted by Peter Lin <wo...@gmail.com>.
looking at the response from tomcat, I see the following

<connect or name='http-8084'><threadInfo  maxThreads="150"
minSpareThreads="25" maxSpareThreads="75" currentThreadCount="25"
currentThreadsBusy="1" />

current busy thread is 1, the current thread count is 25 and max is the
default 150

so that means busy/max is less than 1%, which gets rounded to 0%.

what I generally do is hit tomcat with 20-50 threads and monitor the
performance using the monitor results.

hope that helps

peter


On 7/10/06, Andy Dawson <an...@iti.upv.es> wrote:
>
> Peter Lin wrote:
> > can you post a sample of what your tomcat is returning?  you should be
> > able
> > to just copy paste the response from view result tree.
> >
> > peter
> >
> >
> > On 7/10/06, Andy Dawson <an...@iti.upv.es> wrote:
> >>
> >> Peter Lin escribió:
> >> > make sure you setup an account to view the tomcat's status servlet
> and
> >> > add
> >> > an Auth manager to the test plan. You can see if the request is
> >> > successful
> >> > by adding a View Result Tree
> >> >
> >> > peter
> >> >
> >> > On 7/4/06, Andy Dawson <an...@iti.upv.es> wrote:
> >> >>
> >> >> Hi All,
> >> >>
> >> >> I´m experimenting with JMeter 2.2, Java 1.5, running on Windows XP
> >> >> testing against a Tomcat server running NT.
> >> >>
> >> >> I´ve set up a results monitor, but irrespective of the actual
> >> number of
> >> >> threads used, the thread % reports 0 (memory and load show
> variation,
> >> >> health is always 100% right up until I crash the sever and it stops
> >> >> responding..). Browsing "/manager/status?XML=true" manually I can
> see
> >> >> that the active thread count is not 0 and varies. I´ve done a quick
> >> >> search but can´t find a reason for this - anybody got any tips?
> >> >>
> >> >> Cheers,
> >> >>
> >> >> Andy Dawson
> >> >> PS. Does anybody use the irc channel..?
> >> >>
> >> >>
> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >> >>
> >> >>
> >> >
> >> Hi Peter,
> >>
> >> Many  thanks for the reply.
> >>
> >> The auth manager is present and the results monitor is able to access
> >> the manager url. A graphic is generated showing a none-dead server
> >> status with memory and load fluctuations in line with what I would
> >> expect - the only query is regarding the tread count which always
> >> indicates 0.
> >>
> >> Perhaps the threads for one of the other open ports is being captured
> >> (guess). How is the thread count used in the results monitor
> determined?
> >>
> >> Cheers,
> >>
> >> Andy Dawson
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
> Hi Peter,
>
> Below is what tomcat is returning, the application, is running on port
> 8100. In this example the server was running with approx 75% memory
> usage and 40% load. Although the number of theads is low compared to the
> max defined (not my configuration) it isn't 0 percent and makes no
> difference if I ramp up to 100 threads.
>
> Anything that can be changed to see the thread count?
>
> Regards,
>
> Andy Dawson
>
> I hope the below isn't corrupted.
>
> <?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl"
> href="/manager/xform.xsl" ?><status><jvm><memory free='7357544'
> total='37093376' max='66650112'/></jvm><connector
> name='http-8084'><threadInfo  maxThreads="150" minSpareThreads="25"
> maxSpareThreads="75" currentThreadCount="25" currentThreadsBusy="1"
> /><requestInfo  maxTime="0" processingTime="0" requestCount="0"
> errorCount="0" bytesReceived="0" bytesSent="0" /><workers><worker  stage="R"
> requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0"
> remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;"
> currentQueryString="&#63;" protocol="&#63;"
> /></workers></connector><connector
> name='http-8100'><threadInfo  maxThreads="150" minSpareThreads="25"
> maxSpareThreads="75" currentThreadCount="25" currentThreadsBusy="8"
> /><requestInfo  maxTime="4813" processingTime="255614" requestCount="2569"
> errorCount="1" bytesReceived="559008" bytesSent="40935221"
> /><workers><worker  stage="K" requestProcessingTime="3406"
> requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124"
> virtualHost="?" method="&#63;" currentUri="&#63;" currentQueryString="&#63;"
> protocol="&#63;" /><worker  stage="K" requestProcessingTime="2843"
> requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124"
> virtualHost="?" method="&#63;" currentUri="&#63;" currentQueryString="&#63;"
> protocol="&#63;" /><worker  stage="R" requestProcessingTime="0"
> requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;"
> virtualHost="&#63;" method="&#63;" currentUri="&#63;"
> currentQueryString="&#63;" protocol="&#63;" /><worker  stage="S"
> requestProcessingTime="0" requestBytesSent="0" requestBytesReceived="0"
> remoteAddr="192.168.1.124" virtualHost="mistral" method="GET"
> currentUri="/manager/status" currentQueryString="XML=true"
> protocol="HTTP/1.1" /><worker  stage="K" requestProcessingTime="2796"
> requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124"
> virtualHost="?" method="&#63;" currentUri="&#63;" currentQueryString="&#63;"
> protocol="&#63;" /><worker  stage="R" requestProcessingTime="0"
> requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;"
> virtualHost="&#63;" method="&#63;" currentUri="&#63;"
> currentQueryString="&#63;" protocol="&#63;" /><worker  stage="K"
> requestProcessingTime="968" requestBytesSent="0" requestBytesReceived="0"
> remoteAddr="192.168.1.124" virtualHost="?" method="&#63;"
> currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;"
> /><worker  stage="R" requestProcessingTime="0" requestBytesSent="0"
> requestBytesRecieved="0" remoteAddr="&#63;" virtualHost="&#63;"
> method="&#63;" currentUri="&#63;" currentQueryString="&#63;"
> protocol="&#63;" /><worker  stage="R" requestProcessingTime="0"
> requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;"
> virtualHost="&#63;" method="&#63;" currentUri="&#63;"
> currentQueryString="&#63;" protocol="&#63;" /><worker  stage="R"
> requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0"
> remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;"
> currentQueryString="&#63;" protocol="&#63;" /><worker  stage="R"
> requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0"
> remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;"
> currentQueryString="&#63;" protocol="&#63;" /><worker  stage="K"
> requestProcessingTime="3031" requestBytesSent="0" requestBytesReceived="0"
> remoteAddr="192.168.1.124" virtualHost="?" method="&#63;"
> currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;"
> /><worker  stage="K" requestProcessingTime="609" requestBytesSent="0"
> requestBytesReceived="0" remoteAddr="192.168.1.124" virtualHost="?"
> method="&#63;" currentUri="&#63;" currentQueryString="&#63;"
> protocol="&#63;" /></workers></connector><connector
> name='http-4443'><threadInfo  maxThreads="150" minSpareThreads="25"
> maxSpareThreads="75" currentThreadCount="25" currentThreadsBusy="1"
> /><requestInfo  maxTime="0" processingTime="0" requestCount="0"
> errorCount="0" bytesReceived="0" bytesSent="0" /><workers><worker  stage="R"
> requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0"
> remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;"
> currentQueryString="&#63;" protocol="&#63;"
> /></workers></connector><connector
> name='jk-8009'><threadInfo  maxThreads="200" minSpareThreads="4"
> maxSpareThreads="50" currentThreadCount="4" currentThreadsBusy="1"
> /><requestInfo  maxTime="0" processingTime="0" requestCount="0"
> errorCount="0" bytesReceived="0" bytesSent="0"
> /><workers></workers></connector></status>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

Re: Monitor Results - Thread Count

Posted by Andy Dawson <an...@iti.upv.es>.
Peter Lin wrote:
> can you post a sample of what your tomcat is returning?  you should be 
> able
> to just copy paste the response from view result tree.
>
> peter
>
>
> On 7/10/06, Andy Dawson <an...@iti.upv.es> wrote:
>>
>> Peter Lin escribió:
>> > make sure you setup an account to view the tomcat's status servlet and
>> > add
>> > an Auth manager to the test plan. You can see if the request is
>> > successful
>> > by adding a View Result Tree
>> >
>> > peter
>> >
>> > On 7/4/06, Andy Dawson <an...@iti.upv.es> wrote:
>> >>
>> >> Hi All,
>> >>
>> >> I´m experimenting with JMeter 2.2, Java 1.5, running on Windows XP
>> >> testing against a Tomcat server running NT.
>> >>
>> >> I´ve set up a results monitor, but irrespective of the actual 
>> number of
>> >> threads used, the thread % reports 0 (memory and load show variation,
>> >> health is always 100% right up until I crash the sever and it stops
>> >> responding..). Browsing "/manager/status?XML=true" manually I can see
>> >> that the active thread count is not 0 and varies. I´ve done a quick
>> >> search but can´t find a reason for this - anybody got any tips?
>> >>
>> >> Cheers,
>> >>
>> >> Andy Dawson
>> >> PS. Does anybody use the irc channel..?
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>> >>
>> >>
>> >
>> Hi Peter,
>>
>> Many  thanks for the reply.
>>
>> The auth manager is present and the results monitor is able to access
>> the manager url. A graphic is generated showing a none-dead server
>> status with memory and load fluctuations in line with what I would
>> expect - the only query is regarding the tread count which always
>> indicates 0.
>>
>> Perhaps the threads for one of the other open ports is being captured
>> (guess). How is the thread count used in the results monitor determined?
>>
>> Cheers,
>>
>> Andy Dawson
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
Hi Peter,

Below is what tomcat is returning, the application, is running on port 
8100. In this example the server was running with approx 75% memory 
usage and 40% load. Although the number of theads is low compared to the 
max defined (not my configuration) it isn't 0 percent and makes no 
difference if I ramp up to 100 threads.

Anything that can be changed to see the thread count?

Regards,

Andy Dawson

I hope the below isn't corrupted.

<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="/manager/xform.xsl" ?><status><jvm><memory free='7357544' total='37093376' max='66650112'/></jvm><connector name='http-8084'><threadInfo  maxThreads="150" minSpareThreads="25" maxSpareThreads="75" currentThreadCount="25" currentThreadsBusy="1" /><requestInfo  maxTime="0" processingTime="0" requestCount="0" errorCount="0" bytesReceived="0" bytesSent="0" /><workers><worker  stage="R" requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /></workers></connector><connector name='http-8100'><threadInfo  maxThreads="150" minSpareThreads="25" maxSpareThreads="75" currentThreadCount="25" currentThreadsBusy="8" /><requestInfo  maxTime="4813" processingTime="255614" requestCount="2569" errorCount="1" bytesReceived="559008" bytesSent="40935221" /><workers><worker  stage="K" requestProcessingTime="3406" requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124" virtualHost="?" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="K" requestProcessingTime="2843" requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124" virtualHost="?" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="R" requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="S" requestProcessingTime="0" requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124" virtualHost="mistral" method="GET" currentUri="/manager/status" currentQueryString="XML=true" protocol="HTTP/1.1" /><worker  stage="K" requestProcessingTime="2796" requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124" virtualHost="?" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="R" requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="K" requestProcessingTime="968" requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124" virtualHost="?" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="R" requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="R" requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="R" requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="R" requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="K" requestProcessingTime="3031" requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124" virtualHost="?" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /><worker  stage="K" requestProcessingTime="609" requestBytesSent="0" requestBytesReceived="0" remoteAddr="192.168.1.124" virtualHost="?" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /></workers></connector><connector name='http-4443'><threadInfo  maxThreads="150" minSpareThreads="25" maxSpareThreads="75" currentThreadCount="25" currentThreadsBusy="1" /><requestInfo  maxTime="0" processingTime="0" requestCount="0" errorCount="0" bytesReceived="0" bytesSent="0" /><workers><worker  stage="R" requestProcessingTime="0" requestBytesSent="0" requestBytesRecieved="0" remoteAddr="&#63;" virtualHost="&#63;" method="&#63;" currentUri="&#63;" currentQueryString="&#63;" protocol="&#63;" /></workers></connector><connector name='jk-8009'><threadInfo  maxThreads="200" minSpareThreads="4" maxSpareThreads="50" currentThreadCount="4" currentThreadsBusy="1" /><requestInfo  maxTime="0" processingTime="0" requestCount="0" errorCount="0" bytesReceived="0" bytesSent="0" /><workers></workers></connector></status>




---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org


Re: Monitor Results - Thread Count

Posted by Peter Lin <wo...@gmail.com>.
can you post a sample of what your tomcat is returning?  you should be able
to just copy paste the response from view result tree.

peter


On 7/10/06, Andy Dawson <an...@iti.upv.es> wrote:
>
> Peter Lin escribió:
> > make sure you setup an account to view the tomcat's status servlet and
> > add
> > an Auth manager to the test plan. You can see if the request is
> > successful
> > by adding a View Result Tree
> >
> > peter
> >
> > On 7/4/06, Andy Dawson <an...@iti.upv.es> wrote:
> >>
> >> Hi All,
> >>
> >> I´m experimenting with JMeter 2.2, Java 1.5, running on Windows XP
> >> testing against a Tomcat server running NT.
> >>
> >> I´ve set up a results monitor, but irrespective of the actual number of
> >> threads used, the thread % reports 0 (memory and load show variation,
> >> health is always 100% right up until I crash the sever and it stops
> >> responding..). Browsing "/manager/status?XML=true" manually I can see
> >> that the active thread count is not 0 and varies. I´ve done a quick
> >> search but can´t find a reason for this - anybody got any tips?
> >>
> >> Cheers,
> >>
> >> Andy Dawson
> >> PS. Does anybody use the irc channel..?
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >>
> >>
> >
> Hi Peter,
>
> Many  thanks for the reply.
>
> The auth manager is present and the results monitor is able to access
> the manager url. A graphic is generated showing a none-dead server
> status with memory and load fluctuations in line with what I would
> expect - the only query is regarding the tread count which always
> indicates 0.
>
> Perhaps the threads for one of the other open ports is being captured
> (guess). How is the thread count used in the results monitor determined?
>
> Cheers,
>
> Andy Dawson
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>

Re: Monitor Results - Thread Count

Posted by Andy Dawson <an...@iti.upv.es>.
Peter Lin escribió:
> make sure you setup an account to view the tomcat's status servlet and 
> add
> an Auth manager to the test plan. You can see if the request is 
> successful
> by adding a View Result Tree
>
> peter
>
> On 7/4/06, Andy Dawson <an...@iti.upv.es> wrote:
>>
>> Hi All,
>>
>> I´m experimenting with JMeter 2.2, Java 1.5, running on Windows XP
>> testing against a Tomcat server running NT.
>>
>> I´ve set up a results monitor, but irrespective of the actual number of
>> threads used, the thread % reports 0 (memory and load show variation,
>> health is always 100% right up until I crash the sever and it stops
>> responding..). Browsing "/manager/status?XML=true" manually I can see
>> that the active thread count is not 0 and varies. I´ve done a quick
>> search but can´t find a reason for this - anybody got any tips?
>>
>> Cheers,
>>
>> Andy Dawson
>> PS. Does anybody use the irc channel..?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>>
>>
>
Hi Peter,

Many  thanks for the reply.

The auth manager is present and the results monitor is able to access 
the manager url. A graphic is generated showing a none-dead server 
status with memory and load fluctuations in line with what I would 
expect - the only query is regarding the tread count which always 
indicates 0.

Perhaps the threads for one of the other open ports is being captured 
(guess). How is the thread count used in the results monitor determined?

Cheers,

Andy Dawson

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org


Re: Monitor Results - Thread Count

Posted by Peter Lin <wo...@gmail.com>.
make sure you setup an account to view the tomcat's status servlet and add
an Auth manager to the test plan. You can see if the request is successful
by adding a View Result Tree

peter

On 7/4/06, Andy Dawson <an...@iti.upv.es> wrote:
>
> Hi All,
>
> I´m experimenting with JMeter 2.2, Java 1.5, running on Windows XP
> testing against a Tomcat server running NT.
>
> I´ve set up a results monitor, but irrespective of the actual number of
> threads used, the thread % reports 0 (memory and load show variation,
> health is always 100% right up until I crash the sever and it stops
> responding..). Browsing "/manager/status?XML=true" manually I can see
> that the active thread count is not 0 and varies. I´ve done a quick
> search but can´t find a reason for this - anybody got any tips?
>
> Cheers,
>
> Andy Dawson
> PS. Does anybody use the irc channel..?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>