View Issue Details

IDProjectCategoryView StatusLast Update
0004275SymmetricDSBugpublic2024-05-22 17:13
Reportermnaccari Assigned To 
Prioritynormal 
Status closedResolutionunable to reproduce 
Product Version3.11.4 
Summary0004275: Initial Load does not work anymore - due to cache problems
DescriptionHi guys,
it seems that migrating from 3.11.0 to 3.11.4 initial load doesn't work anymore.

For some reasons, createData() returns null. If createData() fails it throws an exception, so the only reason Data data is null is that TriggerRouterService.getTriggerRouterForTableForCurrentNode() returns an empty set, but, "sym_trigger_router" table is not empty for sure.

After restarting Sym service it finally recognize the new configurations and loads the data, so probably it does not refresh the cache or the TTL (if any, because ) is too much high.

2020-02-05 15:20:31,624 INFO [master-0000] [InitialLoadService] [master-0000-job-17] Found 1 table reload requests to process.
2020-02-05 15:20:31,631 INFO [master-0000] [DataService] [master-0000-job-17] Queueing up an initial load to node farmacia-entro.milano
2020-02-05 15:20:31,648 ERROR [master-0000] [InitialLoadService] [master-0000-job-17] Error while queuing initial loads
org.jumpmind.symmetric.SymmetricException: Unable to issue an update for sym_node_security. Check the sym_trigger_hist for sym_node_security.
        at org.jumpmind.symmetric.service.impl.DataService.insertNodeSecurityUpdate(DataService.java:2143)
        at org.jumpmind.symmetric.service.impl.DataService.insertSqlEventsPriorToReload(DataService.java:1176)
        at org.jumpmind.symmetric.service.impl.DataService.insertReloadEvents(DataService.java:940)
        at org.jumpmind.symmetric.service.impl.InitialLoadService.processTableRequestLoads(InitialLoadService.java:243)
        at org.jumpmind.symmetric.service.impl.InitialLoadService.queueLoads(InitialLoadService.java:94)
        at org.jumpmind.symmetric.job.InitialLoadJob.doJob(InitialLoadJob.java:43)
        at org.jumpmind.symmetric.job.AbstractJob.invoke(AbstractJob.java:227)
        at org.jumpmind.symmetric.job.AbstractJob.run(AbstractJob.java:298)
        at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)
TagsNo tags attached.

Activities

jvanmeter

2024-05-08 17:46

developer   ~0002446

Are you automating something? This looks like the second the node gets registered it kicks off an initial load before there is time to run sync triggers, resulting in this issue.

Issue History

Date Modified Username Field Change
2020-02-05 15:56 mnaccari New Issue
2024-05-08 17:46 jvanmeter Status new => feedback
2024-05-08 17:46 jvanmeter Note Added: 0002446
2024-05-22 17:13 emiller Status feedback => closed
2024-05-22 17:13 emiller Resolution open => unable to reproduce