article Resolving JVM_BIND Errors in up.time

Related Documentation Version of up.time Affected Affected Platforms
4.1.115 or earlier Windows

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.

Related Articles


Resolving uptimeagent Daemon Messages

RatingViews
article

By: uptime Support | Date Created: 6-13-2006 | Last Modified: 10-28-2011 | Index: 081

  5771

Errors when trying to delete performance data

RatingViews
article

When you following the article http://support.uptimesoftware.com/article.php?id=281 - Trim performance data from your Mysql datastore If you experience the following error: mysql> delete from...

By: uptime Support | Date Created: 10-10-2009 | Last Modified: 8-13-2011 | Index: 420

  2056

Windows Agent Perflib Errors

RatingViews
article

By: uptime Support | Date Created: 10-17-2005 | Last Modified: 7-11-2011 | Index: 014

  13806

phperror.log file filled with "File does not exist" errors

RatingViews
article

The default error logging level in is ALL messages. This can cause a number of messages to be registered in the phperror.log, causing it to grow to very large sizes. Some example messages are:...

By: uptime Support | Date Created: 8-13-2010 | Last Modified: 8-13-2011 | Index: 478

  2158

Common Licensing Problems and Solutions

RatingViews
article

This article lists some common problems you may encounter with your up.time license and explains how to resolve the issues.

By: uptime Support | Date Created: 12-22-2006 | Last Modified: 6-12-2012 | Index: 110

  5063

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement