View Issue Details

IDProjectCategoryView StatusLast Update
0003575SymmetricDSBugpublic2019-04-24 14:26
ReporterzulusAssigned Tommichalek 
Prioritynormal 
Status closedResolutionfixed 
Product Version 
Target VersionFixed in Version3.9.19 
Summary0003575: Starting a new process even though the previous 'File Sync Push' process had not finished
DescriptionMy log is full of such messages
Starting a new process even though the previous 'File Sync Push' process had not finished
Details from the previous process: processType=File Sync Push,sourceNodeId=000,targetNodeId=001,queue=null,status=New,startTime=Wed May 23 14:04:43 CEST 2019

I'm using sym_service on one server, multiple channels and queues. Synchronization between postgresql and oracle on highly load database.
TagsNo tags attached.

Relationships

related to 0003913 closedmmichalek Exception during keep alive can cause concurrent loading of batches 

Activities

abrougher

2018-05-23 12:44

developer   ~0001191

There was a similar data sync issue handled recently by sending keep alive messages. We should use this same method when working with file sync.

The work around for now would be to update the timeouts.

Update SDS Parameter http.timeout.ms from 90000 to a larger value.

In bin/setenv or sym_service.conf increase the value of the defaultReadTimeout property.

Issue History

Date Modified Username Field Change
2018-05-23 08:17 zulus New Issue
2018-05-23 12:44 abrougher Note Added: 0001191
2019-04-24 14:25 elong Relationship added related to 0003913
2019-04-24 14:26 elong Assigned To => mmichalek
2019-04-24 14:26 elong Status new => closed
2019-04-24 14:26 elong Resolution open => fixed
2019-04-24 14:26 elong Fixed in Version => 3.9.19