Data point dropout during Execution
While running JazzMon for an extended period of time, 12h. I have noticed at random times that some of the CounterContentServer.html files has the error message:
Javascript is either disabled or not available in your Browser This can happen in the middle of an execution. So files before are okay and then files after this "period" are okay. I noticed because the analyze script chokes on the files because they don't have any real data in them. |
Accepted answer
I went ahead and filed a defect to make the Analyzer more robust. So intermittent errors similar to this one won't continue to halt the analysis. The defect is JazzMon: Unexpected server response during monitoring causes analyzer to choke (247807)
Robert Carter selected this answer as the correct answer
Comments I'll update the defect from my results this week. I am running version, JazzMon_1.4.0_RTC30GA. Yes please, any further information you can can attach (stack traces, html files, etc...) will help our understanding of your issue and if the current code fix will adequately address it.
|
One other answer
|
Hi Robert,
Sorry its been so long and you haven't had response. I am a bit puzzled by the javascript error since we haven't observed anything similar to what you describe and you say its intermittent. The only browser involved with JazzMon is a headless apache http client. It is included inside the JazzMon.jar file (httpclient-4.0.1.jar). The http call to get the CounterService.html page doesn't involve javascript. There is an authentication step for each sample that invokes one bit of javascript. If I check a user login in Firebug, I see this call and the error message you point out: https://yourserver.com/ccm/_theming/allThemeJS <pre> <body class="tundra"> <noscript><div id="net-jazz-ajax-NoScriptMessage">Javascript is either disabled or not available in your Browser</div></noscript> <div id="net-jazz-ajax-InitialLoadMessage">Loading...</div> </pre> The only things I can think of that might be a problem are perhaps the classloader is pulling in an alternate version of httpclient jar that we didn't test or malformed javascript occasionally coming down from the server. Is there a generic set of libraries on your classpath that might possibly have another version of the httpclient-x.x.x.jar? (I think this might be a stretch since it seems to work most of the time). As for the malformed javascript, normally I would suggest that we clear history/cache but I am not sure this applies with the headless apache http client. (Again a stretch because it works most of the time) Even if we can't get to the root of the problem in your specific environment, we could work around your error files in the Analyzer parser code if we had a sample. Let us know if this is still an issue for you and we'll see what we can do. -Ryan |
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.