Errors received while loading the widgets in the CM dashboard
![]() After upgrading to RTC 4.0.0.1 from 3.0.1, most of the widgets in the dashboard including Release Burndown are throwing following error: CRRDV0015E The report query results cannot be displayed. The server encountered an unexpected error that prevented it from retrieving the report query results. To find more details about this issue, open the JavaScript console of your browser by pressing F12, refresh the widget, and check the JavaScript console for any resulting errors. Has anyone seen this issue and knows how to fix this? Thanks.
|
7 answers
![]() We thougth the problems were in a not completted repotools upgrade. (see below).
But this is not true. This is another story. But I let this answer here, because I think it could also make sense to know this for others.
But it is definitivly not the answer to this particular problem.
1. Analyze repotools log files from the migration:
THE BAD THING IS THAT REPOTOOLS TELLS US "SUCCESSFULLY".
The first Message (Two policies can only be merged ) can be ignored for this problem. See
The second message (DB2 SQL Error) ist he bad one and must be solved according: https://jazz.net/forum/questions/88605/error-running-repotoolssh-addtables-during-upgrade-from-3013-to-4001
We did:
2. start Server (or Application server only e.g. Websphere, Tomcat)
3. Reset JTS and CCM
https://clmserver01.company.com/jts/admin/cmd/requestReset
4. Restart
|
![]()
The issue seems to be in WAS JIT
Workaround for this. Please add the following to the servers JVM options and try. -Xjit:exclude={org/mozilla/javascript/UintMap.*} |
![]()
Summary of all of this discussions:
Looks like it is a bug in WAS and there is a APAR and testfix available. WSAS APAR PM79419 See comments in:
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
I did a quick search for your error message in the existing RTC defects and I didn't get any results. Did you try opening the Javascript console, refreshing the widget, and checking the console for errors? You may also want to check the server logs for any related error messages.
Namit,
I am seeing the same issue....did they resolve and if so what was the fix?
I have sae problem after upüdating from v.3.0.1.4 to v.4.0.0.1.
Does you found a solution, or do you still have since one month, no widgets?