Skip to main content

Known Issues / Limitations

This document outlines known issues and limitations encountered during parallel operations. This list might change in the future because we continuously improve our tools.

tip

If you find anything not listed here, please do not hesitate to contact the Designer Development Team via Ticket or any other means.

We greatly appreciate your feedback.

VS Code cannot be started from the ADITO Designer​

If the "Open in Extension Pack" action cannot open VS Code, you can check the following steps:

  • Ensure that VS Code is correctly installed on your system.
  • Ensure that the CLI location of VS Code is correctly set in the ADITO Designer settings under Settings → ADITO → Transpile and Deploy → Extension Pack Location.

Data models do not remember their custom YAML location and are placed in the default location​

Data Models will always be converted. Any custom location of the data model on the file system, e.g. my-project/ADITO/processes/auth/MyAuth_lib will be converted to processes/MyAuth_lib after converting to AOD and to YAML again. This will be fixed in a later release.

Incorrect Initial Autocomplete for Arrays​

YAML documents containing required arrays with default values may be populated incorrectly during the initial autocomplete process.

Relevant Issue: RedHat YAML: Issue #1187

Workaround​

  1. Remove the incorrectly generated default values from the array. The array entry should only contain the key (e.g., key: ).
  2. Press Ctrl+Space to trigger autocomplete again.
  3. Select Default Value from the suggestions.

Issue-1187.png
Figure: Autocomplete of Default Array Value

Deployment Issues​

Deployment Connection Errors (Database)​

When using "Deploy v2," you may encounter a java.sql.SQLNonTransientConnectionException or UnknownHostException similar to the one below:

2026-01-02 10:36:13 [ERROR] Database error: java.sql.SQLNonTransientConnectionException: Socket fail to connect to host:address=(host=adito-db.name-of-your-cloud-system-htc1-adito-cloud.svc.cluster.local)(port=3306)(type=primary). adito-db.name-of-your-cloud-system-htc1-adito-cloud.svc.cluster.local
	at org.mariadb.jdbc.client.impl.ConnectionHelper.connectSocket(ConnectionHelper.java:140)
	at org.mariadb.jdbc.client.impl.StandardClient.<init>(StandardClient.java:102)
	at org.mariadb.jdbc.Driver.connect(Driver.java:69)
	at org.mariadb.jdbc.Driver.connect(Driver.java:95)
	at org.mariadb.jdbc.Driver.connect(Driver.java:26)
	at io.agroal.pool.ConnectionFactory.createConnection(ConnectionFactory.java:225)
	at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:545)
	at io.agroal.pool.ConnectionPool$CreateConnectionTask.call(ConnectionPool.java:526)
	at java.base@21/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at io.agroal.pool.util.PriorityScheduledExecutor.beforeExecute(PriorityScheduledExecutor.java:75)
	at java.base@21/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.base@21/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base@21/java.lang.Thread.runWith(Thread.java:1596)
	at java.base@21/java.lang.Thread.run(Thread.java:1583)
	at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:833)
	at org.graalvm.nativeimage.builder/com.oracle.svm.core.windows.WindowsPlatformThreads.osThreadStartRoutine(WindowsPlatformThreads.java:210)
Caused by: java.net.UnknownHostException: adito-db.name-of-your-cloud-system-htc1-adito-cloud.svc.cluster.local
	at java.base@21/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:567)
	at java.base@21/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:327)
	at java.base@21/java.net.Socket.connect(Socket.java:751)
	at org.mariadb.jdbc.client.impl.ConnectionHelper.connectSocket(ConnectionHelper.java:134)
	... 15 more

This usually indicates that the required SSH tunnels are not open on your local machine.

Fix​

  1. Ensure Pageant is running and your SSH key is loaded.
  2. Download the tunnel script for your specific system from the SSP (Namespace → Tunnel → SSH-Tunnel Script for Windows).
  3. Execute the script to establish the connection.
  4. Verification: Verify the database connection using an external database tool (outside the ADITO Designer) to ensure the tunnel is active.
note

The tunnels opened by the ADITO Designer are not enough, because those tunnels are only open for the ADITO Designer itself and not for any standalone tools like the deployment tool.

Deployment: Driver Warnings ("Driver does not support the provided URL")​

During deployment, you may encounter warning messages in the logs similar to the following:

[WARN ] Datasource 'postgresql': Driver does not support the provided URL: jdbc:mariadb://adito-db.name-of-your-cloud-system-htc1-adito-cloud.svc.cluster.local:3306/_____systemalias

Cause​

The deployment tool supports six different database systems simultaneously. This warning occurs when a driver (e.g., PostgreSQL) attempts to evaluate a connection URL intended for a different database type (e.g., MariaDB).

Solution​

You can safely ignore these warnings, provided the mentioned database system (e.g., 'postgresql' in the example) does not match your actual target database.

Deployment: Inaccurate Change Detection (Oracle)​

The deployment tool uses MD5 hashes to detect differences between local files and database records. When using Oracle databases, a technical limitation affects this process.

Technical Limitation​

Oracle's internal functions can only compute MD5 hashes for the first 32 KB of a BLOB field.

Impact​

  • Files exceeding 32 KB may be incorrectly flagged as "changed" or "unchanged" because only the beginning of the file is compared.
  • Change detection is less reliable for large files on Oracle compared to other supported database systems, which hash the entire file content.

Recommendation​

When deploying to Oracle systems, manually verify changes for large files if the automated detection results seem inconsistent.