|
|
 |

07-21-2008, 07:30 PM
|
|
Member
|
|
Join Date: May 2008
Posts: 24
|
|
|
Market Data Request Reject?
I've started getting errors today on my history client. I'll get one batch of bars fine, then the next request gets errored out:
FIX Message Type: Y (Market Data Request Reject)
MDReqRejReason: A (Unsupported Scope <546>)
Text: Reached maximum connections=50 !
This continues indefinitely, and effectively shuts down my history client. Causes? How can I avoid this in the future?
Entire message enumeration follows:
Code:
Field 262: 1216432536578PriceServer684-22
Field 281: A
Field 35: Y
Field 58: Reached maximum connections=50 !
Field 9011: 0
SID: 1216432536578PriceServer684
I'm logging onto the 'mde' terminal using the standard testing account credentials.
|

07-28-2008, 02:40 PM
|
|
Moderator
|
|
Join Date: Jan 2006
Posts: 2,005
|
|
|
We are looking into this incident. When was the time and date of this message?
Also has it happened again since this instance?
|

07-31-2008, 09:44 AM
|
|
Registered User
|
|
Join Date: Jul 2007
Posts: 3
|
|
|
hi, our pec shows the same logs.
58=Reached maximum connections=50 !
also, our client behaves kind of strange atm. used to run smoothly.
right now we have problems in requesting larger amounts of fx history packets.
after 3 requests ( 3x300 ) it seems to stop sending market data snapshots.
when continuing to the next symbol, we again receive 3x300 and no more.
have there been any changes to the PEC concerning this ?
kindest regards
d.reissmann
|

07-31-2008, 11:21 AM
|
|
Moderator
|
|
Join Date: Jan 2006
Posts: 2,005
|
|
|
Could you please supply us with specific times in which you got the message so that we may be able to investigate it further.
|

08-01-2008, 11:33 AM
|
|
Registered User
|
|
Join Date: Jul 2007
Posts: 3
|
|
|
tested it a couple of times, results do not change.
i.e.
DEBUG - <<< inc Message type=Y
281=A
SID=1217031712479PriceServer1353
9011=0
262=1217031712479PriceServer1353-20
58=Reached maximum connections=50 !
Time: 2008-08-01 18:29:36
(Timezone GMT: + 02:00 Germany)
i can post more of the debug log if it helps ?
|

08-01-2008, 11:38 AM
|
|
Moderator
|
|
Join Date: Jan 2006
Posts: 2,005
|
|
|
Yes please. The more information we get the better we would be able to diagnose the problem.
|

08-01-2008, 04:18 PM
|
|
Registered User
|
|
Join Date: Jul 2007
Posts: 3
|
|
limited to 10.000 chars. not much for a log ^^
seems like the 5 Min Interval works. this happens requesting Min1 data.
Quote:
DEBUG - HTTP HEADER PDAS_SID : 0
DEBUG - <fxmsg v="pdas"><m t="U54" q="0"><f n="112">1217031713894PriceServer1105-8</f><f n="SID">1217031713894PriceServer1105</f><f n="9028">0</f><f n="35">U54</f><f n="336">FXCM</f><l n="9016"><g><f n="9017">BrcastID</f><f n="9018">0</f></g><g><f n="9017">MsgID</f><f n="9018">0</f></g><g><f n="9017">MailID</f><f n="9018">0</f></g><g><f n="9017">MessageFlags</f><f n="9018">0</f></g><g><f n="9017">TimeOut</f><f n="9018" t="l">3000</f></g></l><f n="WaitTime" t="l">3000</f><f n="625">PriceServer</f></m>
</fxmsg>
DEBUG - UniComm::addJobs Exit
DEBUG - PDAS_HEADER_DEFLATE=
eJyVkcsKwjAQRfeC/1BmL8009iG0s1ARXIiCim6DpqGQijZV/HxTLbYoiN2Fk3PvwEyc3nOjnFsC56MwQHHulAls/SE4lwSYBalzSgDRA0IPQ8YxRB6NhqsiO8i1LG6yQGT+IIrdtJb X8+lvuVFHzIuAWAO4D2SntwAPgGb7yeKJ9CuElsXq3YEh0Lg4C FPOp+1ufHe76tNfGNVBFpnuYEtjhJIzLZT5N7PJcrm8lh96dQs NxBlrcq6ujZ3Iyir2ZT1/A89usrX3Vz6nfs++qpvTA2yMhvo=
length=288
DEBUG - ------------ before -------------------
++++++++++++++++++++++++++++++++++++++++
DEBUG - ------------ after -------------------
<fxmsg v="pdas"></fxmsg>
++++++++++++++++++++++++++++++++++++++++
DEBUG - Parsing:
<fxmsg v="pdas"></fxmsg>
DEBUG - start fxmsg
DEBUG - end fxmsg
DEBUG - State Change: FinishedCommunicaton U54 1217031713894PriceServer1105-8
DEBUG - onFinishCommunication()
DEBUG - State Change: Reschedule U54 1217031713894PriceServer1105-8
DEBUG - onReschedule()
DEBUG - State Change: Waiting U54 1217031713894PriceServer1105-8
DEBUG - State Change: ReadyToCommunicate U54 1217031713894PriceServer1105-8
DEBUG - JobDasMessage: nStartCommunication() start
DEBUG - JobDasMessage: nStartCommunication() finish
DEBUG - State Change: StartedCommunicaton U54 1217031713894PriceServer1105-9
DEBUG - UniComm::addJobs Size=1
DEBUG - State Change: WaitingForResponse U54 1217031713894PriceServer1105-9
DEBUG - Channel 0 Batch Size = 1
DEBUG - >>> out Message type=U54
112=1217031713894PriceServer1105-9
SID=1217031713894PriceServer1105
9028=0
336=FXCM
9016=list
--------
1: 9017=BrcastID;9018=0;
2: 9017=MsgID;9018=0;
3: 9017=MailID;9018=0;
4: 9017=MessageFlags;9018=0;
5: 9017=TimeOut;9018=3000;
--------
WaitTime=3000
625=PriceServer
DEBUG - UniComm::addJobs Exit
DEBUG - HTTP HEADER PDAS_SID : 0
DEBUG - <fxmsg v="pdas"><m t="U54" q="0"><f n="112">1217031713894PriceServer1105-9</f><f n="SID">1217031713894PriceServer1105</f><f n="9028">0</f><f n="35">U54</f><f n="336">FXCM</f><l n="9016"><g><f n="9017">BrcastID</f><f n="9018">0</f></g><g><f n="9017">MsgID</f><f n="9018">0</f></g><g><f n="9017">MailID</f><f n="9018">0</f></g><g><f n="9017">MessageFlags</f><f n="9018">0</f></g><g><f n="9017">TimeOut</f><f n="9018" t="l">3000</f></g></l><f n="WaitTime" t="l">3000</f><f n="625">PriceServer</f></m>
</fxmsg>
DEBUG - PDAS_HEADER_DEFLATE=
eJyVkcEKgkAQhu9B7yBzD3fczASdQ0XgIQoq6rrUughrlGvR47 eWpBRE3pZvv/8fmInSe26Uc4vhfBQGKMqdMoatPwTnEgOzIHVOMSB6QOhhwDgG yMfhcFVkB7mWxU0WiMwfhJGb1vI6mf2WGzVk3hiINYD7QHZ6C/AR0Hw/XTyRfoXQski9OzAAmhQHYcpk1u7Gd7erPv2FUR1kkekOtjRGKD nXQpl/M5ssl8tr+aFXt9BAnLEm5+ra2ImsrGJf1vN35NlNtvb+yufU79 lXdXN6AG4+hvs=
length=288
DEBUG - ------------ before -------------------
++++++++++++++++++++++++++++++++++++++++
DEBUG - ------------ after -------------------
<fxmsg v="pdas"><m t="Y" q="0"><f n="281">A</f><f n="SID">1217031713894PriceServer1105</f><f n="35">Y</f><f n="9011">0</f><f n="262">1217031713894PriceServer1105-5</f><f n="58">Reached maximum connections=50 !</f></m><m t="U60" q="0"><f n="112">1217031713894PriceServer1105-9</f><f n="SID">1217031713894PriceServer1105</f><f n="9028">0</f><f n="35">U60</f><f n="58">0;08012008170343;0;0;0;
</f><f n="625">PriceServer</f></m></fxmsg>
++++++++++++++++++++++++++++++++++++++++
DEBUG - Parsing:
<fxmsg v="pdas"><m t="Y" q="0"><f n="281">A</f><f n="SID">1217031713894PriceServer1105</f><f n="35">Y</f><f n="9011">0</f><f n="262">1217031713894PriceServer1105-5</f><f n="58">Reached maximum connections=50 !</f></m><m t="U60" q="0"><f n="112">1217031713894PriceServer1105-9</f><f n="SID">1217031713894PriceServer1105</f><f n="9028">0</f><f n="35">U60</f><f n="58">0;08012008170343;0;0;0;
</f><f n="625">PriceServer</f></m></fxmsg>
DEBUG - start fxmsg
DEBUG - start m
DEBUG - start f
DEBUG - end f
DEBUG - start f
DEBUG - end f
DEBUG - start f
DEBUG - end f
DEBUG - start f
DEBUG - end f
DEBUG - start f
DEBUG - end f
DEBUG - start f
DEBUG - end f
DEBUG - end m
DEBUG - start m
DEBUG - start f
DEBUG - end f
DEBUG - start f
DEBUG - end f
DEBUG - start f
DEBUG - end f
DEBUG - start f
DEBUG - end f
DEBUG - start f
DEBUG - end f
DEBUG - start f
DEBUG - end f
DEBUG - end m
DEBUG - end fxmsg
DEBUG - <<< inc Message type=Y
281=A
SID=1217031713894PriceServer1105
9011=0
262=1217031713894PriceServer1105-5
58=Reached maximum connections=50 !
|
with a Message Reject received before. Originally i asked for
mdr.setFXCMTimingInterval (FXCMTimingIntervalFactory.toCode(iBarCode));
with iBarCode = 1 but in the Message it says Tick(0)
Quote:
DEBUG - ******** FIX Message Received ********* MarketDataRequestReject{mMDReqID='1217031713894Pri ceServer1105-5', mMDReqRejReason=MDReqRejReason:Unsupported Scope (A), mText='Reached maximum connections=50 !', mInstrument=Instrument{mFXCMSymPointSize=0.0, mFXCMSymPrecision=0, mFXCMSymID=0, mSymbol='null', mTouchTime=0, mFXCMSymSortOrder=0}, mFXCMTimingInterval=FXCMTimingInterval:Tick (0), mTradingSessionID='null', mTradingSessionSubID='null', mMakingTime=1217624622687}
Time: 2008-08-01 23:03:42
|
|

08-04-2008, 08:53 PM
|
|
Member
|
|
Join Date: May 2008
Posts: 24
|
|
After several days with no replies, I figured this was getting ignored by the FXCM staff.
I first started getting this after the weekend, the prior week (July 13-18) was fine. Like Valder I am only interested in 1m bars, as I can derive the other bars from that data. Below is the first time I have the error message in my logs (all times are GMT):
Code:
Main - [07/22/08 - 00:16:01] - Info - Loading historical candle data for AUD/CAD from 20080718-20:00:00 to 20080720-21:00:00
Main - [07/22/08 - 00:16:01] - Info - Candle history request sent.
Return Status='Posted to queue'
Status Update - [07/22/08 - 00:16:01] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [07/22/08 - 00:16:01] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [07/22/08 - 00:16:01] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [07/22/08 - 00:16:01] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [07/22/08 - 00:16:01] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [07/22/08 - 00:16:02] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [07/22/08 - 00:16:04] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [07/22/08 - 00:16:05] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [07/22/08 - 00:16:05] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [07/22/08 - 00:16:08] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [07/22/08 - 00:16:08] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [07/22/08 - 00:16:08] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [07/22/08 - 00:16:11] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [07/22/08 - 00:16:12] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [07/22/08 - 00:16:12] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [07/22/08 - 00:16:12] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [07/22/08 - 00:16:12] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Message Update - [07/22/08 - 00:16:12] - Info - Error: request for subscription was rejected. Source follows...
Main - [07/22/08 - 00:16:12] - Info - Enumerating FIX Message values...
Main - [07/22/08 - 00:16:12] - Info - Type: Y
Main - [07/22/08 - 00:16:12] - Info - 262: 1216433409970PriceServer554-13
Main - [07/22/08 - 00:16:12] - Info - 281: A
Main - [07/22/08 - 00:16:12] - Info - 35: Y
Main - [07/22/08 - 00:16:12] - Info - 58: Reached maximum connections=50 !
Main - [07/22/08 - 00:16:12] - Info - 9011: 0
Main - [07/22/08 - 00:16:12] - Info - SID: 1216433409970PriceServer554
Main - [07/22/08 - 00:16:12] - Info - Finished with enumeration.
Main - [07/22/08 - 00:16:12] - Info - Gapfill: Received 0 candles.
I fired up the listener program again just now to check and it's still doing the same error. Here's the relevant bit from the app log:
Code:
Main - [08/05/08 - 01:35:43] - Info - Loading historical candle data for AUD/CAD from 20080723-18:39:00 to 20080804-15:07:00
Status Update - [08/05/08 - 01:35:43] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Main - [08/05/08 - 01:35:43] - Info - Candle history request sent.
Return Status='Posted to queue'
Status Update - [08/05/08 - 01:35:43] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [08/05/08 - 01:35:43] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [08/05/08 - 01:35:43] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [08/05/08 - 01:35:43] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [08/05/08 - 01:35:43] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [08/05/08 - 01:35:45] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
History - [08/05/08 - 01:35:45] - Info - Recvd candle: AUD/CAD Opn: 0.9604 Clo: 0.9603 Hi: 0.9607 Lo: 0.9600 - 20080804-10:07:00
History - [08/05/08 - 01:35:45] - Info - Recvd candle: AUD/CAD Opn: 0.9603 Clo: 0.9601 Hi: 0.9605 Lo: 0.9599 - 20080804-10:08:00
<snip... many more candle records here...>
History - [08/05/08 - 01:35:45] - Info - Recvd candle: AUD/CAD Opn: 0.9621 Clo: 0.9620 Hi: 0.9625 Lo: 0.9617 - 20080804-15:05:00
History - [08/05/08 - 01:35:45] - Info - Recvd candle: AUD/CAD Opn: 0.9620 Clo: 0.9620 Hi: 0.9624 Lo: 0.9617 - 20080804-15:06:00
Status Update - [08/05/08 - 01:35:45] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Main - [08/05/08 - 01:35:45] - Info - Gapfill: Received 300 candles.
Main - [08/05/08 - 01:35:45] - Info - Loading historical candle data for AUD/CAD from 20080723-18:39:00 to 20080804-10:07:00
Status Update - [08/05/08 - 01:35:45] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Main - [08/05/08 - 01:35:45] - Info - Candle history request sent.
Return Status='Posted to queue'
Status Update - [08/05/08 - 01:35:45] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [08/05/08 - 01:35:46] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [08/05/08 - 01:35:46] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [08/05/08 - 01:35:46] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [08/05/08 - 01:35:48] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [08/05/08 - 01:35:48] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [08/05/08 - 01:35:49] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [08/05/08 - 01:35:52] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [08/05/08 - 01:35:52] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [08/05/08 - 01:35:52] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [08/05/08 - 01:35:55] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [08/05/08 - 01:35:55] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Status Update - [08/05/08 - 01:35:56] - Info - Status Code: [2] Sending -- Status Message: Sending request...:
Status Update - [08/05/08 - 01:35:56] - Info - Status Code: [3] Receiving -- Status Message: :
Status Update - [08/05/08 - 01:35:56] - Info - Status Code: [0] Ready -- Status Message: Request sent.:
Message Update - [08/05/08 - 01:35:56] - Info - Error: request for subscription was rejected. Source follows...
Main - [08/05/08 - 01:35:56] - Info - Enumerating FIX Message values...
Main - [08/05/08 - 01:35:56] - Info - Type: Y
Main - [08/05/08 - 01:35:56] - Info - 262: 1217644556080PriceServer1153-21
Main - [08/05/08 - 01:35:56] - Info - 281: A
Main - [08/05/08 - 01:35:56] - Info - 35: Y
Main - [08/05/08 - 01:35:56] - Info - 58: Reached maximum connections=50 !
Main - [08/05/08 - 01:35:56] - Info - 9011: 0
Main - [08/05/08 - 01:35:56] - Info - SID: 1217644556080PriceServer1153
Main - [08/05/08 - 01:35:56] - Info - Finished with enumeration.
Main - [08/05/08 - 01:35:56] - Info - Gapfill: Received 0 candles.
Note that the above request that failed was the third request. The first two requests (which returned 300 bars each) were fine. Letting the app run for the next several minutes shows that every subsequent request for history past this fails with the same error message. If I restart the app it will again always fail on the second or third history request.
More on next message...
|

08-04-2008, 08:55 PM
|
|
Member
|
|
Join Date: May 2008
Posts: 24
|
|
The FXCM debug logs don't have any relevant info (I'm using the C++/COM interface, I guess Valder is using Java, he gets all the cool debug messages!). The info being echoed to the console may be, here it is:
Code:
Status Update - [08/05/08 - 01:51:45] - Info - Status Code: [4] Processing -- St
atus Message: Sending request...:
HostReader::setHttpTimeout. 180000
UniversalUserSession::loadStationDescriptor.....
HostReader::read from Host mde
HostReader::getHttpContent. Start
HostReader::getHttpContent. InternetConnect. Host=www.fxcorporate.com
HostReader::getHttpContent. InternetConnect. Port=80. Done
HostReader::getHttpContent. Use method POST
HostReader::getHttpContent. HttpOpenRequest. URL=/Hosts.jsp?ID=969904953&PN=
mde&SN=TestLive
HostReader::getHttpContent. Set HTTP timeout = 180000
HostReader::getHttpContent. HttpSendRequest
HostReader::getHttpContent. InternetQueryDataAvailable Start.
HostReader::getHttpContent. InternetQueryDataAvailable End. Number of availa
ble bytes 810
HostReader::getHttpContent. InternetReadFile Start. Number of bytes to read
810
HostReader::getHttpContent. InternetReadFile End. Number of bytes received 8
10
HostReader::getHttpContent. InternetQueryDataAvailable Start.
HostReader::getHttpContent. InternetQueryDataAvailable End. Number of availa
ble bytes 436
HostReader::getHttpContent. InternetReadFile Start. Number of bytes to read
436
HostReader::getHttpContent. InternetReadFile End. Number of bytes received 4
36
HostReader::getHttpContent. InternetQueryDataAvailable Start.
HostReader::getHttpContent. InternetQueryDataAvailable End. Number of availa
ble bytes 5
HostReader::getHttpContent. InternetReadFile Start. Number of bytes to read
5
HostReader::getHttpContent. InternetReadFile End. Number of bytes received 5
HostReader::getHttpContent. InternetQueryDataAvailable Start.
HostReader::getHttpContent. InternetQueryDataAvailable End. Number of availa
ble bytes 0
HostReader::getHttpContent. Response received
HostReader::getHttpContent. HttpQueryInfo Status Code=200
HostReader::getHttpContent. Finish. Return 1251 bytes
HostReader::read from Host. Done UniversalUserSession::loadStationDescriptor don
e.....
UniversalUserSession::loadStationDescriptor all OK
Status Update - [08/05/08 - 01:51:45] - Info - Status Code: [7] Wait -- Status M
essage: :
Status Update - [08/05/08 - 01:51:45] - Info - Status Code: [4] Processing -- St
atus Message: Sending request...:
HostReader::setHttpTimeout. 180000
UniversalUserSession::loadStationDescriptor.....
HostReader::read from Host PriceServer
HostReader::getHttpContent. Start
HostReader::getHttpContent. InternetConnect. Host=www.fxcorporate.com
HostReader::getHttpContent. InternetConnect. Port=80. Done
HostReader::getHttpContent. Use method POST
HostReader::getHttpContent. HttpOpenRequest. URL=/Hosts.jsp?ID=969905484&PN=
PriceServer&SN=TestLive
HostReader::getHttpContent. Set HTTP timeout = 180000
HostReader::getHttpContent. HttpSendRequest
HostReader::getHttpContent. InternetQueryDataAvailable Start.
HostReader::getHttpContent. InternetQueryDataAvailable End. Number of availa
ble bytes 863
HostReader::getHttpContent. InternetReadFile Start. Number of bytes to read
863
HostReader::getHttpContent. InternetReadFile End. Number of bytes received 8
63
HostReader::getHttpContent. InternetQueryDataAvailable Start.
HostReader::getHttpContent. InternetQueryDataAvailable End. Number of availa
ble bytes 0
HostReader::getHttpContent. Response received
HostReader::getHttpContent. HttpQueryInfo Status Code=200
HostReader::getHttpContent. Finish. Return 863 bytes
HostReader::read from Host. Done UniversalUserSession::loadStationDescriptor don
e.....
UniversalUserSession::loadStationDescriptor something wrong up there
Status Update - [08/05/08 - 01:51:45] - Info - Status Code: [-2] Error -- Status
Message: Request failed.:
Main - [08/05/08 - 01:51:45] - Info - Opening User Session...
Status Update - [08/05/08 - 01:51:45] - Info - Status Code: [4] Processing -- St
atus Message: Sending request...:
HostReader::setHttpTimeout. 180000
UniversalUserSession::loadStationDescriptor.....
HostReader::read from Host PriceServer
HostReader::getHttpContent. Start
HostReader::getHttpContent. InternetConnect. Host=www.fxcorporate.com
HostReader::getHttpContent. InternetConnect. Port=80. Done
HostReader::getHttpContent. Use method POST
HostReader::getHttpContent. HttpOpenRequest. URL=/Hosts.jsp?ID=969905593&PN=
PriceServer&SN=TestLive
HostReader::getHttpContent. Set HTTP timeout = 180000
HostReader::getHttpContent. HttpSendRequest
HostReader::getHttpContent. InternetQueryDataAvailable Start.
HostReader::getHttpContent. InternetQueryDataAvailable End. Number of availa
ble bytes 863
HostReader::getHttpContent. InternetReadFile Start. Number of bytes to read
863
HostReader::getHttpContent. InternetReadFile End. Number of bytes received 8
63
HostReader::getHttpContent. InternetQueryDataAvailable Start.
HostReader::getHttpContent. InternetQueryDataAvailable End. Number of availa
ble bytes 0
HostReader::getHttpContent. Response received
HostReader::getHttpContent. HttpQueryInfo Status Code=200
HostReader::getHttpContent. Finish. Return 863 bytes
HostReader::read from Host. Done UniversalUserSession::loadStationDescriptor don
e.....
UniversalUserSession::loadStationDescriptor something wrong up there
Status Update - [08/05/08 - 01:51:45] - Info - Status Code: [-2] Error -- Status
Message: Request failed.:
Status Update - [08/05/08 - 01:51:45] - Info - Status Code: [1] Connecting -- St
atus Message: Connecting to the Server...:
URL pdas:http://204.8.241.5:80 to open
Status Update - [08/05/08 - 01:51:46] - Info - Status Code: [6] Logged In -- Sta
tus Message: Connected to the Server.: System indicates login event. Resetting s
ubscriptions.
Main - [08/05/08 - 01:51:46] - Info - Login to the server ok: SessionID = 121764
4543663PriceServer351
Main - [08/05/08 - 01:51:46] - Info - Connected successfully. SessionID: 1217644
543663PriceServer351. SessionDesc: PriceServer
Main - [08/05/08 - 01:51:46] - Info - Sending Trading Session Status Request mes
sage...
Main - [08/05/08 - 01:51:46] - Info - Return Status=Posted to queue
Since the start of this issue, for my uses anyway, the Price Engine Client system has been unusable as the failures are not intermittent or random, they always happen after the second or third request for bars, and from then on all requests result in the "Reached maximum connections=50 !" error until the listener reconnects (which then gives you only 1 or 2 requests before it fails again). The live prices appear unaffected thus far (thankfully), but without history I may as well not bother since I'll have gaps any time my live listener shuts down.
|

08-12-2008, 06:11 PM
|
|
Member
|
|
Join Date: May 2008
Posts: 24
|
|
|
Hey guys... it's been a week and there has been neither comment on this issue by tech support nor a resolution to this serious, ongoing failure of FXCM's server(s) to deliver important and irreplaceable historical data.
As of today I am still unable to request more than one period of (1min) historical data before getting the 'connections=50' error. This was not the case several weeks ago when the problem first started.
Will FXCM continue to allow customers and whitelabel providers access to historical data, or is this problem going to just fester until we find new brokers with working servers?
FXCM may think this is acceptable for its own customers, but this is not the kind of service I intend to provide to my own customers.
|

08-19-2008, 11:23 AM
|
|
Member
|
|
Join Date: Oct 2006
Posts: 13
|
|
|
Hi. I got the same problem
Is there somebody can help us?
I can not get the historical data from the server. It seems that all requests are ignored. Did not get any response from the server.
Please check it and help me.
Thanks
|

08-19-2008, 05:58 PM
|
|
Member
|
|
Join Date: May 2008
Posts: 24
|
|
|
Maybe they're fixing something, because right now at least history requests are once again being honored (no more connections = 50 error).
FXCM_Help, can you please advise on what changes if any were made on the PEC system to repair the connections=50 error, and if there is something that can be done on my end to mitigate any future system errors like this one? Would the PEC system be more robust with a production login, or are the systems the same?
|
 |
| Thread Tools |
|
|
| Rate This Thread |
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|