It's all about the answers!

Ask a question

how to resolve RM error "not a recognised Fronting URI or Storage URI"


Norman Dignard (356696177) | asked Sep 21 '16, 4:06 p.m.
retagged Jan 11 '18, 2:12 a.m. by Minakshi Jaint (5113)

We're setting up our JAZZ CLM services for external access. As part or our corporate security policy, we have a perimeter security network (a box from F5)  where all our JAZZ traffic is being routed through both internally/externally. Due to this we've configured JAZZ as http on port 80 This F5 box does the ssl offload for JAZZ, packet scanning etc... and passes the traffic on to our reverse proxy server (nginx) for redirection to the jazz server. The JAZZ dns entry points to this F5 box. In short the traffic flow is:
Incoming JAZZ access (https) -> F5 (ssl offload) http -> reverse proxy -> JAZZ server.

Both CCM and QM appear to work fine however RM is causing us grief both in accessing rm directly or via cross-app navigation.

For example; logged in as admin, within a CCM PA properties, clicking the assoicated RM PA gives Error the user id is not recognized. You are not authorized to access JTS Admin UI.

in the rm.log on startup i get :

In rm.log get

2016-09-21 12:46:37,857 [   Default Executor-thread-508] ERROR erver.services.process.internal.ProjectAreaService  - CRRRS4122E  Error in HEAD request to determine project context. Falling back to DESCRIBE

java.lang.IllegalArgumentException: The given URI [http://19216810341/rm/cm/stream/_ufaw4H9CEea_9syv_Ta6kw][null] was nota recognised Fronting URI or Storage URI.

at com.ibm.rdm.fronting.server.core.serviceInfo.internal.RRSServiceInfoRegistry.getResourceMapping(RRSServiceInfoRegistry.java:197)
.......
....
and

2016-09-21 12:46:38,056 [   Default Executor-thread-508] ERROR erver.rrs.vvcproxy.internal.RmConfigurationFactory  - The submitted Config URI

http://192.168.103.41/rm/cm/stream/_ufaw4H9CEea_9syv_Ta6kw does not belong to this server http://jazz.navcanada.ca/rm

2016-09-21 12:46:38,058 [   Default Executor-thread-508] ERROR ibm.rdm.fronting.server.services.RMRestServiceBase  - CRRRS1007E  A problem occurred in the Requirements Management (RM) server: Entry [9118cb42a1d2d175]com.ibm.rdm.fronting.server.exception.InternalServerErrorException: Propagated exception; original message [InternalServerErrorException: Propagated exception; original message [RuntimeException: Could not resolve submitted Config URI to an IConfiguration implementation]]

at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:266)

at com.ibm.rdm.fronting.server.exception.RRSException.newException(RRSException.java:800)
at com.ibm.rdm.fronting.server.exception.RRSException.capture(RRSException.java:804) ....
....

Caused by: com.ibm.rdm.fronting.server.exception.InternalServerErrorException: Propagated exception; original message [RuntimeException: Could not resolve submitted Config URI to an IConfiguration implementation]

.....

If I do get into RM PA cannot browse modules in PA is trying to access its contents i get:

 An error has occurred while processing a server request. The server returned this error code: 500.

ID CRRRW7553E  A message that was received from the server indicates an error with no specific handler.

Unable to load /rm/folders/_ucHlQX9CEea_9syv_Ta6kw?childFolders=1&dojo.preventCache=1474477325597 status: 500
_6@https://jazz.navcanada.ca/rm/web/_js/?include=D~&etag=DxX8ecCyvPF_en_US&_proxyURL=%2Frm&ss=JXp1q&locale=en-us:2489:8 _6@https://jazz.navcanada.ca/rm/web/_js/?include=D~&etag=DxX8ecCyvPF_en_US&_proxyURL=%2Frm&ss=JXp1q&locale=en-us:6187:4 _13@https://jazz.navcanada.ca/rm/web/_js/?include=D~&etag=DxX8ecCyvPF_en_US&_proxyURL=%2Frm&ss=JXp1q&locale=en-us:6202:1

URL: /rm/folders/_ucHlQX9CEea_9syv_Ta6kw?childFolders=1

Error 500: Internal Server Error

Propagated exception; original message [InternalServerErrorException: Propagated exception; original message [IllegalArgumentException: The given URI [http://19216810341/rm/folders/_ucHlQX9CEea_9syv_Ta6kw][null] was not a recognised Fronting URI or Storage URI.]] (More info found at entry [758729982e20f02d] in the RM application server log)


Any help in getting this resolved would be great.


 

    


4 answers



permanent link
Bas Bekker (1.4k4) | answered Sep 21 '16, 5:49 p.m.
JAZZ DEVELOPER
edited Sep 21 '16, 6:23 p.m.

Bit hard to say from your post, but what caught my eye is this message

2016-09-21 12:46:38,056 [   Default Executor-thread-508] ERROR erver.rrs.vvcproxy.internal.RmConfigurationFactory  http://192.168.103.41/rm/cm/stream/_ufaw4H9CEea_9syv_Ta6kw- The submitted Config URI does not belong to this server http://jazz.navcanada.ca/rm


It has a mismatch between the RM context root (
http://jazz.navcanada.ca/rm) and the URI to identify a RM configuration, which uses an IP address. See that, looks to me that either the F5 box or the reverse proxy doesn't do it's job to translate the outside URL to the actual RM server, and/or vice versa.

There are some articles (like Understanding reverse proxy and Configuring CLM enterprise reverse proxies) and Jazz knowledge center entries (like Reverse proxy topologies) that maybe can get you going.



permanent link
Leo Shin (1113) | answered Jul 28 '17, 5:43 p.m.

We have a very similar, if not identical issue.  Did you ever find a solution?


permanent link
Norman Dignard (356696177) | answered Jul 31 '17, 9:57 a.m.

 Had raised a PMR on this. Short answer ignore it.

Below is their response: Defect 86779 comments 3 & 8 contains a reference to WI 311128"as we discussed this morning, please add the RM repotools bundle (com.ibm.rdm.fronting.server.repotools)  to your list of bundles in the workaround f(https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/311128)"

 
Defect 411745 was created as the problem with referencing the bundles was not fixed in v6. 
https://jazz.net/jazz/web/projects/Jazz%20Foundation#action=com.ibm.team.workitem.viewWorkItem&id=411745

I (IBM) have not seen any evidence that the messages present a problem with the application for the users. 


permanent link
Leo Shin (1113) | answered Aug 01 '17, 2:39 p.m.

So the response was ignore it, even though you had issues accessing RM?


Comments
Norman Dignard commented Aug 03 '17, 7:28 a.m.

Basically yes . I must note that we do not have an RM access issue and have not noted any adverse effects due to the effort, at least none that have been reported to me that I can attribute to this error.

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.