ACE 3.1.0 includes bug fixes for the permission system and an upgrade to the AWS database driver.
PMC-4921: The Query service no longer returns HTTP 403 when the caller lacks permission on some of the matching content. Inaccessible content is now filtered out instead of failing the entire request.
PMC-4922: The Search service no longer produces queries for the internal (non-public) collection that are incapable of matching ownerless content.
PMC-4897: The AWS JDBC driver has been replaced with the AWS Advanced JDBC Wrapper, as the previous driver has reached end-of-life. The HikariCP database connection pool has also been updated to the latest version.
Installations running on AWS RDS MySQL may need to update their JDBC URL configuration.
AWS RDS MySQL: JDBC URL format change. The previous AWS JDBC driver
included AWS-specific functionality (IAM authentication, failover handling, etc.) automatically
for all jdbc:mysql connections. The new AWS Advanced JDBC Wrapper requires the
URL to be on the form jdbc:aws-wrapper:mysql to activate these features.
Installations using AWS RDS MySQL should update their JDBC URL configuration
accordingly, e.g. jdbc:aws-wrapper:mysql://ace-mysql:3306/ace. Non-AWS
installations using standard jdbc:mysql URLs are not affected.
ACE UI 2.0.2 is a build infrastructure update with no functional changes.
PMC-4886: Node.js upgraded from version 20 to 24. The deprecated
node-sass dependency has been replaced with sass
(Dart Sass).
ACE UI 2.0.1 is a platform upgrade aligning ACE UI with the modernized ACE 3.x runtime. There are no functional changes in this release.
PMC-4866: ACE UI is now built with Java 21 and runs on Jetty 12, matching the platform used by ACE 3.x.
ACE 3.0.1 is a follow-up to ACE 3.0.0 with minor bug fixes and improvements. The primary focus of this release is making the default concurrency behaviour of ACE 3.x more aligned with ACE 2.x, ensuring a smoother upgrade experience for existing installations.
PMC-4856: Default maximum concurrency increased across the board, and new metrics added to track concurrency usage.
PMC-4760: Cookie stores of all HttpClient instances in ACE disabled in order to prevent AWS ELB stickiness.
ACE 3.0.0 is a major platform upgrade. ACE is now built and runs on Java 21 (previously built with Java 8 and running on Java 11) and DropWizard 5.0. This brings ACE onto a modern, long-term supported Java platform with significant improvements to security, performance, and maintainability. All core dependencies have been updated accordingly, including Jetty 12, Jersey 3.x, Jackson 2.19, Guice 7, and the Jakarta EE namespace.
SQL (MySQL) is now the only supported storage backend. Couchbase may still function with ACE 3.0.0 if used together with an older version of kafka-connect (2.8.x), but it is no longer tested, maintained, or supported. Existing Couchbase installations should plan a migration to SQL storage.
PMC-4565: Java 21 runtime (was Java 8). All ACE Docker images are now based on
eclipse-temurin:21-jdk.
PMC-4565: DropWizard 5.0.0 framework (was 1.1.4), including Jetty 12, Jersey 3.1, and the
full javax.* to jakarta.* namespace migration.
PMC-4565: All major dependencies updated. Notable version changes include Jackson 2.19, Guice 7, Guava 33, Kafka client 3.9, SolrJ 8.11, SLF4J 2.0, Mockito 5, and JUnit 5 support.
PMC-4565: HTTP client concurrency model changed from Hystrix THREAD isolation with a blocking connector to SEMAPHORE isolation with a standard async connector. Connection pool defaults have been tuned for more predictable behavior under load.
PMC-4565: Content import file uploads are now throttled to prevent overwhelming the file service under heavy import loads.
PMC-4565: Several potential HTTP connection leak fixes in service-to-service communication, particularly in content resolution and file retrieval operations.
Couchbase as a content storage backend is deprecated and will be removed in a future release. It is no longer tested in CI. Use SQL storage (MySQL) for new deployments.
The Apache Camel integration module (camel-component) is no longer tested
or supported, and will be removed in a future release.
The Swagger UI endpoints have been removed. Use the ACE documentation for API reference.
The following changes may require action when upgrading from ACE 2.x to 3.0.0. Standard Docker-based deployments using the provided images and default configuration files will work without changes, but installations with custom configuration overrides should review the following.
Upgrade to ACE 2.8.2 first. Installations must be running ACE 2.8.2 (or later 2.x) before upgrading to 3.0.0. ACE 2.8.2 includes forward-compatible service-to-service communication that allows 2.x and 3.x services to coexist during rolling deployments. Direct upgrades from older 2.x versions or from 1.x are not supported.
Token key minimum length enforced. The ace.token.key in
token.properties must be at least 32 characters. Keys shorter than this were
previously accepted silently but will now cause a startup failure. Verify your key length
before upgrading.
Environment variable syntax changed. Configuration files now use DropWizard's
built-in substitution: ${VAR:-default} instead of the old
${VAR!"default"} syntax. Custom configuration overrides must be updated.
Note that empty string defaults must use ${VAR:-} (not ${VAR:-""}).
Java 21 and Maven 3.6.3+ required for building projects using ACE dependencies, including the ace-maven-plugin.
ACE annotations plugin 1.3.2+ required. Projects using
ace-annotations-maven-plugin must upgrade to version 1.3.2 or higher for
Java 21 compatibility.
Hystrix metrics stream removed. The /hystrix.stream endpoint
is no longer available. Use the Prometheus /metrics endpoint for monitoring.
The following are release notes for the latest versions of the ACE components.
PMC-4565: ACE 2.x.x is now forwards-compatible with ACE 3.x.x for service-to-service communication. This allows rolling deployments when upgrading from ACE 2.x to 3.0.0, where 2.x and 3.x services can coexist temporarily during the upgrade process. Installations planning to upgrade to ACE 3.0.0 should upgrade to this version first.
Starting with version 2.0.0, ACE UI, ACE CoDE (Content Developer), and ACE Admin are all released together under the same version number. ACE UI remains the name of the underlying UI framework, and the individual applications retain their respective names, but they are now versioned and released as a single bundle.
The following are release notes for the latest versions of the ACE components.
PMC-2639: The ACE Image Service now support watermarking of images. Please see the Image Service documentation for more information.
The following are release notes for the latest versions of the ACE components.
PMC-790: ACE now support exporting content structures as ready-to-import JAR files. Please see the content structure documentation for more information.
PMC-2324: ACE re-indexing operations now process more recently created content before older ones, in order to make sure recent content finish as quickly as possible.
PMC-728: A race condition in the Couchbase to SQL migrator service which could sometimes lead to secondary aliases (not main aliases) not be migrated to the SQL database has been fixed.
PMC-788: ACE Admin now provides an easy way to import either single sections / sites or entire content structures directly into a running ACE installation without having to use content JSON import.
PMC-790: ACE (with UI available in ACE Admin) now support exporting content structures as ready-to-import JAR files. Please see the content structure documentation for more information.
PMC-790: Support for structure export in ACE Admin.
The following are release notes for the latest versions of the ACE components.
PMC-521: It is now possible to re-index content in a specific date range. Please see the ACE re-indexing documentation for more information
PMC-1863: ACE is now verified to be compatible with Kafka 3.5.1 and 3.6.0 in addition to the already tested 3.2.0.
The following are release notes for the latest versions of the ACE components.
PMC-1761: Kafka Connect (Debezium Connect) has been upgraded to version 2.6.1 and now also has a health check available at /healthcheck on the traffic port.
PMC-1750: The ACE Query service will no longer return soft-deleted content.
PMC-1652: It should now be possible to disable the search and indexing service Solr authentication using the enabled configuration property instead of having to completely remove the authentication configuration.
The following are release notes for the latest versions of the ACE components.
PMC-1149: Attempting to open a content with a content type for which there isn't any template will now result in a read-only JSON view of the content data instead of an error.
The following are release notes for the latest versions of the ACE components.
PMC-792: The ACE indexing and search services now support Solr basic authentication. Please see the ACE documentation for more information.
The following are release notes for the latest versions of the ACE components.
PMC-813: It is now possible to query the content repository for specific types of content - for example content of a specific content type - using the new Query service (part of the Content Service). Please see the ACE documentation for more information.
PMC-813: It is now possible to configure the Content Developer left-hand side structure panel using a structure query using the ACE Query service (see release note for ACE 2.3.0 above) instead of manually configuring a list of root aliases. Please see the Content Developer documentation for more information.
The following are release notes for the latest versions of the ACE components.
PMC-213: The File Service can now utilise the default credentials chain of the AWS SDK in cases where no explicit keys have been supplied. This will work with standard AWS environment variables like AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY as well as credentials context automatically available inside ECS containers and EC2 instances.
The following are release notes for the latest versions of the ACE components.
PMC-644: The Content Service now exports Prometheus metrics for the JDBC connection pool, such as number of active and idle connections.
The following are release notes for the latest versions of the ACE components.
PMC-630: The Couchbase to MYSQL migrator should now be able to handle cases where the same version ID string (the 'Y' part of the form c:X:Y) have been generated for more than one version within a single content. In an ACE Couchbase installation this is not an issue since the version ID of a version is the full string on the form c:X:Y, but in an ACE MySQL installation the version ID part is used as a key and needs to be unique across all versions.
The following are release notes for the latest versions of the ACE components.
AD-443: The Image service should now correctly handle delivering monochrome (grayscale) images as webp.
The following are release notes for the latest versions of the ACE components.
PMC-572: A bug has been fixed where the Couchbase to MySQL migrator service was unable to migrate content with view events referencing non-existing versions.
The following are release notes for the latest versions of the ACE components.
PMC-527: A bug has been fixed where the ACE SQL storage could assign two primary aliases to a content when promoted from a workspace, which would lead to the content being unable to be read after that.
PMC-515: The Content Service should no longer try to create SQL storage instances when running Couchbase. NOTE: these storages were never actually used, but created unnecessarily.
The following are release notes for the latest versions of the ACE components.
AD-447: The ACE Image Service no longer reads the image file data into memory before it gets its turn in queue for processing. This makes sure the service doesn't get overwhelmed by incoming queued image requests and should prevent unnecessary out-of-memory errors.
PMC-381: Aliases created by the ACE SQL storage in the Content Service now creates the aliases one by one instead of in a batch, which makes it easier for any error message to contain accurate information.
The following are release notes for the latest versions of the ACE components.
AD-445: ACE version 2.x.x is now implicitly considered API compatible with version 1.x.x. Normally client and server (which are usually both ACE services) have to use the same major version of the API, but major 1 and 2 are actually compatible even though they are not the same.
The following are release notes for the latest versions of the ACE components.
AD-446: The registration of the Kafka Connect MySQL connector now expects an environment variable input for ID to use when registering inside the MySQL cluster; it was previously hard-coded. This makes it possible to use several Kafka Connect MySQL connectors inside the same MySQL cluster without manually changing the configuration.
Please see the documentation for more information.
AD-445: ACE version 2.x.x is now implicitly considered API compatible with version 1.x.x. Normally client and server (which are usually both ACE services) have to use the same major version of the API, but major 1 and 2 are actually compatible even though they are not the same.
The following are release notes for the latest versions of the ACE components.
AD-354: ACE now support SQL (MySQL) storage in addition to the existing Couchbase support. Migration from Couchbase to SQL storage is possible with the help of the ACE SQL Migrator service which can be used to continuously migrate from a running Couchbase server into a MySQL server. Documentation for this will be coming shortly.
Please see the general installation documentation for an overview.
Looking for older release notes? See ACE 1.x release notes (1.19.0 - 1.22.3).