Warning on encoding during Bamboo startup

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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

Problem

When Bamboo starts, the following warning messages appear in atlassian-bamboo.log

2020-06-30 06:24:57,773 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] 51210 : Verify file name encoding (bootstrap)
2020-06-30 06:24:57,773 INFO [localhost-startStop-1] [BootstrapUpgradeManagerImpl] ---------------------------------------------
2020-06-30 06:24:57,776 WARN [localhost-startStop-1] [FileNameEncodingIsReasonable] Encoding [Cp1252] used to encode file names is not capable of handling extended character sets. You may encounter failures during artifact transfers.

Cause

  1. Windows file encoding Cp1252 used in Bamboo does not work well with extended character sets.
  2. Bamboo started by systemctl caused the validation task to fail

Resolution

The following workaround is only required if you are running Bamboo 7.0.5 or earlier. It has been fixed via  BAM-20996 - Getting issue details... STATUS

  1. Restart Bamboo with the following JVM options: 

    -Dsun.jnu.encoding=UTF-8
    -Dfile.encoding=UTF-8

    Configuring your system properties

  2. Disable validation task by commenting the following line in the file <bamboo-install>/atlassian-bamboo/WEB-INF/classes/upgrade.xml 

        <!--<upgrade build="51210" build-min="0" build-max="999999"
                 class="com.atlassian.bamboo.upgrade.tasks.validation.FileNameEncodingIsReasonable"/>-->

Last modified on Mar 21, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.