TCP/IP: Maximum number of inbound connections reached

  • 10099853
  • NOVL104457
  • 06-Dec-2005
  • 06-Dec-2005

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Goal

Domain optimization via the MTA startup file

Domain optimization via ConsoleOne

Fact

Novell GroupWise 6.5

Novell GroupWise 7

Symptom

TCP/IP: Maximum number of inbound connections reached

MTP: Reached inbound connections limit

Cause

Domain being used as routing domain.  Domain is heavily used.

Fix

See Article By Eric Raff, technical editor at http://gwadvisor.com/doc/17228

 

Optimize your Novell GroupWise MTA

Here are a couple of tricks to make sure your MTA is running as efficiently as possible.

   By Eric Raff, technical editor

 

This tip deals with optimizing your GroupWise 6x MTA. You'll want to implement these settings on any MTAs that are used primarily for routing mail, or that have more than 15 direct outgoing or incoming connections. You can handle most of the optimization through ConsoleOne, but there are a couple of tuning parameters you can only set in the MTA startup file.

Domain optimization via ConsoleOne

Edit the properties of the MTA object, and select the Agent Settings tab. From here, the two optimization parameters you'll want to enable are:

·      Use 2nd High Priority Scanner

·      Use 2nd Mail Priority Scanner


These two options provide additional threads to scan for high-priority and normal-priority mail coming into the MTA.

Optimization via the MTA startup file

Edit the GroupWise MTA startup file that loads a particular domain. This file is usually called domainname.mta where domainname is the name of your GroupWise domain. In this example, I show you how to adjust the following parameters:

/tcptrunkwidth-[number]
/tcpinbound-[connections]

The tcptrunkwidth setting can range from 2-4. By default it's set to 1. This controls how many concurrent TCP sessions the MTA can maintain to a particular host or link. For example, if the tcptrunkwidth setting is set to 4 (the maximum) the MTA can open up to four simultaneous connections to any direct link. This setting can greatly increase the throughput of the MTA's routing ability.

The tcpinbound setting controls how many simultaneous connections the MTA is allowed to receive at any given time. The default is 40. If your domain has many agents connecting to it, or receives connections from agents across slower WAN links, you should increase this number. In particular, if your MTA begins displaying the message “TCP/IP: Maximum number of inbound connections (XX) reached” you should increase this setting. The value you choose depends on your environment. I have tcpinbound set to anywhere from 80 to 250, depending on how busy the domain is.

Remember that when you make changes to the MTA startup file, you must unload and reload the MTA before it will pick up the changes you made to the startup file.

.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.