Reset Search
 

 

Article

Netsight fails to launch, 404 error or Java.net.bind or JVM_Bind error occurs.

« Go Back

Information

 
TitleNetsight fails to launch, 404 error or Java.net.bind or JVM_Bind error occurs.
Symptoms
  • Customer gets an Apache 404 error
  • Netsight startup web page does not display
  • Netsight does not start
  • Customer wants to change default web ports of 8080, 8443
Environment
Netsight Console
Cause
  • Duplicate port binding is being used on server
  • Web Service running on server
  • Server.log displays a 
  • java.net.BindException: Address already in use: JVM_Bind:8080
  • netstat -abn shows 8080 or 8443 binding to wrong application
Resolution
  • If the Netsight Server is running on an Extreme appliance, we don't support any other running application on those ports.
  • For customer premise devices, they can modify the ports that they would attach to the Netsight server on by modification of the NSJBoss.properties file.
  • Edit the following to another port .
 
enterasys.tomcat.https.port=8443
enterasys.tomcat.http.port=8080

You can also do this from the Console application
Tools->Options->Web Server
You will see the following. If the defaults are changed. It will ask the to restart the Netsight Server.

User-added image

Another possible resolution is to identify the third-party application running on the same TCP port 8080 and either disable the third-party application or uninstall it. 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255