Application: the discovery resource error "/rs" cannot be accessed:
Hi. I was installing the latest RQM 6.0 in our TEST Environment. And once the application starts up, when the jts diagnostics are run, we get the below error,
Application: the discovery resource at http://rqm-test/rs/rootservices for "/rs" cannot be accessed:
The returned HTTP status was 500
The response body was
Error 500: java.lang.NoSuchMethodError: com/ibm/team/jfs/app/http/client/JazzHttpClient.execute(Lorg/apache/http/HttpHost;Lorg/apache/http/HttpRequest;Lorg/apache/http/protocol/HttpContext;)Lorg/apache/http/client/methods/CloseableHttpResponse;
Accepted answer
Double check that you performed the configuration for shared libraries for rs.war. From the Interactive Upgrade Guide:
"8 Update JRS shared library classpath Back to top
a. In WebSphere Integrated Solutions Console navigation pane click Environment > Shared libraries.
b. Click the JRS shard library name in the list to open it.
c. In the Classpath field, update the path to the new installation directory. For example:
D:\IBM\JazzTeamServer6.0\server\conf\rs\WAS_SharedLibrary
d. Click Apply and then Save directly to the master configuration.
15 Configure the Report Builder application Back to top
a. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
b. On the Enterprise Applications page, in the list of resources, click rs_war.
c. On the Configuration page, in the References section, click Shared library references.
d. Select the rs_war check box and click Reference shared libraries.
e. In the Available list, select JRS Shared Library and click the right arrow.
f. Click OK. Click OK again and then click Save.
g. In the list of resources, click rs_war.
h. On the Configuration page, under Detail Properties, click Class loading and update detection.
i. In the Class loader order group, ensure that Classes loaded with local class loader first (parent last) is selected. Click Apply and then click Save."
"8 Update JRS shared library classpath Back to top
a. In WebSphere Integrated Solutions Console navigation pane click Environment > Shared libraries.
b. Click the JRS shard library name in the list to open it.
c. In the Classpath field, update the path to the new installation directory. For example:
D:\IBM\JazzTeamServer6.0\server\conf\rs\WAS_SharedLibrary
d. Click Apply and then Save directly to the master configuration.
15 Configure the Report Builder application Back to top
a. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
b. On the Enterprise Applications page, in the list of resources, click rs_war.
c. On the Configuration page, in the References section, click Shared library references.
d. Select the rs_war check box and click Reference shared libraries.
e. In the Available list, select JRS Shared Library and click the right arrow.
f. Click OK. Click OK again and then click Save.
g. In the list of resources, click rs_war.
h. On the Configuration page, under Detail Properties, click Class loading and update detection.
i. In the Class loader order group, ensure that Classes loaded with local class loader first (parent last) is selected. Click Apply and then click Save."
One other answer
Hi Chaitra,
Can you please take a look at this forum post and try clearing the WAS cache as noted there?
https://jazz.net/forum/questions/203246/jrs-is-offline-after-restarting-was-crrgw5319e-jazz-reporting-service-experienced-a-serious-exception-error-when-redirecting-to-reportdefinition?utm_campaign=forum&utm_medium=email&utm_source=forum-new-answer&utm_content=forum-question
These steps include clearing WAS logs as well which obviously is not necessary but I have seen few instances of a very similar error after installing JRS (or restarting the WAS profile hosting JRS) and clearing WAS cache resolved them.
We may need to see the full jts.log, rs.log and WAS SystemOut, SystemErr.log
Thanks,
Brett
Brett
Can you please take a look at this forum post and try clearing the WAS cache as noted there?
https://jazz.net/forum/questions/203246/jrs-is-offline-after-restarting-was-crrgw5319e-jazz-reporting-service-experienced-a-serious-exception-error-when-redirecting-to-reportdefinition?utm_campaign=forum&utm_medium=email&utm_source=forum-new-answer&utm_content=forum-question
These steps include clearing WAS logs as well which obviously is not necessary but I have seen few instances of a very similar error after installing JRS (or restarting the WAS profile hosting JRS) and clearing WAS cache resolved them.
We may need to see the full jts.log, rs.log and WAS SystemOut, SystemErr.log
Thanks,
Brett
Brett