What steps will reproduce the problem?
1. use the replicator (build 145) in --direct mode for a while
2. set the replicator offline and then online again (or restart the replicator)
3. Check the replicator logs
What is the expected output?
Replicator goes online, jumping at the event where it was before
What do you see instead?
The log files are flooded with lines like this:
INFO | jvm 1 | 2011/06/29 10:42:21 | 2011-06-29 10:42:21,662 INFO
replicator.applier.JdbcApplier Skipping over previously applied event:
seqno=238042 fragno=0
In this particular case, the online operation lasted about 2 minutes, and 3
additional log files were created, all filled with lines like the above one,
from 0 to 238042
Original issue reported on code.google.com by g.maxia on 29 Jun 2011 at 8:55
Original issue reported on code.google.com by
g.maxia
on 29 Jun 2011 at 8:55