Fixed a bug on the state transfer protocol, that would render the leader change protocol from changing leader a second time. However, the leader change is still unstable when ciclying through replicas. I'm investigating the issue.

This commit as a lot of debugging message related to the leader change protocol.

Small but important change in the leader change implementation: When a replica suspects the leader, such computations will be done by the CS thread isntead of the RequestTask Thread. This shall reduce the changes of concurrency and race conditions, thus, making  the code more resilient.

Small but important change in the communication system: when a connection to a replica is lost, the OutQueue is erased. This is meant to avoid gaps in the sequence of messages upon reconnection, and thus, avoid the "break" of upper protocols.

Also, small refractor in TomUtil.

- Changed ServiceReplica to implement TOMReceiver;
- Created interfaces Executable and Recoverable, so the replicas can choose which methods to implement;
- Changed replicas to use ServiceReplica instead of extend it.

Moved executeOrdered method to the server implementation.
Added ant code to compile and export Jar of the project.
Added JUnit tests for the keyvalue demo.
Refactored keyvalue code.

Huge update: merging corrections of Eduardo with current version of the repository. The reconfiguration protocol should work properly now!

Fixed some bugs in the leader change (although it still needs plenty of work, specially when re-integrating the replica).

Fixed a bug related to read only requests. Moved RadomDemo to a dedicated package.

State transfer protocol can now notify the recovered replica about the most recente view. 

Added apache codecs do deal with base64 encode/decode.

Moved the code of the state transfer protocolo from class tomlayer to class statemanager. Also fixed the arrayindexoutofboud exception related to state transfer. Fixed a bug that wouldn't start the request timeout.

Cleanup on the TOMConfiguration. Removed several configuration parameters that do not make sense anymore. Besides that merged some packages and cleaned a bit more of code here and there.

Removed useless code. Classes RTInfo, RTCollect, RTLeaderChange and RTMessage are gone. Various methods that used these classes were also deleted.

In this commit, it was fixed a bug on leader change messages related to the serialization of messages contained in the STOP message. It was also added a method in the BatchBuilder class, that makes it easer to create a batch and is also used during the leader change.

Removed and refactored a lot of code, added new microbenchmarks and improved the parallelism between the delivery thread and server communication thread. Additionally, processing of out of context message changed a bit (done in the server communication thread, instead of the delivery thread).
IMPORTANT: Service replica API changed!!!
NOTE: currently achieving a zero-byte throughput of 151Kops/sec ;-)

- Improvements on the performance of communication system
- big clean up of the code (many old methods deleted)
- corrected bug in out of context (now, a consensus is only started if a propose is received)
Note: still need to verify if state transfer and leader change works right

In this commit, I fixed a bug that manifested itself during the leader change protocol (when the original leader crashed). I also added a few more locks to protect the sessionTable of the comunication system.

In this commit, I have submitted the code for the leader change. Unfortunately there is some kind of conflict between the code I developed for an older version of smart, and the most recent code available on the svn. Such conflict renders the leader change protocol faulty. Further debugging is necessary. The normal operating remains good, though.

store replies to be sent if requests arrive from client after their processing (when comming from the leader). Very subtle missing feature found by Andre!!!

No commit message

Added the patch produced by Andre Nogueira, that fixes the case of when a replica joins the group, the information about its ip address and port not being broadcasted to the other replicas.

In this commit, it has been added a timeout for the state transfer protocol, and fixed an implementantion error regarding f + 1 state hashes consistent amoung them, and a complete state inconsistent with those ashes.

It was also fixed a bug that would crash clients when a a reconfiguration was applied, and also fixed 2 bugs related to the checkpoints, which  would make replicas crash.

Finally, there are also some lines of code that have been slightly modified, but which shouls not affect the behavior of SMaRt.

Not much was changed. This commit only has minor changes, a bug fix that covers a recovered old leader so it doesn't trigger unnecessary timeouts, and some code to help test the library

Removed out of context thread. The processing out of context messages is now made at the delivery thread and Server CS thread
Removed paxos internal timers.  From now on, the external timers from the total ordering layer shall trigger the leader change
Added a few debugging messages for delivering messages
Fixed a bug related to signatures of forwarded messages from replicas to the leader
Fixed a bug on the TTP that would make it crash in some cases
Fixed 2 bugs on the state transfer protocol responsable for not letting the old leader fetch the state once it recovered

In this commit, it was added a new feature to SMaRt. It now supports dynamic views. Some bugs from the previous commit were also fixed. This was a fairly extensive update to SMaRt.

Nonces are now generated for each TOMMessage in a Batch with a single seed that is sent along with the batch instead of a fixed number of nonces per Batch.
Decided notification in Consensus.java now is done via a sync monitor instead of busy waiting on the decided value to be set. Because of the Java MemoryModel the former mechanism was problematic and could theoretically lead to the DeliveryThread never learning the new value - which is very unlikely though.

In this commit I updated the readme and configuration file, and also made the state transfer protocol able to be disabled

In this commit I made an optimization to the state transfer protocol that consists on the sending of hash's of the state. Only one replica will send the actual state. I also worked towards fixing some bugs.

In this commit I started to clean up the code that I wrote. I also added some debug messages which are produced with the Logger object.

In this commit, I continued to work on the state transfer protocol.I finally tested the protocol in the case of a crash of a replica. I was able to make the replica recover the state on those circunstances.  However, the replica will still only requests the state after it passes the highmark value. I started working on an optimization to request the state before it reaches that highmark, but its still not completed.

I this commit, I tried to fix some race conditions and bugs regarding the out of context thread, when it executes concurrently with the update of the delayed replica

I this commit, I made the TOM layer pass information about the execution id, decision round, and leader to the application. I also continued to work on the exchange of leader info in the state transfer protocol, and implemented a new demo which is more sofisticated than the counter.

In this commit, i've continued to try to find the errors on the state transfer protocol. I think i found one, and I'm beginning to add code to fix it. However, I would like to speak to the teachers tomorrow about this.

P.S. I also added more debug messages

I this commit, I continued the work on the state transfer protocol. I implemented the modifications discussed. However, the protocol remains faulty. Further debugging is required.

In this commit, i've only added some debug messages.But I committed it anyway, so I can work on SMaRt during the weekend at home

In this commit, i've continued my task of debuging the code.I finally managed to get the replica to update itself. However, when the clients finish to send requests, that same replica still remains a little behind, even though it sucessfully updates itself during previous executions of the state transfer protocol.