Build result summary

Details

	Commit	Message	Commit date
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.	17 Jun 2020
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.	17 Jun 2020
Florian Schmaus <flo@geekplace.eu>	f9292a23fbdec8612e9e2554a2068cf6b1e86dc5	[tcp] Add and improve log of reader/writer thread termination	17 Jun 2020
Florian Schmaus <flo@geekplace.eu>	884ee327e1521f410e29b27f318c57f4784b61f0	Remove writerException in XMPPTCPConnection This delay mechanism is no longer necessary.	17 Jun 2020
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.	17 Jun 2020

Issue		Description	Status