CODEWITHSUNDEEP
corda
JohnZ
JohnZ

Reputation: 144

Soft lock update error

We do explicit soft-locking with serviceHub.vaultService.softLockReserve(txBuilder.lockId, NonEmptySet.of(balanceStateS2R.ref))

Things were working until today when we got this exception repeatedly.
And now we cannot run the flow anymore. There was no double-spend going on. What is causing it and how can we get out of it?

[m[1;31mE 17:01:57-0500 [Node thread] vault.NodeVaultService.softLockReserve - soft lock update error attempting to reserve states for acace05e-b0fb-4d4e-9b96-a7d0d4728f68 and [392D84F9CF931F17438399D36607CAFDB549C02A5E7B63E8F8D2B2FADE1AFF57(1)]") Soft locking error: Attempted to reserve [392D84F9CF931F17438399D36607CAFDB549C02A5E7B63E8F8D2B2FADE1AFF57(1)] for acace05e-b0fb-4d4e-9b96-a7d0d4728f68 but only 0 rows available.

Upvotes: 1

Views: 200

Answers (1)

Jose Coll
Jose Coll

Reputation: 246

Without more context (e.g. what actions the flow is executing), I cannot provide an accurate answer, but some points to raise:

  • The error message indicates that the previously locked state has been consumed in some way (perhaps by the flow that originally locked it) and was not explicitly released after consumption
  • Use the softLockRelease() API call to explicitly release states that have been explicitly previously locked

Upvotes: 1

Related Questions