Dukascopy | Page 128 | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Dukascopy Europe vs Dukascopy Bank SA 7 replies

DukasCopy question 68 replies

Swiss Law and Dukascopy.com/Finex.com 21 replies

Trading with Dukascopy 17 replies

Dukascopy Price Feed 4 replies

Attachments: Dukascopy
Exit Attachments

Dukascopy

  • #2,541
  • May 6, 2015 6:52pm May 6, 2015 6:52pm
I traded my friend's account with dukascopy earlier. It was nice those days 3 years back. I think they do not accept clients from US
  • #2,542
  • May 7, 2015 3:19am May 7, 2015 3:19am
Quoting fxarms.com
I traded my friend's account with dukascopy earlier. It was nice those days 3 years back. I think they do not accept clients from US
It is the US that will not allow their citizens to use an external broker.
Carbon-Dioxide: the gas of life! https://youtu.be/ttJBdr6eBuo
  • #2,543
  • May 15, 2015 3:00am May 15, 2015 3:00am
Is this normal that they fill my sl 1,8 pips above the visible quotes of the platform?
Attached Image (click to enlarge)
Click to Enlarge Name: gbp-short-sl-slip.PNG Size: 77 KB
  • #2,544
  • May 15, 2015 4:38pm May 15, 2015 4:38pm
Quoting Ryuken
Is this normal that they fill my sl 1,8 pips above the visible quotes of the platform?{image}
I think 1.8 pips negative slippage can be possible anytime. Try using different trigger for SL order (BID <-> ASK).
Simplicity is the ultimate sophistication - Leonardo da Vinci
  • #2,545
  • May 15, 2015 5:00pm May 15, 2015 5:00pm
Quoting Ryuken
Is this normal that they fill my sl 1,8 pips above the visible quotes of the platform?{image}
Are you seriously complaining about 1.8 pips of slippage?
  • #2,546
  • May 16, 2015 1:56am May 16, 2015 1:56am
Not complaining,just a little unclear to me why do i get filled on my micro lot position at a level that had no ask/bid price there.
if anyone could explain it,it would be great.
If they dont have liquidity at the levels shown on the platform to fill micro lots, why don't they print those higher levels on to the chart?
  • #2,547
  • May 16, 2015 4:43pm May 16, 2015 4:43pm
Was this during news? If yes, then it might be normal. I am trading Dukascopy also. You should forward your question to your account manager if this was during normal times. I mean, what is normal these days?
If you're not part of the solution then you're part of the problem.
  • #2,548
  • May 18, 2015 5:34am May 18, 2015 5:34am
Not during news,but it was a fast spike.
  • #2,549
  • May 23, 2015 3:09am May 23, 2015 3:09am
Some recent examples of POSITIVE slippage I've had with Dukascopy:

Attached Image (click to enlarge)
Click to Enlarge Name: Dukascopy_ps1.jpg Size: 113 KB


Attached Image (click to enlarge)
Click to Enlarge Name: Dukascopy_ps2.jpg Size: 50 KB
  • #2,550
  • Jun 5, 2015 9:57pm Jun 5, 2015 9:57pm
Quoting Aragorn
Some recent examples of POSITIVE slippage I've had with Dukascopy: {image} {image}
I also experienced some positive slippage in XU trade early this week during late NY session. TP was 50 pips but it ended in +62 pips. Interestingly, my Pepperstone account also had very similar positive slippage. (I had opened same XU trade manually in both Dukas and Pepperstone accounts).
Simplicity is the ultimate sophistication - Leonardo da Vinci
  • #2,551
  • Jun 12, 2015 3:08pm Jun 12, 2015 3:08pm
Hi dudes,
Could you please let me know the exact different between Dukascopy EU and Dukascopy Swiss? Can we trust the EU one?
thanks in advance
  • #2,552
  • Jun 15, 2015 7:32pm Jun 15, 2015 7:32pm
besides the slippage, I almost experience a disconnect on a live acct once a day. This has become more and more unreliable in the past and if there is planned downtime, I receive no notice. instead I experience gap's in market data after they are down, which leads me to the conclusion that their entire internet is gone. whatsoever, Im affected by that more frequently. How do others experience that?

ksh
  • #2,553
  • Jun 15, 2015 8:16pm Jun 15, 2015 8:16pm
Quoting ksh
besides the slippage, I almost experience a disconnect on a live acct once a day. This has become more and more unreliable in the past and if there is planned downtime, I receive no notice. instead I experience gap's in market data after they are down, which leads me to the conclusion that their entire internet is gone. whatsoever, Im affected by that more frequently. How do others experience that? ksh
I don't experience frequent disconnection. Check your internet connection quality first.
Simplicity is the ultimate sophistication - Leonardo da Vinci
  • #2,554
  • Jun 15, 2015 9:24pm Jun 15, 2015 9:24pm
heispark, thank you for the comment, I guess I was missing to mention: server system, one of the biggest DC's on Europe w/ multi-gigabit peering just to my telco, while only I have 2 gbit interfaces, and yes, im still connected to the server when Dukas disconnects.
  • #2,555
  • Jun 16, 2015 1:49am Jun 16, 2015 1:49am
I get occasional disconnect/reconnect. I will try to get an idea of how many of these are not self-inflicted.
Carbon-Dioxide: the gas of life! https://youtu.be/ttJBdr6eBuo
  • #2,556
  • Jun 16, 2015 4:08am Jun 16, 2015 4:08am
One disconnect at 08:05 GMT
Carbon-Dioxide: the gas of life! https://youtu.be/ttJBdr6eBuo
  • #2,557
  • Jun 16, 2015 4:44am Jun 16, 2015 4:44am
I occasionally experience disconnecton and quick reconnection but it doesn't disturb me much. My MT4 broker Pepperstone also does this occasionally... Once or twice i remember there were relatively longer disconnectons (longer than 10M), but it's rare. One happened weeks ago (due to Ddos attack) as you remember.
Simplicity is the ultimate sophistication - Leonardo da Vinci
  • #2,558
  • Jun 16, 2015 9:29am Jun 16, 2015 9:29am
I get a lot "TO LARGE EXECUTION WAIT TIME" and sockets are closed.

$ fgrep "TO LARGE EXECUTION WAIT TIME" JForexLog.log
2015-06-16 07:07:34.892 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3690, possible application problem or deadLock
2015-06-16 10:41:46.376 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 6177, possible application problem or deadLock
2015-06-16 10:41:46.482 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 6283, possible application problem or deadLock
2015-06-16 10:41:46.521 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 6322, possible application problem or deadLock
2015-06-16 15:31:18.996 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3035, possible application problem or deadLock
2015-06-16 15:31:19.027 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3066, possible application problem or deadLock
2015-06-16 15:31:19.063 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3102, possible application problem or deadLock
2015-06-16 15:31:19.338 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3377, possible application problem or deadLock
2015-06-16 15:31:19.372 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3411, possible application problem or deadLock
2015-06-16 15:31:19.653 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3692, possible application problem or deadLock
2015-06-16 15:31:19.747 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3786, possible application problem or deadLock
2015-06-16 15:31:25.331 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 5371, possible application problem or deadLock
2015-06-16 15:31:25.840 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 5880, possible application problem or deadLock
2015-06-16 15:31:26.143 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 6183, possible application problem or deadLock
2015-06-16 15:31:26.443 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 6483, possible application problem or deadLock
2015-06-16 15:31:28.491 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3160, possible application problem or deadLock
2015-06-16 15:54:45.531 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4428, possible application problem or deadLock
2015-06-16 15:54:46.918 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 5815, possible application problem or deadLock
2015-06-16 15:54:46.949 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 5846, possible application problem or deadLock
2015-06-16 15:54:47.074 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 5486, possible application problem or deadLock
2015-06-16 16:03:58.894 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3153, possible application problem or deadLock
2015-06-16 16:03:58.923 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3182, possible application problem or deadLock
2015-06-16 16:03:58.954 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3213, possible application problem or deadLock
2015-06-16 16:03:59.231 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3490, possible application problem or deadLock
2015-06-16 16:03:59.260 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3519, possible application problem or deadLock
2015-06-16 16:03:59.715 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3974, possible application problem or deadLock
2015-06-16 16:03:59.819 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4078, possible application problem or deadLock
2015-06-16 16:04:00.044 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4303, possible application problem or deadLock
2015-06-16 16:04:00.340 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4599, possible application problem or deadLock
2015-06-16 16:04:00.438 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4697, possible application problem or deadLock
2015-06-16 16:04:01.888 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 6147, possible application problem or deadLock
2015-06-16 16:04:01.916 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 6175, possible application problem or deadLock
2015-06-16 16:11:53.637 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3124, possible application problem or deadLock
2015-06-16 16:11:54.342 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3829, possible application problem or deadLock
2015-06-16 16:11:54.633 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4120, possible application problem or deadLock
2015-06-16 16:11:54.664 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4151, possible application problem or deadLock
2015-06-16 16:12:14.682 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 7940, possible application problem or deadLock

That's when I don't receive the data requested from the DK servers and connection is being closed.

Just for today:
$ fgrep reset JForexLog.log
2015-06-16 07:14:25.874 ERROR RequestHandler - Connection 1 - Socket error in request handler Error: Connection reset
java.net.SocketException: Connection reset
2015-06-16 07:14:57.889 ERROR RequestHandler - Connection 2 - Socket error in request handler Error: Connection reset
java.net.SocketException: Connection reset

ksh
  • #2,559
  • Jun 16, 2015 10:06am Jun 16, 2015 10:06am
Carbon-Dioxide: the gas of life! https://youtu.be/ttJBdr6eBuo
  • #2,560
  • Jun 16, 2015 4:41pm Jun 16, 2015 4:41pm
from right now:

2015-06-16 17:32:29.164 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3095, possible application problem or deadLock
2015-06-16 17:32:41.769 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4090, possible application problem or deadLock
2015-06-16 17:40:33.629 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3848, possible application problem or deadLock
2015-06-16 19:47:58.314 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4253, possible application problem or deadLock
2015-06-16 19:47:58.736 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4675, possible application problem or deadLock
2015-06-16 19:47:59.063 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 5002, possible application problem or deadLock
2015-06-16 19:58:24.399 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3621, possible application problem or deadLock
2015-06-16 19:58:26.154 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 5376, possible application problem or deadLock
2015-06-16 19:58:28.338 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 6764, possible application problem or deadLock
2015-06-16 20:23:47.097 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3009, possible application problem or deadLock
2015-06-16 20:23:47.354 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3266, possible application problem or deadLock
2015-06-16 20:23:47.448 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3360, possible application problem or deadLock
2015-06-16 20:23:47.671 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3583, possible application problem or deadLock
2015-06-16 20:23:47.933 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3845, possible application problem or deadLock
2015-06-16 20:23:47.964 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3876, possible application problem or deadLock
2015-06-16 20:23:47.996 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 3908, possible application problem or deadLock
2015-06-16 20:23:48.370 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4282, possible application problem or deadLock
2015-06-16 20:23:48.620 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4532, possible application problem or deadLock
2015-06-16 20:23:48.744 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4656, possible application problem or deadLock
2015-06-16 20:23:48.776 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 4688, possible application problem or deadLock
2015-06-16 21:25:53.893 ERROR com.dukascopy.dds4.transport.client.ClientProtocolHandler - fireFeedbackMessageReceived: TO LARGE EXECUTION WAIT TIME: 10594, possible application problem or deadLock

Thats horrible from a strategy and automatic trading point of view. autoreconnect cant work on this as you have to enter the pin!!

ksh
0 traders viewing now