The test currently executes some OAP, but never changes the running flag to false after the OAP has been successfully executed, thus creating an infinite loop unless human interaction has been applied by sending in the stop command.  This is bad for automated testing where the framework won't be able to do this.  The looping condition needs to be fixed to change the running flag to false if all OAP has been successfully executed on the requestor side.