Issues fixed in Pro2 6.5.3

The pro2.6.5.2.exe installer fails to run when using JDK 11.0.26, but works as expected with JDK 11.0.13.

Pro2-6.5.2.exe overwrites predefs.i when system configured for embedded tables.

The Enterprise Push (enterprisepush.p) is sending unnecessary Errors and Alerts

The code at the top of the ProcBlock logs a default LOCKED message if the block is in a RETRY state. This can also happen for any number of other reasons, and the locked error message is very misleading.

Replication Performance is impacted drastically if ReplQueue is behind and has a large amount of records marked-as-applied in play.

Pro2SQL generates bulkload code with missing fields.

Pro2 Processor Library procedures are generated with code that leaves the empty TEMP-TABLE buffer.

Pro2 enterprise Instance Name link is hard wired to the wrong URL.

Pro2 change password screen not allowing “&” symbol in user password.

Pro2 alerts are showing the same number of errors as the thread number.

Pro2 6.5.2 sends out an alert when table is reassigned to a split thread

Index assignment errors in replProc.p are experiencing STOP conditions which are causing the thread to dump out until the next retry interval.

In source delta df, drop statement shows for tables included in SQL_EXCLUDE_LIST. This is causing issues when dropping tables that may actually be replicating.

In a 2nd pass config After upgrading from 5.3 to 6.5.2 purgequeue causes rogue transactions.

Error 2624 reported in ReplProc while creating thread errors.

Dummy thread needed for Pro2 2nd pass when upgrading 5.3 to 6.5.2