- You received intermittent socket exhaustion alerts.
- You notice high CPU usage and increased memory usage in the UAG IIS worker process (w3wp.exe).
- You find that event ID 111 is logged in the Windows event log.
For example, consider the following scenario:
- A web application uses an application-specific host name, or a Microsoft SharePoint application is configured as the initial internal application for the UAG 2010 trunk.
- A request is made to the application for a fully qualified domain name (FQDN) that differs from the public host name that is configured in the application.
In this scenario, an internal loop may be encountered that leads to socket exhaustion and to high CPU usage and high memory usage during the loop. The loop does recover as soon as the socket exhaustion is encountered. Then, resources are released, and the working resource levels revert to typical levels.
- Create the following registry subkey:Registry location:
DWORD name: RejectUnknownHost
Value data: 1
- Start the UAG configuration.
- Run IISReset as an administrator to restart Internet Information Services (IIS).
Article ID: 2745313 - Last Review: 7 Dec 2012 - Revision: 1