Unix Agent FileTransfer fails with InvalidPathException on non-UTF-8 filenames in v24.
Article ID: 440046
Updated On:
Products
Issue/Introduction
An Automic File Transfer (JOBF) object fails immediately during the directory scanning phase when the source directory contains filenames with non-UTF-8 characters (e.g., ISO-8859-15 single-byte characters like ä).
The Job aborts and the following error is visible in the Agent log:
U00063030 FT '[RunID]': File sampling error. Filter: '/tmp'. Error: 'java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters: /tmp/�.txt'.
Additionally, the Agent log shows that it is forcing an internal UTF-8 charset despite being configured for a legacy code page: U07001001 Charset used by the Agent: 'UTF-8'
Environment
- Product: Automic Automation
- Component: Java-based Unix Agent (Linux)
- Version: 24.4.x (Confirmed in 24.4.3 and 24.4.4)
- OS Configuration: Non-UTF-8 locale (e.g.,
LANG=de_DE@euro/ISO-8859-15)
Cause
This is caused by a product defect (DE194521).
In version 24, the Java-based Unix Agent application logic explicitly overrides OS locale settings, Agent INI properties (utf8=0), and JVM-level properties (e.g., -Dfile.encoding). It forces the internal java.nio.file scanner to use UTF-8, which cannot map single-byte legacy characters, resulting in a fatal InvalidPathException during directory sampling.
Resolution
This issue is currently being investigated.
Workaround:
Currently, there is no known configuration-based workaround (INI settings or JVM flags) that can override this application-level behavior. For a permanent fix, please upgrade the Agent to a version containing the fix for DE194521.
Additional Information
Article title: How to register to Broadcom Software Product updates and Critical Alerts
https://knowledge.broadcom.com/external/article?articleId=133819
Feedback
