Description of the bug

• Master fires up the gateway of the OOP
• Follower connects through Directory Service
• Follower disconnects
• Master keeps the old socket open
• Follower reconnects
• Master still sends OOP communication to the old socket resulting in 500 status code