Menu

Ack was not sent successfully on try number X

Help
2017-05-03
2021-03-10
  • Aaron Lease

    Aaron Lease - 2017-05-03

    Hi,

    I'm using:

    • SymmetricDS 3.8.21
    • Server Node: MS SQL Server
    • Client Nodes: SQLite

    I'm getting this error intermitently, but more often now for whatever reason. Just tried to sync 3 new clients, and all 3 got this error.

    When a client node tries to connect to the Server for the first time:

    1.) Registration begins
    2.) SQLite DB file gets created on client
    3.) sym_tables are created on client DB
    4.) triggers on the database I'm replicating get created on client DB
    5.) "Done synchronizing triggers"
    6.) then I see "Ack was not sent successfully..."

    After that the SQLite DB locks up and initial load never takes place.

    This happens every now and then - to fix I've had to delete client DB and "tmp" directory and start the SymmetricDS service up again and hope it works.

    Below is the log portion.

    Any advice would be appreciated :-)

    Regards,
    Aaron von Awesome



    2017-05-03 16:58:33,091 INFO [sqliteclient-001] [TriggerRouterService] [sqliteclient-001-job-1] Done synchronizing triggers
    2017-05-03 16:58:54,706 WARN [sqliteclient-001] [DataLoaderService] [sqliteclient-001-job-1] Ack was not sent successfully on try number 1.  
    2017-05-03 16:58:54,784 WARN [sqliteclient-001] [DataLoaderService] [sqliteclient-001-job-1] Ack was not sent successfully on try number 2.  
    2017-05-03 16:58:59,869 WARN [sqliteclient-001] [DataLoaderService] [sqliteclient-001-job-1] Ack was not sent successfully on try number 3.  
    2017-05-03 16:59:04,950 WARN [sqliteclient-001] [DataLoaderService] [sqliteclient-001-job-1] Ack was not sent successfully on try number 4.  
    2017-05-03 16:59:10,031 WARN [sqliteclient-001] [DataLoaderService] [sqliteclient-001-job-1] Ack was not sent successfully on try number 5.  
    2017-05-03 16:59:10,035 WARN [sqliteclient-001] [PullService] [sqliteclient-001-job-1] Could not communicate with node 'server:000:000' at https://awesomeurl.com:443/sync/server-000 because of unexpected error StackTraceKey.init [IOException:1713856479]
    java.io.IOException: 657
        at org.jumpmind.symmetric.service.impl.AbstractService.sendAck(AbstractService.java:289)
        at org.jumpmind.symmetric.service.impl.DataLoaderService.loadDataFromPull(DataLoaderService.java:311)
        at org.jumpmind.symmetric.service.impl.DataLoaderService.loadDataFromPull(DataLoaderService.java:335)
        at org.jumpmind.symmetric.service.impl.PullService.execute(PullService.java:126)
        at org.jumpmind.symmetric.service.impl.NodeCommunicationService$1.run(NodeCommunicationService.java:499)
        at org.jumpmind.symmetric.service.impl.NodeCommunicationService.execute(NodeCommunicationService.java:513)
        at org.jumpmind.symmetric.service.impl.PullService.pullData(PullService.java:97)
        at org.jumpmind.symmetric.job.PullJob.doJob(PullJob.java:54)
        at org.jumpmind.symmetric.job.AbstractJob.invoke(AbstractJob.java:172)
        at org.jumpmind.symmetric.job.AbstractJob.run(AbstractJob.java:219)
        at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
    
     
  • Charming Man

    Charming Man - 2021-03-04

    Hi,

    Did you resolve or find solution for this? If yes, please guide me.

    Thanks in advance.

     
  • Josh Hicks

    Josh Hicks - 2021-03-10

    This has been resolved in 3.12.7. Let us know if you are still running into the issue

     

Log in to post a comment.