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:
CRJAZ1440I A new type "StorageNode" was added.
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
Two policies can only be merged if their operation rules are exactly the same, but the two policies had a different number of rules
The user "ADMIN" has logged in to the database "//db1.clm.company.com:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;".
Running post addTables for "com.ibm.team.repository"...
Running post addTables for "com.ibm.team.repository.auth"...
Running post addTables for "com.ibm.team.process"...
Running post addTables for "com.ibm.team.dashboard"...
Running post addTables for "com.ibm.team.jfs.resource"...
Running post addTables for "com.ibm.team.links"...
Running post addTables for "com.ibm.team.reports"...
DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=RIODS.TIMELINE, DRIVER=3.57.82
Running post addTables for "com.ibm.team.repository.friends"...
Running post addTables for "Full Text Migration Handler"...
The user "ADMIN" has logged out of the database "//db1.clm.company.com:50000/JTS:user=xxxxxxxx;password=xxxxxxxx;".
Database tables were added successfully.
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
https://jazz.net/forum/questions/86047/two-policies-can-only-be-merged-if-their-operation-rules-are-exactly-the-same-but-the-two-policies-had-a-different-number-of-rules
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:
a) stop websphere (or tomcat in other deployments)
b) repotools-jts.bat -addTables
2. start Server (or Application server only e.g. Websphere, Tomcat)
3. Reset JTS and CCM
https://clmserver01.company.com/jts/admin/cmd/requestReset
https://clmserver01.company.com/ccm/admin/cmd/requestReset
4. Restart
I upgraded to 8.5.0.1.... that was a no no.
I had to downgrade to WAS 8.0.0.4.
the moment I did that it worked.
I see the same issues with 8.0.0.5.
Hope this helps.
Karl
Comments
Hello Karl,
Yesterday I thought I have found the problem. But today, the problems came back, after a restart of WAS.
Then we went back to our testsystem, where we run 4.0.0.1 since weeks without problem.
There we run WAS 8.0.0.4. We upgraded WAS to 8.0.0.5, the version we run on the productive server. AND: the problem occured also on the testmachine.
Now I read your answer and I think we can say: WAS 8.0.0.5/64bit has problems with WAS 8.0.0.4!!
Looks like it is a bug in WAS and there is a APAR and testfix available.
WSAS APAR PM79419
I will use the work around (-xjit...) but just wanted others to know about this problem. Perhaps the docs or the product should be patched?
Comments
The workaround to add the generic JVM option
-Xjit:exclude={org/mozilla/javascript/UintMap.*} is indeed fixing the dashboard problem for us.
However, it seems , that JVM is not always taking the new option into account upon startup. We added the option and restartet WAS, but still dashboards did not work. Then we changed in addtion the minumum heap size and all-of-a-sudden it was working. After the next Server reboot, the correct functionality was gone again allthough the -Xjit option is still in place in the server.xml config file.
Does anybody has recognized such a similiar JVM behavior ?
It seems like JVM is having some persistency behavior ? How can I trace JVM to display the startup options ?
or maybe the persistency is within JTS/CCM ?
1 vote
This is actually not an issue with RTC... It is an identified issue with WebSphere.
An defect/bug/whatever was opened and they are working on getting the fix into the next WAS patch release.
I do not have the APAR/bug/whatever number.
I will try the option: -Xjit:exclude={org/mozilla/javascript/UintMap.*}
Comments
Lauren Hayward Schaefer
JAZZ DEVELOPER Oct 17 '12, 7:07 a.m.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.
Karl Athanasiou
Nov 01 '12, 10:59 a.m.Namit,
Anthony Giordano
Nov 08 '12, 2:31 p.m.I am seeing the same issue....did they resolve and if so what was the fix?
Guido Schneider
Nov 24 '12, 10:16 a.m.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?