View Issue Details

IDProjectCategoryView StatusLast Update
0006433SymmetricDSBugpublic2024-05-17 21:00
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.15.0 
Target Version3.15.7Fixed in Version3.15.7 
Summary0006433: Exception when auto resolver tries to lock row in conflict
DescriptionNumberFormatException when auto resolver tries to lock row in conflict because the primary key on target table is different than batch. It locks the current row in conflict by using an update of the row before it queries the change log for a newer change. It mismatches the values with columns in the where clause because it expects the PK in batch to match the target table.

[DefaultDatabaseWriter] [dataloader-169298] Failed to process delete event in batch 1-263660 on channel 'default'.
Failed pk data was: "1159990"
Failed old data was: "1159990","256405001","4","SHIPPING","930","15169995"
 StackTraceKey.init [RuntimeException:4199732638] java.lang.RuntimeException: Could not convert a value of SHIPPING: 0 Destination(s) for column task_id of mapped type INTEGER jdbc type INT (4)
    at org.jumpmind.db.platform.AbstractDatabasePlatform.getObjectValues(AbstractDatabasePlatform.java:416)
    at org.jumpmind.db.platform.AbstractDatabasePlatform.getObjectValues(AbstractDatabasePlatform.java:398)
    at org.jumpmind.symmetric.io.data.writer.DefaultDatabaseWriterConflictResolver.isCaptureTimeNewer(DefaultDatabaseWriterConflictResolver.java:142)
    at org.jumpmind.symmetric.io.data.writer.AbstractDatabaseWriterConflictResolver.needsResolved(AbstractDatabaseWriterConflictResolver.java:152)
    at org.jumpmind.symmetric.io.data.writer.AbstractDatabaseWriter.write(AbstractDatabaseWriter.java:204)
    at org.jumpmind.symmetric.io.data.writer.NestedDataWriter.write(NestedDataWriter.java:62)
    at org.jumpmind.symmetric.model.ProcessInfoDataWriter.write(ProcessInfoDataWriter.java:98)
    at org.jumpmind.symmetric.io.data.writer.NestedDataWriter.write(NestedDataWriter.java:62)
    at org.jumpmind.symmetric.io.data.writer.TransformWriter.write(TransformWriter.java:186)
    at org.jumpmind.symmetric.io.data.DataProcessor.forEachDataInTable(DataProcessor.java:194)
    at org.jumpmind.symmetric.io.data.DataProcessor.forEachTableInBatch(DataProcessor.java:160)
    at org.jumpmind.symmetric.io.data.DataProcessor.process(DataProcessor.java:108)
    at org.jumpmind.symmetric.service.impl.DataLoaderService$LoadIntoDatabaseOnArrivalListener$2.call(DataLoaderService.java:1076)
    at org.jumpmind.symmetric.service.impl.DataLoaderService$LoadIntoDatabaseOnArrivalListener$2.call(DataLoaderService.java:1052)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
    at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.NumberFormatException: For input string: "SHIPPING"
    at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67)
    at java.base/java.lang.Integer.parseInt(Integer.java:668)
    at java.base/java.math.BigInteger.<init>(BigInteger.java:538)
    at java.base/java.math.BigInteger.<init>(BigInteger.java:676)
    at org.jumpmind.db.platform.AbstractDatabasePlatform.parseInteger(AbstractDatabasePlatform.java:521)
    at org.jumpmind.db.platform.AbstractDatabasePlatform.getObjectValue(AbstractDatabasePlatform.java:452)
    at org.jumpmind.db.platform.AbstractDatabasePlatform.getObjectValues(AbstractDatabasePlatform.java:410)
    ... 17 more
Tagsconflict manager

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.15 99c3a41b

2024-05-17 20:44:38

admin

Details Diff
0006433: Exception when auto resolver tries to lock row in conflict Affected Issues
0006433
mod - symmetric-io/src/main/java/org/jumpmind/symmetric/io/data/writer/DefaultDatabaseWriterConflictResolver.java Diff File

Issue History

Date Modified Username Field Change
2024-05-17 20:41 elong New Issue
2024-05-17 20:41 elong Status new => assigned
2024-05-17 20:41 elong Assigned To => elong
2024-05-17 20:41 elong Tag Attached: conflict manager
2024-05-17 20:44 elong Status assigned => resolved
2024-05-17 20:44 elong Resolution open => fixed
2024-05-17 20:44 elong Fixed in Version => 3.15.7
2024-05-17 21:00 admin Changeset attached => SymmetricDS 3.15 99c3a41b
2024-06-07 16:46 admin Status resolved => closed