View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003575||SymmetricDS||Bug||public||2018-05-23 08:17||2018-05-23 12:44|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0003575: Starting a new process even though the previous 'File Sync Push' process had not finished|
|Description||My 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.
|Tags||No tags attached.|
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.