It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×42,787

question asked: Dec 12 '07, 11:57 a.m.
question was seen: 6,625 times
last updated: Dec 12 '07, 11:57 a.m.

Related questions

FAQ - How this Forum works

Setting up Dashboard Trend Reports

0
Gabriel Castro (121●6) | asked Dec 12 '07, 11:57 a.m.
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?

8 answers

Most liked answers|Newest answers ↑|Oldest answers

0
permanent link
Rafik Jaouani (5.0k●1●6) | answered Dec 16 '07, 4:58 a.m.
JAZZ DEVELOPER
Gabriel,
When you install Beta2, I would recommend running a migration of the repo. This will auto-deploy and auto-update any new or modified reports. If not, you would have to manually redeploy all report templates for all projet areas.
0
permanent link
Balaji Krish (1.8k●1●2) | answered Dec 14 '07, 9:48 a.m.
JAZZ DEVELOPER
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...
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
0
permanent link
Balaji Krish (1.8k●1●2) | answered Dec 13 '07, 4:08 p.m.
JAZZ DEVELOPER
Gabriel,

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
0
permanent link
Gabriel Castro (121●6) | answered Dec 13 '07, 10:31 a.m.
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

0
permanent link
Christophe Elek (2.9k●1●30●21) | answered Dec 13 '07, 4:45 a.m.
JAZZ DEVELOPER
"Balaji Krish" <balajik@us.ibm.com> wrote in news:fjpm5q$hjt$1
@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
0
permanent link
Balaji Krish (1.8k●1●2) | answered Dec 12 '07, 5:18 p.m.
JAZZ DEVELOPER
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...
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?
0
permanent link
Gabriel Castro (121●6) | answered Dec 12 '07, 3:14 p.m.
Yes, that looks just like it.
0
permanent link
Christophe Elek (2.9k●1●30●21) | answered Dec 12 '07, 11:57 a.m.
JAZZ DEVELOPER
gabriel_castro@ca.ibm-dot-com.no-spam.invalid (gcastro) wrote in
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

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.