Description:
Microsoft® Internet Explorer (IE) and Google® Chrome on Microsoft windows intermittently experience random error popups in the UI stating a 'Server Error'. However the message showing to the end-user in the application user interface is incorrect. The true, client-side errors are reported in the app-ca.log:
ERROR 2015-02-16 12:44:05,434 [http-bio-14001-exec-4095] clarity.ui (clarity:admin:5609057__6CBF491C-9C95-4A99-B2EC-ADB4888BD9FC:none) UI_MSG[:Wed Apr 16 13:40:27 EDT 2014:OnError called--Client Side Exception java.lang.Exception: VXMLRequest failed. HTTP status code was: 12031
ERROR 2015-02-16 07:01:20,678 [http-bio-14001-exec-4050] clarity.ui (clarity:unknown::none) UI_MSG[:Wed Apr 16 17:31:07 UTC 0530 2014:OnError called--Client Side Exception
java.lang.Exception: VXMLRequest failed. HTTP status code was: 12152
ERROR 2015-02-16 07:01:20,678 [http-bio-14001-exec-4050] clarity.ui (clarity:unknown::none) UI_MSG[:Wed Apr 16 17:31:07 UTC 0530 2014:OnError called--Client Side Exception
java.lang.Exception: VXMLRequest failed. HTTP status code was: 12030
Steps to Reproduce:
Expected Result: The CA PPM application should retry the POST operation if it is encountered without first reporting an error. Alternatively, if a Client-Side error is encountered, then the application UI should provide the correct error message.
Actual Result: A popup appears stating "Unable to process request - Server error" and a "client-side" error is reported in app-ca.log indicating the error is in fact client-side and not server side.
Solution:
The fix implemented for this issue is that when these errors are generated, the application user interface will display a message to indicate a 'Client-Side' error is generated.
For information in resolving Client-Side error messages you encounter, visit the company website associated with the specific browser for identified error codes.
For example, if you are using IE, visit the Microsoft® Website; if you are using Chrome, visit the Google® Website.