Fisheye Upgrade Fails With "timeString 'xxxx' for commandTimeout is not valid"

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

Upon upgrading Fisheye, the following error message is displayed in the logs:

1 2 3 4 Caused by: java.lang.IllegalArgumentException: timeString '6000' for commandTimeout is not valid at com.atlassian.fisheye.util.FieldValidator.validTimeString(FieldValidator.java:68) at com.atlassian.fisheye.spi.admin.data.SvnRepositoryData.setCommandTimeout(SvnRepositoryData.java:158) at com.atlassian.fisheye.spi.admin.impl.AdminSpiUtil.copySvnFieldsToRepData(AdminSpiUtil.java:452)

Cause

The upgrade process failed to convert the units of a defined SVN Timeout parameter.

Resolution

You will need to manually edit your FISHEYE_HOME/config.xml file to fix this error. To do so:

  1. Shut down your Fisheye instance, and make a copy of your FISHEYE_HOME/config.xml file.

  2. Manually edit the FISHEYE_HOME/config.xml and remove any instances of the command-timeout variable in your repository configurations.

  3. Start Fisheye.

  4. Go to the Administration console and configure your repository timeout following the Subversion guide.

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.