Cisco Bug: CSCuo89376 - FSI connection in close_wait if ExposeContent for non local ingested
Jun 21, 2020
- Cisco Videoscape Distribution Suite for Television
Known Affected Releases
Symptom: 1. Give expose request for any content which is not ingested in master vault 2. Master vault doesn't close its socket with BO, leaving the socket in CLOSE_WAIT state When such requests comes in huge number, FSI becomes unresponsive when the total socket slots of 1024 is exhausted(CLOSE_WAIT state). Conditions: Client/BO send a close request after the expose request, sometimes it might reuse the socket but will close after sometime for sure. But this close request was not handled properly by FSI leaving the socket in CLOSE_WAIT state.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases