Issue
The Semarchy xDI Runtime does not start successfully. Depending on the environment, one of the following symptoms may be observed:
- The Runtime service starts and stops immediately.
- The Runtime process terminates a few seconds after startup.
- No Runtime process remains active after startup.
- The Runtime appears to start but is not reachable from Designer or Analytics.
Cause
Multiple issues can prevent the Runtime from starting correctly, including:
- Invalid Runtime configuration
- Unsupported Java version
- Port conflicts
- Missing modules or JDBC drivers
- Insufficient permissions
- Invalid Runtime startup parameters
- Memory allocation issues
Solution
- Start the Runtime from a command line instead of using a service manager.
- Redirect the Runtime output to a log file.
- Example on Windows:
startcommand.bat > runtime-start.log 2>&1- Example on Linux:
./startcommand.sh > runtime-start.log 2>&1- Review the generated log file for startup errors.
- Check the Runtime logs located in the Runtime log directory.
- Verify the Java version used by the Runtime.
- Validate that all required modules and JDBC drivers are present.
- Confirm that the configured ports are available and not already used by another process.
Additional Checks
- Verify the Runtime can resolve all referenced hosts and databases.
- Verify the Runtime service account has access to installation and working directories.
- Check antivirus or endpoint protection software for blocked processes.
- Validate Runtime memory settings if the process stops during initialization.
Tip: For xDI 2024.x, 2025.x and later releases, verify that the Runtime is running with a supported Java version and that all third-party modules and JDBC drivers have been migrated after upgrades.
Information: The Runtime startup log is typically the fastest way to identify the root cause. Always collect and review the startup output before troubleshooting further.