Consideration
FME Flow is not loading in the web browser. All FME Flow services are running, but in the Tomcat log files, there is an error similar to the examples below, reporting a bind.
java.net.BindException: Address already in use: bind
java.lang.Exception: Socket bind failed: [730013] An attempt was made to access a socket in a way forbidden by its access permissions.
Why This Happens
This occurs when another program is using a port required by the FME Flow Application Server service (Apache Tomcat). This process uses two ports:
1. The port the Application Server connects to is set during installation and defaults to port 80 on Windows and 8080 on Linux.
2. The shutdown port, which must be available for the service to run correctly:
- Prior to FME Flow 2024.1 b24591, port 8005 was the default shutdown port
- For FME Flow 2024.1 b24591 and later, the default shutdown port is now 8006.
How to Resolve It
Disable or change the port used by services that are using FME Flow's port. On Windows, these may include Internet Information Services (IIS), World Wide Web Publishing Service, Windows Remote Management, Microsoft SMS Agent, and Skype. On Linux, there may be web servers such as Nginx. Alternatively, you may wish to reconfigure FME Flow to use a different port to avoid future conflict.
To check what service is using the same port as your web application you can use netstat, in the following commands update <port> to the port number reported in the error.
Windows
To retrieve the PID number of the process using a port open command prompt and run
netstat -ano | find "<port>"
The final column is the PID number. To retrieve the service name associated with this PID, run
tasklist /fi "pid eq <PID>"
This information can also be found in Windows Task Manager under the Details tab.
If the service name returned does not belong to FME Flow, another service is using the port, and you will need to free the port to successfully access FME Flow. To stop the service from using this port, select 'End Task' in Windows Task Manager. Restart the FME Flow Application Server service, and verify that FME now occupies this port. Alternatively, you may wish to reconfigure this service or FME Flow to use a different port to avoid future conflict.
Linux
To retrieve the process using a port, open a console, and as the root user, run
netstat -apn | grep :<port>
If the associated process is not FME-related, it is likely to blame. To end the process, use
kill <PID>
Restart the FME Flow Application Server service and confirm that FME Flow now occupies this port. Alternatively, you may wish to reconfigure this service or FME Flow to use a different port to avoid future conflict.
Changing the Port
Change the Web Application Port
Follow the instructions in our documentation.
Change the Shutdown Port
1. Run a Text Editor as an Administrator and open server.xml located in <FMEInstallDir>\Utilities\tomcat\conf
2. Find the line <Server port="8005" shutdown="SHUTDOWN"> and change 8005 to another unoccupied port, e.g., port 8006.
Confirm your chosen port is unoccupied by using the netstat command above, and make sure there is nothing in the response.
FME Flow 2024.1 b24591 and later use port 8006 as the default shutdown port. If 8006 is in use, try 8007
3. Save the file and restart the FME Flow Application Server service
4. Open the FME Flow Web UI and make sure FME Flow now loads as expected.
Troubleshooting
If this doesn't resolve the problem, the error may indicate that some other FME Flow process did not shut down properly during a restart of FME Flow. You'll need to identify and terminate this process.
1. Shut down the FME Flow services.
2. In Windows, open the Task Manager. Visit the details tab and sort by "Name". In Linux, use the ps command in a terminal to list all running processes.
3. Locate processes that begin with 'fme*'. If you do not see any, then this likely isn't the cause of your error message, and you should contact Customer Support to investigate
4. Right-click on each process and select "End Process" or use 'kill' in Linux. Do this until no fme* processes remain.
5. Restart FME Flow.
This should clear up the processes and allow FME Flow to start in a good state.
If you are still experiencing issues, please consult our Web Interface Login Troubleshooting Guide. If the troubleshooting guide does not resolve your issue, please contact Safe Software Support.