the TCP MSS resource exhaustion commit

Thorsten Greiner thorsten at
Fri Jan 9 02:59:16 PST 2004

* Andre Oppermann <andre at> [2004-01-09 11:34]:
> You can simply increase net.inet.tcp.minmssoverload to any
> higher value.  I suggest 2,000 as next step.  If set it to
> 0 the check will be disabled entirely.
> This makes we wonder why the Oracle database server is sending
> so many small packets.  Is your JBoss application doing connection
> pooling (eg. multiplexing multiple SQL sessions over one tcp
> session)?
> The documentation for these sysctl's is on its way.

Thanks for your response, I will try your suggestion soon. In the
meantime I have found another problem: remote login via ssh, do a
'tar tvf largefile.tar' and you are out:

Jan  9 11:54:41 tybalt kernel: too many small tcp packets from
XX.XX.XX.XX:5632, av. 215byte/packet, dropping connection

The destination machine is the same SUN database server I mentioned
above and I have not applied the sysctl changes you suggested.


Any fool can paint a picture, but it takes a wise person to be able to
sell it.

This message is digitally signed. To verify its integrity, download a copy
of GnuPG for your operating system from .
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the freebsd-current mailing list