Corda Community Edition 4.9 release notes
Corda Community Edition 4.9.9 release notes
Corda Community Edition 4.9.9 is a patch release of Corda Community Edition focused on resolving issues.
Fixed issues
- In the default log4j2.xml file, the Delete action in the DefaultRolloverStrategy policy for log files beginning with
diagnostic-*
orcheckpoints_agent-*
was incorrect. It erroneously compared against the wrong file names. This issue has been rectified, ensuring that files are now deleted in accordance with the policy. - Previously, a rare error scenario could occur where a node would erroneously perceive a valid connection to a peer when, in fact, it was not connected. This issue typically arose when the peer node was disconnecting/connecting.
Third party component upgrades
- Jetty version was upgraded from 9.4.51.v20230217 to 9.4.53.v20231009.
Corda Community Edition 4.9.8 release notes
Corda Community Edition 4.9.8 is a patch release of Corda Community Edition focused on resolving issues.
Fixed issues
- Some log messages at warning level relating to failed SSL handshakes were accidentally introduced as part of improvements to SSL certificate handling in the previous patch release, and would appear frequently in the logs as part of connectivity tests of traffic load balancers and system monitoring. These log messages have been silenced to reduce “noise” in the logs.
- Node thread names have been made more specific to make logging more descriptive and debugging easier.
- Delays when SSL handshaking with new nodes no longer impact existing connections with existing nodes.
- An issue has been resolved where, sometimes, the order of the states returned by a vault query would be incorrect if they belonged to the same transaction.
- An issue has been resolved where, previously, an incorrect value for
Page.totalStatesAvailable
was returned for queries onexternalIds
, when there where external IDs mapped to multiple keys.
Corda Community Edition 4.9.7 release notes
Corda Community Edition 4.9.7 is a patch release of Corda Community Edition which includes resolved issues.
Fixed issues
Debug logging of the Artemis server has been added.
The SSL handshake timeout for inbound connections has been increased to 60 seconds. If during SSL handshake, certificate revocation lists (CRLs) take a long time to download, or are unreachable, then this 60 seconds gives the node enough time to establish the connection if crlCheckSoftFail is enabled.
Corda provides the NodeDriver to help developers write integration tests. Using the NodeDriver, developers can bring up nodes locally to run flows and inspect state updates. Previously, there was an issue with build pipelines with tests failing, as on some occasions, notaries took more than one minute (the default timeout value) to start.
To resolve this, the NodeDriver now has a new parameter, notaryHandleTimeout. This parameter specifies how long to wait (in minutes) for a notary handle to come back after the notary has been started.
The certificate revocation checking has been improved with the introduction of a read timeout on the download of the certificate revocation lists (CRLs). The default CRL connect timeout has also been adjusted to better suit Corda nodes. The caching of CRLs has been increased from 30 seconds to 5 minutes.
Corda Community Edition 4.9.6 release notes
Corda Community Edition 4.9.6 is a patch release of Corda Community Edition to keep it synchronised with the release of Corda Enterprise Edition 4.9.6.
Corda Community Edition 4.9.5 release notes
Corda Community Edition 4.9.5 is a patch release of Corda Community Edition which includes resolved issues.
Fixed issues
Previously, a memory leak in the transaction cache occurred due to the weight of in-flight entries being undervalued. Improvements have been made to prevent in-flight entry weights from being undervalued and because they are now estimated more correctly, this results in a large decrease in the total size of cached entities.
A rare condition was fixed relating to roll back of database transactions under heavy load, which caused flow state machine threads to stop processing flows, leading to eventual node lock up in certain circumstances.
Corda Community Edition 4.9.2 release notes
Corda Community 4.9.2 is a patch release of Corda Community which includes the addition of a new Gradle 7 plugin, security upgrades, and fixes for minor bugs.
Fixed issues
- As part of this patch a new Gradle plugin is provided that supports CorDapp development using Gradle 7. This is in addition to the existing Gradle support. The plugin has been uploaded to Artifactory.
- Artemis messaging has been implemented to indicate when disk space is low (below 10%).
- AMQP frame tracing can now be enabled in the Corda node when running embedded Artemis or bridges. This is in addition to the previous ability to turn it on via firewall configuration.
Fixed issues
The following issues were resolved in this patch release:
- The
corda-shell --version
command has been updated to always return the correct version. - The time it takes for first-time flows to be run in a signed CorDapp has been significantly reduced.
- Java serialization has been disabled in the Corda firewall, closing a potential security vulnerability.
Third party component upgrades
Library | Version 4.9.2 | Previous version |
---|---|---|
Caffeine | 2.9.3 | 2.7.0 |
Jackson | 2.13.3 | 2.13.1 |
Netty | 4.1.77.Final | 4.1.68.Final |
Quasar | 0.7.15_r3 | 0.7.14_r3 |
Shiro | 1.9.1 | 1.4.1 |
Corda Community Edition 4.9.1 release notes
Corda Community Edition 4.9.1 is a patch release of Corda Community Edition which includes minor bug fixes and dependency upgrades.
Fixed issues
In this patch release:
- Fixing of a bug where
SuspensionMeta
inFlowInfo
shows as null even when a runnable flow has previously been hospitalized. - Update Hibernate version to a more secure version that matches Corda Enterprise.
- Oracle JDK version 8u322 now supported.
Corda Community Edition 4.9 release notes
Corda Community Edition is here. This edition of Corda gives you the freedom of Corda’s Community Edition platform, with the benefits of affordable support. All the same fundamentals of Corda 4.8 are included, along with security updates, newly available APIs and sample code improvements. You can upgrade your existing Corda projects to Community Edition any time to be eligible for our support packages.
Highlights
The Corda Community Edition features:
- Support for your open source projects. Find out more about available support and how to upgrade.
- An open source version of network map and doorman is available and recommended for Community Edition users, provided by Cordite.
- Community Edition Docker images are now available.
- Access to node health data and node status.
Platform version change
Corda 4.9 uses platform version 11.
For more information about platform versions, see Versioning.
Fixed issues
Issues fixed in Corda Community 4.9:
- Corda Shell has been removed to its own repository for improved security. You can now use a standalone shell outside of the node, or from within the node’s drivers. You can read more about using the standalone shell here.
- Security updates to prevent possibility of Denial of Service attacks.
- Improvements to demos and sample code.
- Improvements to improve compatibility with Intel Macs.
- An issue affecting Node JVM deadlocks is resolved.
- An issue with failed attachments from a notary has been fixed.
- An issue preventing attachments to subflows in certain circumstances has been fixed.
Database Schema Changes
The
node_named_identities
table has been re-introduced. It was removed in Corda Enterprise Edition 4.7 following updates to certificate rotation functionality.The reintroduction of this table ensures that the behavior of
rpcOps.wellKnownPartyFromX500Name
is identical for both revoked and non-revoked identities.
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.