Build #739

Plan branch:
Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).

Build: #739 was successful Changes by Florian Schmaus <flo@geekplace.eu>

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
4 minutes
Labels
None
Agent
Default Agent
Revision
63f133e68bab8e861ea2fcc18464c50349c34dc3
Total tests
773
Successful since
#690 ()

Tests

Code commits

Author Commit Message Commit date
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> c3848495328bf6ebaf7de1adfe0e5c8685afa1f3 Set 'running' to false before calling notifyConnectionError()
Since the current variant of notifyConnectionError() does not execute
most of its work in a new thread, especially since instantShutdown()
is called in the invoking thread, we have to mark the connections
reader or writer threads as no longer running prior them invoking
notifyConnectionError(). Otherwise they will end up waiting for
themselves to terminate.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> ddc39030d77d8319be613c60fbf88492276f4030 Rename waitForCondition() to waitForConditionOrConnectionException()
To make it clear that this will either return if the condition is
true *or* if a connection exception happened.

Also introduce waitFor(), which is deliberately not named
waitForCondition() because it carries a different semantic.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> 63f133e68bab8e861ea2fcc18464c50349c34dc3 Set 'running' to true prior starting the reader/writer threads
To ensure the thread starting the reader/writer threads sees them
running and eventually waits until the 'running' boolean is reset to
'false' upon connection termination.
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> f9292a23fbdec8612e9e2554a2068cf6b1e86dc5 [tcp] Add and improve log of reader/writer thread termination
Florian Schmaus <flo@geekplace.eu> Florian Schmaus <flo@geekplace.eu> a05b46403225059efbc4d2f17a806058a8509e6d Do not use waitForConditionOrConnectionException() in XMPPTCPConnection
Since at this point, there will potentially be an active connection
exception, which would cause the call to return immediately.

2 more changes...