Fixed issues

You do not have the option to configure task-level Java Virtual Memory (JVM) for tasks running in serverless runtime environments.

For application ingestion and replication and database ingestion and replication combined load jobs, markers intended for initial load and backlog processing might incorrectly trigger the incremental load processing with no recovery checkpoints written, which might lead to duplicate data on restart.

Data Ingestion and Replication components contain outdated jose4j release 0.9.4 inherited from a third party driver.

When an application ingestion and replication job or a database ingestion and replication job restarts after a failure, data for a table that was already sent to the target might be resent while recovering data for other tables not yet sent to the target.

For organizations that use the shared secure agent group with multiple agents from parent organization, same unload tasks within a database ingestion and replication or application ingestion and replication might be are assigned to more than one agent, resulting in duplicate unloads for the same table.

Application ingestion and replication combined load jobs and database ingestion and replication combined load jobs that use custom properties related to the load transition processing might ignore those custom properties and instead apply only the default values. The following error might be issued:

Adding the customPrimaryKeys source custom property to an existing incremental load or combined initial and incremental load task might result in a primary key change not allowed error. Following a resync, new DML changes are not replicated to the target, and a restart of the task shows the primary key change not allowed error for the resynced table.

Data Ingestion and Replication components contain vulnerable Simba JDBC driver.