Resolving JVM_BIND Errors in up.time

This article describes how to resolve JVM_Bind errors that appear in the uptime.log file on Windows systems. These errors will typically resemble the following examples:

2010-06-04 00:59:05,125 ERROR (PerfERDC:226) - Error collecting configuration:
No buffer space available (maximum connections reached?): JVM_Bind
2010-06-04 00:59:05,156 ERROR (PerfERDC:164) - Exception during data collection
java.net.SocketException: No buffer space available (maximum connections reached?): JVM_Bind
  at java.net.PlainSocketImpl.socketBind(Native Method)

2010-06-04 01:03:25,906 ERROR (PerfERDC:226) - Error collecting configuration:
Address already in use: JVM_Bind
2010-06-04 01:03:26,437 ERROR (PerfERDC:164) - Exception during data collection
java.net.BindException: Address already in use: JVM_Bind

Details

This problem generally occurs on Windows systems (often Windows XP) that have the IPv6 TCP Stack installed. If both IPv4 and IPv6 are installed on the system, the Java Virtual Machine (JVM) may have problems closing or opening sockets at the operating system level. Additional information about this problem is available from Sun Microsystems under Bug ID 6286189.

Resolution

Resolve this problem by upgrading up.time to version 4.2 or later.