Support Board
Date/Time: Sat, 10 May 2025 12:44:41 +0000
Frequent disconnect from CQG
View Count: 3596
[2016-01-28 17:37:17] |
User295967 - Posts: 32 |
Since a few days I get frequent disconnects from CQG. I eliminated any antivirus and firewall, but the issue stayed. I also upgraded to latest Sierra. See attached log Software version: 1361 | 2016-01-28 16:11:51 Uses New Spreadsheets | 2016-01-28 16:11:51 Enabled for: Advanced Features. | 2016-01-28 16:11:51 Enabled for: Sierra Chart Historical Data Service. | 2016-01-28 16:11:51 Allow Support for Sierra Chart Data Feeds is enabled. | 2016-01-28 16:11:51 Current selected Data/Trading service: CQG FIX Trading | 2016-01-28 16:11:51 Chart Update Interval: 100 | 2016-01-28 16:11:51 Data/Trade Service Settings automatically set. | 2016-01-28 16:11:51 Time Zone: +01:00:00 (CET+01CEST+01,M3.5.0/02:00,M10.5.0/03:00) | 2016-01-28 16:11:51 2016-01-28 16:11:51 Local computer time | 2016-01-28 16:11:51 2016-01-28 15:11:51 Local computer time in UTC | 2016-01-28 16:11:51 2016-01-28 16:11:51 Local computer time in SC Time Zone | 2016-01-28 16:11:51 2016-01-28 15:11:53 Server time in UTC | 2016-01-28 16:11:51 Local computer UTC time and Server UTC time difference: 3 seconds. | 2016-01-28 16:11:51 Program path: C:\SierraChart\ | 2016-01-28 16:11:51 Data Files path: C:\SierraChart\Data\ | 2016-01-28 16:11:51 OS Version Number: 6.1 | 2016-01-28 16:11:51 Locale Information: C | 2016-01-28 16:11:51 Checking for new symbol settings for cqg | 2016-01-28 16:11:51 HTTPS connection to www.sierrachart.com:443 (0) | Resolved address sierrachart.com to IP 5.9.8.236 | 2016-01-28 16:11:51 HTTPS connection to www.sierrachart.com:443 (3) | Connected. | 2016-01-28 16:11:52 HTTPS connection to www.sierrachart.com:443 (3) | Starting TLS 1.2 connection. | 2016-01-28 16:11:52 HTTPS connection to www.sierrachart.com:443 (3) | SSL connection established. | 2016-01-28 16:11:52 Requesting symbol settings for cqg. Overwrite = on. | 2016-01-28 16:11:52 Symbol settings received. | 2016-01-28 16:11:52 Processed received symbol settings | 2016-01-28 16:11:52 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-01-28 16:11:56 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214 | 2016-01-28 16:11:57 HTTPS connection to www.sierrachart.com:443 (3) | SSL connection closed by remote side. | 2016-01-28 16:11:57 HTTPS connection to www.sierrachart.com:443 (3) | SSL object has been freed. SSL state is now disconnected. | 2016-01-28 16:11:57 HTTPS connection to www.sierrachart.com:443 (3) | Shutdown and closed. | 2016-01-28 16:11:57 socket (4) | Connected. | 2016-01-28 16:11:57 CQG FIX: Sending the Logon message. | 2016-01-28 16:11:57 CQG FIX Trading | Connected to trading server. | 2016-01-28 16:11:57 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-01-28 16:11:57 CQG WebAPI | Connecting to websocket server. | 2016-01-28 16:11:57 CQG FIX - FCM name: AMP | 2016-01-28 16:11:57 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 208.48.16.35 | 2016-01-28 16:11:57 CQG WebAPI websocket (5) | Connected. | 2016-01-28 16:11:58 CQG WebAPI websocket (5) | Starting SSL 3/2 connection. | 2016-01-28 16:11:58 CQG WebAPI websocket (5) | SSL connection established. | 2016-01-28 16:11:58 CQG WebAPI | Opening websocket. | 2016-01-28 16:11:58 CQG WebAPI | Sending websocket handshake. | 2016-01-28 16:11:58 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-01-28 16:11:58 CQG WebAPI | Web socket state is now open. | 2016-01-28 16:11:58 CQG FIX Trading | Websocket connected. | 2016-01-28 16:11:58 CQG FIX Trading | Sending market data logon message. | 2016-01-28 16:11:58 CQG FIX Trading | Logon successful. Session Token = bCqPBIdHvAMCKQXfJmt/WbbtQbyfOeIMVN1zLJnc9OE | 2016-01-28 16:11:59 CQG FIX Trading | Connected to data and trading server. | 2016-01-28 16:11:59 File >> Disconnect selected. | 2016-01-28 16:12:10 CQG FIX: DisconnectFIX called. | 2016-01-28 16:12:10 CQG FIX: Sending a Logout message. | 2016-01-28 16:12:10 CQG FIX Trading | Sending logoff message. | 2016-01-28 16:12:10 CQG WebAPI websocket (5) | SSL shutdown indicates not able to send 'close notify'. | 2016-01-28 16:12:10 CQG WebAPI websocket (5) | SSL has been shut down. | 2016-01-28 16:12:10 CQG WebAPI websocket (5) | SSL object has been freed. SSL state is now disconnected. | 2016-01-28 16:12:10 CQG WebAPI websocket (5) | Shutdown and closed. | 2016-01-28 16:12:10 CQG FIX Trading | Websocket closed. | 2016-01-28 16:12:10 CQG FIX Trading | Disconnected. | 2016-01-28 16:12:10 CQG FIX: Received a Logout message. Text = NormalLogoutInitiatedByCounterparty | 2016-01-28 16:12:10 socket (4) | Shutdown and closed. | 2016-01-28 16:12:10 CQG FIX: Disconnected. | 2016-01-28 16:12:10 Current selected Data/Trading service: CQG WebAPI | 2016-01-28 16:12:19 Checking for new symbol settings for cqg | 2016-01-28 16:12:19 HTTPS connection to www.sierrachart.com:443 (0) | Resolved address sierrachart.com to IP 5.9.8.236 | 2016-01-28 16:12:19 HTTPS connection to www.sierrachart.com:443 (6) | Connected. | 2016-01-28 16:12:19 HTTPS connection to www.sierrachart.com:443 (6) | Starting TLS 1.2 connection. | 2016-01-28 16:12:19 HTTPS connection to www.sierrachart.com:443 (6) | SSL connection established. | 2016-01-28 16:12:19 Requesting symbol settings for cqg. Overwrite = on. | 2016-01-28 16:12:19 Symbol settings received. | 2016-01-28 16:12:19 Processed received symbol settings | 2016-01-28 16:12:20 CQG WebAPI | Connecting to market data server api.cqg.com | 2016-01-28 16:12:21 CQG WebAPI | Connecting to websocket server. | 2016-01-28 16:12:21 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 208.48.16.35 | 2016-01-28 16:12:21 CQG WebAPI websocket (7) | Connected. | 2016-01-28 16:12:21 CQG WebAPI websocket (7) | Starting SSL 3/2 connection. | 2016-01-28 16:12:21 CQG WebAPI websocket (7) | SSL connection established. | 2016-01-28 16:12:21 CQG WebAPI | Opening websocket. | 2016-01-28 16:12:21 CQG WebAPI | Sending websocket handshake. | 2016-01-28 16:12:21 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-01-28 16:12:22 CQG WebAPI | Web socket state is now open. | 2016-01-28 16:12:22 CQG WebAPI | Websocket connected. | 2016-01-28 16:12:22 CQG WebAPI | Sending market data logon message. | 2016-01-28 16:12:22 CQG WebAPI | Logon successful. Session Token = Jai4Ss/8XaOYQ6VlZ7H0K6a5UsuArQuzmYxtIvHLm7U | 2016-01-28 16:12:22 CQG WebAPI | Connected to data and trading server. | 2016-01-28 16:12:22 CQG WebAPI | Sending Trade Accounts request message. | 2016-01-28 16:12:22 CQG WebAPI | Brokerage name: AMP Account Name: 86078 | 2016-01-28 16:12:22 HTTPS connection to www.sierrachart.com:443 (6) | SSL connection closed by remote side. | 2016-01-28 16:12:24 HTTPS connection to www.sierrachart.com:443 (6) | SSL object has been freed. SSL state is now disconnected. | 2016-01-28 16:12:24 HTTPS connection to www.sierrachart.com:443 (6) | Shutdown and closed. | 2016-01-28 16:12:24 File >> Disconnect selected. | 2016-01-28 16:14:08 CQG WebAPI | Sending logoff message. | 2016-01-28 16:14:08 CQG WebAPI websocket (7) | SSL shutdown indicates not able to send 'close notify'. | 2016-01-28 16:14:08 CQG WebAPI websocket (7) | SSL has been shut down. | 2016-01-28 16:14:08 CQG WebAPI websocket (7) | SSL object has been freed. SSL state is now disconnected. | 2016-01-28 16:14:08 CQG WebAPI websocket (7) | Shutdown and closed. | 2016-01-28 16:14:08 CQG WebAPI | Websocket closed. | 2016-01-28 16:14:08 CQG WebAPI | Disconnected. | 2016-01-28 16:14:08 Current selected Data/Trading service: CQG FIX Trading | 2016-01-28 16:14:20 Checking for new symbol settings for cqg | 2016-01-28 16:14:20 HTTPS connection to www.sierrachart.com:443 (0) | Resolved address sierrachart.com to IP 5.9.8.236 | 2016-01-28 16:14:20 HTTPS connection to www.sierrachart.com:443 (9) | Connected. | 2016-01-28 16:14:20 HTTPS connection to www.sierrachart.com:443 (9) | Starting TLS 1.2 connection. | 2016-01-28 16:14:20 HTTPS connection to www.sierrachart.com:443 (9) | SSL connection established. | 2016-01-28 16:14:20 Requesting symbol settings for cqg. Overwrite = on. | 2016-01-28 16:14:20 Symbol settings received. | 2016-01-28 16:14:20 Processed received symbol settings | 2016-01-28 16:14:20 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-01-28 16:14:21 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214 | 2016-01-28 16:14:21 socket (10) | Connected. | 2016-01-28 16:14:22 CQG FIX: Sending the Logon message. | 2016-01-28 16:14:22 CQG FIX Trading | Connected to trading server. | 2016-01-28 16:14:22 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-01-28 16:14:22 CQG WebAPI | Connecting to websocket server. | 2016-01-28 16:14:22 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 208.48.16.35 | 2016-01-28 16:14:22 CQG FIX - FCM name: AMP | 2016-01-28 16:14:22 CQG WebAPI websocket (11) | Connected. | 2016-01-28 16:14:22 CQG WebAPI websocket (11) | Starting SSL 3/2 connection. | 2016-01-28 16:14:22 CQG WebAPI websocket (11) | SSL connection established. | 2016-01-28 16:14:23 CQG WebAPI | Opening websocket. | 2016-01-28 16:14:23 CQG WebAPI | Sending websocket handshake. | 2016-01-28 16:14:23 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-01-28 16:14:23 CQG WebAPI | Web socket state is now open. | 2016-01-28 16:14:23 CQG FIX Trading | Websocket connected. | 2016-01-28 16:14:23 CQG FIX Trading | Sending market data logon message. | 2016-01-28 16:14:23 CQG FIX Trading | Logon successful. Session Token = vyP2jtJjkyZ9gebKzexyjVGeyObec+d1mZGLoqjnDWc | 2016-01-28 16:14:23 CQG FIX Trading | Connected to data and trading server. | 2016-01-28 16:14:23 HTTPS connection to www.sierrachart.com:443 (9) | SSL connection closed by remote side. | 2016-01-28 16:14:25 HTTPS connection to www.sierrachart.com:443 (9) | SSL object has been freed. SSL state is now disconnected. | 2016-01-28 16:14:25 HTTPS connection to www.sierrachart.com:443 (9) | Shutdown and closed. | 2016-01-28 16:14:25 CQG FIX Trading | Using primary service for historical data. | 2016-01-28 16:22:02 CQG FIX Trading | Using primary service for historical data. | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: F.US.SF6H16. ID: 1 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for F.US.SF6H16. ID: 888203 | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: F.US.BP6H16. ID: 2 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for F.US.BP6H16. ID: 888204 | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: F.US.CA6H16. ID: 3 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for F.US.CA6H16. ID: 888205 | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: F.US.ENQH16. ID: 4 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for F.US.ENQH16. ID: 888206 | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: F.US.DA6H16. ID: 5 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for F.US.DA6H16. ID: 888207 | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: F.US.EPH16. ID: 6 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for F.US.EPH16. ID: 888208 | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: F.US.JY6H16. ID: 7 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for F.US.JY6H16. ID: 888209 | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: F.US.TFEH16. ID: 8 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for F.US.TFEH16. ID: 888210 | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: F.US.YMH16. ID: 9 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for F.US.YMH16. ID: 888211 | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: F.US.EU6H16. ID: 10 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for F.US.EU6H16. ID: 888212 | 2016-01-28 16:22:02 Using Bid/Ask average for last trade price for AUDCHF | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: AUDCHF. ID: 11 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888213 | 2016-01-28 16:22:02 Subscribing to common currency symbol for profit/loss currency calculations. Symbol: USDCHF | 2016-01-28 16:22:02 Using Bid/Ask average for last trade price for USDCHF | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: USDCHF. ID: 12 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for USDCHF. ID: 888214 | 2016-01-28 16:22:02 CQG FIX Trading | Using primary service for historical data. | 2016-01-28 16:22:02 Intraday data recording state for symbol AUDCHF is set to download 'Pending'. | 2016-01-28 16:22:02 HD Request # 2 | Downloading Intraday chart data for AUDCHF to the file AUDCHF.scid. Service: fxcm | 2016-01-28 16:22:02 HD Request # 2 | Download start Date-Time: 2016-01-28 16:06:58.000 | 2016-01-28 16:22:02 Using Bid/Ask average for last trade price for AUDCAD | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: AUDCAD. ID: 13 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888215 | 2016-01-28 16:22:02 Subscribing to common currency symbol for profit/loss currency calculations. Symbol: USDCAD | 2016-01-28 16:22:02 Using Bid/Ask average for last trade price for USDCAD | 2016-01-28 16:22:02 CQG FIX Trading | Starting real-time market data updates for: USDCAD. ID: 14 | 2016-01-28 16:22:02 CQG FIX Trading | Sending symbol resolution request for USDCAD. ID: 888216 | 2016-01-28 16:22:02 CQG FIX Trading | Using primary service for historical data. | 2016-01-28 16:22:02 Intraday data recording state for symbol AUDCAD is set to download 'Pending'. | 2016-01-28 16:22:02 Intraday data recording state for symbol F.US.TFEH16 is set to download 'Pending'. | 2016-01-28 16:22:02 HD Request # 3 | Downloading Intraday chart data for F.US.TFEH16 to the file F.US.TFEH16.scid. Service: cqg | 2016-01-28 16:22:03 HD Request # 3 | Download start Date-Time: 2016-01-28 16:11:04.000 | 2016-01-28 16:22:03 HD Request # 3 | Using server: ds4.sierracharts.com port 10149 | 2016-01-28 16:22:03 Socket (0) | Resolved address ds4.sierracharts.com to IP 204.11.49.26 | 2016-01-28 16:22:03 CQG FIX Trading | Received symbol resolution report for symbol F.US.SF6H16. Request ID: 888203. Contract ID: 1. | 2016-01-28 16:22:03 CQG FIX Trading | Requesting market data for F.US.SF6H16 | 2016-01-28 16:22:03 Socket (16) | Connected. | 2016-01-28 16:22:03 HD Request # 3 | Sending historical data logon request message. | 2016-01-28 16:22:03 CQG FIX Trading | Received symbol resolution report for symbol F.US.BP6H16. Request ID: 888204. Contract ID: 2. | 2016-01-28 16:22:03 CQG FIX Trading | Requesting market data for F.US.BP6H16 | 2016-01-28 16:22:03 CQG FIX Trading | Received symbol resolution report for symbol F.US.CA6H16. Request ID: 888205. Contract ID: 3. | 2016-01-28 16:22:03 CQG FIX Trading | Requesting market data for F.US.CA6H16 | 2016-01-28 16:22:03 CQG FIX Trading | Received symbol resolution report for symbol F.US.ENQH16. Request ID: 888206. Contract ID: 4. | 2016-01-28 16:22:03 CQG FIX Trading | Requesting market data for F.US.ENQH16 | 2016-01-28 16:22:03 CQG FIX Trading | Received symbol resolution report for symbol F.US.DA6H16. Request ID: 888207. Contract ID: 5. | 2016-01-28 16:22:03 CQG FIX Trading | Requesting market data for F.US.DA6H16 | 2016-01-28 16:22:03 CQG FIX Trading | Received symbol resolution report for symbol F.US.EPH16. Request ID: 888208. Contract ID: 6. | 2016-01-28 16:22:03 CQG FIX Trading | Requesting market data for F.US.EPH16 | 2016-01-28 16:22:03 CQG FIX Trading | Received symbol resolution report for symbol F.US.JY6H16. Request ID: 888209. Contract ID: 7. | 2016-01-28 16:22:03 CQG FIX Trading | Requesting market data for F.US.JY6H16 | 2016-01-28 16:22:03 CQG FIX Trading | Received symbol resolution report for symbol F.US.TFEH16. Request ID: 888210. Contract ID: 8. | 2016-01-28 16:22:03 CQG FIX Trading | Requesting market data for F.US.TFEH16 | 2016-01-28 16:22:03 CQG FIX Trading | Received symbol resolution report for symbol F.US.YMH16. Request ID: 888211. Contract ID: 9. | 2016-01-28 16:22:03 CQG FIX Trading | Requesting market data for F.US.YMH16 | 2016-01-28 16:22:03 CQG FIX Trading | Received symbol resolution report for symbol F.US.EU6H16. Request ID: 888212. Contract ID: 10. | 2016-01-28 16:22:03 CQG FIX Trading | Requesting market data for F.US.EU6H16 | 2016-01-28 16:22:03 HD Request # 2 | Error downloading historical Intraday data for AUDCHF. Exact match not found for symbol AUDCHF | 2016-01-28 16:22:03 HD Request # 2 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCHF | 2016-01-28 16:22:03 HD Request # 4 | Downloading Intraday chart data for AUDCHF to the file AUDCHF.scid. Service: fxcm | 2016-01-28 16:22:03 HD Request # 4 | Download start Date-Time: 2016-01-28 16:06:58.000 | 2016-01-28 16:22:03 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888217 | 2016-01-28 16:22:03 Symbol Error - USDCHF is unknown, unavailable, or improperly formatted. Exact match not found for symbol USDCHF | 2016-01-28 16:22:03 Symbol Error - AUDCAD is unknown, unavailable, or improperly formatted. Exact match not found for symbol AUDCAD | 2016-01-28 16:22:03 Symbol Error - USDCAD is unknown, unavailable, or improperly formatted. Exact match not found for symbol USDCAD | 2016-01-28 16:22:03 HD Request # 4 | Error downloading historical Intraday data for AUDCHF. Exact match not found for symbol AUDCHF | 2016-01-28 16:22:03 HD Request # 4 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCHF | 2016-01-28 16:22:03 HD Request # 5 | Downloading Intraday chart data for AUDCHF to the file AUDCHF.scid. Service: fxcm | 2016-01-28 16:22:03 HD Request # 5 | Download start Date-Time: 2016-01-28 16:06:58.000 | 2016-01-28 16:22:03 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888218 | 2016-01-28 16:22:03 HD Request # 3 | Requesting Intraday data. Start Date-Time: 2016-01-28 16:11:04. Record interval: 1. Symbol: F.US.TFEH16 | 2016-01-28 16:22:03 HD Request # 5 | Error downloading historical Intraday data for AUDCHF. Exact match not found for symbol AUDCHF | 2016-01-28 16:22:03 HD Request # 5 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCHF | 2016-01-28 16:22:03 HD Request # 5 | Intraday download COMPLETE for AUDCHF. Completion time: 0s. Unique request ID: 1 | 2016-01-28 16:22:03 Removed historical data download ID 1 | 2016-01-28 16:22:03 Real-time Intraday chart data file updates started for AUDCHF | 2016-01-28 16:22:03 Intraday chart data file opened for AUDCHF | 2016-01-28 16:22:03 HD Request # 6 | Downloading Intraday chart data for AUDCAD to the file AUDCAD.scid. Service: fxcm | 2016-01-28 16:22:03 HD Request # 6 | Download start Date-Time: 2016-01-28 16:06:57.000 | 2016-01-28 16:22:03 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888219 | 2016-01-28 16:22:03 HD Request # 3 | Decompressing data. | 2016-01-28 16:22:03 HD Request # 3 | Receiving Intraday data for F.US.TFEH16 starting at 2016-01-28 16:11:04 | 2016-01-28 16:22:03 HD Request # 3 | Timestamp of first Intraday data file record written: 2016-01-28 16:11:04 | 2016-01-28 16:22:03 HD Request # 6 | Error downloading historical Intraday data for AUDCAD. Exact match not found for symbol AUDCAD | 2016-01-28 16:22:03 HD Request # 6 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCAD | 2016-01-28 16:22:03 HD Request # 7 | Downloading Intraday chart data for AUDCAD to the file AUDCAD.scid. Service: fxcm | 2016-01-28 16:22:03 HD Request # 7 | Download start Date-Time: 2016-01-28 16:06:57.000 | 2016-01-28 16:22:03 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888220 | 2016-01-28 16:22:03 Socket (16) | Shutdown and closed. | 2016-01-28 16:22:03 The network socket for historical data has been closed. | 2016-01-28 16:22:03 HD Request # 3 | Received 550 records from 2016-01-28 16:11:04 to 2016-01-28 16:22:04 (11.0 minutes) and wrote 550 records for F.US.TFEH16 | 2016-01-28 16:22:03 HD Request # 3 | Intraday download COMPLETE for F.US.TFEH16. Completion time: 0s. Unique request ID: 3 | 2016-01-28 16:22:03 Removed historical data download ID 3 | 2016-01-28 16:22:03 Real-time Intraday chart data file updates started for F.US.TFEH16 | 2016-01-28 16:22:03 Intraday chart data file opened for F.US.TFEH16 | 2016-01-28 16:22:03 HD Request # 7 | Error downloading historical Intraday data for AUDCAD. Exact match not found for symbol AUDCAD | 2016-01-28 16:22:04 HD Request # 7 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCAD | 2016-01-28 16:22:04 HD Request # 8 | Downloading Intraday chart data for AUDCAD to the file AUDCAD.scid. Service: fxcm | 2016-01-28 16:22:04 HD Request # 8 | Download start Date-Time: 2016-01-28 16:06:57.000 | 2016-01-28 16:22:04 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888221 | 2016-01-28 16:22:04 HD Request # 8 | Error downloading historical Intraday data for AUDCAD. Exact match not found for symbol AUDCAD | 2016-01-28 16:22:04 HD Request # 8 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCAD | 2016-01-28 16:22:04 HD Request # 8 | Intraday download COMPLETE for AUDCAD. Completion time: 0s. Unique request ID: 2 | 2016-01-28 16:22:04 Removed historical data download ID 2 | 2016-01-28 16:22:04 Real-time Intraday chart data file updates started for AUDCAD | 2016-01-28 16:22:04 Intraday chart data file opened for AUDCAD | 2016-01-28 16:22:04 Requesting market depth updates for: AUDCAD if supported. | 2016-01-28 16:22:04 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888222 | 2016-01-28 16:22:04 Requesting market depth updates for: AUDCHF if supported. | 2016-01-28 16:22:04 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888223 | 2016-01-28 16:22:04 Requesting market depth updates for: F.US.TFEH16 if supported. | 2016-01-28 16:22:04 CQG FIX Trading | Requesting market data including full depth for F.US.TFEH16 | 2016-01-28 16:22:04 Symbol Error - AUDCAD is unknown, unavailable, or improperly formatted. Exact match not found for symbol AUDCAD | 2016-01-28 16:22:06 Symbol Error - AUDCHF is unknown, unavailable, or improperly formatted. Exact match not found for symbol AUDCHF | 2016-01-28 16:22:06 CQG WebAPI websocket (11) | Closed. No error. | 2016-01-28 16:34:40 CQG WebAPI websocket (11) | SSL shutdown indicates not able to send 'close notify'. | 2016-01-28 16:34:40 CQG WebAPI websocket (11) | SSL has been shut down. | 2016-01-28 16:34:40 CQG WebAPI websocket (11) | SSL object has been freed. SSL state is now disconnected. | 2016-01-28 16:34:40 CQG WebAPI websocket (11) | Shutdown and closed. | 2016-01-28 16:34:40 CQG WebAPI | Network socket for websocket has been closed by remote side. | 2016-01-28 16:34:40 CQG FIX Trading | Websocket closed. | 2016-01-28 16:34:40 Connection to the external service has been lost. | 2016-01-28 16:34:40 CQG FIX: DisconnectFIX called. | 2016-01-28 16:34:40 CQG FIX: Sending a Logout message. | 2016-01-28 16:34:40 CQG FIX Trading | Disconnected. | 2016-01-28 16:34:40 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-01-28 16:34:40 CQG FIX: Received a Logout message. Text = NormalLogoutInitiatedByCounterparty | 2016-01-28 16:34:40 socket (10) | Shutdown and closed. | 2016-01-28 16:34:40 CQG FIX: Disconnected. | 2016-01-28 16:34:40 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-01-28 16:34:43 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214 | 2016-01-28 16:34:43 socket (23) | Connected. | 2016-01-28 16:34:43 CQG FIX: Sending the Logon message. | 2016-01-28 16:34:43 CQG FIX Trading | Connected to trading server. | 2016-01-28 16:34:43 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-01-28 16:34:43 CQG WebAPI | Connecting to websocket server. | 2016-01-28 16:34:43 CQG FIX - FCM name: AMP | 2016-01-28 16:34:44 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 208.48.16.35 | 2016-01-28 16:34:44 CQG WebAPI websocket (24) | Connected. | 2016-01-28 16:34:44 CQG WebAPI websocket (24) | Starting SSL 3/2 connection. | 2016-01-28 16:34:44 CQG WebAPI websocket (24) | SSL connection established. | 2016-01-28 16:34:44 CQG WebAPI | Opening websocket. | 2016-01-28 16:34:44 CQG WebAPI | Sending websocket handshake. | 2016-01-28 16:34:44 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-01-28 16:34:45 CQG WebAPI | Web socket state is now open. | 2016-01-28 16:34:45 CQG FIX Trading | Websocket connected. | 2016-01-28 16:34:45 CQG FIX Trading | Sending market data logon message. | 2016-01-28 16:34:45 CQG FIX Trading | Logon successful. Session Token = 9880Z6ijKH7KZpy3uNAzXIKexLoGN4UcDKZg4BzSXR0 | 2016-01-28 16:34:45 CQG FIX Trading | Connected to data and trading server. | 2016-01-28 16:34:45 Using Bid/Ask average for last trade price for AUDCHF | 2016-01-28 16:34:45 CQG FIX Trading | Starting real-time market data updates for: AUDCHF. ID: 1 | 2016-01-28 16:34:45 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888224 | 2016-01-28 16:34:45 Subscribing to common currency symbol for profit/loss currency calculations. Symbol: USDCHF | 2016-01-28 16:34:45 Using Bid/Ask average for last trade price for USDCHF | 2016-01-28 16:34:45 CQG FIX Trading | Starting real-time market data updates for: USDCHF. ID: 2 | 2016-01-28 16:34:45 CQG FIX Trading | Sending symbol resolution request for USDCHF. ID: 888225 | 2016-01-28 16:34:45 CQG FIX Trading | Using primary service for historical data. | 2016-01-28 16:34:45 Intraday data recording state for symbol AUDCHF is set to download 'Pending'. | 2016-01-28 16:34:45 HD Request # 9 | Downloading Intraday chart data for AUDCHF to the file AUDCHF.scid. Service: fxcm | 2016-01-28 16:34:45 HD Request # 9 | Download start Date-Time: 2016-01-28 16:06:58.000 | 2016-01-28 16:34:45 CQG FIX Trading | Starting real-time market data updates for: F.US.TFEH16. ID: 3 | 2016-01-28 16:34:45 CQG FIX Trading | Sending symbol resolution request for F.US.TFEH16. ID: 888226 | 2016-01-28 16:34:45 Intraday data recording state for symbol F.US.TFEH16 is set to download 'Pending'. | 2016-01-28 16:34:45 HD Request # 10 | Downloading Intraday chart data for F.US.TFEH16 to the file F.US.TFEH16.scid. Service: cqg | 2016-01-28 16:34:45 HD Request # 10 | Download start Date-Time: 2016-01-28 16:33:56.000 | 2016-01-28 16:34:45 HD Request # 10 | Using server: ds5.sierracharts.com port 10149 | 2016-01-28 16:34:45 Using Bid/Ask average for last trade price for AUDCAD | 2016-01-28 16:34:45 CQG FIX Trading | Starting real-time market data updates for: AUDCAD. ID: 4 | 2016-01-28 16:34:45 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888227 | 2016-01-28 16:34:45 Subscribing to common currency symbol for profit/loss currency calculations. Symbol: USDCAD | 2016-01-28 16:34:45 Using Bid/Ask average for last trade price for USDCAD | 2016-01-28 16:34:45 CQG FIX Trading | Starting real-time market data updates for: USDCAD. ID: 5 | 2016-01-28 16:34:45 CQG FIX Trading | Sending symbol resolution request for USDCAD. ID: 888228 | 2016-01-28 16:34:45 CQG FIX Trading | Using primary service for historical data. | 2016-01-28 16:34:45 Intraday data recording state for symbol AUDCAD is set to download 'Pending'. | 2016-01-28 16:34:45 Socket (0) | Resolved address ds5.sierracharts.com to IP 204.15.192.106 | 2016-01-28 16:34:45 HD Request # 9 | Error downloading historical Intraday data for AUDCHF. Exact match not found for symbol AUDCHF | 2016-01-28 16:34:45 HD Request # 9 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCHF | 2016-01-28 16:34:45 HD Request # 11 | Downloading Intraday chart data for AUDCHF to the file AUDCHF.scid. Service: fxcm | 2016-01-28 16:34:45 HD Request # 11 | Download start Date-Time: 2016-01-28 16:06:58.000 | 2016-01-28 16:34:45 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888229 | 2016-01-28 16:34:45 Socket (25) | Connected. | 2016-01-28 16:34:45 HD Request # 10 | Sending historical data logon request message. | 2016-01-28 16:34:45 CQG FIX Trading | Received symbol resolution report for symbol F.US.TFEH16. Request ID: 888226. Contract ID: 2. | 2016-01-28 16:34:45 CQG FIX Trading | Requesting market data including full depth for F.US.TFEH16 | 2016-01-28 16:34:45 Symbol Error - USDCHF is unknown, unavailable, or improperly formatted. Exact match not found for symbol USDCHF | 2016-01-28 16:34:45 Symbol Error - AUDCAD is unknown, unavailable, or improperly formatted. Exact match not found for symbol AUDCAD | 2016-01-28 16:34:45 Symbol Error - USDCAD is unknown, unavailable, or improperly formatted. Exact match not found for symbol USDCAD | 2016-01-28 16:34:45 HD Request # 11 | Error downloading historical Intraday data for AUDCHF. Exact match not found for symbol AUDCHF | 2016-01-28 16:34:45 HD Request # 11 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCHF | 2016-01-28 16:34:45 HD Request # 12 | Downloading Intraday chart data for AUDCHF to the file AUDCHF.scid. Service: fxcm | 2016-01-28 16:34:45 HD Request # 12 | Download start Date-Time: 2016-01-28 16:06:58.000 | 2016-01-28 16:34:45 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888230 | 2016-01-28 16:34:45 HD Request # 10 | Requesting Intraday data. Start Date-Time: 2016-01-28 16:33:56. Record interval: 1. Symbol: F.US.TFEH16 | 2016-01-28 16:34:46 CQG FIX Trading | Starting real-time market data updates for: F.US.SF6H16. ID: 6 | 2016-01-28 16:34:46 CQG FIX Trading | Sending symbol resolution request for F.US.SF6H16. ID: 888231 | 2016-01-28 16:34:46 CQG FIX Trading | Starting real-time market data updates for: F.US.BP6H16. ID: 7 | 2016-01-28 16:34:46 CQG FIX Trading | Sending symbol resolution request for F.US.BP6H16. ID: 888232 | 2016-01-28 16:34:46 CQG FIX Trading | Starting real-time market data updates for: F.US.CA6H16. ID: 8 | 2016-01-28 16:34:46 CQG FIX Trading | Sending symbol resolution request for F.US.CA6H16. ID: 888233 | 2016-01-28 16:34:46 CQG FIX Trading | Starting real-time market data updates for: F.US.ENQH16. ID: 9 | 2016-01-28 16:34:46 CQG FIX Trading | Sending symbol resolution request for F.US.ENQH16. ID: 888234 | 2016-01-28 16:34:46 CQG FIX Trading | Starting real-time market data updates for: F.US.DA6H16. ID: 10 | 2016-01-28 16:34:46 CQG FIX Trading | Sending symbol resolution request for F.US.DA6H16. ID: 888235 | 2016-01-28 16:34:46 CQG FIX Trading | Starting real-time market data updates for: F.US.EPH16. ID: 11 | 2016-01-28 16:34:46 CQG FIX Trading | Sending symbol resolution request for F.US.EPH16. ID: 888236 | 2016-01-28 16:34:46 CQG FIX Trading | Starting real-time market data updates for: F.US.JY6H16. ID: 12 | 2016-01-28 16:34:46 CQG FIX Trading | Sending symbol resolution request for F.US.JY6H16. ID: 888237 | 2016-01-28 16:34:46 CQG FIX Trading | Starting real-time market data updates for: F.US.YMH16. ID: 13 | 2016-01-28 16:34:46 CQG FIX Trading | Sending symbol resolution request for F.US.YMH16. ID: 888238 | 2016-01-28 16:34:46 CQG FIX Trading | Starting real-time market data updates for: F.US.EU6H16. ID: 14 | 2016-01-28 16:34:46 CQG FIX Trading | Sending symbol resolution request for F.US.EU6H16. ID: 888239 | 2016-01-28 16:34:46 HD Request # 10 | Decompressing data. | 2016-01-28 16:34:46 HD Request # 10 | Receiving Intraday data for F.US.TFEH16 starting at 2016-01-28 16:33:56 | 2016-01-28 16:34:46 HD Request # 10 | Timestamp of first Intraday data file record written: 2016-01-28 16:33:56 | 2016-01-28 16:34:46 Socket (25) | Shutdown and closed. | 2016-01-28 16:34:46 The network socket for historical data has been closed. | 2016-01-28 16:34:46 HD Request # 10 | Received 43 records from 2016-01-28 16:33:56 to 2016-01-28 16:34:43 (47.0 seconds) and wrote 43 records for F.US.TFEH16 | 2016-01-28 16:34:46 HD Request # 10 | Intraday download COMPLETE for F.US.TFEH16. Completion time: 0s. Unique request ID: 5 | 2016-01-28 16:34:46 Removed historical data download ID 5 | 2016-01-28 16:34:46 Real-time Intraday chart data file updates started for F.US.TFEH16 | 2016-01-28 16:34:46 Intraday chart data file opened for F.US.TFEH16 | 2016-01-28 16:34:46 HD Request # 12 | Error downloading historical Intraday data for AUDCHF. Exact match not found for symbol AUDCHF | 2016-01-28 16:34:47 HD Request # 12 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCHF | 2016-01-28 16:34:47 HD Request # 12 | Intraday download COMPLETE for AUDCHF. Completion time: 2s. Unique request ID: 4 | 2016-01-28 16:34:47 Removed historical data download ID 4 | 2016-01-28 16:34:47 Real-time Intraday chart data file updates started for AUDCHF | 2016-01-28 16:34:47 Intraday chart data file opened for AUDCHF | 2016-01-28 16:34:47 HD Request # 13 | Downloading Intraday chart data for AUDCAD to the file AUDCAD.scid. Service: fxcm | 2016-01-28 16:34:47 HD Request # 13 | Download start Date-Time: 2016-01-28 16:06:57.000 | 2016-01-28 16:34:47 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888240 | 2016-01-28 16:34:47 CQG FIX Trading | Received symbol resolution report for symbol F.US.SF6H16. Request ID: 888231. Contract ID: 6. | 2016-01-28 16:34:47 CQG FIX Trading | Requesting market data for F.US.SF6H16 | 2016-01-28 16:34:47 CQG FIX Trading | Received symbol resolution report for symbol F.US.BP6H16. Request ID: 888232. Contract ID: 7. | 2016-01-28 16:34:47 CQG FIX Trading | Requesting market data for F.US.BP6H16 | 2016-01-28 16:34:47 CQG FIX Trading | Received symbol resolution report for symbol F.US.CA6H16. Request ID: 888233. Contract ID: 8. | 2016-01-28 16:34:47 CQG FIX Trading | Requesting market data for F.US.CA6H16 | 2016-01-28 16:34:47 CQG FIX Trading | Received symbol resolution report for symbol F.US.ENQH16. Request ID: 888234. Contract ID: 9. | 2016-01-28 16:34:47 CQG FIX Trading | Requesting market data for F.US.ENQH16 | 2016-01-28 16:34:47 CQG FIX Trading | Received symbol resolution report for symbol F.US.DA6H16. Request ID: 888235. Contract ID: 10. | 2016-01-28 16:34:47 CQG FIX Trading | Requesting market data for F.US.DA6H16 | 2016-01-28 16:34:47 CQG FIX Trading | Received symbol resolution report for symbol F.US.EPH16. Request ID: 888236. Contract ID: 11. | 2016-01-28 16:34:47 CQG FIX Trading | Requesting market data for F.US.EPH16 | 2016-01-28 16:34:47 CQG FIX Trading | Received symbol resolution report for symbol F.US.JY6H16. Request ID: 888237. Contract ID: 12. | 2016-01-28 16:34:47 CQG FIX Trading | Requesting market data for F.US.JY6H16 | 2016-01-28 16:34:47 CQG FIX Trading | Received symbol resolution report for symbol F.US.YMH16. Request ID: 888238. Contract ID: 13. | 2016-01-28 16:34:47 CQG FIX Trading | Requesting market data for F.US.YMH16 | 2016-01-28 16:34:47 CQG FIX Trading | Received symbol resolution report for symbol F.US.EU6H16. Request ID: 888239. Contract ID: 14. | 2016-01-28 16:34:47 CQG FIX Trading | Requesting market data for F.US.EU6H16 | 2016-01-28 16:34:47 Requesting market depth updates for: AUDCAD if supported. | 2016-01-28 16:34:50 Requesting market depth updates for: AUDCHF if supported. | 2016-01-28 16:34:50 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888241 | 2016-01-28 16:34:50 Requesting market depth updates for: F.US.TFEH16 if supported. | 2016-01-28 16:34:50 CQG FIX Trading | Requesting market data including full depth for F.US.TFEH16 | 2016-01-28 16:34:50 HD Request # 13 | Error downloading historical Intraday data for AUDCAD. Exact match not found for symbol AUDCAD | 2016-01-28 16:34:50 HD Request # 13 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCAD | 2016-01-28 16:34:50 HD Request # 14 | Downloading Intraday chart data for AUDCAD to the file AUDCAD.scid. Service: fxcm | 2016-01-28 16:34:50 HD Request # 14 | Download start Date-Time: 2016-01-28 16:06:57.000 | 2016-01-28 16:34:50 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888242 | 2016-01-28 16:34:50 Symbol Error - AUDCHF is unknown, unavailable, or improperly formatted. Exact match not found for symbol AUDCHF | 2016-01-28 16:34:53 HD Request # 14 | Error downloading historical Intraday data for AUDCAD. Exact match not found for symbol AUDCAD | 2016-01-28 16:34:54 HD Request # 14 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCAD | 2016-01-28 16:34:54 HD Request # 15 | Downloading Intraday chart data for AUDCAD to the file AUDCAD.scid. Service: fxcm | 2016-01-28 16:34:54 HD Request # 15 | Download start Date-Time: 2016-01-28 16:06:57.000 | 2016-01-28 16:34:54 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888243 | 2016-01-28 16:34:54 HD Request # 15 | Error downloading historical Intraday data for AUDCAD. Exact match not found for symbol AUDCAD | 2016-01-28 16:34:58 HD Request # 15 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCAD | 2016-01-28 16:34:58 HD Request # 15 | Intraday download COMPLETE for AUDCAD. Completion time: 4s. Unique request ID: 6 | 2016-01-28 16:34:58 Removed historical data download ID 6 | 2016-01-28 16:34:58 Real-time Intraday chart data file updates started for AUDCAD | 2016-01-28 16:34:58 Intraday chart data file opened for AUDCAD | 2016-01-28 16:34:58 CQG WebAPI websocket (24) | Closed. No error. | 2016-01-28 18:19:23 CQG WebAPI websocket (24) | SSL shutdown indicates not able to send 'close notify'. | 2016-01-28 18:19:23 CQG WebAPI websocket (24) | SSL has been shut down. | 2016-01-28 18:19:23 CQG WebAPI websocket (24) | SSL object has been freed. SSL state is now disconnected. | 2016-01-28 18:19:23 CQG WebAPI websocket (24) | Shutdown and closed. | 2016-01-28 18:19:23 CQG WebAPI | Network socket for websocket has been closed by remote side. | 2016-01-28 18:19:23 CQG FIX Trading | Websocket closed. | 2016-01-28 18:19:23 Connection to the external service has been lost. | 2016-01-28 18:19:23 CQG FIX: DisconnectFIX called. | 2016-01-28 18:19:23 CQG FIX: Sending a Logout message. | 2016-01-28 18:19:23 CQG FIX Trading | Disconnected. | 2016-01-28 18:19:23 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-01-28 18:19:23 CQG FIX: Received a Logout message. Text = NormalLogoutInitiatedByCounterparty | 2016-01-28 18:19:23 socket (23) | Shutdown and closed. | 2016-01-28 18:19:23 CQG FIX: Disconnected. | 2016-01-28 18:19:23 CQG FIX: Connecting to fixapi.cqgtrader.com. Port: 6912. | 2016-01-28 18:19:26 socket (0) | Resolved address fixapi.cqgtrader.com to IP 208.48.16.214 | 2016-01-28 18:19:26 socket (79) | Connected. | 2016-01-28 18:19:26 CQG FIX: Sending the Logon message. | 2016-01-28 18:19:26 CQG FIX Trading | Connected to trading server. | 2016-01-28 18:19:26 CQG FIX Trading | Connecting to market data server api.cqg.com | 2016-01-28 18:19:26 CQG WebAPI | Connecting to websocket server. | 2016-01-28 18:19:26 CQG FIX - FCM name: AMP | 2016-01-28 18:19:27 CQG WebAPI websocket (0) | Resolved address api.geo.cqg.com to IP 208.48.16.35 | 2016-01-28 18:19:27 CQG WebAPI websocket (80) | Connected. | 2016-01-28 18:19:27 CQG WebAPI websocket (80) | Starting SSL 3/2 connection. | 2016-01-28 18:19:27 CQG WebAPI websocket (80) | SSL connection established. | 2016-01-28 18:19:28 CQG WebAPI | Opening websocket. | 2016-01-28 18:19:28 CQG WebAPI | Sending websocket handshake. | 2016-01-28 18:19:28 CQG WebAPI | Received websocket handshake acknowledgment. | 2016-01-28 18:19:28 CQG WebAPI | Web socket state is now open. | 2016-01-28 18:19:28 CQG FIX Trading | Websocket connected. | 2016-01-28 18:19:28 CQG FIX Trading | Sending market data logon message. | 2016-01-28 18:19:28 CQG FIX Trading | Logon successful. Session Token = 3hriPuHVEMtMoLOfsDW/pW9A6dPjHeNV8/IQzd0192g | 2016-01-28 18:19:28 CQG FIX Trading | Connected to data and trading server. | 2016-01-28 18:19:28 Using Bid/Ask average for last trade price for AUDCAD | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: AUDCAD. ID: 1 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888244 | 2016-01-28 18:19:28 Subscribing to common currency symbol for profit/loss currency calculations. Symbol: USDCAD | 2016-01-28 18:19:28 Using Bid/Ask average for last trade price for USDCAD | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: USDCAD. ID: 2 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for USDCAD. ID: 888245 | 2016-01-28 18:19:28 CQG FIX Trading | Using primary service for historical data. | 2016-01-28 18:19:28 Intraday data recording state for symbol AUDCAD is set to download 'Pending'. | 2016-01-28 18:19:28 HD Request # 16 | Downloading Intraday chart data for AUDCAD to the file AUDCAD.scid. Service: fxcm | 2016-01-28 18:19:28 HD Request # 16 | Download start Date-Time: 2016-01-28 16:06:57.000 | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: F.US.TFEH16. ID: 3 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for F.US.TFEH16. ID: 888246 | 2016-01-28 18:19:28 Intraday data recording state for symbol F.US.TFEH16 is set to download 'Pending'. | 2016-01-28 18:19:28 HD Request # 17 | Downloading Intraday chart data for F.US.TFEH16 to the file F.US.TFEH16.scid. Service: cqg | 2016-01-28 18:19:28 HD Request # 17 | Download start Date-Time: 2016-01-28 18:18:54.000 | 2016-01-28 18:19:28 HD Request # 17 | Using server: ds3.sierracharts.com port 10149 | 2016-01-28 18:19:28 Using Bid/Ask average for last trade price for AUDCHF | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: AUDCHF. ID: 4 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888247 | 2016-01-28 18:19:28 Subscribing to common currency symbol for profit/loss currency calculations. Symbol: USDCHF | 2016-01-28 18:19:28 Using Bid/Ask average for last trade price for USDCHF | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: USDCHF. ID: 5 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for USDCHF. ID: 888248 | 2016-01-28 18:19:28 CQG FIX Trading | Using primary service for historical data. | 2016-01-28 18:19:28 Intraday data recording state for symbol AUDCHF is set to download 'Pending'. | 2016-01-28 18:19:28 Socket (0) | Resolved address ds3.sierracharts.com to IP 65.182.172.164 | 2016-01-28 18:19:28 HD Request # 16 | Error downloading historical Intraday data for AUDCAD. Exact match not found for symbol AUDCAD | 2016-01-28 18:19:28 HD Request # 16 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCAD | 2016-01-28 18:19:28 HD Request # 18 | Downloading Intraday chart data for AUDCAD to the file AUDCAD.scid. Service: fxcm | 2016-01-28 18:19:28 HD Request # 18 | Download start Date-Time: 2016-01-28 16:06:57.000 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888249 | 2016-01-28 18:19:28 Socket (81) | Connected. | 2016-01-28 18:19:28 HD Request # 17 | Sending historical data logon request message. | 2016-01-28 18:19:28 CQG FIX Trading | Received symbol resolution report for symbol F.US.TFEH16. Request ID: 888246. Contract ID: 2. | 2016-01-28 18:19:28 CQG FIX Trading | Requesting market data including full depth for F.US.TFEH16 | 2016-01-28 18:19:28 Symbol Error - USDCAD is unknown, unavailable, or improperly formatted. Exact match not found for symbol USDCAD | 2016-01-28 18:19:28 Symbol Error - AUDCHF is unknown, unavailable, or improperly formatted. Exact match not found for symbol AUDCHF | 2016-01-28 18:19:28 Symbol Error - USDCHF is unknown, unavailable, or improperly formatted. Exact match not found for symbol USDCHF | 2016-01-28 18:19:28 HD Request # 18 | Error downloading historical Intraday data for AUDCAD. Exact match not found for symbol AUDCAD | 2016-01-28 18:19:28 HD Request # 18 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCAD | 2016-01-28 18:19:28 HD Request # 19 | Downloading Intraday chart data for AUDCAD to the file AUDCAD.scid. Service: fxcm | 2016-01-28 18:19:28 HD Request # 19 | Download start Date-Time: 2016-01-28 16:06:57.000 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888250 | 2016-01-28 18:19:28 HD Request # 19 | Error downloading historical Intraday data for AUDCAD. Exact match not found for symbol AUDCAD | 2016-01-28 18:19:28 HD Request # 19 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCAD | 2016-01-28 18:19:28 HD Request # 19 | Intraday download COMPLETE for AUDCAD. Completion time: 0s. Unique request ID: 7 | 2016-01-28 18:19:28 Removed historical data download ID 7 | 2016-01-28 18:19:28 Real-time Intraday chart data file updates started for AUDCAD | 2016-01-28 18:19:28 Intraday chart data file opened for AUDCAD | 2016-01-28 18:19:28 HD Request # 20 | Downloading Intraday chart data for AUDCHF to the file AUDCHF.scid. Service: fxcm | 2016-01-28 18:19:28 HD Request # 20 | Download start Date-Time: 2016-01-28 16:06:58.000 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888251 | 2016-01-28 18:19:28 HD Request # 17 | Requesting Intraday data. Start Date-Time: 2016-01-28 18:18:54. Record interval: 1. Symbol: F.US.TFEH16 | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: F.US.SF6H16. ID: 6 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for F.US.SF6H16. ID: 888252 | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: F.US.BP6H16. ID: 7 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for F.US.BP6H16. ID: 888253 | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: F.US.CA6H16. ID: 8 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for F.US.CA6H16. ID: 888254 | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: F.US.ENQH16. ID: 9 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for F.US.ENQH16. ID: 888255 | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: F.US.DA6H16. ID: 10 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for F.US.DA6H16. ID: 888256 | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: F.US.EPH16. ID: 11 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for F.US.EPH16. ID: 888257 | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: F.US.JY6H16. ID: 12 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for F.US.JY6H16. ID: 888258 | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: F.US.YMH16. ID: 13 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for F.US.YMH16. ID: 888259 | 2016-01-28 18:19:28 CQG FIX Trading | Starting real-time market data updates for: F.US.EU6H16. ID: 14 | 2016-01-28 18:19:28 CQG FIX Trading | Sending symbol resolution request for F.US.EU6H16. ID: 888260 | 2016-01-28 18:19:28 HD Request # 20 | Error downloading historical Intraday data for AUDCHF. Exact match not found for symbol AUDCHF | 2016-01-28 18:19:29 HD Request # 20 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCHF | 2016-01-28 18:19:29 HD Request # 21 | Downloading Intraday chart data for AUDCHF to the file AUDCHF.scid. Service: fxcm | 2016-01-28 18:19:29 HD Request # 21 | Download start Date-Time: 2016-01-28 16:06:58.000 | 2016-01-28 18:19:29 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888261 | 2016-01-28 18:19:29 HD Request # 17 | Decompressing data. | 2016-01-28 18:19:29 HD Request # 17 | Receiving Intraday data for F.US.TFEH16 starting at 2016-01-28 18:18:54 | 2016-01-28 18:19:29 HD Request # 17 | Timestamp of first Intraday data file record written: 2016-01-28 18:18:54 | 2016-01-28 18:19:29 Socket (81) | Shutdown and closed. | 2016-01-28 18:19:29 The network socket for historical data has been closed. | 2016-01-28 18:19:29 HD Request # 17 | Received 14 records from 2016-01-28 18:18:54 to 2016-01-28 18:19:28 (34.0 seconds) and wrote 14 records for F.US.TFEH16 | 2016-01-28 18:19:29 HD Request # 17 | Intraday download COMPLETE for F.US.TFEH16. Completion time: 1s. Unique request ID: 8 | 2016-01-28 18:19:29 Removed historical data download ID 8 | 2016-01-28 18:19:29 Real-time Intraday chart data file updates started for F.US.TFEH16 | 2016-01-28 18:19:29 Intraday chart data file opened for F.US.TFEH16 | 2016-01-28 18:19:29 CQG FIX Trading | Received symbol resolution report for symbol F.US.SF6H16. Request ID: 888252. Contract ID: 6. | 2016-01-28 18:19:29 CQG FIX Trading | Requesting market data for F.US.SF6H16 | 2016-01-28 18:19:29 CQG FIX Trading | Received symbol resolution report for symbol F.US.BP6H16. Request ID: 888253. Contract ID: 7. | 2016-01-28 18:19:29 CQG FIX Trading | Requesting market data for F.US.BP6H16 | 2016-01-28 18:19:29 CQG FIX Trading | Received symbol resolution report for symbol F.US.CA6H16. Request ID: 888254. Contract ID: 8. | 2016-01-28 18:19:29 CQG FIX Trading | Requesting market data for F.US.CA6H16 | 2016-01-28 18:19:29 CQG FIX Trading | Received symbol resolution report for symbol F.US.ENQH16. Request ID: 888255. Contract ID: 9. | 2016-01-28 18:19:29 CQG FIX Trading | Requesting market data for F.US.ENQH16 | 2016-01-28 18:19:29 CQG FIX Trading | Received symbol resolution report for symbol F.US.DA6H16. Request ID: 888256. Contract ID: 10. | 2016-01-28 18:19:29 CQG FIX Trading | Requesting market data for F.US.DA6H16 | 2016-01-28 18:19:29 CQG FIX Trading | Received symbol resolution report for symbol F.US.EPH16. Request ID: 888257. Contract ID: 11. | 2016-01-28 18:19:29 CQG FIX Trading | Requesting market data for F.US.EPH16 | 2016-01-28 18:19:29 CQG FIX Trading | Received symbol resolution report for symbol F.US.JY6H16. Request ID: 888258. Contract ID: 12. | 2016-01-28 18:19:29 CQG FIX Trading | Requesting market data for F.US.JY6H16 | 2016-01-28 18:19:29 CQG FIX Trading | Received symbol resolution report for symbol F.US.YMH16. Request ID: 888259. Contract ID: 13. | 2016-01-28 18:19:29 CQG FIX Trading | Requesting market data for F.US.YMH16 | 2016-01-28 18:19:29 CQG FIX Trading | Received symbol resolution report for symbol F.US.EU6H16. Request ID: 888260. Contract ID: 14. | 2016-01-28 18:19:29 CQG FIX Trading | Requesting market data for F.US.EU6H16 | 2016-01-28 18:19:29 HD Request # 21 | Error downloading historical Intraday data for AUDCHF. Exact match not found for symbol AUDCHF | 2016-01-28 18:19:29 HD Request # 21 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCHF | 2016-01-28 18:19:29 HD Request # 22 | Downloading Intraday chart data for AUDCHF to the file AUDCHF.scid. Service: fxcm | 2016-01-28 18:19:29 HD Request # 22 | Download start Date-Time: 2016-01-28 16:06:58.000 | 2016-01-28 18:19:29 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888262 | 2016-01-28 18:19:29 HD Request # 22 | Error downloading historical Intraday data for AUDCHF. Exact match not found for symbol AUDCHF | 2016-01-28 18:19:30 HD Request # 22 | Received 0 records from 00:00:00 to 00:00:00 (0.0 seconds) and wrote 0 records for AUDCHF | 2016-01-28 18:19:30 HD Request # 22 | Intraday download COMPLETE for AUDCHF. Completion time: 1s. Unique request ID: 9 | 2016-01-28 18:19:30 Removed historical data download ID 9 | 2016-01-28 18:19:30 Real-time Intraday chart data file updates started for AUDCHF | 2016-01-28 18:19:30 Intraday chart data file opened for AUDCHF | 2016-01-28 18:19:30 Requesting market depth updates for: AUDCAD if supported. | 2016-01-28 18:19:33 CQG FIX Trading | Sending symbol resolution request for AUDCAD. ID: 888263 | 2016-01-28 18:19:33 Requesting market depth updates for: AUDCHF if supported. | 2016-01-28 18:19:33 CQG FIX Trading | Sending symbol resolution request for AUDCHF. ID: 888264 | 2016-01-28 18:19:33 Requesting market depth updates for: F.US.TFEH16 if supported. | 2016-01-28 18:19:33 CQG FIX Trading | Requesting market data including full depth for F.US.TFEH16 | 2016-01-28 18:19:33 Symbol Error - AUDCAD is unknown, unavailable, or improperly formatted. Exact match not found for symbol AUDCAD | 2016-01-28 18:19:33 Symbol Error - AUDCHF is unknown, unavailable, or improperly formatted. Exact match not found for symbol AUDCHF | 2016-01-28 18:19:33 |
[2016-01-28 18:44:55] |
User546713 - Posts: 15 |
Hi, I got similar problem with AMP-CQG-SC and sent a ticket to SC support. Your log: CQG WebAPI websocket (11) | Closed. No error. | 2016-01-28 16:34:40 CQG WebAPI websocket (11) | SSL shutdown indicates not able to send 'close notify'. | 2016-01-28 16:34:40 CQG WebAPI websocket (11) | SSL has been shut down. | 2016-01-28 16:34:40 CQG WebAPI websocket (11) | SSL object has been freed. SSL state is now disconnected. | 2016-01-28 16:34:40 CQG WebAPI websocket (11) | Shutdown and closed. | 2016-01-28 16:34:40 CQG WebAPI | Network socket for websocket has been closed by remote side. | 2016-01-28 16:34:40 CQG FIX Trading | Websocket closed. | 2016-01-28 16:34:40 Connection to the external service has been lost. | 2016-01-28 16:34:40 CQG FIX: DisconnectFIX called. | 2016-01-28 16:34:40 CQG FIX: Sending a Logout message. | 2016-01-28 16:34:40 CQG FIX Trading | Disconnected. | 2016-01-28 16:34:40 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-01-28 16:34:40 CQG FIX: Received a Logout message. Text = NormalLogoutInitiatedByCounterparty | 2016-01-28 16:34:40 socket (10) | Shutdown and closed. | 2016-01-28 16:34:40 CQG FIX: Disconnected. | 2016-01-28 16:34:40 However there is error code on my log: CQG WebAPI | Websocket received OpCode Close. Received status code: 1000 | 2016-01-28 15:27:46 CQG FIX Trading | Websocket closed. | 2016-01-28 15:27:46 Connection to the external service has been lost. | 2016-01-28 15:27:46 CQG FIX: DisconnectFIX called. | 2016-01-28 15:27:46 CQG FIX: Sending a Logout message. | 2016-01-28 15:27:46 CQG FIX Trading | Sending logoff message. | 2016-01-28 15:27:46 CQG WebAPI websocket (30) | SSL shutdown indicates not able to send 'close notify'. | 2016-01-28 15:27:46 CQG WebAPI websocket (30) | SSL has been shut down. | 2016-01-28 15:27:46 CQG WebAPI websocket (30) | SSL object has been freed. SSL state is now disconnected. | 2016-01-28 15:27:46 CQG WebAPI websocket (30) | Shutdown and closed. | 2016-01-28 15:27:46 CQG FIX Trading | Websocket closed. | 2016-01-28 15:27:46 CQG FIX Trading | Disconnected. | 2016-01-28 15:27:46 Will reconnect to the server in 3.0 seconds. Select 'File >> Disconnect' to prevent further connection attempts. | 2016-01-28 15:27:46 CQG FIX: Received a Logout message. Text = NormalLogoutInitiatedByCounterparty | 2016-01-28 15:27:46 socket (29) | Shutdown and closed. | 2016-01-28 15:27:46 CQG FIX: Disconnected. | 2016-01-28 15:27:46 Awaiting response from SC support |
[2016-01-28 18:53:22] |
User75096 - Posts: 48 |
here the same and not the first day, regards
|
[2016-01-28 20:17:37] |
|
Here is the relevant documentation for this: CQG Trading Platform Service: Solving CQG Market Data Feed Problems Refer specifically to the section titled "Frequent Reconnections". For both of these cases this is what applies. CQG has been made aware of this problem. So we do not think there is anything more that needs to be done right now. This is an issue for CQG to resolve. We will let CQG know about these cases as well. 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: 2016-01-28 20:25:31
|
[2016-01-28 20:28:47] |
|
We just sent CQG the following message: We have three more reports today of users losing connections:
Frequent disconnect from CQG It seems unlikely this is a problem on the users side in all of these cases. This is just too many of them. 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 |
[2016-01-28 21:59:46] |
User295967 - Posts: 32 |
There are more issues with CQG server. I now got a new type of error message in the log. Data feed was lost from CQG. Well, I also run other PC with Ninja on Continuum (CQG) and there no issues at all for months - using same hardwired connections/router/ISP. Could SC support please report this as well to CQG? I think it is unacceptable if the CQG server just shows no activity. Or is it something at SC side where SC is not noticing CQG server activity? FYI: Time 21:34 corresponds with 15:34 EST CQG FIX: No heartbeat messages received from server. Sent Test Request message to server. | 2016-01-28 21:34:26 The data feed was lost. There was no activity for at least 60.0 seconds. | 2016-01-28 21:34:43 Connection to the external service has been lost. | 2016-01-28 21:34:43 CQG FIX: DisconnectFIX called. | 2016-01-28 21:34:43 CQG FIX: Sending a Logout message. | 2016-01-28 21:34:43 CQG FIX Trading | Sending logoff message. | 2016-01-28 21:34:43 CQG WebAPI websocket (80) | SSL shutdown indicates not able to send 'close notify'. | 2016-01-28 21:34:43 CQG WebAPI websocket (80) | SSL has been shut down. | 2016-01-28 21:34:43 CQG WebAPI websocket (80) | SSL object has been freed. SSL state is now disconnected. | 2016-01-28 21:34:43 CQG WebAPI websocket (80) | Shutdown and closed. | 2016-01-28 21:34:43 CQG FIX Trading | Websocket closed. | 2016-01-28 21:34:43 CQG FIX Trading | Disconnected. | 2016-01-28 21:34:43 |
[2016-01-28 22:15:48] |
|
This is a less common problem and indicates some connectivity issue: CQG FIX: No heartbeat messages received from server. Sent Test Request message to server. | 2016-01-28 21:34:26 Or is it something at SC side where SC is not noticing CQG server activity?
No this is not it. Sierra Chart has very reliable software which we developed that maintains connections to external services. The FIX connection code/software works with multiple services and it is very stable and reliable. It is extensively used every day without any problem.
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: 2016-01-28 22:16:32
|
[2016-01-28 22:26:04] |
|
If this is an ongoing issue: CQG FIX: No heartbeat messages received from server. Sent Test Request message to server. | 2016-01-28 21:34:26 Then change Global Settings >> Data/Trade Service Settings >> Service to "CQG Web API". 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: 2016-01-28 22:26:30
|
[2016-01-29 12:51:34] |
User295967 - Posts: 32 |
Then change Global Settings >> Data/Trade Service Settings >> Service to "CQG Web API".
Will not help in my case as I need the server sided OCO handling. The Web API does not provide for that. I am fully aware that Sierra is not in control over the datafeed for live trading (e.g. CQG, TT, Rithmic etc.) So what can I do to get the most likely reliable stable datafeed connection when using Sierra? Which datafeed supplier for live trading? If this problem is ongoing, then it is recommended you use the Sierra Chart Exchange Data Feed. This data feed requires a Direct Account.
Go "direct" with Sierra ? Please explain why the AMP Sierra offer/license is technically different from the Sierra "direct" offer? In the end both AMP and Sierra "direct" make use of the same datafeed for live trading - or not? I am confused.
|
[2016-01-29 17:26:53] |
User75096 - Posts: 48 |
with 1344 all is fine , regards
|
[2016-01-29 18:30:01] |
|
Will not help in my case as I need the server sided OCO handling. The Web API does not provide for that. with 1344 all is fine , regards Therefore, this is a clue that the new protocol buffer definition file provided by CQG maybe has a compatibility problem with their current server. We will look into this. So what can I do to get the most likely reliable stable datafeed connection when using Sierra? Which datafeed supplier for live trading? Sierra Chart Exchange Data Feed For information about a direct account, refer to: https://www.sierrachart.com/index.php?page=doc/doc_DirectAccount.html Although in the case of using the Sierra Chart Exchange Data Feed a direct account will not be necessary sometime later in February. You can use the account provided by your broker AMP. We will try to have this ready as soon as possible. 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: 2016-01-29 18:34:23
|
[2016-01-29 19:05:28] |
User75096 - Posts: 48 |
thanks
|
[2016-01-29 21:44:13] |
|
Regarding this: with 1344 all is fine , regards
We checked with CQG, and the version of the protocol buffer interface file is not going to matter. So in other words, being that the latest versions of Sierra Chart use the newest version of the protocol buffer interface file, it does not matter. So if you notice a difference with one Sierra Chart version compared to another, it is only coincidental especially when it comes to lost connections. That cannot be possibly specific to certain versions of Sierra Chart. It will happen with all of them. 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: 2016-01-29 21:45:17
|
[2016-01-30 07:20:56] |
crazybears - Posts: 314 |
Hi i'm not alone with this issue,maybe now will be resolved I've had this kind of problem from a long time .randomly i lost connection and after a while connection starts again. as User295967 i have NT+CQG run at the same time without any disconnection CQG issues Wrong Candle SC CQG random interruption // partial resolved ,rrandom disconnections persist. I'm just lazy because changing to Rithmic datafeed ain't a hard work.... |
[2016-01-30 08:11:32] |
|
CQG has been notified of the problem and this is clearly a CQG issue. Sierra Chart is not the provider of the CQG data feed and it uses the CQG Web API connection method. It is clear that NT does not. We also want to make 2 technical comments: 1. CQG is using an outdated and known insecure SSL version. This makes no sense. They need to use TLS version 1.2. Why are they are using a known insecure SSL version which no website should even be using any longer makes no sense. Reference: http://disablessl3.com/ So what is CQG's official response to this? Why are they using an known insecure security layer? 2. CQG is using the Websocket protocol. This makes no sense. They should not be sent using any framing layer on top of the TCP/IP socket other than Google protocol buffer encoding. With TLS (Encryption) and Google protocol buffering encoding, the use of the Websocket protocol makes no sense at all. We see no usefulness in it. That is the opinion of two senior engineers here at Sierra Chart. We have looked at this closely. We have looked at the Websocket protocol specification and we see no usefulness with what CQG is doing. It could very well be that the problems that exist with the CQG data feed are in the Websocket layer. We are not saying this is the case, and we may very well be completely wrong. we are only suggesting a possibility. But the point is there is an unnecessary layer in the communication stack which serves no useful purpose and can be the source of additional problems. The Sierra Chart Exchange Data Feed uses an unencrypted connection for market data and use the DTCProtocol: http://DTCProtocol.org The particular encoding that Sierra Chart uses, is binary with variable length strings. 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: 2016-01-30 08:29:31
|
[2016-01-30 08:14:45] |
|
Prior posting has been revised.
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 |
[2016-02-01 18:19:23] |
User295967 - Posts: 32 |
The very best will be the Sierra Chart Exchange Data Feed:
Sierra Chart Exchange Data Feed For information about a direct account, refer to: https://www.sierrachart.com/index.php?page=doc/doc_DirectAccount.html Although in the case of using the Sierra Chart Exchange Data Feed a direct account will not be necessary sometime later in February. You can use the account provided by your broker AMP. We will try to have this ready as soon as possible. Will not help in my case as I need the server sided OCO handling. The Web API does not provide for that.
We think this is now available. If so we will add this in the next few days. Please bear with me as I do not have the technical level you guys have. I just wat to be able to trade server sided OCO without the frequent disconnects. I understand there is an issue at CQG and not with Sierra. But given the quotes above I do not comprehend how a Sierra Direct implementation should correct the frequest disconnects: In the end the order should be transmitted to CQG - where the problems are. How does the Sierra direct technically then solve the frequesnt disconnect issue? Should I use the Web API once the server sided OCO is implemented? Will that resolve the frequent disconnects? My broker suggests me to switch to Rithmic to get around the CQG issue. Will Rithmic indeed have a more stable connection? I use the Sierra chart DOM for order entry. |
[2016-02-01 18:24:00] |
|
Should I use the Web API once the server sided OCO is implemented?
Yes. Please allow us about one to two weeks to complete this.We recommend waiting for us to have the server-side OCO support for CQG ready. 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 |
[2016-02-04 03:56:57] |
|
We are releasing Sierra Chart version 1365 now which supports server-side OCO (Order Cancels Order) when using the CQG Web API. This is from CQG relating to the CQG Web API disconnections: Disconnections #3 and #4 (with sessionToken "vyP2jtJjkyZ9gebKzexyjVGeyObec+d1mZGLoqjnDWc" and "9880Z6ijKH7KZpy3uNAzXIKexLoGN4UcDKZg4BzSXR0" correspondingly) happened because of exceeding real-time market data delay: it reached more than 15 seconds. Most probably it related with client-side connection problems. Disconnections #1 and #2 (with sessionToken "Jai4Ss/8XaOYQ6VlZ7H0K6a5UsuArQuzmYxtIvHLm7U" and "bCqPBIdHvAMCKQXfJmt/WbbtQbyfOeIMVN1zLJnc9OE" correspondingly) are more tricky. In both cases I didn't saw nothing serious except of some unknown warnings from websocket library. Looks like in these cases WebAPI didn't disconnect user connections, user sessions were deleted after 'Logoff' message from client. I also saw some unknown warnings like "websocketpp [error]: Timer Expired" and they also look like a client-side problems, but I'm not sure that these problems related with SierraCharts users (I have no way to get IP-addresses or session tokens of connections that leaded to these messages). 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 |
[2016-02-04 10:27:00] |
User295967 - Posts: 32 |
My goal is to execute orders on a stable and reliable Sierra platform using server sided OCO where also bracketing is supported once the master entry is activated. In post 15 I read what Sierra thinks CQG is using an outdated and known insecure SSL version. This makes no sense
CQG is using the Websocket protocol. This makes no sense.
In post 19 I read what CQG thinks Most probably it related with client-side connection problems.
I didn't saw nothing serious except of some unknown warnings from websocket library
I also saw some unknown warnings like "websocketpp [error]: Timer Expired"
but I'm not sure that these problems related with SierraCharts users
In another thread here on the forum I read what Sierra writes regarding another report of disconnecting Many users have been reporting this over the last two weeks when using CQG. CQG has been advised of it.
So CQG is using questionable technology and CQG has no real clue what is happening and for sure they state they can NOT solve the issue. So what should I do as Sierra trader? Close my eyes and just execute orders on questionable technology with known issues which can not be resolved by CQG? Trading is no casino activity! All the time Ninja on Continuum (which is CQG) runs rockstable with NO disconnection whatsoever. So there are no issues on my side with ISP, hardwiring, PC, updated Windows, dedicated PC only for trading and in my country all communication cables are under the ground for reliability issues. And I turn off all anti virus and firewalls. Sierra received from other traders similar issues, so it is unlikely all these cases are due to client issues at traders. Updating to a latest Sierra is no solution as this does not change anything to the issues at CQG site - issues confirmed by Sierra as stated above. My question to Sierra: I know Sierra has no influence on CQG issues. But Sierra offers trading through the chart DOM. So: how can I trade reliable with Sierra using NON questionable technology and dealing with parties (here CQG) who are able to solve their problems instead of saying they can not. I am open to use other datafeed than CQG if that will enable Sierra to offer a rocksolid tradingplatform for placing orders. My conclusion now is that CQG is using outdated and known insecure technolgy whereby CQG makes implementations that make no sense (see Sierra conclusions above). Is that Sierra's partner for a rockstable platform? Date Time Of Last Edit: 2016-02-04 10:52:28
|
[2016-02-04 14:49:37] |
opmetal - Posts: 72 |
I'm in the same boat. The last couple of weeks have shown that the CQG feed is utter garbage.
|
[2016-02-04 18:35:25] |
|
We will be following up with CQG about this. We do not need any further information because we also have a CQG data feed connection that we can provide all the information they need regarding this problem. 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 |
[2016-02-04 19:49:08] |
User47643 - Posts: 13 |
We will be following up with CQG about this.
Please see if you can get them to implement TLS on the Web API. Please see if you can get them to disable Nagle's algorithm on the Web API: http://www.boost.org/doc/libs/1_55_0/doc/html/boost_asio/reference/ip__tcp/no_delay.html |
[2016-02-05 08:59:56] |
|
Regarding post #20: So CQG is using questionable technology and CQG has no real clue what is happening and for sure they state they can NOT solve the issue. So what should I do as Sierra trader? Close my eyes and just execute orders on questionable technology with known issues which can not be resolved by CQG? Trading is no casino activity! Please contact your broker AMP and have them switch you over to TT. This is definitely going to be better. Also, what markets do you trade? The reason why we ask this question is because there is the Sierra Chart Exchange Data Feed which we are going to be making available perhaps as early as next week, to users with Sierra Chart accounts provided through brokers. Here is information about the Data Feed: Sierra Chart Exchange Data Feed 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: 2016-02-05 09:00:07
|
[2016-02-05 11:25:06] |
User295967 - Posts: 32 |
My goal is to execute orders on a stable and reliable Sierra platform using server sided OCO where also bracketing is supported once the master entry is activated.
Combo Sierra and TT does not offer server sided OCO. I trade mainly the TF - Russel. Date Time Of Last Edit: 2016-02-05 11:34:05
|
To post a message in this thread, you need to log in with your Sierra Chart account: