After integration of issue #9 , sequencer algorithm does not terminate when -f|--frequency argument is specified.
This is because, with this option, Session Layer which plays the role of the sequencer starts thread SessionLayer::sendPeriodicPerfMessage(). But, unlike thread corresponding to participants, this thread never goes beyond instruction okToSendPeriodicPerfMessage.wait(); as its AlgoLayer does not broadcast any message ==> This thread never ends.
One possible solution is to make SequencerAlgoLayer evolve so that this thread participates in total order braodcasting like a plain participant.
Note: If -f|--frequency argument is not specified, sequencer algorithm terminates properly.
After integration of issue #9 , sequencer algorithm does not terminate when -f|--frequency argument is specified. This is because, with this option, Session Layer which plays the role of the sequencer starts thread
SessionLayer::sendPeriodicPerfMessage()
. But, unlike thread corresponding to participants, this thread never goes beyond instructionokToSendPeriodicPerfMessage.wait();
as its AlgoLayer does not broadcast any message ==> This thread never ends.One possible solution is to make SequencerAlgoLayer evolve so that this thread participates in total order braodcasting like a plain participant.
Note: If -f|--frequency argument is not specified, sequencer algorithm terminates properly.