View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005692SymmetricDSBugpublic2023-02-06 20:472023-11-28 20:35
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.8.0 
Target Version3.14.5Fixed in Version3.14.5 
Summary0005692: Pulling corrupted batch gets null pointer in loop
DescriptionWhen a batch is pulled and written to staging, if the "batch" token is missing (corrupted file on source), the writer will get a NullPointerException. There is not a batch ID to acknowledge, so the same batch will be pulled and get the same error. The user must manually clear the batch from staging on the source.

2023-02-01 12:00:00,000 ERROR [client-A] [SimpleStagingDataWriter] [client-a-pull-default-1] Failed to write batch into staging from server:000:000. java.lang.NullPointerException: null

The client should log that the incoming batch is corrupt and acknowledge the server that one of the batches it sent were corrupt. The server should remove any batches from staging that did not get an acknowledgement.
Tagsdata sync

Relationships

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

Activities

elong

2023-02-06 20:47

developer   ~0002256

Cherry-picked commit up from 3.13

Issue History

Date Modified Username Field Change
2023-02-06 20:47 elong New Issue
2023-02-06 20:47 elong Status new => assigned
2023-02-06 20:47 elong Assigned To => elong
2023-02-06 20:47 elong Tag Attached: data sync
2023-02-06 20:47 elong Issue generated from: 0005691
2023-02-06 20:47 elong Relationship added related to 0005691
2023-02-06 20:47 elong Status assigned => resolved
2023-02-06 20:47 elong Resolution open => fixed
2023-02-06 20:47 elong Fixed in Version => 3.14.5
2023-02-06 20:47 elong Note Added: 0002256
2023-02-15 20:26 admin Status resolved => closed
2023-11-28 20:35 elong Relationship added related to 0006131