Error processing 204 No Content Response

[dai...@gmail.com]

Hi all,

I am having the following problem when receiving a 204 No Content Response:

Even when I have confirmed with another tool that the response was received, WebLOAD takes 30 seconds to recognize that the response was received (which alters much the response time I obtain for endpoints which sometimes respond with 204).

The response contains nothing else but the header 204 No Content. It seems like WebLOAD is stuck there trying to process a content which is just not there.

Any help will be appreciated.

Thanks and regards,

Daimiel

[Thirumoorthy Chettiannan]

Looks like bug. Talk to Radview. Back during my Webload days (7 years ago), there will be something called probing client to collect response time and webload console is used to collect other performance metrics such as HPS, Counter (everything in client side except response time). I'm not sure how it works now.

I stopped working in Webload like 7 years go. So I'm not sure how things are now.

Thiru

--
--
You received this message because you are subscribed to the Google
Groups "Performance Testing using Webload" group.
To post to this group, send email to
performance-test...@googlegroups.com
To unsubscribe from this group, send email to
performance-testing-us...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/performance-testing-using-webload?hl=en
---
You received this message because you are subscribed to the Google Groups "Performance Testing using Webload" group.
To unsubscribe from this group and stop receiving emails from it, send an email to performance-testing-us...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
அன்புடன்,
திருமூர்த்தி செட்டியண்ணன்.

பன்னிரெண்டாம் வகுப்பில் இர‌ண்டாவ‌து முறையாக‌ தவறியவுடன்
"என்னுடன் திருப்பூருக்கு வந்துவிடு" என்றார் பெரியப்பா
"நிலத்தை விற்று வெளிநாட்டுக்கு அனுப்பலாம்" என்றார் மாமா
"பக்கத்து நகரில் பெட்டிக்கடை வைத்துக்கொள்" என்றார் அப்பா

கடைசிவரை யாருமே சொல்லவில்லை விவசாயம் பார் என்று.

[dai...@gmail.com]

Hi Thiru,

I did get the same behavior when trying with a probing client.

I will post the solution if I find it.

Thanks!

Daimiel

El viernes, 22 de noviembre de 2013 11:14:41 UTC+1, ThirumoorthyC escribió:

Looks like bug. Talk to Radview. Back during my Webload days (7 years ago), there will be something called probing client to collect response time and webload console is used to collect other performance metrics such as HPS, Counter (everything in client side except response time). I'm not sure how it works now.

I stopped working in Webload like 7 years go. So I'm not sure how things are now.

Thiru

On Fri, Nov 22, 2013 at 3:37 PM, <dai...@gmail.com> wrote:

Hi all,

I am having the following problem when receiving a 204 No Content Response:

Even when I have confirmed with another tool that the response was received, WebLOAD takes 30 seconds to recognize that the response was received (which alters much the response time I obtain for endpoints which sometimes respond with 204).

The response contains nothing else but the header 204 No Content. It seems like WebLOAD is stuck there trying to process a content which is just not there.

Any help will be appreciated.

Thanks and regards,

Daimiel

--
--
You received this message because you are subscribed to the Google
Groups "Performance Testing using Webload" group.
To post to this group, send email to

performance-testing-using-web...@googlegroups.com

To unsubscribe from this group, send email to

performance-testing-using-webload+unsubscribe@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/performance-testing-using-webload?hl=en
---
You received this message because you are subscribed to the Google Groups "Performance Testing using Webload" group.

To unsubscribe from this group and stop receiving emails from it, send an email to performance-testing-using-webload+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

[dai...@gmail.com]

I have tested this with version 10.1 and it works fine.