From: Ronnie J. <ra...@us...> - 2007-04-27 21:13:27
|
Olivier, I am using seagull version 1.5.0, and this is where I found the issue. The reason for setting the global parameter to "yes" was due to the conf.client.xml file having the global parameter set to "no" by default. When it was set to "no", I saw the call-rate decrease during test runs. Once I discovered setting the global parameter to "yes" fixed the decrease in call-rate, I assume this setting fixed that issue but I was not aware that I was only using one socket. Now that I'm aware that seagull opens one socket based on my reported configuration, I reviewed by application server setting to find that there is a parameter that closes the socket after 100 requests. So I think this is the actual reason for why I can't get pass 100 number-calls. Since I'm fairly new to using seagull, and you mentioned below that I'm using only one socket for all my requests when I use global = "yes", so how do I configure seagull where I can open multiple sockets? Also, if a socket closes on the server side, can the seagull be configured to open a new socket? Thanks for all your help, Ronnie "Boulkroune, Olivier (Non-HP:Atos Origin)" <oli...@hp...> Sent by: gul...@li... 04/26/2007 09:35 AM To <gul...@li...> cc Subject Re: [Seagull-users] XCAP GET: Can not exceed 100 number-calls Hello Ronnie, Which Seagull version are you using ? If not already done, may I ask you to retry with the latest version (1.5.0) and let us know if the problem still remains? I noticed that you set the global parameter of the channel configuration to 'yes', which meant you use one socket for all the calls (and is actually the default parameter), but opened one socket for each call in your scenario. There was a bug on the <open> action which impacted the call number computing, which has been fixed in the latest version. Regards, Olivier Boulkroune ---------------------------------------------------------------------- Message: 1 Date: Mon, 23 Apr 2007 06:50:09 -0600 From: Ronnie Jones <ra...@us...> Subject: [Seagull-users] XCAP GET: Can not exceed 100 number-calls To: gul...@li... Message-ID: <OF3...@us...> Content-Type: text/plain; charset="us-ascii" I need help to understand why XCAP GET calls driven by the seagull client stops every time at 100 calls. In my conf.client.xml file I have the number-calls set to 200 but the test stops at 100 every time. If I set number-calls to 20, the test stops at 20 as expected. I have another test that does XCAP PUT/DELETE calls. When I execute this test with numberr-calls set at 200 or above, I get the expected number of calls executed. It seems that it is only on the XCAP GET calls that I see a problem where seagull stops unexpectedly at 100 when the number-calls is set higher than 100. Here are my test files: I'm hoping this is a configuration issue that is easy to fix. Thanks, Ronnie -------------- next part -------------- An HTML attachment was scrubbed... -------------- next part -------------- A non-text attachment was scrubbed... Name: client_cdl.xml Type: application/octet-stream Size: 2343 bytes Desc: not available -------------- next part -------------- A non-text attachment was scrubbed... Name: conf.client.xml Type: application/octet-stream Size: 3351 bytes Desc: not available ------------------------------ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Gull-users mailing list Gul...@li... https://lists.sourceforge.net/lists/listinfo/gull-users |