It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×6,033
×3,954

question asked: Aug 26 '15, 2:17 p.m.
question was seen: 4,002 times
last updated: Sep 25 '15, 8:42 a.m.

Related questions

RM 6 Crashing CRRRS1007E A problem occurred in the Requirements Management (RM) serve

0
Rafael Rodriguez Montes (230●13●130●258) | asked Aug 26 '15, 2:17 p.m.
edited Aug 28 '15, 10:57 p.m. by Geoffrey Clemm (30.1k●3●30●35)
 CRRRS1007E  A problem occurred in the Requirements Management (RM) server: Entry [6f0d90d3cf253b3a]
java.lang.NullPointerException: vvcConfigUrl must not be null
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:229)
at com.ibm.rdm.fronting.server.services.recentfeeds.internal.EntryListCacheKey.from(EntryListCacheKey.java:64)
at com.ibm.rdm.fronting.server.services.recentfeeds.internal.RecentResourcesManager.getRecentResources(RecentResourcesManager.java:395)
at com.ibm.rdm.fronting.server.services.recentfeeds.internal.RecentResourcesManager.getRecentResources(RecentResourcesManager.java:360)
at com.ibm.rdm.fronting.server.services.storedqueries.internal.runtime.GetUpdatedRequirementsQuery.computeResults(GetUpdatedRequirementsQuery.java:97)
at com.ibm.rdm.fronting.server.services.storedqueries.internal.runtime.ProgrammaticStoredQueryExecutor.generateResults(ProgrammaticStoredQueryExecutor.java:190)
at com.ibm.rdm.fronting.server.services.storedqueries.internal.runtime.GetUpdatedRequirementsQuery.generateResults(GetUpdatedRequirementsQuery.java:113)
at com.ibm.rdm.fronting.server.services.storedqueries.internal.runtime.ProgrammaticStoredQueryExecutor.execute(ProgrammaticStoredQueryExecutor.java:80)
at com.ibm.rdm.fronting.server.services.storedqueries.internal.model.StoredQueryQueryModel.execute(StoredQueryQueryModel.java:69)
at com.ibm.rdm.fronting.server.services.storedqueries.internal.model.StoredQueryModel.execute(StoredQueryModel.java:199)
at com.ibm.rdm.fronting.server.services.storedqueries.internal.StoredQueryServiceInternal.doPostInternal(StoredQueryServiceInternal.java:203)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.runInternalMethod(RRSRestServiceBase.java:757)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:641)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doPost(RRSRestServiceBase.java:144)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.performService(RRSRestServiceBase.java:428)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:236)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:155)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:282)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleAppSdkRestServiceRequest2(AbstractTeamServerServlet.java:1963)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.access$2(AbstractTeamServerServlet.java:1918)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet$2.service(AbstractTeamServerServlet.java:259)
at com.ibm.team.repository.service.internal.compatibility.auth.DelegatedAuthHandler$1.run(DelegatedAuthHandler.java:250)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleAuthentication(AbstractTeamServerServlet.java:2019)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleAppSdkRestServiceRequest(AbstractTeamServerServlet.java:1894)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1622)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
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:668)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1230)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:939)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1818)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
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:1881)
2015-08-26 11:12:49,521 [              WebContainer : 3] ERROR m.ibm.rdm.fronting.server.services.RMBridgeService  - Service Error: Unable to resolve expected configuration.
2015-08-26 11:12:50,865 [              WebContainer : 3] ERROR m.ibm.rdm.fronting.server.services.RMBridgeService  - Service Error: Unable to resolve expected configuration.
2015-08-26 11:13:02,666 [              WebContainer : 3]  INFO ibm.rdm.fronting.server.rrs.publish.PublishService  - GET: https://ibmjts:9443/rm/publish/templateLibrary?dojo.preventCache=1440612701135

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Erica Tran (1.4k●7) | answered Aug 31 '15, 9:30 a.m.
JAZZ DEVELOPER
Hi Rafael,

Do you see the error when accessing a newly created project in version 6.0?  And existing projects will work?  If so the error seems to be an issue resolved with the following defect.  

Defect 266829: Test Failure (RJF-I20130527-1930): com.ibm.team.jfs.sdk.query.tests.SdkLegacyQueryTests.test071_QueryAfterCommitOfAChange

The problem has been seen when creating a project area in RDNG. Periodically resources are not indexed and skipped which causes the error.  The fix for this issue is targeted for 6.0 ifix003 which is to be released the second week of September.

I hope this helps.
Comments
Brian Lahaie commented Sep 24 '15, 3:01 p.m.

 I am encountering a similar type error...I am going to apply ifix003.  Will report back later.
0
permanent link
Brian Lahaie (108●15●14) | answered Sep 25 '15, 1:36 a.m.
edited Sep 25 '15, 1:37 a.m.
As per Erica Tran's recommendation, I applied ifix003 to my 6.0 install.  The problem did not go away until did the following steps after applying the ifix:
(1)Stop the rm.war running in WebSphere
(2)Ran this repotools command, repotools-rm.bat -reindex all
(3)Start the rm.war in WebSphere
(4)The error was still being displayed when accessing the project's dashboards
(5)Archived and then Unarchived the troubled project area, and the error message went away.
Comments
Erica Tran commented Sep 25 '15, 8:42 a.m. | edited Sep 25 '15, 8:42 a.m.
JAZZ DEVELOPER

Hi Brian, I would suggest keeping the project that ran into the error archived.  It might not have been created successfully if you ran into the problem. One symptom might be type errors in the rm log.   And it is always recommended to have the latest ifix install for any upgrades or new installs as they have critical fixes. 
Thanks.

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.