new methods to allow closing connection pool connections either immed… …

…iately, or as soon as the connection is no longer borrowed

added documentation to make clear that a connection can no longer be … …

…borrowed after a call to restoreAndScheduleClose

fixed bug where immediate-close property was not getting set correctly

tuning test probabilities

simplify parameter passing to test-caller threads in TestRunner

fix the test class used in new tests

there is no need for a special mock connection class for these tests.… …

… The generic MockKeepAliveConnection class is adequate for this test

additional reduction of parameter passing in TestRunner

simplifying testrunner for new tests

changed new methods to NO LONGER restore a connection when safeClosin… …

…g or scheduling a safeClose

updated test classes to work with new safeClose and schedule-safeClos… …

…e methods

add warning that safeClosed or scheduled-safeClosed connectionTokens … …

…must still be restored to the ppol

sheduleSafeClose -> scheduledSafeClose

standardize on 8 threads for all mock tests

change method names to present-tense verbs for scheduling safeCloses

fixed logging bug where class connection class was logged rather than… …

… connection source-port

fixed order of logs - said connection closure was about to happen AFT… …

…ER it had already happened

add log for case when thread requests to remove connection-tracking f… …

…or a connection that was already-removed by another thread

fixed small typo in docs

fixed order of log message indicating that a connection was scheduled… …

… for closure

changed spacing in source code

added docs explaining that its NOT required to close connections from… …

… the connection token: 'It is NOT necessary to use this method to close connections. SimpleConnectionPool and

     * SimpleURIConnectionPool are specifically designed to handle unexpected connections closures'

clean up docs a bit

emphasis that users should not use this method unless needed

added updated and emphasized warning to schedule-close methods as well

source code cleanup

added some clarity in docs

made order where call to get 'now' time is made more consistent

update docs to be clearer on appropriate use of safeClose() and sched… …

…uleSafeClose()

update docs for safeClose: SimpleUndertowConnectionMaker.instance(), … …

…not SimpleUndertowConnectionMaker.getInstance()

update docs for safeClose: fix code example

additional tweak / simplication of docs for safeClose() and scheduled… …

…SafeClose()

additional tweak / simplication of docs for safeClose() and scheduled… …

…SafeClose()

correction in scheduleSafeClose() docs

small formatting update to the docs for safeClose() and scheduleSafeC… …

…lose()

changed formatting of docs for safeClose() and scheduleSafeClose(). A… …

…lso, clarified / cleaned code for safeClose()

capitalized some log messages for consistency

made order where call to get 'now' time is made more consistent in sc… …

…heduleSafeClose()

(1) skip safeClose() and scheduleSafeClose() tests if connectionToken… …

… is null, and (2) rename randomReconnectJitterMs -> randomWaitTimeJitterMs for consistency in the wait() method