It's all about the answers!

Ask a question

Not able to see recently viewed work items, plans, and source control items in RTC


Ken Murphy (1032933) | asked Jan 27 '16, 3:53 p.m.
We are using CLM 5.0.2 iFix7 with RQM, RTC, and RDNG.  We have the tools installed in Linux SLES-11 servers in WAS 8.5 and are using SQL Server 2014 databases.  We are using both the Firefox 34 and IE-11 browsers.

We upgraded to v5.0.2 back in November.  Starting this week, we are no longer able to see recently viewed plans, work items, and source control items via the capability menus.  To my knowledge, no maintenance was performed on the CLM servers or to the CLM applications.  We can still see recently viewed test assets in RQM.

Has anyone run into this already or have any recommendations for something to check?

One other thing we are seeing is with regard to the Recently Viewed widget in RTC.  We are getting the error trace below.  We do not see this in RQM; the Recently Viewed widget works just fine there.

An error occurred while loading the widget.
RequestError: Unable to load /rtc/view-history?application=https%3A%2F%2Frubylake%3A9443%2Frtc%2Fapplication-about&size=5&startIndex=0&user=WFQ019 status: 500

{"errorClass":"java.lang.RuntimeException","nestedError":{"errorClass":"org.apache.jasper.JasperException","nestedError":{"errorClass":"java.io.FileNotFoundException","errorCode":null,"errorTraceMarshall":[{"errorTraceFileName":"FileOutputStream.java","errorTraceClassName":"java.io.FileOutputStream","errorTraceMethodName":"","errorTraceLineNumber":204},{"errorTraceFileName":"FileOutputStream.java","errorTraceClassName":"java.io.FileOutputStream","errorTraceMethodName":"","errorTraceLineNumber":94},{"errorTraceFileName":"Compiler.java","errorTraceClassName":"org.apache.jasper.compiler.Compiler","errorTraceMethodName":"setupContextWriter","errorTraceLineNumber":292},{"errorTraceFileName":"Compiler.java","errorTraceClassName":"org.apache.jasper.compiler.Compiler","errorTraceMethodName":"generateJava","errorTraceLineNumber":230},{"errorTraceFileName":"Compiler.java","errorTraceClassName":"org.apache.jasper.compiler.Compiler","errorTraceMethodName":"compile","errorTraceLineNumber":347},{"errorTraceFileName":"Compiler.java","errorTraceClassName":"org.apache.jasper.compiler.Compiler","errorTraceMethodName":"compile","errorTraceLineNumber":327},{"errorTraceFileName":"Compiler.java","errorTraceClassName":"org.apache.jasper.compiler.Compiler","errorTraceMethodName":"compile","errorTraceLineNumber":314},{"errorTraceFileName":"JspCompilationContext.java","errorTraceClassName":"org.apache.jasper.JspCompilationContext","errorTraceMethodName":"compile","errorTraceLineNumber":589},{"errorTraceFileName":"JspServletWrapper.java","errorTraceClassName":"org.apache.jasper.servlet.JspServletWrapper","errorTraceMethodName":"service","errorTraceLineNumber":317},{"errorTraceFileName":"JspPage.java","errorTraceClassName":"net.jazz.web.jsp.internal.JspPage","errorTraceMethodName":"service","errorTraceLineNumber":56},{"errorTraceFileName":"JspEngine.java","errorTraceClassName":"net.jazz.web.jsp.JspEngine","errorTraceMethodName":"service","errorTraceLineNumber":51},{"errorTraceFileName":"ViewHistoryService.java","errorTraceClassName":"com.ibm.team.dashboard.service.internal.markers.ViewHistoryService","errorTraceMethodName":"perform_GET","errorTraceLineNumber":80},{"errorTraceFileName":"TeamRawService.java","errorTraceClassName":"com.ibm.team.repository.service.TeamRawService","errorTraceMethodName":"service","errorTraceLineNumber":84},{"errorTraceFileName":"NativeMethodAccessorImpl.java","errorTraceClassName":"sun.reflect.NativeMethodAccessorImpl","errorTraceMethodName":"invoke0","errorTraceLineNumber":-2},{"errorTraceFileName":"NativeMethodAccessorImpl.java","errorTraceClassName":"sun.reflect.NativeMethodAccessorImpl","errorTraceMethodName":"invoke","errorTraceLineNumber":60},{"errorTraceFileName":"DelegatingMethodAccessorImpl.java","errorTraceClassName":"sun.reflect.DelegatingMethodAccessorImpl","errorTraceMethodName":"invoke","errorTraceLineNumber":37},{"errorTraceFileName":"Method.java","errorTraceClassName":"java.lang.reflect.Method","errorTraceMethodName":"invoke","errorTraceLineNumber":611},{"errorTraceFileName":"ExportProxyServiceRecord.java","errorTraceClassName":"org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord","errorTraceMethodName":"invoke","errorTraceLineNumber":361},{"errorTraceFileName":"ExportProxyServiceRecord.java","errorTraceClassName":"org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord","errorTraceMethodName":"access$0","errorTraceLineNumber":347},{"errorTraceFileName":"ExportProxyServiceRecord.java","errorTraceClassName":"org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler","errorTraceMethodName":"invoke","errorTraceLineNumber":56},{"errorTraceFileName":null,"errorTraceClassName":"com.sun.proxy.$Proxy365","errorTraceMethodName":"service","errorTraceLineNumber":-1},
(and many more lines)

Comments
Donald Nong commented Jan 27 '16, 9:17 p.m.

You do know the most important information is at the top and the bottom of the stack trace, right?

If you access the below link, do you get the same 500 error?
https://rubylake:9443/rtc/view-history?application=https%3A%2F%2Frubylake%3A9443%2Frtc%2Fapplication-about&size=5&startIndex=0&user=WFQ019

Also, check ccm.log for more detailed information.

One answer



permanent link
Kim Soederhamn (1.4k23638) | answered Jan 28 '16, 3:58 a.m.
The recently viewed is not stored in the browser but comes from the application. If you have not changed anything then maybe something has happened to the data(perhaps an aprupt shutdown). I would suggest you tried reindexing RTC  - eg running repotools-ccm -reindex and possibly also repotools-ccm -rebuildtextindices - this can take quite a while to do if you have a big enterprise install so in that case you could try to find a backup(from before the problems started) of the folder where your indexes are located and try to restart the server with this copy (they should bring them selves up to date).



Comments
Ken Murphy commented Jan 28 '16, 11:50 a.m.

Thanks, Kim.  We'll give this a shot.

Your answer


Register or to post your answer.