Connector should throw an obvious exception if an action is performed but the connector is not started
Some transport dispatchers send messages even when the connector has been stopped
Review connector lifecyle
Connector lifecycle needs clarification
Does this still applies after the new life cycle improvements?
This is fixed by MessageProcessor work for send/dispatch. No idea about request() though.