Warning on encoding during Bamboo startup
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
Problem
When Bamboo starts, the following warning messages appear in atlassian-bamboo.log
1
2
3
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
Windows file encoding
Cp1252used in Bamboo does not work well with extended character sets.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 - File name encoding validation task works incorrectly when Bamboo started by systemctl
Restart Bamboo with the following JVM options:
1 2-Dsun.jnu.encoding=UTF-8 -Dfile.encoding=UTF-8Disable validation task by commenting the following line in the file
<bamboo-install>/atlassian-bamboo/WEB-INF/classes/upgrade.xml1 2<!--<upgrade build="51210" build-min="0" build-max="999999" class="com.atlassian.bamboo.upgrade.tasks.validation.FileNameEncodingIsReasonable"/>-->
Was this helpful?