Fisheye fails to start due to invalid bind address

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

Following error is reported in the logs when the Fisheye start-up fails:

1 2 3 2012-08-08 14:42:16,138 INFO [main ] fisheye.app Bind-parse - problem parsing our own bind address java.lang.NumberFormatException: For input string: "8060/fisheye" at java.lang.NumberFormatException.forInputString(Unknown Source)

Cause

Fisheye is expecting a number in the bind address field.

Resolution

Edit the config.xml file in FISHEYE_INST and if you've placed a context path such as :8060/fisheye then remove the context path, so that the bind address only contains the port number :8060.

For example:

1 2 3 ... <http bind=":8060"/> ...

Restart Fisheye.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.