Corda Enterprise release notes

Corda Enterprise 4.8.1

Corda Enterprise 4.8.1 is a patch release of Corda Enterprise that fixes a security vulnerability in Corda Enterprise 4.8.

Upgrade recommendation

As a developer, you should upgrade to the latest released version of Corda as soon as possible. The latest Corda Enterprise release notes are on this page, and you can find the latest upgrade guide here .

As a node operator, you should upgrade to the latest released version of Corda if the fixed issues listed below are relevant to your work.

Fixed issues

In this patch release:

  • Support for Oracle 19C database has been validated.
  • A fix has been introduced to reduce memory consumption during batched transaction resolution of large backchains.
  • Support has been introduced for RedHat Enterprise Linux 8.x in Corda 4.8.1.
  • Performance verification of the HA Notary with CockroachDB 20.2.8 has been carried out - performance is not worse in comparison to the HA Notary configured on CockroachDB 20.1.6.
  • Support for PostgreSQL 13.3 for node databases has been added.
  • Hibernate ORM has been updated to version to 5.4.32 to remove a security concern.
  • The Node management console configuration has been updated. Configuration is now set in node.management.plugin.middleware, no longer node.admin.middleware.
  • The Flow management console configuration has been updated. Configuration is now set in flow.management.plugin.middleware, no longer flow.admin.middleware.
  • LedgerGraph has been updated to version 1.2.2. This upgrade minimizes memory footprint, and is not a functional change.

Corda Enterprise 4.8 release overview

Corda Enterprise 4.8, released on April 21st 2021, includes several new features, enhancements, and fixes.

Long-term support release

Corda 4.8 and Corda Enterprise 4.8 are our long-term support (LTS) platform versions.

R3 provides LTS for this release for 30 months starting April 21st 2021. This is 6 months longer than the support periods for previous releases, giving Corda customers extra time to plan for the next upgrade.

Platform version change

Corda 4.8 uses platform version 10.

For more information about platform versions, see Versioning .

New features and enhancements

Notary database support update

The JPA notary now supports Oracle DB version 19c . This database is supported until April 30th 2027.

Azure managed identities authentication

If you use an Azure Key Vault HSM with Corda Enterprise, you can now use an existing Azure Managed Identities service as authentication.

See Using an HSM with Corda Enterprise for more information.

Time-window metrics gathering

You can now configure timer and histogram metrics to use time-window data gathering. Time-window data gathering collects all data points for a given time window, allowing outlying data points to be properly represented.

See Node metrics for more information.

Additional notary metrics

You can use StartupQueueTime and BatchSignLatency metrics to help calculate notary latency and assess notary worker performance across a notary cluster.

  • StartupQueueTime represents the time a flow has been queued before starting, in milliseconds.
  • BatchSignLatency represents the time elapsed during a batch signature, in milliseconds.

See Monitoring Notary Latency for more information.

Fixed issues

Corda Enterprise 4.8 fixes:

  • A security issue that affects notary systems that use the JPA notary implementation in an HA configuration and when the notary backing database has been set up using the Corda database management tool. The new version of the Corda database management tool must be re-run for the fix to take effect.
  • Several issues that cause memory leaks. As a result, we have added a new node configuration field - enableURLConnectionCache - and we have modified the attachmentClassLoaderCacheSize node configuration field. See the node configuration fields page for details.
  • An issue where the node is unable to resolve transaction chains that contain states or contracts that it did not relate to installed CorDapps.
  • Flow state, invocation source, and suspension source filters breaking in the node GUI.
  • Transaction verification being performed outside of the attachments class loader.
  • HA utilities not logging messages that state that the master key is not needed when using a native mode HSM.
  • HA utilities not logging information about the freshIdentitiesConfiguration.
  • Log messages incorrectly stating that a confidential identity key has been created.
  • An issue that causes the node to hang if shut down using SIGTERM.
  • Attachment presence cache containing the attachment contents.
  • The Corda Firewall throwing an error when retrieving version information.
  • HA utilities creating erroneous logs when using confidential identities.

Known issues

  • An issue with the Oracle 12c database that causes the JDBC driver to hang if blocked by an empty entropy pool.

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.