none
TCP buffer size in WEC7 RRS feed

  • Question

  • Hi,

    Is it possible to increase the TCP buffer size to more than 128KB. I checked the possible registry configuration but couldn't find.

    Thank you.

    Regards,


    Seeth

    Monday, October 17, 2016 12:26 PM

All replies

  • Hi Seeth,

    Can you please give far more detail on how you are configuring the size?  For example, are you hitting something like this windowing issue in Compact 2013? https://support.microsoft.com/en-us/kb/3082654

    Sincerely,

    IoTGirl

    Monday, October 17, 2016 4:36 PM
    Moderator
  • Hi,

    I'm trying to run a .NET application on WEC7 with TCP send buffer size more than 128KB, throws below error:

    "Setting SendBufferSize failed with An invalid argument was supplied". If I set 128KB it proceeds further with other things.

    In WinCE6.0 it was working fine. 


    Seeth

    Tuesday, October 18, 2016 7:18 AM
  • Hi Seeth,

    When you step through the code can you see the arguments in the call? What value are you sending when it fails?  Also what QFE level do you have in your CE 7 build?

    Sincerely,

    IoTGirl

    Tuesday, October 18, 2016 4:52 PM
    Moderator
  • Hi ,

    When I send 129KB it throws the error I mentioned above. Our CE7 build is based on Apr 2014 QFE base.

    Regards,


    Seeth

    Wednesday, October 19, 2016 10:32 AM
  • We have also tested this on the OS image built with Feb 2016 QFE base.

    Regards


    Seeth

    Wednesday, October 19, 2016 10:57 AM
  • Any clue?

    Seeth

    Thursday, October 20, 2016 7:33 AM
  • could you provide a code sample? that could help

    Good Luck,

    Erwin Zwart, eMVP
    Check out my blog: http://guruce.com/blog
    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Thursday, October 20, 2016 8:53 AM
  • It's like below:

    With New System.Net.Sockets.TcpClient
            .SendBufferSize = 128 * 1024 ' Throws the exception "An invalid argument was supplied".

    Regards,


    Seeth

    Thursday, October 20, 2016 9:24 AM
  • Checking you code, but on what platform are you testing.

    On Embedded Compact 7 and 8 this property is not supported? Are you perhaps running desktop code on a CE device?



    Good Luck,

    Erwin Zwart, eMVP
    Check out my blog: http://guruce.com/blog
    GuruCE
    Microsoft Embedded Partner
    http://guruce.com
    Consultancy, training and development services.

    Thursday, October 20, 2016 6:34 PM
  • Hi Erwin,

    I was actually using this property in CE6 so same application is tried in CE7. 

    If this property is deprecated in CE7 any idea what is the alternative?

    Regards,


    Seeth

    Friday, October 21, 2016 8:59 AM
  • Hi Seeth,

    As a side note, the larger the packet, the more likelihood of corruption and failure. As a general rule in data communications I keep packet sizes smaller to avoid painfully large retries.

    Sincerely,

    IoTGirl

    Friday, October 21, 2016 4:16 PM
    Moderator
  • Hi IoTGirl,

    So is it that we can't increase the size greater than 128KB in WEC7. I wanted to confirm that.

    As it works in CE6, if at all the API is deprecated in WEC7.

    Regards,


    Seeth

    Friday, October 21, 2016 5:03 PM
  • Hi Seeth,

    I don't have that answer for you.  Only stated that larger packet sizes are problematic and I personally would consider 128 a max but have not found that in the code at this point.  Do smaller sizes also fail?

    Sincerely,

    ioTGirl

    Friday, October 21, 2016 5:47 PM
    Moderator
  • No. Using the values lesser and equal to 128KB works good. 

    Thanks,


    Seeth

    Monday, October 24, 2016 5:22 AM
  • Any clue? Or anyone has tried this?

    Regards,


    Seeth

    Wednesday, October 26, 2016 5:23 AM