Add more of a timeout in restart functionality

I have found on occasion that the restart functionality on a Object doesn't always really help. Occasionally I noticed that sequence in Stopping an object, then immediately Starting the object back up doesn't give the system significant time to fully drop the connection of the Object restarting. I have seen this with EnsLib.JavaGateway.Service and HL7 TCP operations as well. Looking at the code for EnsLib.JavaGateway.Service and the Heartbeat Failure functionality the Stop of the Java Gateway Service is not synchronis as it does not wait till the tSC is returned before it tries to Start the service back up. When this happens we get a "Failure to restart". With TCP connections, there needs to be some kind of verification that the Disconnect was sent across the port before trying to restart, or else you have to have the end point system restart their side as it never received the full disconnect before IRIS immediately brought the connection back up.

While there are ways around this by writing your own functions to put a sleep/pause in-between when the EnableConfigItem is ran to disable and enable, it still would be nice if we didn't have to do it.

}