We're updating the issue view to help you get more done. 

O(n+1) Transaction failing to store correctly in tables, after O(n) transaction SQL failure

Description

Replicated using OS 3.2 branching off from https://github.com/roger3cev/obligation-cordapp/tree/release-V3

AB-Testing
Modified the obligation state with additional field called remark and added jpa schemas.

On 3.0

  1. Created an obligation linear state with remark with text larger than 256.

  2. Error is thrown in log.

  3. This tx was recorded in initiator's vault_states, NOT in vault_linear_states, not in obligation_states_table

  4. Nothing is recorded in responder's side.

  5. Created a new obligation linear state with remark with text LESS than 256.

  6. State created successfully.

  7. This tx was recorded in initiator's vault_states, NOT in vault_linear_states, not in obligation_states_table

  8. This tx was recorded in responder's vault_states, vault_linear_states, obligation_states_table

On 3.2

  1. Created an obligation linear state with remark with text larger than 256.

  2. Error is thrown in log.

  3. Nothing is recorded at initiator's side

  4. Nothing is recorded in responder's side.

  5. Created a new obligation linear state with remark with text LESS than 256.

  6. State created successfully.

  7. This tx was recorded in initiator's vault_states, NOT in vault_linear_states, not in obligation_states_table

  8. This tx was recorded in responder's vault_states, vault_linear_states, obligation_states_table

IT IS THE "NEXT" TRANSACTION AFTER THE FAILED TRANSACTION THAT IS THE ISSUE

Status

Assignee

Tudor Malene

Reporter

Neal Shah

Priority

High

Labels

Severity

Medium

Fix versions

Ported to...

None

Feature Team

Corda Core

Affects versions

Corda 3.2