On this page
- New Installation
- Updating Conversion and ADx
- Configuration Changes
- Known Issues
This is a patch release to ADx 2.2.
In this release, we introduce the possibility to update repository configuration from a
.zip package provided by Braintribe. Bug fixes and documentation improvements are provided as well.
This release adds the following features and fixes:
|AD-1107||Bug||Critical||Update repository configuration||See Updating Repository Configuration|
|AD-1148||Documentation||Critical||Update repository documentation||See Adding Repositories|
|AD-1130||Story||Critical||WebReader: Option to print a document||N/A|
|AD-1142||Bug||Major||Auto-commit not working in Admin area in certain situations||N/A|
|AD-1164||Documentation||Minor||New configuration items for Conversion Job Cleanup||See Configuration Changes|
For information about the 2.2 release, please read ADx 2.2 Release Notes.
You can install this release from the provided package. Follow Installation Instructions if you're installing from scratch.
For information on how to update the previously installed Conversion and ADx, see the following:
Note that this release includes configuration changes - please update your settings file accordingly if you want to re-use it.
This patch introduces new runtime properties for Conversion related to job cleanup.
New runtime properties can be added to the installation settings file - see New Runtime Properties.
The following runtime properties are added in this release:
|CONV_CLEANUP_WORKER_THREADCOUNT||The number of threads deleting old jobs in parallel (used to be hardcoded |
|CONV_CLEANUP_WORKER_BATCHSIZE||The maximum number of jobs cleaned up in a single run (used to be hardcoded |
|CONV_CLEANUP_WORKER_COOLOFF_INTERVAL||The number of jobs after which a short cool-off period is used to reduce the continuous load on the database. It will simply pause every n Jobs (used to be hardcoded |
|CONV_CLEANUP_WORKER_COOLOFF_TIME||How long the cool-off phase should last (in |
Issues mentioned below have been reported in the previous releases - we are currently working on fixing them.
|AD-321||CRITICAL||Add missing indices|
|AD-354||CRITICAL||ADx Admin: Problem when synchronizing Type Definitions form DCTM/CMIS|
|AD-1096||MAJOR||Stopping ADx Tomcat process may take multiple minutes|
|AD-348||MAJOR||ADx Admin: Repository Modification-Status not updated on Update|
|AD-1204||MAJOR||Repository Filters Don't Return Any Results|
|AD-342||MINOR||Hibernate warnings in the log files|
|AD-341||MINOR||Java warnings with Java 9 and later during startup|
|AD-311||MINOR||Oracle - DbLockManager prints Oracle constraint message|
At the moment, if you query for a specific repository type in Administration area (for Standard, CMIS or DCTM), you will get no results, even if you have repositories of the given type. As a workaround, please either query for all repositories or active/inactive repositories:
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.
After starting newly installed ADx with Standard repository and trying use Open API, an error occurs:
This problem only occurs on clustered ADx installations. After restarting the ADx node, it should be gone (you can also switch to Swagger 2.0 which works in all situations).
|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.