VMware Blockchain 1.0.0.2 | 07 JAN 2021 | Build 1.0.0.2.92 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
• Component Versions
• Known Issues

What's New

VMware Blockchain is an enterprise-grade blockchain platform that meets the needs of business-critical multi-party workflows. This patch release includes a DAML execution engine (DAMLe) fix.

Fixed an integrity issue in the DAMLe.

This issue occurred when two or more transactions using the same contract key were evaluated at the same time. In this scenario, both transactions would be committed to the DAML ledger, resulting in two contracts with the same contract key being active, violating contract key uniqueness.

Component Versions

The supported domain versions include:

Domain	Version
VMware Blockchain Platform	1.0.0.2.92
VMware Blockchain Orchestrator	1.0.0.67
DAML SDK	1.6.1

^{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.

• Cannot submit DAML transactions right after deployment

  If you submit a DAML transaction before the entire system is up and running, you receive the following error message from the DAML Ledger API,  UNAVAILABLE: The ledger configuration is not available.

  Workaround: Complete the following steps:

  1. Run the DAML transaction.
  2. Check if the transaction completes successfully.
  3. Verify that the key generation is completed successfully.
  4. Verify that in the Concord logs, all the replica node exchanged keys can start accepting messages.
  5. If the transaction fails, restart the DAML Ledger API and resubmit your DAML transaction.
• In rare cases, a Replica node might remain in an infinite state transfer loop regardless of the incoming rate

  If the Concord logs on a given node indicate to remain in the state transfer mode with a block gap up to 300, then state transfer is in an infinite loop. The blockchain system continues to function if 2f+1 Replica nodes are in consensus.

  Workaround: Complete the following steps:

  1. In the Concord logs, search for the Start fetching checkpoint entry.
     The block gap is the difference between the newCheckpoint.lastBlock:2352173 and lastReachableBlockNum:2351979.
  2. Refer to the instructions in the Backup and Restore run book to restore the state from another Replica node.
• Storage size might increase without any transactions in the system

  With time service, requests are generated every second. All the Replica nodes add seven requests even if there are no transactions in the system.

  Workaround: None

• When you disconnect and connect a Replica node from the network, the disconnected Replica node might show up in the advanced view

  When you disconnect and connect a Replica node from the network, the disconnected Replica node might show up in an advanced view. After the Replica is connected, the Replica node initiates the state transfer and remains in the previous view.

  Workaround: Complete the following steps:

  1. Use Wavefront to verify that the state transfer has been completed.
  2. If the Replica is in the advanced view, induce a view change.
  3. If the state transfer is in an infinite loop, refer to the instructions in the Backup and Restore run book to restore the state from another Replica node.