It's all about the answers!

Ask a question

Upgrading RTC 5.0.2 to 6.0.1 results in JRS not being accessible anymore.

Stephane Couillaud (15632344) | asked Feb 02 '16, 5:45 p.m.
edited Feb 02 '16, 5:48 p.m.
I just upgraded RTC 5.0.2 to 6.0.1 and in the process managed to break JRS.  I now get the following error in diagnostics:

Application: the discovery resource at 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;

I followed in the interactive guide to a T (at least I think I did).  Tried it many times but to no avail.   I also looked at other posts such as: 

but that did not help.  Here's a more detailed listing if I try and access  Perhaps it has more clues.  Any help to solve this would be much appreciated.  (I apologize for the format below)
@prefix err:   <> .

[ err:errorCause    [ err:detailedMessage  "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;\r\n\tat\r\n\tat org.apache.http.impl.client.AbstractHttpClient.execute(\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat javax.servlet.http.HttpServlet.service(\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat javax.servlet.http.HttpServlet.service(\r\n\tat javax.servlet.http.HttpServlet.service(\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat\r\n\tat$\r\n\tat$\r\n"^^<> ;
                      err:errorMessage     "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;"^^<> ;
                      err:errorStatus      "500"^^<>
                    ] ;
  err:errorMessage  "Internal Error"^^<> ;
  err:errorStatus   "500"^^<>

5 answers

permanent link
Donald Nong (14.5k414) | answered Feb 28 '16, 11:18 p.m.
The conflicting class appears to be org.apache.http.impl.client.AbstractHttpClient, not

The class has no changes regarding the execute() function between 5.0.2 and 6.0.1.

As for org.apache.http.impl.client.AbstractHttpClient, CLM 5.0.2 should come with org.apache.http.client 4.1.2 package, which contains the execute() function that matches the stack shown in the OP. But, CLM 6.0.1 should come with org.apache.http.client 4.5.0 package, which no longer has the execute() function in the AbstractHttpClient class.

So it appears that an older version of the org.apache.http.client package was loaded when JRS started. Apart from ensuring application paths and library paths are correct, make sure that the class loading policy is set to "Parent Last" for the JRS application in WAS.

permanent link
Francesco Chiossi (5.7k11119) | answered Feb 03 '16, 4:31 a.m.
edited Feb 03 '16, 4:32 a.m.
Hello Stephane,

this could be related to the configuration of the Shared libraries references (assuming you are using WAS).
I suggest to review the configuration described in the Configure the Report Builder (RS) application section of
Deploying applications for the Rational solution for Collaborative Lifecycle Management on WebSphere Application Server

Best Regards,

Francesco Chiossi

Stephane Couillaud commented Feb 03 '16, 12:49 p.m.

 Yes I did exactly what's in that link as well but to no avail.

permanent link
Erik Mats (10511025) | answered Feb 26 '16, 6:36 a.m.
edited Feb 26 '16, 6:45 a.m.

Have you been able to find a solution?

Your error message contains this:
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
This is NOT saying that the class JazzHttpClient does not exist. It is saying that this class has no method called "execute" that takes the parameters listed. (I am now researching this same problem but for a different "missing" function for a customer.

So this is not about a missing library. It must be due to a version incompatibility somewhere.

There are essentially three sources for such an incompatibility:
1. WAS cached files not cleared during upgrade
2. Wrong SW component versions being brought in.

My advice is that you add this custom Java flag to WAS:
Then stop/start the server

Then look for JazzHttpClient in the output and check that the versions loaded match what you expect for your JRS version. If you find that  this references a file that did not come from the latest time you deployed JRS, then you should re-deploy, clean out temp files and caches on WAS.

Example native_stderr.log output with -verbose:class:
class load: from: file:/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/Node01Cell/rs_war.ear/rs.war/WEB-INF/lib/jfs-sdk.jar

But the version incompatibility could also come from elsewhere in the callstack. other classes to check based on your callstack:

So look up the classes higher in the call stack in the "class load" info from native_stderr.log after you enable -verbose:class. See if you find a class that is being loaded from the wrong place.

Here is a technote about a similar problem by the way (but since that technote doesn't show the full callstack we can't be sure that it's the exact same problem 

Hope this helps

permanent link
Stephane Couillaud (15632344) | answered Mar 15 '16, 6:20 p.m.
Here are the findings from IBM summarized below:

1) For background JRS (Report Builder) is installed in the same WAS profile as RTC, DCC, JTS, LQE, RQM and DNG. Apparently, this topology is known to cause issues because not all applications use the same version of common libraries such as the Apache httpcore.jar and httpclient.jar. The hierarchical class loader in WAS can inadvertently load classes from the wrong version of the library.

2) From the stack trace in the WAS SystemOut.log the JazzHttpClient method execute(HttpHost, HttpRequest, HttpContext) is being called from the JazzHttpClient class in the jsf-sdk.jar library. The JazzHttpClient class actually extend the org.apache class DefaultHttpClient which in turn extends the org.apache class AbstractHttpClient. The method which does not exist but is being called is actually defined in the AbstractHttpClient class. Both DefaultHttpClient and AbstracthttpClient are included the common Apache library httpclient.jar.

Therefore, the WAS class loader (for the rs_war application) is picking up the wrong version of that httpclient.jar library. Report Builder 6.0.1 requires version 4.5 of that library and the actual jar file is httpclient-4.5.jar. In 5.0.2 the version of that library was httpclient-4.1.2.jar. I think WAS itself also has those HttpClient classes included in one of its own libraries and that version is not the same as the one Report Builder requires. So, it appears that the class loader from Report Builder (rs_war application) is picking up the wrong version of those Http Client library classes.

The next step for me is to provision a separate VM for JRS & DCC.  As an FYI this is a development environment that has worked just fine until now running on a single server.  I will provide an additional post if that solution solved the problem.

permanent link
Stephane Couillaud (15632344) | answered Apr 07 '16, 6:11 p.m.
As an FYI provisioning separate VMs for RS & DCC to avoid loading classes from the wrong libraries solved our problem.  Our conclusion was that a single server topology is no longer stable with 6.X.  At least this was only a development environment.

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.