My Oracle Support Banner

File Manager Failed to Start with Error "java.net.BindException: Address already in use: bind" in agilefm-stderr.log (Doc ID 2870534.1)

Last updated on MAY 23, 2022

Applies to:

Oracle Agile PLM Framework - Version 9.3.6.0 and later
Information in this document applies to any platform.

Symptoms

File Manager is failing to start with below error after changing the file manager port to 80:

Error

In agilefm-stdout.YYYY-MM-DD.log:

******************************************************************************************************************
 *** File Manager Initialization failed ***
Reason :Uncaught exception thrown.HTTP transport error: java.net.ConnectException: Connection refused: connect

 The failure could be attributed to:
1. The Application Server is currently Unavailable
2. File Manager is not configured correctly - [Admin -> Server Settings -> Locations ->
  -> File Manager Internal Locator] must EXACTLY match the above-mentioned File Manager URL
3. File Manager Entry has been DISABLED or the setting is incorrectly specified
4. ifsuser username/password may not be correct.
*********************************************************************************************************************

In agilefm-stderr.YYYY-MM-DD.log:

13-May-2022 18:09:18.380 SEVERE [main] org.apache.coyote.AbstractProtocol.init Failed to initialize end point associated with ProtocolHandler ["http-nio-80"]
 java.net.BindException: Address already in use: bind


Steps

The issue can be reproduced at will with the following steps:

  1. Open server.xml under %Agile_Home%\FileManager\conf\server.xml with text editor
  2. Go to below line, and change the connector port from default "8080" to "80":

  3. Save the file
  4. Log into Java Client as admin user, and go to Admin tab > Server Settings > Locations > File Manager, and change the port of the File Manager URLs to the port defined in step 2
  5. Open server.conf under %Agile_Home%\agileDomain\config, and change the port of the URL of the one in file.server.url to the port specified in step 2
  6. Restart File Manager server service
  7. Check agilefm-stdout.YYYY-MM-DD.log and agilefm-stderr.YYYY-MM-DD.log generated under %Agile_Home%\FileManager\logs
  8. See the error



Other Details

- Agile Application Server and File Manager is running on the same server machine
- Agile Application Server (WebLogic) is also configured to run on port 80

Changes

Changed File Manager port from default port 8080 to port 80

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.