Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind <null>:80
search cancel

Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind <null>:80

book

Article ID: 37976

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When I launch UMP, it just shows blank page and doesn't pop up for login.and given the below error message

Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind <null>:80

 

 

 

 

Environment

UIM & UMP 8.51 & later

Cause

Something on this system is already trying to use port 80 so the wasp probe is unable to.

Resolution

You can find what this is by doing this command at a command prompt:

netstat -ano | findstr 80

This will show all connections to and from port 80. (and other ports and addresses that contain '80' in them) You can use this output to find something that shows that it is listening on port 80, and in the 4th column will be the PID of the process that is binding to that port. You can then look in Task Manager at the 'processes' tab to find out what process goes with that PID and find out why it's using port 80 and either change/disable the software that is responsible.

In some cases if you can't determine what's using port 80 it could be because the port is "stuck" due to some crashed process so a machine reboot would be required.

Note:-
If IIS has been installed then please remove the IIS from the server.

Additional Information

Blow information for Port configuration:

Waasp configuration › The Setup Tab
Port configuration
Displays the ports specified and verified during the UMP installation.

Note: At least one port must be configured. Raw Configure provides additional port configuration options for wasp. See the section setup.

http port
Specifies the HTTP port for UMP to use.


and Deactivate & activate the wasp
probe.