Knowledgebase:
Issues With Asian Characters on Cloud Storage
Posted by Aly Essa, Last modified by Aly Essa on 15 October 2018 02:04 PM

Overview

Currently, there is a known issue with transferring files that contain some Asian characters in the file name when using the following Object Storage providers on the FileCatalyst Server:

  • OpenStack EFS driver
  • Google Cloud Storage
  • Backblaze B2
These Object Storage providers are all supported on our latest build v3.7.3 running the FileCatalyst Server as a service. If you are running the application in standalone mode the issues reported with Asain characters in the filename were not observed or reported. There is an issue where filenames with Asian characters (or likely any extended characters) are not interpreted properly when viewing listings in Express, or when attempting to download files in any way when the FileCatalyst Server is running as a service.

We are actively working to resolve this and will update this notification when we have news.

Environment

FileCatalyst Server v3.7.2 and newer.
OpenStack EFS driver

Google Cloud Storage
Backblaze B2


Resolution

The resolution for this issue is to force the Java Service Wrapper to force files to use UTF-8 character set by default.

Windows:

i) Shut down the FileCatalyst Server.
ii) Open the fcconf.conf file in a text editor. This file is located in your installation directory of the FileCatalyst Server. Before you proceed make a copy of this file.
iii) Search for wrapper.java.additional.
iv) In the list shown, add the following property incrementing from the last available number possible. A default fcconf.conf file will contain the following:
wrapper.java.additional.1=-XX:+IgnoreUnrecognizedVMOptions
wrapper.java.additional.2=--add-modules=java.xml.bind
wrapper.java.additional.3=-Dsun.java2d.d3d=false
wrapper.java.additional.4=-XX:+UseConcMarkSweepGC
wrapper.java.additional.5=-Dsun.java2d.noddraw=true

v) Add -Dfile.encoding=UTF-8 as the sixth property. Your properties will look like:

wrapper.java.additional.1=-XX:+IgnoreUnrecognizedVMOptions
wrapper.java.additional.2=--add-modules=java.xml.bind
wrapper.java.additional.3=-Dsun.java2d.d3d=false
wrapper.java.additional.4=-XX:+UseConcMarkSweepGC
wrapper.java.additional.5=-Dsun.java2d.noddraw=true

wrapper.java.additional.6=-Dfile.encoding=UTF-8

vi) Save the fcconf.conf file and restart the FileCatalyst Server service.

Linux:

i) Shut down the FileCatalyst Server.
ii) Open the wrapper.conf file in a text editor. This file is located in your installation directory of the FileCatalyst Server (/opt/utechsoft/server/conf/wrapper.conf). Before you proceed make a copy of this file.
iii) Search for wrapper.java.additional.
iv) In the list shown, add the following property incrementing from the last available number possible. A default fcconf.conf file will contain the following:
wrapper.java.additional.1=-XX:+IgnoreUnrecognizedVMOptions
wrapper.java.additional.2=--add-modules=java.xml.bind
wrapper.java.additional.3=-Dsun.java2d.d3d=false
wrapper.java.additional.4=-XX:+UseConcMarkSweepGC
wrapper.java.additional.5=-Dsun.java2d.noddraw=true

v) Add -Dfile.encoding=UTF-8 as the sixth property. Your properties will look like:

wrapper.java.additional.1=-XX:+IgnoreUnrecognizedVMOptions
wrapper.java.additional.2=--add-modules=java.xml.bind
wrapper.java.additional.3=-Dsun.java2d.d3d=false
wrapper.java.additional.4=-XX:+UseConcMarkSweepGC
wrapper.java.additional.5=-Dsun.java2d.noddraw=true

wrapper.java.additional.6=-Dfile.encoding=UTF-8

vi) Save the wrapper.conf file and restart the FileCatalyst Server service.


MacOSX:

i) Shut down the FileCatalyst Server.
ii) Open the Info.plist file in a text editor. This file is located in your Applications folder under the following path /Applications/FileCatalystServer.app/Contents. Before you proceed, make a copy of this file.
iii) Search for the array tag and at the bottom of the list add the following in a <string> tag:
<string>-Dfile.encoding=UTF-8</string>

iv) Your new configuration block should look like:

vi) Save the file and restart the FileCatalyst Server service.





Comments (0)