View Issue Details

IDProjectCategoryView StatusLast Update
0006129SymmetricDSImprovementpublic2023-11-28 21:00
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.12.22 
Target Version3.12.24Fixed in Version3.12.24 
Summary0006129: Too many "Expected but did not receive an ack for batch"
DescriptionSome deployments receive too many log entries for "Expected but did not receive an ack for batch" because any exception, including network errors, is causing the logic to run that looks for missing acks due to batch corruption. It should only run the logic for a ProtocolException. Also, when a corrupt batch is detected on the receiving side, it immediately throws an exception, which prevents subsequent batches from being received. For example, server sends batches 1 through 10 to client, but batch 5 has corruption, so client immediately stops with only batches 1 through 4 and acknowledges them. The server logic removes batches 5 through 10 from staging, but only batch 5 needs to be removed.
TagsNo tags attached.

Relationships

related to 0005690 closedelong Pulling corrupted batch gets null pointer in loop 
related to 0006130 closedelong Too many "Expected but did not receive an ack for batch" 

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.12 fa090562

2023-11-28 20:16:23

admin

Details Diff
0006129: Too many "Expected but did not receive an ack for batch" Affected Issues
0006129
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/io/stage/SimpleStagingDataWriter.java Diff File
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/AcknowledgeService.java Diff File
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/DataLoaderService.java Diff File

Issue History

Date Modified Username Field Change
2023-11-28 20:15 elong New Issue
2023-11-28 20:15 elong Status new => assigned
2023-11-28 20:15 elong Assigned To => elong
2023-11-28 20:15 elong Relationship added related to 0005690
2023-11-28 20:16 elong Status assigned => resolved
2023-11-28 20:16 elong Resolution open => fixed
2023-11-28 20:16 elong Fixed in Version => 3.12.23
2023-11-28 20:17 elong Fixed in Version 3.12.23 => 3.12.24
2023-11-28 20:17 elong Issue cloned: 0006130
2023-11-28 20:17 elong Relationship added related to 0006130
2023-11-28 21:00 admin Changeset attached => SymmetricDS 3.12 fa090562
2023-12-16 01:56 admin Status resolved => closed