000027387 - No buffer space available (maximum connections reached?): JVM_Bind for ApplicationInfo

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000027387
Applies ToenVision Core
By default envison have a maximum allowed connections. This error will occur by opening more than 4000 active sockets in the envision appliance. The default maximum number of ephemeral TCP ports is 5000 in Win 2003 server. So when the load is steep, then there is a chance of encountering this issue. Keep in mind that this is an OS hard set default and not the envision application.
IssueAn error has been detected. Please report the fact to your administrator with a description of what you were attempting to do. The webserver log may contain additional information about this error.
(maximum connections reached)
ResolutionThe server encountered an internal error () that prevented it from fulfilling this request.
root cause
java.sql.SQLException: JZ006: Caught IOException: java.net.SocketException: No buffer space available JVM_Bind

Please apply the following workaround along with it :
1. Take the backup of the registry.
2. Start Registry Editor.
3. Locate the following subkey in the registry, and then click Parameters:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
On the Edit menu, click New, and click DWORD value then add the following registry entry:
Value Name: MaxUserPort
Value Type: DWORD
Value data: 65534 (decimal)

Description: This parameter controls the maximum port number that is used when a program requests any available user port from the system. Typically, ephemeral (short-lived) ports are allocated between the values of 1024 and 5000 inclusive. After the release of security bulletin MS08-037, the behavior of Windows Server 2003 was changed to more closely match that of Windows Server 2008 and Windows Vista

Microsoft article http://support.microsoft.com/kb/196271/EN-US

Legacy Article IDa63048

Attachments

    Outcomes