It's all about the answers!

Ask a question

RTC 4.x Imapct of long running com.ibm.team.reports.service.rest.internal.service.ReportableService.service?


Natarajan Thirumeni (288116) | asked Nov 11 '15, 7:47 a.m.

We are running RTC 407 with iFix008.

We are On WAS and on distributed environment, where JTS 407 and CCM 407 runs on two dedicated VMs. On CCM server machine we are seeing large number of Imapct of long running com.ibm.team.reports.service.rest.internal.service.ReportableService.service?

  1. Who is initiating this service? From the active service page, it shows it's running a functional user but who is actually initiating this service to be run in the first place?

  2. What are the impact are long and several instances of com.ibm.team.reports.service.rest.internal.service.ReportableService.service? We are seeing the whole system is responding very very slowly, so practically cannot be used, and had to restarted.

Have you see this issue in your environment? Any idea how to fix this long running queries? We are looking for a way to forcibly kill them to avoid slowness and restart.

2 answers



permanent link
Kevin Ramer (4.5k6171190) | answered Nov 11 '15, 10:47 a.m.
We battled this for long time ( 18 months ) due to user-written reports.   In RTC 4.0.7 it is possible for JazzAdmin to view running reports and request that the run be cancelled.   That may or may not work and you'd need to restart the RTC application server.   You can also view the details of report executions on the "Counters" page of the application administration.   To see this page insert ?internal=true just after /admin and before any other data on the admin URL and refresh the page.  There will be a section added below Communication on the left hand side, one of the items is Counters.   Search for reporting to see the table.

There is also a report design about report executions lying around somewhere that one can install into an RTC Project.



permanent link
Natarajan Thirumeni (288116) | answered Nov 23 '15, 5:23 a.m.
Hi Kevin

In our case it appears to be that, long running workitem ETL is causing an issue with the load. When looking through the logs, it further appears to that a WI created by an automation tool isn't viewable using any of the supported clients. We had remove the workitem and now trying to re-run ETL. We will keep you posted.

And thanks for your valuable inputs.

Your answer


Register or to post your answer.