On this page
- Updating Conversion and ADx
- Configuration changes
- Known Issues
This is a patch release to ADx 2.3, fixing a critical problem where the default repository, when configured to run with either S3 or GCP storage, would cause an error on application startup (ticket AD-1532).
For information on how to update previously installed Conversion and ADx, see the following:
Important! After updating to ADx 2.3 from an earlier release, it's required to re-synchronize your existing repositories.
Below you can find a list of problems we're still working on.
|AD-1529||MAJOR||One Deep Health Check test related to the copying of contents fails on CMIS and Documentum repositories. Copy and Move functionality is not available on those repositories.|
|AD-321||CRITICAL||Add missing indices|
|AD-348||MAJOR||ADx Admin: Repository Modification-Status not updated on Update|
|AD-342||MINOR||Hibernate warnings in the log files|
|AD-341||MINOR||Java warnings during for Java 9 and later|
|AD-311||MINOR||Oracle - DbLockManager prints Oracle constraint message|
In some cases, when reimporting an existing repository, repository properties are not rendered correctly. To make sure properties are rendered correctly, refresh your browser after each import.
Due to cache database being shared between repositories, it's not possible for now to run multiple migration jobs from a single legacy repository at the same time. You need to wait for the previous migration to finish before running a new one.
|AD-338>||CRITICAL||Introduce roles for conversion|
|AD-337>||MAJOR||Make TF Conversion workbench consistent to ADx|
|AD-501>||MAJOR||tf-conversion user has the admin role assigned|
|EXTDOCS-71>||MINOR||Fix wrong encoding on opening resource in Browser|
The following error currently appears in ADx console output. It doesn't affect ADx functionality or performance.
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'org.apache.logging.log4j.simplelog.StatusLogger.level' to TRACE to show Log4j2 internal initialization logging.
The following warning is sometimes thrown by Tomcat when stopping the service:
./tribefire-console-stop.sh ... Tomcat did not stop in time. PID file was not removed. To aid diagnostics a thread dump has been written to standard out. Tribefire Host stopped.
This happens when shutdown takes longer than Tomcat expects. Shutdown may take several minutes, which will result in this message being printed out. This warning could appear on both Conversion and ADx.
When using Java 9 or later, the following warning may appear in application logs and also during installation procedure:
WARNING: An illegal reflective access operation has occurred WARNING : Illegal reflective access by com.braintribe.model.processing.itw.asm.AsmClassLoaderWrapper$1 (file:/path/to/instant-type-weaving-1.0.28.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte,int,int) WARNING: Please consider reporting this to the maintainers of com.braintribe.model.processing.itw.asm.AsmClassLoaderWrapper$1 WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release
The log files may contain Hibernate-related warnings. They can be identified based on the fully qualified class which starts with
org.hibernate, as in:
WARNING org.hibernate.tuple.entity.EntityMetamodel 'HHH000084: Entity [com.braintribe.model.user.User] is abstract-class/interface explicitly mapped as non-abstract; be sure to supply entity-names' [TribefireServices-2.0:tribefire-services#initialize,ApplicationLoader:/tribefire-services#initialize]
These warnings do not affect the functionality of the application and can be ignored. We are working on a fix.