Clear the acquiring ledger when shutting down NetworkOPs:
This solves a circular destruction problem on exit.
Change to the Application io_service:
* Simplified the implementation and removed class IoServicePool
* The io_service outlives the components of the Application
Remove spurious assert in ResolverAsioImpl
Fix Overlay stop on exit:
The stop sequence for Overlay had a race condition where autoconnect could
be called after close_all, resulting in a hang on exit. This resolves the
problem by putting the close and timer operations on a strand:
* Rename some Overlay members
* Put close on strand and tidy up members
* Use completion handler instead of coroutine for timer
* Use App io_service in PeerFinder
Fix race conditions closing HTTP I/O objects:
This fixes a case where stop can sometimes skip calling close on some
I/O objects or crash in a rare circumstance where a connection is in the
process of being torn down at the exact time the server is stopped. When
the acceptor receives errors, it logs the error and continues listening
instead of stopping.
Add bin/stop-test.js shutdown testing script:
This script launches rippled repeatedly and then issues a stop command
after a variable amount of time. This is to test the shutdown of the
application and catch errors.
[checkpoint] Testing out the functionality of the ws.
[checkpoint] Use new wallet class in ripple-lib
* Pending pull https://github.com/ripple/ripple-lib/pull/161
[checkpoint] Submit and process a transaction
[checkpoint] Simulate random transactions over time
[checkpoint] Ledger summary stats.
[checkpoint] Don't output the full ledger.
[checkpoint] Need a newer version of ripple-lib
* Force exit on server disconnect.
[checkpoint] Organize a function library. Attack scenario.
[checkpoint] Create a bunch of trustlines for 1 account.
[checkpoint] Up the ledger_accept timeout
[checkpoint] more timing tweaks
[checkpoint] use the function library in test4.
[wip] Transaction rate measuring.
[wip] more logging