It's all about the answers!

Ask a question

RTC 6 issue on WAS 8.0 : some URL's are using https://server:9080/jts

Renzo Disi (112) | asked Jul 22 '15, 1:00 p.m.
 After install RTC 6.0.0 on Websphere Application server 8.0 We have some issues, a lot of errors in logs and We are not able to access any DAshboard, this because for some reason there are calls to https://server:9080/jts

9080 is the non-secure port on WAS
9443 is the secure port on WAS

We use IHS to "proxy" (via Plugin) to Was/

URI registered in jts setup is https://server/jts  (IHS by access)

Is this a bug of RTC6 ? 

===== Method Not Allowed
<H1>Error Page Exception</H1>
<H4>SRVE0260E: The server cannot use the error page specified for your application to handle the Original Exception printed below.</H4>
<BR><H3>Original Exception: </H3>
<B>Error Message: </B>javax.servlet.ServletException: Failed to determine authentication method.  The URL from the request is:<BR>
<B>Error Code: </B>500<BR>
<B>Target Servlet: </B>equinoxbridgeservlet<BR>
<B>Error Stack: </B><BR> Unrecognized SSL message, plaintext connection?

One answer

permanent link
Ralph Schoon (63.2k33646) | answered Jul 23 '15, 4:55 a.m.
These are the general steps to take
  1. If you install the applications, make sure to provide a WAS profile that has a port that is secure e.g. 443 or 9443.
  2. Install IHS and make sure to provide a port that is secure e.g. 443 or 9443. See
  3. Configure IHS to forward the requests to the applications. 
  4. After all that is done, run the setup using the Public URI of the IHS.

I can only assume that you somehow got a http port into the setup.

Renzo Disi commented Jul 23 '15, 10:43 a.m.

 Ralph : 

I did all the steps you mentioned above. 

As I said before, registered URI es https://server/jts (IHS)

RTC is working (accesing https://server/ccm) that mean I can see most of the things ; Workitems, plans, builds, Streams, but there are some internals calls to https://server:9080/jts/discovery (by example), then We got errors in the App : Dashboard never load for this reason. Is just some calls, not  alls

Ralph Schoon commented Jul 23 '15, 11:04 a.m.

Check the *.properties files for 9080, check the URL's in the registration and friends/consumers. Something must have gone wrong, otherwise that should never show up. all communication should - as far as I can tell - work using the https port.

Consider to open a PMR with support.

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.