series400.example450__MarketPrice__QueryServiceDiscovery

Hello,

I used Eclipse to set the proxy, and when I ran "series400.example450__MarketPrice__QueryServiceDiscovery", an error message was displayed on the console screen of Eclipse. When I checked with our network team, it was possible to communicate via a proxy. What are the possible causes of the error?

image






Best Answer

Answers

  • Hello @yuichiro.saito

    Did you generate the keystore file and pass it to the application via -keyfile and -keypasswd parameters yet?

    Please refer to this post answer and this article.

  • wasin.waeosri

    The keystore file has been created and I ran the program with the keystore file location and password in the command.

  • Hello @yuichiro.saito

    Could you please give me a full log or error messages when the problem occur?

    I have run the same example450__MarketPrice__QueryServiceDiscovery in my environment and it can connect to ERT in Cloud via port 14002 (default RSSL port) successfully.

    image

    Please note that my environment does not require the proxy to access internet RDP/ERT in Cloud server.

  • Hello. @wasin.waeosri

    Since our network requires a connection via a proxy, the sample program is executed after setting the proxy. When I checked with our network staff, I got the answer that it is considered that it is possible to communicate with your company without being blocked by our network. Please tell me the cause of login failure to ERT in Cloud.

    Error details: "Exception Type ='OmmInvalidUsageException', Text ='login failed (timed out after waiting 45000 milliseconds) for amer-3.pricing.streaming.edp.thomsonreuters.com:14002)', Error Code ='-4052' "

    image


  • @yuichiro.saito san,
    May I know what kind of trouble-isolation have you tried?
    And is there any authentication attempts logged on your company's network?
    We strongly suggest you to build a pilot test environment to isolate from your proxy and try it as it seems to be network reachability issue.

  • Hello @yuichiro.saito

    Do you still encounter the issue? Did you have a chance to test scenario as suggested by Naoto?