Cisco Bug: CSCvi53619 - CWA 6.2.1, 6.3.x Transporter stale connections in CM Web Interface
Mar 20, 2018
- Cisco Tidal Enterprise Transporter
Known Affected Releases
Symptom: I ran a couple of scenarios over the weekend in my environment (TESPLugin .792) where the Transporter connection sessions don't seem to adhere to the Session Timeout values in the webdefault.xml. It was brought to my attention by a customer and after some testing it looks like sometimes (Not always) the Transporter sessions go stale in the CM interface and do not purge. Conditions: I ran 6 test with two scenarios; one scenario was just shutting down transporter and the second was disconnecting the sessions and logging out of transporter. All three of my, 'Shutting Down' sessions had the connection remain in the client UI after the initial 5 minute session timeout value (I updated it to 5 minutes in my webdefault.xml to expedite testing). This really isn't a surprise. In those cases I stopped the CM and purged the cache which cleared them. However in my, 'Disconnecting/Logging Out' tests, 2 out 3 still showed the connections as active after I had logged out. Again, purging the cache seem to update it correctly.
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