Cisco Bug: CSCuq25091 - UCCX: REST Step Java Exceptions Should Be Logged at Level 3, Not 7
May 04, 2017
- Cisco Unified Contact Center Express
- Cisco Unified IP Interactive Voice Response (IVR) 10.5(1)
- Cisco Unified Contact Center Express 10.5(1)
Known Affected Releases
Symptom: When the Make REST Call step fails with a Java exception that prevents a response from being returned and written to the response string, the only error logged is seen in APP_MGR. For example: 6055: Aug 02 11:15:22.900 EDT %MIVR-APP_MGR-3-EXCEPTION:java.lang.ClassCastException: java.lang.String cannot be cast to com.cisco.expression.Modifiable 6056: Aug 02 11:15:22.900 EDT %MIVR-APP_MGR-3-EXCEPTION: at com.cisco.wf.steps.io.RestMethodCallStep.setOutput(RestMethodCallStep.java:441) The default logging is not enough for the administrator to solve the problem, so the REST step's debugging needs to be enabled to see what is actually leading to this step failure. Exceptions like this one: 5992: Aug 02 11:15:22.889 EDT %MIVR-STEP_REST-7-EXCEPTION:com.sun.jersey.api.client.ClientHandlerException: javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty should be logged at Level 3 so that administrators can be alerted to the root cause of the problem. Conditions: REST Step Failure during script execution.
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