|
/ | Forum |
  |
tradermaji
2006.10.07 08:12
Metaquotes,
Take a look at an output of my log file during today's NFP. All you can see is tradecontext is busy. Can you program something that does not hang orders up this way? A few of my buy stop orders did not get triggered because by the time the orders were placed the price had too close to the entry (less than MODE_STOPLEVEL). My EA tries to place the orders repeatedly every 5000 msec for a certain number of times. However, this is not a good solution. I think you all are lazy and are not programming your system properly. Why can't it be programmed to pipe in the orders faster? Or maybe keep it in buffer and then release it? Why should it be on the user to do this? As system developers, it is your duty to provide the users with this solution. Here is the sample that has got me mad... 07:33:04 TradeDispatcher: trade context is busy 07:33:10 TradeDispatcher: trade context is busy 07:33:15 TradeDispatcher: trade context is busy 07:33:20 TradeDispatcher: trade context is busy 07:33:24 '1247189': request was accepted by server 07:33:24 '1247189': request in process 07:33:24 '1247189': order is open : #13251746 buy stop 5.10 EURUSDm at 1.2700 sl: 1.2660 tp: 1.3080 07:33:26 '1247189': pending order sell stop 5.30 USDCHFm at 1.2501 sl: 1.2550 tp: 1.2041 07:34:32 TradeDispatcher: trade context is busy 07:34:36 TradeDispatcher: trade context is busy 07:34:36 TradeDispatcher: trade context is busy 07:34:39 '1247189': request was accepted by server 07:34:39 '1247189': request in process 07:34:39 '1247189': order is open : #13252070 sell stop 5.30 USDCHFm at 1.2501 sl: 1.2550 tp: 1.2041 07:34:40 '1247189': modify order #13242243 buy 4.30 GBPCHFm at 2.3569 sl: 2.3487 tp: 2.4139 -> sl: 2.3571 tp: 2.4139 07:35:17 TradeDispatcher: trade context is busy 07:35:22 TradeDispatcher: trade context is busy 07:35:27 TradeDispatcher: trade context is busy 07:35:32 TradeDispatcher: trade context is busy 07:35:37 TradeDispatcher: trade context is busy 07:35:42 TradeDispatcher: trade context is busy 07:35:47 TradeDispatcher: trade context is busy 07:35:52 TradeDispatcher: trade context is busy 07:35:57 TradeDispatcher: trade context is busy 07:36:02 TradeDispatcher: trade context is busy 07:36:07 TradeDispatcher: trade context is busy 07:36:12 TradeDispatcher: trade context is busy 07:36:17 TradeDispatcher: trade context is busy 07:36:23 TradeDispatcher: trade context is busy 07:36:28 TradeDispatcher: trade context is busy 07:36:33 TradeDispatcher: trade context is busy 07:36:38 TradeDispatcher: trade context is busy 07:36:43 TradeDispatcher: trade context is busy 07:36:48 TradeDispatcher: trade context is busy 07:36:48 '1247189': request was accepted by server 07:36:48 '1247189': request in process 07:36:49 '1247189': order #13242243 buy 4.30 GBPCHFm at 2.3569 was modified -> sl: 2.3571 tp: 2.4139 07:36:49 '1247189': modify order #13242243 buy 4.30 GBPCHFm at 2.3569 sl: 2.3571 tp: 2.4139 -> sl: 2.3592 tp: 2.4139 07:36:53 TradeDispatcher: trade context is busy 07:36:58 TradeDispatcher: trade context is busy 07:37:03 TradeDispatcher: trade context is busy 07:37:09 TradeDispatcher: trade context is busy 07:37:12 '1247189': request was accepted by server 07:37:12 '1247189': request in process 07:37:12 '1247189': order #13242243 buy 4.30 GBPCHFm at 2.3569 was modified -> sl: 2.3592 tp: 2.4139 07:37:14 '1247189': instant order sell 2.80 GBPUSDm at 1.8796 sl: 1.8874 tp: 1. 8111 07:38:15 TradeDispatcher: trade context is busy 07:38:17 '1247189': request was accepted by server 07:38:17 '1247189': request in process |
 |
Secrets of MetaTrader 4 Client Terminal 21 way to ease the life: Latent features in MetaTrader 4 Client Terminal. Full screen; hot keys; Fast Navigation bar; minimizing windows; favorites; traffic reduction; disabling of news; symbol sets; Market Watch; templates for testing and independent charts; profiles; crosshair; electronic ruler; barwise chart paging; account history in the chart; types of pending orders; modifying of StopLoss and TakeProfit; undo deletion; chart print. |
|
richplank
2006.10.07 09:50
Dear MetaQuotes, nothing in the posting above represents my view and opinion. Your
product is excellent. Worth saying twice: Your product is excellent.
|
|
Zap
2006.10.07 13:09
Geeez, Tradermaji,
I would first understand the way FOREX works (just the basics at least) before thinking on trading and proceeding. Second unclear thing in a row, which could cause frustration and more headache in the future for you. As I said before, MT4 is an extremly adjustable/customizable platform, but you need to set it up, whatever you need it for. |
|
irusoh1
2006.10.07 19:51
If you want to trade during NFP be ready for this kind of stuff. busy, off quotes,
wide spreads, etc.
|
|
tradermaji
2006.10.08 19:38
Guys,
I am talking about making a system more fault tolerant. The way MetaTrader is programmed and rejects orders because of Tradecontext is busy is a wrong way, in my opinion. By the way Zap, I perfectly understand how forex works and that is why I am asking metatrader to improve their product. Have you heard of a platform called Strategybuilder? I use Strategybuilder too for trading futures and there are no such problems. SB is a server side solution, so it has its advantages (and disadvantages). However, SB has limited Forex applications and hence does not suite my needs there. Did you notice that my EA had been trying repeatedly over 1 min 30 sec trying to place an order? I don't like the "tradecontext is busy" deal and I am asking MT to help me get my orders in. If you like that "tradecontext is busy" then so be it. Don't make any assumptions. Irusoh, the system trades whenever there is a signal generated. It does not know what is happening. By the way, it is a volatility expansion type of system and of course, news events will trigger it. If one cannot trade volatility expansions, then one gives away a very very vital tool. That is why I am asking MT to help us. |
|
Zap
2006.10.08 20:38
It is brokerside error as far as I know, not platform.
I've had my battles with the broker of course, it won't be easy for you either I guess. ;) Who do you use by the way? |
|
tradermaji
2006.10.09 01:30
My broker is InterbankFX. I think if the problem is with the back end, and MT supplies
that, then it is MT's responsibility to correct it. |
|
plj
2006.10.09 01:53
tradermaji wrote: My broker is InterbankFX. I think if the problem is with the back end, and MT supplies that, then it is
MT's responsibility to correct it. SB is a MetaTrader platform too ... |
|
tradermaji
2006.10.09 04:09
plj wrote: tradermaji wrote: My broker is InterbankFX. I think if the problem is with the back end, and MT supplies
that, then it is MT's responsibility to correct it. SB is a MetaTrader platform too ... Sorry, It was a slip.. .it should have been StrategyRunner. They are based in Israel. |
 5198 |
stringo
2006.10.09 13:47
tfadermaji, did You read article about "Trade context is busy"? See 'Error 146 ("Trade context busy") and How to Deal with It' |
|
tradermaji
2006.10.10 04:06
Stringo,
That is the whole point of my posting. You want the users to write all this goop because MT cannot stage the orders and execute them fast enough. Also, that should be done transparent to the user and not force him/her to keep on revising the entry orders. Putting the burden on the back of the user is LAZY PROGRAMMING BY THE DEVELOPERS. That was the whole point of contention of my posting. Did you read my posting before you suggested that I read your article? |