logoBack to home screen

ADx 2.4 (27/10/2020) Release Notes


Important: After deploying ADx 2.4, make sure you synchronize each of your repositories.

This release introduces several key features and bug fixes, including:

  • Support for Windows-based servers
  • Support for e-mail files
  • Support for alternative repository storage configuration
  • Policies
  • Content preview in ADx Explorer

For a detailed list with corresponding documentation links, see New Features and Improvements.

New Features and Improvements

The following features are added in this release:

AD-1448StoryCriticalSupport e-mail conversionFor a full list of supported files, see Supported Contents.
AD-1094StoryCriticalRepository PoliciesSee Configuring Repository Policies
AD-1457StoryMajorAdd distributed tracingSee Using Request Tracing. Jaeger is the only tracing tool supported at the moment.
AD-571StoryMajorImplement alternative storage configurations on a repositorySee Configuring Alternative Repository Storage, Relocating Individual Contents, and Relocating All Repository Contents.
AD-494StoryMajorAdd preview (embedded) WebReaderSee Previewing Contents in WebReader
AD-487StoryMajorAdd parameters to show or hide WebReader panelsSee Hiding and Showing WebReader Panels
AD-762StoryMajorAdd conversion statistics to ADxSee Checking Conversion Statistics. There are Known Issues related to this feature.
AD-1493TaskMajorRedirection to the latest/correct documentation page from OpenAPIThe OpenAPI documentation link now redirects to the main page of REST API documentation.
AD-1550StoryMinorADx Landing Page should not show status of Remote Conversions when no repository is activeN/A

Bug Fixes

AD-1621BugCriticalCombined Conversion Job does not support several sub job typesN/A - this is an internal Conversion fix. Combined Conversion Jobs now work as expected.
AD-1572BugCriticalWord imported in a Word template does not get variables replacedSee Word Templates for detailed information. Word templates now replace variables correctly, provided that the -build suffix is added.


You can install this release from the provided package. Please follow the Installation Instructions if you're installing from scratch.

Updating Conversion and ADx

For information on how to update previously installed Conversion and ADx, see the following:

Configuration changes

This release introduces new runtime properties and changes to some of the existing runtime properties:

New Runtime Properties


Changed Runtime Properties


Removed Runtime Properties


Known Issues

A list of problems we're still working on.

Known Issues ADx

AD-1647MajorWarning is thrown when uploading content to a folder with DefaultType policy assigned.
AD-1619MajorWhen using an on-prem 2.4 installation jobs are not displayed correctly in Conversion Statistic page when selecting all/panic
AD-994MinorError when running "Owned by me" global search query
AD-321CRITICALAdd missing indices
AD-348MAJORADx Admin: Repository Modification-Status not updated on Update
AD-342MINORHibernate warnings in the log files
AD-341MINORJava warnings during for Java 9 and later
AD-311MINOROracle - DbLockManager prints Oracle constraint message

Reimporting an Existing Repository Requires UI Reload

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.

Cannot migrate legacy contents simultaneously

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.

Known Issues Conversion

AD-338CRITICALIntroduce roles for conversion
AD-337MAJORMake TF Conversion workbench consistent to ADx
AD-501MAJORtf-conversion user has the admin role assigned
 EXTDOCS-71MINORFix wrong encoding on opening resource in Browser

Minor Warnings

StatusLogger Error

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.

Tomcat Shutdown Warning

The following warning is sometimes thrown by Tomcat when stopping the service:

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.

Java Warnings

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

Ticket: AD-341

Hibernate Warnings

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]

Ticket: AD-342

These warnings do not affect the functionality of the application and can be ignored. We are working on a fix.