731a5b5 Ticket 51035 - Heavy StartTLS connection load can randomly fail with err=1

Authored and Committed by tbordaz 3 years ago
    Ticket 51035 - Heavy StartTLS connection load can randomly fail with err=1
    
    Bug Description:
    	startTls pushes a network layer on top of the connection.
    	So when processing startTLS, there should not be a pending operation
    	else there is a risk that the operation sends back data on moving
            network layer.
            When startTls detects a pending operation it aborts startTls.
    	However if a new operation is received while processing startTls,
    	the operation is pending but can not be read because startTls
    	holds c_mutex.
    
    Fix Description:
    	In case of unread pending operation, relax the control
    	and just log an information message.
    
    https://pagure.io/389-ds-base/issue/51035
    
    Reviewed by: Mark Reynolds, William Brown
    
    Platforms tested: F30
    
    Flag Day: no
    
    Doc impact: no