Professional Web Applications Themes

Aborted clients - Got an error reading communication packets - MySQL

Hello, I get pages of error logs with this message - "Got an error reading communication packets". And the aborted clients are easily in hundreds. Here is my set of configurations: I am running Microsoft .Net 2.0 on Windows 2003 Server using IIS 6.0. I am using Mysql 5.0 with Mysql/.Net Connector 1.0. Some of the settings on my.ini - Connection timeout - 180 Wait timeout - 360 Max packet size - 10 M Max connections - 5000 (pretty high, but set to be on a safer side) When a perform a netstat -ao - I have lot many sockets ...

  1. #1

    Default Aborted clients - Got an error reading communication packets

    Hello,

    I get pages of error logs with this message -
    "Got an error reading communication packets". And the aborted clients
    are easily in hundreds.

    Here is my set of configurations:
    I am running Microsoft .Net 2.0 on Windows 2003 Server using IIS 6.0.
    I am using Mysql 5.0 with Mysql/.Net Connector 1.0.

    Some of the settings on my.ini -
    Connection timeout - 180
    Wait timeout - 360
    Max packet size - 10 M
    Max connections - 5000 (pretty high, but set to be on a safer side)

    When a perform a netstat -ao - I have lot many sockets open with
    TIME_WAIT status. On the MySql Command client - the Aborted clients
    average around 100's

    The connection string from ,Net application has pooling=false with no
    help.

    The webserver does not have a heavy load and has less than 5 users at
    any point in time.

    On the registry settings, I have the max ports > 60000 and the
    time_wait setting changed to 30.

    My application is opens a connection, performs a query and closes the
    connection and this is the fashion followed for all DB operations.

    Been hunting around for a solution and it has been driving me crazy.
    Any suggestions will be highly appreciated.

    Thanks,
    Narmatha

    narmathabala@gmail.com Guest

  2. #2

    Default Re: Aborted clients - Got an error reading communication packets

    == Quote from narmathabala ( com)'s article 


    increase your packet size
    --
    POST BY: lark with PHP News Reader
    lark Guest

  3. #3

    Default Re: Aborted clients - Got an error reading communication packets

    On Jun 26, 12:46 pm, lark <net> wrote: 
    >
    > increase your packet size
    > --
    > POST BY: lark with PHP News Reader[/ref]

    Bigger than 10 M?

    Thanks,
    Narmatha

    narmathabala@gmail.com Guest

  4. #4

    Default Re: Aborted clients - Got an error reading communication packets

    com wrote: 

    Ouch, not sure if even microsoft would run that combination, they seem to like
    BSD servers.
     

    Is the mysql on the same machine as the web server? if not, maybe you have
    trouble with firewalls, try to allow unblocked traffic between the machines.




    --

    //Aho
    J.O. Guest

  5. #5

    Default Re: Aborted clients - Got an error reading communication packets

    == Quote from narmathabala ( com)'s article 
    > >
    > > increase your packet size
    > > --
    > > POST BY: lark with PHP News Reader[/ref]
    > Bigger than 10 M?
    > Thanks,
    > Narmatha[/ref]


    apparently so. also look at the client packet size because that is also
    controllable. all of your clients must be configured to use the same packet size
    and this packets size has to be less than the packet size allowed by the server.
    increase your packet size to 32 or 64 M.
    --
    POST BY: lark with PHP News Reader
    lark Guest

  6. #6

    Default Re: Aborted clients - Got an error reading communication packets

    com wrote: 

    You get that message in the log every time the server closes a client
    connection because it was inactive too long. Too long is "longer than
    wait_timeout".
     

    This is 6 minutes. Each client connection that stays idle will be
    forcibly closed by the MySQL server after 6 minutes.
    What was your reason to decrease wait_timeout from the 8 hour default?
     

    This safety is expensive. You risk running out of memory instead.
    On Windoze you may run out of TCP handles even before...
     

    Obviously the connections were *not* closed.


    XL
    --
    Axel Schwenke, Support Engineer, MySQL AB

    Online User Manual: http://dev.mysql.com/doc/refman/5.0/en/
    MySQL User Forums: http://forums.mysql.com/
    Axel Guest

Similar Threads

  1. IO Error on Server Communication
    By DaPurpleDude in forum Coldfusion Database Access
    Replies: 6
    Last Post: March 16th, 07:51 PM
  2. Clients registry error ?
    By e.esquivel in forum Coldfusion Server Administration
    Replies: 2
    Last Post: May 2nd, 01:09 PM
  3. Error: Thread was aborted from WaitForSingleObject
    By Rachit Agarwal via DotNetMonster.com in forum ASP.NET Web Services
    Replies: 0
    Last Post: March 31st, 12:36 PM
  4. #13146 [Com]: installer aborted ,error message corupt I/O file
    By totakoka1 at hotmail dot com in forum PHP Development
    Replies: 1
    Last Post: October 18th, 10:57 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139