Setting up Dashboard Trend Reports
I've successfully upgraded my server from M3a to M4 but I can't seem to get my trend reports to work on Dashboard.
All I get is:
Parameter loading failed: : null com.ibm.team.reports.service.internal.ReportService.getParameterGroupValues(ReportService.java:942) sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:615) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:324) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:316) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$1.invoke(ExportProxyServiceRecord.java:106) $Proxy111.getParameterGroupValues(Unknown Source) com.ibm.team.reports.service.internal.ReportRestService.getParameterGroupValues(ReportRestService.java:361) sun.reflect.GeneratedMethodAccessor198.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:615) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:324) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:316) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$1.invoke(ExportProxyServiceRecord.java:106) $Proxy112.getParameterGroupValues(Unknown Source) sun.reflect.GeneratedMethodAccessor197.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:615) com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:429) com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1257) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:115) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) java.lang.Thread.run(Thread.java:801)
Any suggestions? What am I missing?
All I get is:
Parameter loading failed: : null com.ibm.team.reports.service.internal.ReportService.getParameterGroupValues(ReportService.java:942) sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:615) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:324) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:316) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$1.invoke(ExportProxyServiceRecord.java:106) $Proxy111.getParameterGroupValues(Unknown Source) com.ibm.team.reports.service.internal.ReportRestService.getParameterGroupValues(ReportRestService.java:361) sun.reflect.GeneratedMethodAccessor198.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:615) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:324) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:316) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$1.invoke(ExportProxyServiceRecord.java:106) $Proxy112.getParameterGroupValues(Unknown Source) sun.reflect.GeneratedMethodAccessor197.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:615) com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:429) com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1257) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:115) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) java.lang.Thread.run(Thread.java:801)
Any suggestions? What am I missing?
8 answers
gabriel_castro@ca.ibm-dot-com.no-spam.invalid (gcastro) wrote in
news:fjp3um$9p5$2@localhost.localdomain:
Gabriel,
Is this the exact symptom you are getting ?
https://jazz.net/jazz/web/projects/Jazz%
20Project#action=com.ibm.team.workitem.viewWorkItem&id=39576
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
news:fjp3um$9p5$2@localhost.localdomain:
All I get is:
Parameter loading failed: : null
com.ibm.team.reports.service.internal.ReportService.getParameterGroupVa
lues(ReportService.java:942)
Gabriel,
Is this the exact symptom you are getting ?
https://jazz.net/jazz/web/projects/Jazz%
20Project#action=com.ibm.team.workitem.viewWorkItem&id=39576
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
Hi Gabriel,
We made few changes to our report migration after M4. Few of our reports are
automatically deployed as part of migration. Is there a particular reason
you chose to migrate using M4. Can you try a migration from M3 to Beta2
using our Beta2 builds (officially release on Friday, Dec 14th)
Note : M4 migrated db will work against Beta2 server bits. Some of the
reports that are deployed as part of Beta2 migration will not be present in
your database if you used M4 for migration.
Thanks
Balaji
"gcastro" <gabriel_castro@ca.ibm-dot-com.no-spam.invalid> wrote in message
news:fjp3um$9p5$2@localhost.localdomain...
We made few changes to our report migration after M4. Few of our reports are
automatically deployed as part of migration. Is there a particular reason
you chose to migrate using M4. Can you try a migration from M3 to Beta2
using our Beta2 builds (officially release on Friday, Dec 14th)
Note : M4 migrated db will work against Beta2 server bits. Some of the
reports that are deployed as part of Beta2 migration will not be present in
your database if you used M4 for migration.
Thanks
Balaji
"gcastro" <gabriel_castro@ca.ibm-dot-com.no-spam.invalid> wrote in message
news:fjp3um$9p5$2@localhost.localdomain...
I've successfully upgraded my server from M3a to M4 but I can't seem
to get my trend reports to work on Dashboard.
All I get is:
Parameter loading failed: : null
com.ibm.team.reports.service.internal.ReportService.getParameterGroupValues(ReportService.java:942)
sun.reflect.GeneratedMethodAccessor199.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:615)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:324)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:316)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$1.invoke(ExportProxyServiceRecord.java:106)
$Proxy111.getParameterGroupValues(Unknown Source)
com.ibm.team.reports.service.internal.ReportRestService.getParameterGroupValues(ReportRestService.java:361)
sun.reflect.GeneratedMethodAccessor198.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:615)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:324)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:316)
org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$1.invoke(ExportProxyServiceRecord.java:106)
$Proxy112.getParameterGroupValues(Unknown Source)
sun.reflect.GeneratedMethodAccessor197.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:615)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:429)
com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1257)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:115)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
java.lang.Thread.run(Thread.java:801)
Any suggestions? What am I missing?
"Balaji Krish" <balajik@us.ibm.com> wrote in news:fjpm5q$hjt$1
@localhost.localdomain:
Yes it seems the issue is that, in my case, I have no report
I believe Mike is trying to see if we can have a better error report from
the service, something like 'report does not exist' or something like that
instead of <null> :)
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
@localhost.localdomain:
will not be present in
your database if you used M4 for migration.
Yes it seems the issue is that, in my case, I have no report
I believe Mike is trying to see if we can have a better error report from
the service, something like 'report does not exist' or something like that
instead of <null> :)
--
Christophe Elek
Serviceability Architect
IBM Software Group - Rational
Hi Balaji,
We chose to migrate using M4 because Beta2 wasn't available yet and we needed some of the functionality ASAP. Unfortunately the data has already changed in the past weeks so we can't really revert to the M3 data.
So if I understand you correctly, the Dashboard will show trend reports in the list even if the actual reports are not deployed, right? That doesn't seem very intuitive.
Now the question is, how can I deploy the reports to match the trend reports in the dashboard?
Gabriel
We chose to migrate using M4 because Beta2 wasn't available yet and we needed some of the functionality ASAP. Unfortunately the data has already changed in the past weeks so we can't really revert to the M3 data.
So if I understand you correctly, the Dashboard will show trend reports in the list even if the actual reports are not deployed, right? That doesn't seem very intuitive.
Now the question is, how can I deploy the reports to match the trend reports in the dashboard?
Gabriel
Hi Gabriel,
We made few changes to our report migration after M4. Few of our reports are
automatically deployed as part of migration. Is there a particular reason
you chose to migrate using M4. Can you try a migration from M3 to Beta2
using our Beta2 builds (officially release on Friday, Dec 14th)
Note : M4 migrated db will work against Beta2 server bits. Some of the
reports that are deployed as part of Beta2 migration will not be present in
your database if you used M4 for migration.
Thanks
Balaji
Gabriel,
I am not sure about it. I sent a note to our Dashboard and report team. They
should be able to reply to your query.
-----
Balaji
I am not sure a
"gcastro" <gabriel_castro@ca.ibm-dot-com.no-spam.invalid> wrote in message
news:fjrjkn$bhs$1@localhost.localdomain...
So if I understand you correctly, the Dashboard will show trend
reports in the list even if the actual reports are not deployed,
right? That doesn't seem very intuitive.
I am not sure about it. I sent a note to our Dashboard and report team. They
should be able to reply to your query.
-----
Balaji
I am not sure a
"gcastro" <gabriel_castro@ca.ibm-dot-com.no-spam.invalid> wrote in message
news:fjrjkn$bhs$1@localhost.localdomain...
Hi Balaji,
We chose to migrate using M4 because Beta2 wasn't available yet and we
needed some of the functionality ASAP. Unfortunately the data has
already changed in the past weeks so we can't really revert to the M3
data.
So if I understand you correctly, the Dashboard will show trend
reports in the list even if the actual reports are not deployed,
right? That doesn't seem very intuitive.
Now the question is, how can I deploy the reports to match the trend
reports in the dashboard?
Gabriel
Hi Gabriel,
We made few changes to our report migration after M4. Few of our
reports are
automatically deployed as part of migration. Is there a particular
reason
you chose to migrate using M4. Can you try a migration from M3 to
Beta2
using our Beta2 builds (officially release on Friday, Dec 14th)
Note : M4 migrated db will work against Beta2 server bits. Some of
the
reports that are deployed as part of Beta2 migration will not be
present in
your database if you used M4 for migration.
Thanks
Balaji
Gabriel,
The reports team confirmed that they added the automatic reports deployment
as part of migration to address the exact same problem you are experiencing.
There is no UI action to deploy these reports. James Moody is going to help
you deploy the reports. You can contact him directly to address your
concerns.
Thanks
Balaji
"gcastro" <gabriel_castro@ca.ibm-dot-com.no-spam.invalid> wrote in message
news:fjrjkn$bhs$1@localhost.localdomain...
The reports team confirmed that they added the automatic reports deployment
as part of migration to address the exact same problem you are experiencing.
There is no UI action to deploy these reports. James Moody is going to help
you deploy the reports. You can contact him directly to address your
concerns.
Thanks
Balaji
"gcastro" <gabriel_castro@ca.ibm-dot-com.no-spam.invalid> wrote in message
news:fjrjkn$bhs$1@localhost.localdomain...
Hi Balaji,
We chose to migrate using M4 because Beta2 wasn't available yet and we
needed some of the functionality ASAP. Unfortunately the data has
already changed in the past weeks so we can't really revert to the M3
data.
So if I understand you correctly, the Dashboard will show trend
reports in the list even if the actual reports are not deployed,
right? That doesn't seem very intuitive.
Now the question is, how can I deploy the reports to match the trend
reports in the dashboard?
Gabriel
Hi Gabriel,
We made few changes to our report migration after M4. Few of our
reports are
automatically deployed as part of migration. Is there a particular
reason
you chose to migrate using M4. Can you try a migration from M3 to
Beta2
using our Beta2 builds (officially release on Friday, Dec 14th)
Note : M4 migrated db will work against Beta2 server bits. Some of
the
reports that are deployed as part of Beta2 migration will not be
present in
your database if you used M4 for migration.
Thanks
Balaji