Error messages in RQM log when adding RQM connection to Eclipse client
Leonardo Marzo (249●6●48●52)
| asked Apr 12 '13, 12:19 p.m.
retagged Jun 22 '13, 12:03 p.m. by Lisa Caten (342●9●13)
Hi,
When we add the RQM connection to Eclipse Client, the RQM log shows the error message below. RQM works properly, however my concern is that RQM log grows so quickly that it may impact the performance. The error message below is shown many times in a few seconds 2013-04-12 13:06:36,342 [ WebContainer : 10] INFO .team.repository.service.feed.internal.FeedService - CRJAZ0838I CRJAZ0835I FeedBadRequestException in FeedService GET. - Exception message: "CRJAZ0845I Specified itemQueryProvider with id "build" not registered." - Request parameters: "[provider:build],[since:1970-01-01T00:00:00Z],[user:DGVH48]"com.ibm.team.repository.service.feed.FeedBadRequestException: CRJAZ0845I Specified itemQueryProvider with id "build" not registered. at com.ibm.team.repository.service.feed.internal.FeedService.getQueryProvider(FeedService.java:862) at com.ibm.team.repository.service.feed.internal.FeedService.doPerformGet(FeedService.java:285) at com.ibm.team.repository.service.feed.internal.FeedService.perform_GET(FeedService.java:240) at com.ibm.team.repository.service.TeamRawService.service(TeamRawService.java:82) at sun.reflect.GeneratedMethodAccessor2186.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347) at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) at $Proxy1321.service(Unknown Source) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doRestService(AbstractTeamServerServlet.java:872) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2054) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:1878) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.access$0(AbstractTeamServerServlet.java:1863) at com.ibm.team.repository.servlet.AbstractTeamServerServlet$1.service(AbstractTeamServerServlet.java:208) at com.ibm.team.repository.internal.service.auth.impl.JAuthHandler$1.run(JAuthHandler.java:102) at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1682) at javax.servlet.http.HttpServlet.service(HttpServlet.java:831) at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76) at javax.servlet.http.HttpServlet.service(HttpServlet.java:831) at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120) at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:68) at javax.servlet.http.HttpServlet.service(HttpServlet.java:831) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1657) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1597) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:131) at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:133) at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:154) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:188) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:116) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:77) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:934) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:502) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3935) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:931) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1583) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:452) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:511) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:305) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:276) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) 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:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604) Do you know what's the meaning of this message? I would appreciate your help. Thanks. |
Accepted answer
Leonardo.
Not a problem. I think you found the answer to your question. Just remove the RQM connection. It's not supported anyway. And, you never said why you added it to the eclipse client in the first place. Leonardo Marzo selected this answer as the correct answer
|
3 other answers
Stephane Leroy (1.4k●1●4●9)
| answered Jun 17 '13, 5:37 a.m.
JAZZ DEVELOPER edited Jun 17 '13, 5:38 a.m.
Hi,
- The common way to interact with RQM is through the its Web UI. Definitely. And yes. There is no real RQM client (like it exists for RTC for example). See https://voicejam.ideajam.net/ideajam/hosted/VoiCE/IdeaJam.nsf/0/606A49496DB6D05E80257AC9004CCDB0 for more insight on this. - Nonetheless (and contrarily to what was stated multiple time earlier in this thread), scenario for connecting the RTC Eclipse client to a QM project area would be supported AFAIK at least for some particular administrative tasks : 1) both approaches are proposed for modifying the process behavior (4.0.3 Information center: http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?re=1&topic=/com.ibm.rational.test.qm.doc/topics/c_define_preconditions.html&scope=null ) 2) it enables you to extract your process templates: "process templates can be extracted from an existing project areas using the RTC Eclipse Client" https://jazz.net/library/article/1181 Back to the core of your question: - which CLM version level do you run ? - did you upgrade it recently ? - from which version ? Asking as there were some issues for upgrades to 4.0.1. If you fall it into this category, would worth have a read to this TechNote: http://www-01.ibm.com/support/docview.wss?uid=swg21620879 If it doesn't solve your problem, you might want to reach out to Rational Support. Regards, Stéphane Comments We're running CLM 4.0.1
|
Bo Chulindra (1.3k●2●7●18)
| answered Jun 18 '13, 1:50 p.m.
JAZZ DEVELOPER edited Jun 18 '13, 1:52 p.m.
Were feeds created for you RQM connection? If so, have you tried deleting them? You can find your RTC client's feeds in the Feeds section of the Team Artifacts view.
Note that in general, two feeds are created automatically for every repository connection, and one more for each connected project area. |
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.
Comments
I'm seeing this as well. Is the [user:DGVH48] indicative of a specific user in this instance.
And since when is eclipse UI not supported for connecting to QM project areas or did I misunderstand Kevin's point. Work item customization and most management is far simpler using the RTC client.
Correct. The RTC client is for connecting to an RTC project area, not a QM project area. Workitem customization is done in a RTC project area, not a QM project area. What other management are you referring to.
I've been using RTC Eclipse client to administer RQM since we started on 2.0 3 years ago. During migrations to 3.x and then 4.0.1 I've always been able to perform tasks on both (we do not use the CM repository to store our defects at the moment, although we are going to moving forward.) I've created customized work items for dozens of RQM projects and continue to use the RTC Eclipse client for most RQM-related administration. We do not use full CCM or any of the RM as we only own the "Quality Professional" license.