Global Sync – “Failed to regenerate transformation jar” when saving topology

Environment

• Global Sync
• RadiantOne / VDS 8.2.x
• Environments with custom Java-based scripts under the VDS custom source tree

Symptoms

When clicking Save on a Global Sync topology, the following issues occur:

• The UI returns an error: "Failed to regenerate transformation jar"
• The error details show an Ant/Javac build failure referencing the custom build file
• The compiler output shows a "cannot find symbol" error for an imported class in a custom script
• A script may appear to "compile successfully" when compiled directly from the UI, but Save still fails because the server-side jar regeneration compiles a broader set of sources

Cause

One or more leftover or incompatible custom .java files under the VDS custom scripts source tree cause the server-side compilation to fail during transformation jar regeneration. This commonly occurs after upgrades from previous versions when obsolete custom files remain in the directory structure.

Resolution

To resolve this issue:

• Identify the custom Java file(s) referenced in the compile error output (the failing path/file is typically shown in the "cannot find symbol" message)
• Navigate to the VDS custom scripts source directory (example location: /opt/radiantone/vds/vds_server/custom/src/com/rli/scripts/customobjects/)
• Remove or correct the incompatible/leftover .java files from the directory
• Retry saving the Global Sync topology after the cleanup

The save should succeed once the custom compilation completes without errors.

Additional Notes

• This issue is most likely to occur after upgrades from earlier versions where custom files were carried forward but are no longer compatible with the current runtime/libraries
• If troubleshooting is still needed after cleanup, collect logs from the time of the Save attempt (such as sync_engine.log and vds_server.log with DEBUG enabled) to confirm whether the failure is still a compilation issue