Archive Service release notes

The Archive Service is a standalone service that operates on a different release cadence to the Corda platform.

In this release:

  • Previously, an issue occurred where the Archive Service misunderstood reference states. This would prevent a transaction from being archivable if it referenced an unconsumed transaction and did not have any unconsumed transactions that referenced it.

    Now, a transaction that only has outbound references (to unconsumed transactions) and no inbound references (from unconsumed transactions) will be marked as archivable by the Archive Service. Any inbound references will still make a transaction unarchivable.

In this release:

  • Previously, when using a Microsoft SQL Server database, an error was generated when using the vault-states filter with a positive value specified for the retentionDays parameter; this issue has been resolved.

In this release:

  • A new configuration option has been added which allows the Archive Service to ignore transactions that cause failures when exporting a JSON snapshot. For more information, see the Archive Service documentation.

In this release:

  • Improved Archiving support of tokens when they are moved between more than one party and then redeemed.
  • Logging of the Archiving tool has been increased to aid in troubleshooting.
  • The Archiving client can now connect to nodes which are set up to use RPC SSL connection settings.
  • Tables are now ordered by table name length in descending order to prevent foreign key constraints from being violated when deleting rows.

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.