View Issue Details

IDProjectCategoryView StatusLast Update
0004184SymmetricDSBugpublic2019-12-09 12:26
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.10.0 
Target Version3.10.7Fixed in Version3.10.7 
Summary0004184: Incorrect resolver behavior: Failed to find and delete the blocking row
DescriptionIncorrect resolver behavior when two conflicts occur in the same batch and the second conflict is caused by an UPDATE that affects zero rows.

ERROR [client-1] [DefaultDatabaseWriterConflictResolver] [client-1-dataloader-22] Failed to find and delete the blocking row by primary key: DELETE from "DB"."PUBLIC"."MYTEST" where "ID" = ? {2}

For example, a batch that contains an INSERT for a row that already exists, followed by an UPDATE to a row that does not exist. The first conflict gets an exception, but the exception is not cleared from memory. On the second conflict, there is no exception from the database, so it incorrectly uses the first exception to determine its behavior.
TagsNo tags attached.

Relationships

related to 0004185 closedelong Incorrect resolver behavior: Failed to find and delete the blocking row 

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.10 bb5ae6d6

2019-12-05 12:53:44

admin

Details Diff
0004184: Incorrect resolver behavior: Failed to find and delete the
blocking row
Affected Issues
0004184
mod - symmetric-io/src/main/java/org/jumpmind/symmetric/io/data/writer/AbstractDatabaseWriterConflictResolver.java Diff File

Issue History

Date Modified Username Field Change
2019-12-05 12:50 elong New Issue
2019-12-05 12:50 elong Status new => assigned
2019-12-05 12:50 elong Assigned To => elong
2019-12-05 12:54 elong Status assigned => resolved
2019-12-05 12:54 elong Resolution open => fixed
2019-12-05 12:54 elong Fixed in Version => 3.10.7
2019-12-05 12:55 elong Issue cloned: 0004185
2019-12-05 12:55 elong Relationship added related to 0004185
2019-12-05 13:00 admin Changeset attached => SymmetricDS 3.10 bb5ae6d6
2019-12-09 12:26 admin Status resolved => closed