It's all about the answers!

Ask a question

Various Chart Errors


Michael Boyd (5175) | asked Aug 04 '09, 2:11 p.m.
Hello,

We have recently updated a server to Jazz V2.0 and have several project areas that have experienced a particular issue when navigating to the "charts" tab from within a sprint plan. When loading that Burndown chart, an error is display along with an incomplete report output. Here is a picture of what I am trying to explain:

https://wst.austin.ibm.com/isahome/3341/version/default/part/ImageData/data/reportsError.JPG

The error heading can be seen at the bottom of the picture. The error stack will be posted within a reply.

However, when you select the button at the bottom of the page to select a report, it displays the burndown chart without an error. We believe that there must be something wrong with the page defaults that we cannot seem to find or alter. Any help would be greatly appreciated.

-Michael Boyd

7 answers



permanent link
Michael Boyd (5175) | answered Aug 04 '09, 2:12 p.m.
Error Stack:

Error.UnhandledScriptError ( 1 time(s) )
detail : org.eclipse.birt.report.engine.api.EngineException: Unhandled exception when executing script.
at org.eclipse.birt.report.engine.script.internal.ScriptExecutor.addException(ScriptExecutor.java:199)
at org.eclipse.birt.report.engine.script.internal.ScriptExecutor.addException(ScriptExecutor.java:176)
at org.eclipse.birt.report.engine.script.internal.ReportScriptExecutor.handleInitialize(ReportScriptExecutor.java:49)
at org.eclipse.birt.report.engine.api.impl.EngineTask.loadDesign(EngineTask.java:1328)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:87)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:72)
at com.ibm.team.reports.service.birt.internal.BirtReportEngineService.internalGetRenderedReport(BirtReportEngineService.java:668)
at com.ibm.team.reports.service.birt.internal.BirtReportEngineService.getRenderedReport(BirtReportEngineService.java:297)
at sun.reflect.GeneratedMethodAccessor250.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:378)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:364)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy291.getRenderedReport(Unknown Source)
at com.ibm.team.reports.service.internal.InternalReportService.getRenderedReport(InternalReportService.java:1097)
at sun.reflect.GeneratedMethodAccessor249.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:378)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:364)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy151.getRenderedReport(Unknown Source)
at com.ibm.team.reports.service.internal.ReportRestService$1.run(ReportRestService.java:409)
at com.ibm.team.reports.service.internal.ReportRestService.getRenderedReport(ReportRestService.java:416)
at com.ibm.team.reports.service.internal.ReportRestService.postRenderReport(ReportRestService.java:483)
at sun.reflect.GeneratedMethodAccessor295.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:378)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:364)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy170.postRenderReport(Unknown Source)
at sun.reflect.GeneratedMethodAccessor294.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:555)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1655)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1471)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:121)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1146)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:592)
at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3507)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:269)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:815)
at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1466)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:122)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:387)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)
Caused by: org.eclipse.birt.core.exception.CoreException: There are errors evaluating script "importPackage(Packages.java.lang);
importPackage(Packages.java.util);

// First and last set represented by data points.
firstDate = null;
lastDate = null;

// Start and end date of the specified interval(s) if they exist, null otherwise
startDate = null;
endDate = null;

// The interval parameter. This is filled in by the common data set onFetch.
intervals = [];

hasData = false;

totalWiCount = 0;
totalNotEstimatedCount = 0;

// Workaround for defect 50065

// Parse the team areas parameter
teamAreas = [];
if (params && params != '' && params != "\'\'") {
var tokenizer = new StringTokenizer(params, ',');
while (tokenizer.hasMoreTokens()) {
var next = tokenizer.nextToken();
if (next.indexOf("'") == 0) next = next.substr(1);
if (next.lastIndexOf("'") == next.length - 1) next = next.substr(0, next.length - 1);
teamAreas = next;
}
}

// Assume they are item ids until we see one that is not
var isItemId = true;
for (var i = 0; i < teamAreas.length; i++) {
var teamArea = teamAreas;
if (teamArea.length == 23 && teamArea == "_") {
} else if (teamArea == "{My Team Areas}") {
} else {
isItemId = false;
break;
}
}

teamAreaItemId = null;
teamAreaName = null;
if (isItemId) {
teamAreaItemId = "" + params;
} else {
teamAreaName = "" + params;
}":
TypeError: Cannot find function substr. (/report/method#28).
at org.eclipse.birt.core.script.ScriptContext.eval(ScriptContext.java:307)
at org.eclipse.birt.core.script.ScriptContext.eval(ScriptContext.java:335)
at org.eclipse.birt.report.engine.executor.ExecutionContext.evaluate(ExecutionContext.java:665)
at org.eclipse.birt.report.engine.script.internal.ScriptExecutor.handleJSInternal(ScriptExecutor.java:60)
at org.eclipse.birt.report.engine.script.internal.ScriptExecutor.handleJS(ScriptExecutor.java:47)
at org.eclipse.birt.report.engine.script.internal.ReportScriptExecutor.handleInitialize(ReportScriptExecutor.java:41)
... 65 more
Caused by: org.mozilla.javascript.EcmaError: TypeError: Cannot find function substr. (/report/method#28)
at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3350)
at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3340)
at org.mozilla.javascript.ScriptRuntime.typeError(ScriptRuntime.java:3356)
at org.mozilla.javascript.ScriptRuntime.typeError1(ScriptRuntime.java:3368)
at org.mozilla.javascript.ScriptRuntime.notFunctionError(ScriptRuntime.java:3428)
at org.mozilla.javascript.ScriptRuntime.getPropFunctionAndThis(ScriptRuntime.java:2052)
at org.mozilla.javascript.gen.c7729._c0(/report/method:28)
at org.mozilla.javascript.gen.c7729.call(/report/method)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834)
at org.mozilla.javascript.gen.c7729.call(/report/method)
at org.mozilla.javascript.gen.c7729.exec(/report/method)
at org.eclipse.birt.core.script.ScriptContext.eval(ScriptContext.java:302)
... 70 more

permanent link
Rafik Jaouani (5.0k16) | answered Aug 04 '09, 3:33 p.m.
JAZZ DEVELOPER
Make sure you are using the Burndown report template that is included with RTC 2.0.
The migration of your 1.0 server should have upgraded your report template unless your Burndown report template did not have the proper identifier which should be: workitems.Burndown. If your report template does not have the proper identifier, please fix the identifier and upload the latest report template to the server.

permanent link
Michael Boyd (5175) | answered Aug 04 '09, 5:15 p.m.
Ok, how do you do that?

permanent link
Rafik Jaouani (5.0k16) | answered Aug 04 '09, 7:54 p.m.
JAZZ DEVELOPER
Using the Eclipse Client:
1) Go to the Team Artifacts Navigator view.
2) Expand the node for the your project area.
3) Expand the Reports node.
4) Expand the Report Templates node.
5) Look for the Report Template named Burndown.
6) Open its properties Dialog.
7) Ensure its Identifier is workitems.Burndown; if not, change it to that.
8) Click OK to save the changes.
9) Right click the Burndown Report Template and select Restore Initial Contents. This will refresh the template from the template that is bundled with the RTC Server.

permanent link
Michael Boyd (5175) | answered Aug 05 '09, 9:43 a.m.
I still am seeing the same error in the web UI: ReportDesign (id = 1): + Unhandled exception when executing script.

permanent link
Rafik Jaouani (5.0k16) | answered Aug 05 '09, 11:10 a.m.
JAZZ DEVELOPER
Does the chart have two series one blue and one gray. If your chart has only one series (the blue), then you are still using the old template.

permanent link
Rafik Jaouani (5.0k16) | answered Aug 05 '09, 5:32 p.m.
JAZZ DEVELOPER
The problem described above was caused by the fact that a report template with an identifier of apt.WorkItems was deployed. Deploying such report to a given project area will cause that report template to always be used in the Plan Chart page.

To fix this:

1) Delete the report template identified as apt.WorkItems. In this case the report was named "Sprint Burndown"
2) Rigth click the Burndown report template that we shipped with RTC 2.0 and select "Set as Default Plan Chart".

Your answer


Register or to post 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.