Debugging JazzSM DASH client side issues with Chrome Developer Tools - Part 1
VictorDiaz 270002DX0R Visits (3275)
A well known among DASH Support Engineers, the spinning wheel that appears when loading certain pages:
and commonly encountered after environment migrations and/or upgrades. During these, it is common for WebSphere *.xml application deployment descriptors to become corrupted, develop invalid references and sometimes just missing *.js files, which is the case we are going to examine:
We hit the spinning wheel when opening 'Data Sources' from the 'Administration' menu:
at this point, we can launch Chrome Developer tools from the menus or with 'Ctrl + Shift + J' or 'F12' on Windows or 'Cmd + Opt + J' on Mac, which will split the screen and bring the 'Console' into focus. Type of messages can be grouped by opening the 'Console Settings' menu; in this case can see an HTTP '404' error generated by 'dojo.js':
These client-side errors are in turn being logged by the Webcontainer filter on the server-side in '$JA
[10/12/18 16:17:33:214 GMT] 00001802 filter E com.
the path to the file, as reported by the Developer Tools console error:
since the misisng page is a 'Webtop' object, ot translates in server filesystem terms to:
we can copy this file over from another working system or from backup.