article Error: java.net.BindException: Address already in use

If up.time can not bind to a specific port, it will write an error to the uptime.log file and you will not be able to connect to the up.time web interface.  This exception (see example below) appears when starting the up.time data collector service under the following scenarios:

  1. The up.time data collector is already running or is using the wrong port.  In this case, open the httpd.conf file in a text editor, find the Listen xxxx line and set xxxx to the appropriate port number.
  2. Another service is using the up.time data collector port (9995 default).  In this case, determine which service is using the same port and adjust port settings to resolve the conflict.

Example Exception:

 

2007-11-28 13:29:54,467 FATAL (Uptime:277) - up.time can not run, exiting... java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(Unknown Source) at java.net.ServerSocket.bind(Unknown Source) at java.net.ServerSocket. (Unknown Source) at java.net.ServerSocket. (Unknown Source) at com.uptimesoftware.uptime.dataservice.ProtocolListener. (ProtocolListener.java:35) at com.uptimesoftware.uptime.base.UptimeThreadManager.startDataService(UptimeThread Manager.java:142) at com.uptimesoftware.uptime.base.UptimeThreadManager.startBasicThreadsOnly(UptimeT hreadManager.java:71) at com.uptimesoftware.uptime.base.UptimeInstance.runUptime(UptimeInstance.java:89) at com.uptimesoftware.uptime.base.Uptime.main(Uptime.java:275) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.zerog.lax.LAX.launch(DashoA8113) at com.zerog.lax.LAX.main(DashoA8113)

Related Articles


IOException: Not enough space (Java heap)

RatingViews
article

This article explains the IOException: Not enough space message and how to resolve it.

By: uptime Support | Date Created: 1-12-2007 | Last Modified: 7-6-2011 | Index: 115

  4306

uptime.log shows error: java.sql.SQLException ORA-00018

RatingViews
article

This error indicates that the up.time Data Collector was unable to open more sessions with your Oracle database backend. This can have a negative impact on up.time performance and stability....

By: uptime Support | Date Created: 8-5-2010 | Last Modified: 8-10-2011 | Index: 465

  1743

Java heap space Throwable: java.lang.OutOfMemoryError

RatingViews
article

Example error message: 2010-07-09 16:42:41,654 ERROR (PerfERDC:137) - service Platform Performance Gatherer (192) on host DKLBMMDB1 (34) Error getting data from agent: Java heap space Throwable:...

By: uptime Support | Date Created: 8-26-2010 | Last Modified: 8-10-2011 | Index: 495

  2934

Adjusting the Java Heap Size

RatingViews
article

By: uptime Support | Date Created: 2-16-2006 | Last Modified: 8-5-2013 | Index: 056

  22023

Graphing Issues in Firefox / Chrome after Recent Critical Java Up...

RatingViews
article

Oracle recently released a Critical Update for Java that addressed a variety of security concerns.As part of this update, there was changes in how the JRE handles permissions for Java Applets.As a...

By: uptime Support | Date Created: 1-29-2014 | Last Modified: 5-15-2014 | Index: 609

  2032

User Comments



No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement