It's all about the answers!

Ask a question

Could not locate storage service from https://app.elm.com:443/jts/rootservices. Make sure that server property Public URI Root is correct


Lucas Howlett (111) | asked Aug 02, 4:16 a.m.
Hi guys,

During jts/setup I am finalizing the RM application, during the Perform User Synchronization step I am getting the error:

Error 500: Propagated exception; original message [InternalServerErrorException: com.ibm.rdm.fronting.server.exception.InternalServerErrorException]

In the rmExt.log it dumps several:

[[TID: EA5EE16E]][][Default Executor-thread-19 @@ 18:02 <unauthenticated> <Mozilla/5.0 (Windows NT 10.0, Win64, x64, rv:103.0) Gecko/20100101 Firefox/103.0@192.168.104.130> /rm/process/templates] ERROR com.ibm.team.process.service                       - CRJAZ2675I A client action caused the server exception that is listed below. The identifier for the error is 35b41594-dd7e-4817-a1b8-9d4d592e61b6.
com.ibm.team.repository.common.TeamRepositoryException: Error 500

Could not locate storage service from https://app.elm.com:443/jts/rootservices. Make sure that server property Public URI Root is correct.

And then it dumps:

Request
        POST https://app.elm.com/rm/process/templates?overwrite=true HTTP/1.1
        x-com-ibm-team-prevent-csrf: true
        X-com-ibm-team-Trace-Identifier: EA5EE16E
        --Start entity---
        PK^C^D
        ^@^@^H^@^@q�=I^@^@^@^@^@^@^@^@^@^@^@^@^N^@^@^@RRSTemplateID/PK^C^D
        ^@^@^H^@^@��=I^@^@^@^@^@^@^@^@^@^@^@^@^Z^@^@^@RRSTemplateID/attachments/PK^C^D
        ^@^@^H^H^@q�=I�G^Uc`^@^@^@}^A^@^@^]^@^T^@RRSTemplateID/attachments.txt^A^@^P^@}^A^@^@^@^@^@^@`^@^@^@^@^@^@^@+I�-�I,I�OI��M-.NLO-��*��^V��;^Ea���~H���&���M4�^D�!!��$�~J��&^Wc^SM�~K^O
        �&���U9VC�2��^V�b^S��*Z��E^T��^R��^@PK^C^D
        ^@^@^H^H^@^S��N��xT�^C^@^@�^H^@^@$^@^T^@RRSTemplateID/attachments/0.messages^A^@^P^@�^H^@^@^@^@^@^@�^C^@^@^@^@^@^@�U�n�F^T��+.*�h^A[�^\ǩ��^@^]�FP�5$'(�^@���^R����<$��~F��^F���~O��^Qi�
        \t#p���s^_��~UN�8�h�<[�
        G^Gtc�~J���rJ^_�~F�.�/�;�g��7^�������>~�'=��(h$^F�F��.9�u���8��r��,�x�^HU��V�^^ik�^C��S^V�B����Pi)�.-J^W,#�}v����8�����i�Y(^X���*���>^?F�~A�����p0^^'����F���˧d^DD
�u�|I�3�P���m����m�$���~Q6��EQ� !�iķ^H��~Di�
        ����+R^^>��,�^C^A^R�1��^RlR{��)�c^@�o       6�^Q}�^G��^UJ�^N^Y�g��^@�^�Q�����Q^Tm�_^Z��-�`He�^V���h\HsR�>^?^N���c2^LzA        �Y�@9�^F  ,��b��^Y�Ʒ���^W���3%f�&^K�jY�B�����B<-m�V^TT
^Ke �^Ahy^_��\3��2��Y�1�p�=��9�^?�%^L�����b�Ӽ^R��B^[��J�[�c�~F]�kH^?-^W^R�^[���3S=^K6��S/F^?^C�?�[^?��^X��^C�2t^Q�\<��ڰ� p4�p����^R�y����U���#����z�����      �ʮ^_� H^DX�?y�^^
O(��)NM�!����^F�^L�L�`�~Z6�?��J�Xۮ'�:���j,^\���&̦���h���@�mH��4@�~T~[��Sle�Y��0��eA�s���G��[�o�x�~E�|Q^Gr
        b^Ht$yp5<��f�vp�*^Rja�a��z        �t�pY[...]
        --End entity-----
Response:
        HTTP/1.1 500 Internal Server Error
        X-Powered-By: Servlet/3.0
        Strict-Transport-Security: max-age=31536000
        Content-Type: text/plain;charset=UTF-8
        Content-Language: en-US
        Content-Length: 495
        Date: Tue, 02 Aug 2022 08:03:07 GMT
        Expires: Thu, 01 Dec 1994 16:00:00 GMT
        Cache-Control: no-cache="set-cookie, set-cookie2"
        Content-Length: 495
        ---Start entity---
Error 500

Error 500

Could not locate storage service from https://app.elm.com:443/jts/rootservices. Make sure that server property Public URI Root is correct.
CRJAZ2676I Details about the error were written to the log file. To find this data, search the log file for this identifier: bced4b92-f80d-4f57-91c5-0f88260b777a.
CRJAZ2676I Details about the error were written to the log file. To find this data, search the log file for this identifier: cac9d5c0-a8a2-4341-a6f4-aa1b76dc155e

jts.log dumps:

[Default Executor-thread-120 @@ 18:05 <unauthenticated> <Mozilla/5.0 (Windows NT 10.0, Win64, x64, rv:103.0) Gecko/20100101 Firefox/103.0@192.168.104.130> /jts/process-authoring/resource] ERROR com.ibm.team.process.service                       [TID: 15ACE308] - CRJAZ2675I A client action caused the server exception that is listed below. The identifier for the error is db8460af-8896-4835-86a3-15981b4392b1.
com.ibm.team.repository.common.TeamRepositoryException: Could not locate storage service from https://app.elm.com:443/jts/rootservices. Make sure that server property Public URI Root is correct.

If I curl https://app.elm.com:443/jts/rootservices from the server I get the specified xml document. There is an entry there for <jfs:storage rdf:resource="https://app.elm.com/jts/storage"/>

The server is sitting behind a reverse proxy. The reverse proxy forwards 443 -> 9443.

There is another JTS running behind the reverse proxy which was set up fine.

The public URI is correct, I have set this with the jts/setup GUI and it resolves.

Can anyone provide any help? The server can resolve the URLs it is asking for I am not sure why it's getting a 500 error when syncing the users? Why can't it find the storage


Comments
Ralph Schoon commented Aug 02, 4:40 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Several thoughts:

1. Version numbers?
2. If using 443 as well known port for the proxy, why would you have that port in the public URI? The purpose of 443 is to not have to have to specify it. For all I know the public URI should be https://app.elm.com/jts/rootservices   
3. Just because you can access the Public URI with a browser does not mean the DNGserver can, unless it is from the same server.
 
Other than that, I can't tell why the error happens.  It is most certainly a configuration issue e.g. in the proxy. 


Lucas Howlett commented Aug 02, 6:54 a.m.
Hi Ralph,

1. Sorry I forgot to mention in the question I am using 7.0.2 iFix 011

2. That is an interesting point, because I have never entered 443 in the public uri. I will not share the exact url but, as seen in jts/admin, it is https://app.elm.com/jts. There is no 443.

So, for some reason the server is looking for the storage unit at https://app.elm.com:443/jts/rootservices (with 443 added)

But the same log also tries a request to - POST https://app.elm.com/rm/process/templates?overwrite=true HTTP/1.1

3. Yes you are correct, however by using curl command from the app server I am receiving the intended response.

Thanks for your answer, I will examine the proxy layer.


Ralph Schoon commented Aug 02, 7:44 a.m. | edited Aug 02, 7:47 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Somewhere along the setup, the 443 sneaked into the public URI (of at least part of the applications). I do not know when and why. Maybe the configuration e.g. of the proxy. Maybe when registering applications. At least DNG seems to believe the public URI has the 443 in the URI. I think there is a fundamental configuration issue that caused this. The applications are very sensitive to the public URI and DNG seems to be the worst. This needs to be corrected. You may want to check the configuration of the working setup. 

My experience is that the 500 is due to a call that has no response, so it got stuck somewhere.


The POST is a red herring. 

Sorry to be not more helpful. 


Lucas Howlett commented Aug 04, 9:55 p.m.
So I am almost certain that this is relating to the Public URI and the reverse proxy setup.

I get the following error in the logs from:

./repotools-jts.sh -setup repositoryURL=https://app.elm.com/jts adminUserId=uuid adminPassword=password

AND

./repotools-rm.sh -syncUsers repositoryURL=https://app.elm.com/rm

2022-08-05 11:02:31,038 CRJAZ2906E The following URL could not be reached because of a general authentication error: https://isw.elm.iswcloud.com/jts
com.ibm.team.repository.common.transport.ServiceNotAvailableException: CRJAZ0106E The server is temporarily unavailable. The request for the following URL was denied: /jts/versionCompatibility?clientVersion=7.0.2.

I can curl from the server and get the response {"compatible":true,"isJTS":true}.

The server can resolve the URLs that the logs say it cant, it can get a response but the application itself can't get a response?

Ralph Schoon commented Aug 05, 2:25 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

This is not really a support case, more consulting. Anyway, you might want to consider opening a case with support and ask for hints what could be the issue, if noting come up here on the forum.

Be the first one to answer this question!


Register or to post your answer.