D1 2.8.297 (07/10/2023) Patch Release Notes
This is a patch release to D1 2.8. Here's a list of bug fixes (see below) and new features:
Java version
The on-prem installation packages for this release have been tested with JDK JDK 11.0.12 (package zulu11.50.19-ca-jdk11.0.12-linux_x64)
Changes in the actual version
Nothing has been removed since the previous release.
Changes in upcoming versions
Nothing is going to be removed in future releases.
Runtime properties and configuration changes
No runtime properties have been added, changed, or removed in this release.
List of new features and improvements
| Issue | Priority | Summary Description |
|---|
Bug fixes
| Issue | Priority | Summary Description |
|---|---|---|
| https://jira.braintribe.com/browse/AD-321 | CRITICAL | Add missing indices |
Updating Conversion and ADx
For information on how to update previously installed Conversion and ADx, see the following:
Known issues
Below you can find a list of problems we're still working on.
Known issues D1
| Ticket | SEVERITY | Description |
|---|---|---|
| https://jira.braintribe.com/browse/AD-348 | MAJOR | ADx Admin: Repository Modification-Status not updated on Update |
| https://jira.braintribe.com/browse/AD-4049 | CRITICAL | Unencrypted cloud secrets can be downloaded from GUI |
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.
Min and Max length metadata not respected on initial upload
String length checks are only applied when values are updated but not on the initial upload.
Known issues Conversion
| Ticket | SEVERITY | Description |
|---|---|---|
| https://jira.braintribe.com/browse/AD-338 | CRITICAL | Introduce roles for conversion |
| https://jira.braintribe.com/browse/AD-337 | MAJOR | Make TF Conversion workbench consistent to ADx |
| https://jira.braintribe.com/browse/EXTDOCS-71 | MINOR | Fix 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:
./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.
Java warnings
When using Java 9 or later, the following warning may appear in application logs and also during the 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: https://jira.braintribe.com/browse/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: https://jira.braintribe.com/browse/AD-342
These warnings do not affect the functionality of the application and can be ignored. We are working on a fix.