Thrown to indicate that the remote process failed to respond within a specified timeout.
This typically happens when the browser fails to call us back, but if the driver is using a proxy or a CommandBridge, the remote driver may have failed to give us a new command in time.
When a SeleniumCommandTimedOutException is thrown, we have to assume that the command queue is out-of-sync with the remote process (e.g. browser). When this happens, the browser should be stopped (killed) and the queue should be flushed.
@see com.thoughtworks.selenium.outbedded.CommandBridge
@author paul