Cisco Bug: CSCvi84995 - Different behavior in Call Studio 11 and 9 for "connection timeout" setting in webservice element.
May 03, 2018
- Cisco Unified Customer Voice Portal
Known Affected Releases
Symptom: ) In version 9.X ?connect timeout? in web service element impacted the read timeout along with initial socket timeout. For instance a value set to ?8 seconds? here would trigger read timeout at 8. (service being called accepts connection immediately but delays response by 40 seconds "Connect timeout" in Web Services element set to 8 seconds) 10.169.0.29.1519984978160.6.TopUp,03/02/2018 10:02:58.252,InitialQPCI,enter, 10.169.0.29.1519984978160.6.TopUp,03/02/2018 10:03:06.773,InitialQPCI,element,error,The error was: java.net.SocketTimeoutException: Read timed out 10.169.0.29.1519984978160.6.TopUp,03/02/2018 10:03:06.774,InitialQPCI,exit,error 2) In version 11.5 ?connect timeout? only impacts initial socket timeout and not the read timeout which is in line with the documentation. Same app* on V11.5 without -Dsun.net.client.defaultReadTimeout set in JVM params in registry: service being called accepts connection immediately but delays response by 40 secondsb"Connect timeout" in Web Services element set to 3 seconds Conditions: Behaviour changes in 11.X
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