You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Fred Preston (JIRA)" <ax...@ws.apache.org> on 2005/07/18 17:47:14 UTC

[jira] Created: (AXISCPP-748) The TCP transmit message boundary is set by SO_SNDBUF. What happens when the message > buffer?

The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?
-----------------------------------------------------------------------------------------------

         Key: AXISCPP-748
         URL: http://issues.apache.org/jira/browse/AXISCPP-748
     Project: Axis-C++
        Type: Test
 Environment: n/a
    Reporter: Fred Preston


The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (AXISCPP-748) Test: The TCP transmit message boundary is set by SO_SNDBUF. What happens when the message > buffer?

Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/AXISCPP-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nadir amra closed AXISCPP-748.
------------------------------

    Resolution: Won't Fix

The buffer sizes affect flow control of data, and I guess I do not see any reason to override what the  send/receive buffer for a system.  

> Test: The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?
> -----------------------------------------------------------------------------------------------------
>
>                 Key: AXISCPP-748
>                 URL: https://issues.apache.org/jira/browse/AXISCPP-748
>             Project: Axis-C++
>          Issue Type: Test
>          Components: Transport (axis3), Transport (Client)
>    Affects Versions: current (nightly)
>         Environment: n/a
>            Reporter: Fred Preston
>            Priority: Trivial
>
> The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Updated: (AXISCPP-748) The TCP transmit message boundary is set by SO_SNDBUF. What happens when the message > buffer?

Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-748?page=all ]

Samisa Abeysinghe updated AXISCPP-748:
--------------------------------------

    Component: Transport (axis3)
               Transport (Client)
      Version: current (nightly)

> The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?
> -----------------------------------------------------------------------------------------------
>
>          Key: AXISCPP-748
>          URL: http://issues.apache.org/jira/browse/AXISCPP-748
>      Project: Axis-C++
>         Type: Test
>   Components: Transport (axis3), Transport (Client)
>     Versions: current (nightly)
>  Environment: n/a
>     Reporter: Fred Preston

>
> The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXISCPP-748) Test: The TCP transmit message boundary is set by SO_SNDBUF. What happens when the message > buffer?

Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
    [ http://issues.apache.org/jira/browse/AXISCPP-748?page=comments#action_12336775 ] 

nadir amra commented on AXISCPP-748:
------------------------------------

By default, send/recv buffers are either 4k or 8k.   It would be a good idea to use something bigger, such as 32K or even 64K for both sizes. More information below.  

TCP send buffer size
================
The TCP send buffer size provides a limit on the number of outgoing bytes that are buffered by TCP. Once this limit is reached, attempts to send additional bytes may result in the application blocking until the number of outgoing bytes buffered drops below this limit. The number of outgoing bytes buffered is decremented when the remote system acknowledges the data sent.

Setting this parameter does not guarantee the size of the TCP send buffer. This is the default buffer size that is used for initial TCP connection negotiations.

TCP receive buffer size
==================
Specifies what to allocate for the default receive buffer size. The TCP receive window size is based on this value. Decreasing this value decreases the amount of data that the remote system can send before being read by the local application. Decreasing this value may improve performance in situations where many retransmissions occur due to the overrunning of a network adapter.

Setting this parameter does not guarantee the size of the TCP receive buffer. This is the default buffer size that is used for initial TCP connection negotiations.



> Test: The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?
> -----------------------------------------------------------------------------------------------------
>
>          Key: AXISCPP-748
>          URL: http://issues.apache.org/jira/browse/AXISCPP-748
>      Project: Axis-C++
>         Type: Test
>   Components: Transport (axis3), Transport (Client)
>     Versions: current (nightly)
>  Environment: n/a
>     Reporter: Fred Preston
>     Priority: Trivial

>
> The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Re: [jira] Created: (AXISCPP-748) The TCP transmit message boundary is set by SO_SNDBUF. What happens when the message > buffer?

Posted by Nadir Amra <am...@us.ibm.com>.
Not sure why a jira is created.  But the socket send buffer is just a 
method for flow control used by the TCP/IP stack.  By default I believe on 
most systems it is 8k. 

There is also a receive buffer too. 

Depending on the system, it may be good to set the values to higher values 
so one can get larger chunks of the data at one time. But this is 
dependent on a lot of things, network, the system, server, etc...


"Fred Preston (JIRA)" <ax...@ws.apache.org> wrote on 07/18/2005 
10:47:14 AM:

> The TCP transmit message boundary is set by SO_SNDBUF.  What happens
> when the message > buffer?
> 
-----------------------------------------------------------------------------------------------
> 
>          Key: AXISCPP-748
>          URL: http://issues.apache.org/jira/browse/AXISCPP-748
>      Project: Axis-C++
>         Type: Test
>  Environment: n/a
>     Reporter: Fred Preston
> 
> 
> The TCP transmit message boundary is set by SO_SNDBUF.  What happens
> when the message > buffer?
> 
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>    http://www.atlassian.com/software/jira
> 


[jira] Updated: (AXISCPP-748) Test: The TCP transmit message boundary is set by SO_SNDBUF. What happens when the message > buffer?

Posted by "John Hawkins (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-748?page=all ]

John Hawkins updated AXISCPP-748:
---------------------------------

     Summary: Test: The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?  (was: The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?)
    Priority: Trivial  (was: Major)

Let's create a test for this and see what happens !

> Test: The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?
> -----------------------------------------------------------------------------------------------------
>
>          Key: AXISCPP-748
>          URL: http://issues.apache.org/jira/browse/AXISCPP-748
>      Project: Axis-C++
>         Type: Test
>   Components: Transport (axis3), Transport (Client)
>     Versions: current (nightly)
>  Environment: n/a
>     Reporter: Fred Preston
>     Priority: Trivial

>
> The TCP transmit message boundary is set by SO_SNDBUF.  What happens when the message > buffer?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira