Support Board
Date/Time: Mon, 20 Jan 2025 14:02:42 +0000
Post From: Rithmic Data Connection Failure
| [2018-06-06 19:47:12] |
| |
|
To understand what we mean by complicated connection information, these are the connection details specified by Rithmic: REngineParams : REngineParams.sAdmCnnctPt : dd_admin_sslc REngineParams.envp : The following variables need to be present : * MML_DMN_SRVR_ADDR=ritpz01001.01.rithmic.com:65000~ritpz01000.01.rithmic.com:65000~ritpz01001.01.rithmic.net:65000~ritpz01000.01.rithmic.net:65000~ritpz01001.01.theomne.net:65000~ritpz01000.01.theomne.net:65000~ritpz01001.01.theomne.com:65000~ritpz01000.01.theomne.com:65000 * MML_DOMAIN_NAME=rithmic_prod_01_dmz_domain * MML_LIC_SRVR_ADDR=ritpz01000.01.rithmic.com:56000~ritpz01001.01.rithmic.com:56000~ritpz01000.01.rithmic.net:56000~ritpz01001.01.rithmic.net:56000~ritpz01000.01.theomne.net:56000~ritpz01001.01.theomne.net:56000~ritpz01000.01.theomne.com:56000~ritpz01001.01.theomne.com:56000 * MML_LOC_BROK_ADDR=ritpz01000.01.rithmic.com:64100 * MML_LOGGER_ADDR=ritpz01000.01.rithmic.com:45454~ritpz01000.01.rithmic.net:45454~ritpz01000.01.theomne.net:45454~ritpz01000.01.theomne.com:45454 * MML_LOG_TYPE=log_net * MML_SSL_CLNT_AUTH_FILE=rithmic_ssl_cert_auth_params (full path to file) * MML_SSL_CLNT_CERT_FILE=rithmic_ssl_client_params (full path to file) * MML_SSL_CLNT_KEY_FILE=rithmic_ssl_client_private_key (full path to file) * USER=my_user_name (put your user name) Login Params: * LoginParams.sMdCnnctPt : login_agent_tp_r01c * LoginParams.sIhCnnctPt : login_agent_historyc * LoginParams.sTsCnnctPt : login_agent_prodc * LoginParams.sPnLCnnctPt : login_agent_pnl_sslc And what has happened, is there are small changes with characters here and there among all of these details. They do not have one or two simple domain names like everyone else would have. Like where they would be responsible for setting the actual IP addresses. And multiply those above details by 15 and we mean by 15 because there are 15 sets of those! So they occasionally make changes across this immense set of information here and there with little character changes. And they expect us to keep those up-to-date without notice. So who's to blame? None of this makes any sense. And something inadvertent as actually having an extra space character at the beginning or possibly the end of one of these text strings will cause a connection problem. Whereas that would never cause a connection problem when a simple domain name is used and we are responsible for the network connection using our own software rather than the Rithmic software. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2018-06-06 19:53:57
|