| VMware Blockchain 1.1.0.2 | 08 APR 2021 | Build XX Check for additions and updates to these release notes. |
What's in the Release Notes
The release notes cover the following topics:What's New
VMware Blockchain is an enterprise-grade blockchain platform that meets the needs of business-critical multi-party workflows. The VMware Blockchain release includes the following new features and enhancements:
Component Versions
The supported domain versions include:
| Domain | Version |
|---|---|
| VMware Blockchain Platform |
|
| VMware Blockchain Orchestrator |
|
| DAML SDK |
The VMware products and solutions discussed in this document are protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware is a registered trademark or trademark of VMware, Inc. and its subsidiaries in the United States and other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies.
Known Issues
- Possible performance degradation after continuous high transaction load for an extended time frame
Running a blockchain deployment under a continuous high transaction load for over 30 hours could lead to an observable degradation in the throughput performance of the system.
Workaround: None
- VMware Blockchain does not support a specific version of the ELK stack
Environment specific configurations might be required to your default ELK stack settings to ensure that the collected metrics information is accurate.
Workaround: Contact your VMware Blockchain technical specialist for assistance with ELK stack configurations.
- Time across the Replica and Client nodes becomes inaccurate if the NTP service is down or not synchronized
If the NTP service is down or not synchronized, the time across Replica and Client nodes might become inaccurate leading to data discrepancies or cause errors in the DAML Ledger API.
Workaround: To avoid any DAML Ledger API errors and data discrepancies, you must keep the NTP service up and synchronized to ensure that all the servers running VMware Blockchain reflect the accurate time.
- Configured CLIENT_AUTH parameter value is not implemented in the DAML Ledger API
If you change the ClientAuth parameter value to mandatory during the deployment process, the deployed DMAL Ledger defaults to the optional value.
Workaround: The optional client auth works with both empty and mTLS values. The DAML Ledger API can be configured to communicate over TLS or over plain text depending on whether the files are provided.
- The --client-auth parameter to enable server-side TLS on the DAML Ledger API is not recognized
The connection to the DAML Ledger API can be either in plain text or encrypted using TLS. By default, the TLS settings require the Client node certificates for mutual TLS (mTLS) authentication. The command line parameter --client-auth to disable Client node authentication is not recognized.
Workaround: Either use certificates for the applications connecting to the DAML Ledger API or disable TLS altogether.
