ADx 2.0.330 (26/08/2019) Release Notes
The most critical feature of this release is the possibility to migrate content from legacy ADx repositories to the current ADx 2.0 repositories. New runtime properties were introduced and a number of bugs were fixed, as described in this document. Online documentation has been updated with information about the latest changes.
Installation
You can install this release from the provided package. Follow Installation Instructions for more details.
New Features and Improvements
These updates and bug fixes are provided in this release.
| Ticket | SEVERITY | Description |
|---|---|---|
| https://jira.braintribe.com/browse/AD-444 | CRITICAL | ADx Explorer: Explicit Move Operation missing |
| https://jira.braintribe.com/browse/AD-417 | CRITICAL | Default Repository: Oracle Connector: Connection Option "ORACLE_SID" not set |
| https://jira.braintribe.com/browse/AD-415 | CRITICAL | Default Repository has no Conversion settings |
| https://jira.braintribe.com/browse/CORETS-438 | CRITICAL | ADx Admin: Error when searching for UserSessions |
| https://jira.braintribe.com/browse/AD-355 | CRITICAL | ADx Admin: Support of data migration from ADX 1.1 to 2.0 |
| https://jira.braintribe.com/browse/CORETS-459 | MAJOR | ADx Core: "Stay Signed In" checkbox did not send the checkbox state to the server |
| https://jira.braintribe.com/browse/CORETS-455 | MAJOR | ADx Core: Error when searching in a closed Elastic Index. The server now ensures that the Index remains opened |
| https://jira.braintribe.com/browse/CORETS-436 | MAJOR | ADx Explorer: Delete Tags is throwing UI Error |
| https://jira.braintribe.com/browse/CORETS-422 | MAJOR | ADx API: Delete tag not working |
| https://jira.braintribe.com/browse/AD-403, https://jira.braintribe.com/browse/AD-405, https://jira.braintribe.com/browse/AD-406, https://jira.braintribe.com/browse/AD-407 | MAJOR | Architecture documentation update related to databases, explaining which databases can be shared together with recommendations. Updated documentation: https://adx.tribefire.com/tribefire.adx.phoenix/adx-doc/getting_started/ADx_Architecture/adx_architecture_overview.html#databases |
| https://jira.braintribe.com/browse/AD-331 | MAJOR | ADx Content: After updating content with new file, old one is still presented in ADx explorer and is opened in web-reader |
| https://jira.braintribe.com/browse/CORETS-412 | MINOR | When clicking on "Parent Folder" in the properties panel, the folder should be opened |
| https://jira.braintribe.com/browse/CORETS-457 | MINOR | ADx Explorer: Fixed a problem with the About page in the Control Center |
| https://jira.braintribe.com/browse/AD-440 | MINOR | Deep health check: Extension with new tests |
| https://jira.braintribe.com/browse/CORETS-458 | TRIVIAL | ADx Explorer: Vertically realigned buttons in the footer area of the Explorer |
New Runtime Properties
The following runtime properties were added in this release:
| Property | Description | Default Value |
|---|---|---|
| ADX_DEFAULT_CACHE_DB_TYPE | This property was missing in previous releases. It's related to initializing a cache database, specifying the DB type. | ${ADX_DEFAULT_DB_TYPE} |
| TRIBEFIRE_RUNTIME_OFFER_STAYSIGNED | When set to true, the login dialog offers the option Stay signed in. If this option is selected, the session cookie will remain active, even if the user closes the browser session. If it's set to false (or, if the user disables the check box in the login dialog), the session cookie sent to the browser will have no expiry date, thus will be removed when the browser is closed (unless the default behaviour of your browser is different). | false |
| TRIBEFIRE_USER_SESSIONS_MAX_IDLE_TIME | Specifies how long a user session should remain active when there is no activity on the session. After the specified inactive time has passed (i.e. no request with the corresponding session ID has been received by the server), the session is flagged as inactive and consequently removed by a periodic cleanup process. The time span can be specified as a human-readable string, using numbers and the time unit, as in 12h, 30m, 3600s, etc. | 24h |
Removed Runtime Properties
None.
Known Issues
A list of problems we're aware of and working on.
Known Issues ADx
| Ticket | SEVERITY | Description |
|---|---|---|
| https://jira.braintribe.com/browse/AD-447 | CRITICAL | Potential Race Condition when checkout & updating Content consecutively |
| https://jira.braintribe.com/browse/AD-321 | CRITICAL | Add missing indices |
| https://jira.braintribe.com/browse/AD-354 | CRITICAL | ADx Admin: Problem when synchronizing Type Definitions form DCTM/CMIS |
| https://jira.braintribe.com/browse/AD-350 | CRITICAL | ADx Admin: Repository Activation state sometimes not correct in case of errors |
| https://jira.braintribe.com/browse/AD-306 | CRITICAL | ADx Admin: Demo repository Documentum 6.7 is not working |
| https://jira.braintribe.com/browse/AD-324 | CRITICAL | ADx Content: DCTM/CMIS Repositories throws error on some queries |
| https://jira.braintribe.com/browse/AD-348 | MAJOR | ADx Admin: Repository Modification-Status not updated on Update |
| https://jira.braintribe.com/browse/AD-347 | MAJOR | ADx Admin: Repository Deletion not properly working |
| https://jira.braintribe.com/browse/AD-330 | MAJOR | ADx Content: Missing ADx context information for conversion jobs |
| https://jira.braintribe.com/browse/AD-342 | MINOR | Hibernate warnings in the log files |
| https://jira.braintribe.com/browse/AD-341 | MINOR | Java warnings during for Java 9 and later |
| https://jira.braintribe.com/browse/AD-311 | MINOR | Oracle - DbLockManager prints Oracle constraint message |
Connection refused error for Conversion and Statictics
When using Health/Conversion or Health/Conversion/Conversion Statistics from the admin access, you may get the following error in case the health check page cannot be embedded:
In that case, simply click the indicated icon to open the page in a separate tab, where it should work normally.
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
| Ticket | SEVERITY | Description |
|---|---|---|
| https://jira.braintribe.com/browse/AD-337 | MAJOR | Make TF Conversion workbench consistent to ADx |
| https://jira.braintribe.com/browse/TFSTUD-187 | MINOR | Add diagnostic package for failed resources |
| https://jira.braintribe.com/browse/EXTDOCS-71 | MINOR | Fix wrong encoding on opening resource in Browser |
Minor Warnings
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: 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.