Setting limits for client connections to WebMarshal


This article applies to:

  • WebMarshal 6.10 and above

Question:

  • What is the limit on concurrent connections from a client computer to WebMarshal?
  • How do I adjust the client connection limit?

Procedure:

WebMarshal 6.10 and above allows a limit on concurrent connections from any one client IP to the WebMarshal Proxy service. This feature helps to avoid inadvertent or intentional flooding of the WebMarshal server.

By default the limit is 6000 concurrent connections from any one IP (for 32 bit operating systems, 4000 concurrent connections from any one IP). This default applies to all installations of WebMarshal 6.10 and above, whether new, or upgraded from a previous version.

You can adjust the setting as follows.

Note: If you have more than one processing server (node), you must make the changes on each server.

  • Add an entry in the WebMarshal Proxy Configuration file (WMProxy.config.xml)
    <WebMarshal> 
        <Proxy>
         <Config>
    <ProxySettings maxClientConnections="{value}" [other attributes...] />      </Config>
       </Proxy>
    </WebMarshal>

Notes:

  • To disable connection limits, set the value to zero or a negative number.
  • To accept the default, remove the entire string maxClientConnections="{value}"
  • For general information about editing XML settings files, see article Q12705.
  • The file WMProxy.config.xml is located on the processing server. If you have more than one processing server, you must make the changes on each server.
  • To apply the change, restart the WebMarshal Proxy service.
  • When entering the value, do not include the braces {}, but do include the quote marks.
  • Back up configuration before making changes.
  • The file WMProxy.config.xml normally contains additional settings. The ProxySettings node can have multiple attributes. This node should only occur once.
  • To adjust this setting, only add (or remove) the specific attribute maxClientConnections.

Last Modified 3/4/2018.
https://support.trustwave.com/kb/KnowledgebaseArticle15037.aspx