P
peggycole
Guest
Hi Sam, Pro2 is taking care of the locking because in the logfiles of the thread you can find things like this: 06-06-2018 15:08:22 - Replication Queue Finished (ReplBlock). Processed a total of 216 records. Total time to process these items was: 00:00:01 06-06-2018 15:08:22 - 3 records were locked, and 3 transactions were open during this run. Every run it checks whether the records are available and unlocked yet or not. If not, they are not processed and re-checked every run till they are. But I guess we have the same issue as you. In the past 2 months it happened 3 times. The thread crashes and after a restart, it crashes immediately. I guess, it is not the replqueue-record that is locked because I'm able to change the replqueue.qthread-field of that record (I change it to 6 so no other thread will pick it up). After changing the thread of the first replqueue-record that is not yet applied, pro2 works fine. I have no clue how this can happen, I'm still in "investigation phase".. Pro2 version 5.0.2. Kind regards, Peggy
Continue reading...
Continue reading...