Menber Node testers are stuck when the MNWebTester hangs / crashes
When the WebTester hangs, there isn't a way for Member Node testers to notify us, leaving them blocked in their own testing. We need a way to give them more control, as well as a better way to monitor the WebTester itself.
The WebTester creates and destroys a lot of HttpClients in due to the architecture of libclient_java_V1.x. This exercises the GC quite a bit.
The solution seems to be to give Member Node developers control over the test environment if they want it. What is lacking currently is a push-button solution for running the web tests. Presently, if people wanted control, they needed to download and build the d1_integration project, which requires maven and rudimentary Java development knowledge.
Tasks for this story will define solutions for this situation.