Apparently, the S4 connector sets up logging by using basicConfig. While this is convenient for quick tests, it messes with all the fine tuned loggers and handlers that are used in other software of UCS. More specifically, we had to workaround this twice in admin-diary. The diary client logged into the s4 connector log file although he was never meant to do that. Other software cannot guarantee that its logging mechanisms suit the s4 connector.
This issue has been filed against UCS 4.4. UCS 4.4 is out of general maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed. If this issue still occurs in newer versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.