SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 3 of 3
  1. #1
    Member
    Join Date
    Mar 2000
    Location
    Los Angeles CA USA
    Posts
    41
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Winsock errors when testing a Win2K server

    Has anyone else experienced Winsock error messages when running a load test against a Windows 2000/IIS5 server?

    I get various errors (connection timed out, socket already closed, socket in error state, invalid protocol) when testing a server with high users (200) at a high line speed (384K or greater).

    If I run the same tests against a NT4/IIS4 server, I don't get a Winsock error at all.

    I'm running Silk Performer 3.5.1 on NT4.

    I've opened a ticket with Segue, but they're as mystified as I am about these errors.

  2. #2
    Moderator AJ's Avatar
    Join Date
    Jun 1999
    Location
    San Jose, CA
    Posts
    1,691
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winsock errors when testing a Win2K server

    Correct me if I'm wrong, but you're running a test on IIS5/W2K from a performer 3.5.1 controller installed on NT4 right?

    So if there is a problem, wouldn't it be IIS5 on Y2K installed? Did you try to re-record the scripts from the IIS5 system? Maybe they add additional server responces to parse? Also, Make sure your Win2K server can support that many connections. (After all NT servers do come with a license) which has a limit to the amount of users that can access it (including Web users)



    ------------------
    AJ Alhait
    BetaSoft Inc.
    AJ Alhait
    BetaSoft Inc.

  3. #3
    Member
    Join Date
    Mar 2000
    Location
    Los Angeles CA USA
    Posts
    41
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Winsock errors when testing a Win2K server

    Yes, I'm running Performer on NT4 systems against W2K/IIS5 servers.

    It's not a client licensing issue.

    From what I have read it appears that Performer does some manipulation of the TCP/IP stack on the agents (for client IP address simulation and recording TCP/IP level scripts) so that's why I considered Performer as a suspect.

    I do consider Windows 2000 as the most likely suspect, but I can't really confirm this at this time. I am still considering that it might be our hardware, but I think that's very unlikely.

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 12.50%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 01:55 AM.

Copyright BetaSoft Inc.