Dukascopy Support Board http://www.dukascopy.com/swiss/english/forex/jforex/forum/ |
|
The latest version, this function (getorders() ) is incorrect http://www.dukascopy.com/swiss/english/forex/jforex/forum/viewtopic.php?f=16&t=56973 |
Page 1 of 1 |
Author: | grosskt [ Tue 19 Mar, 2019, 07:09 ] | ||
Post subject: | The latest version, this function (getorders() ) is incorrect | ||
package COM.Mystrategies; import java.util.*; console print message :
|
Author: | API Support [ Tue 19 Mar, 2019, 17:49 ] |
Post subject: | Re: The latest version, this function (getorders() ) is incorrect |
We were unable to reproduce this issue. Could you provide more info for reproducing? Especially about orders in console log. When and under what condition they were opened? Did you do it manually or by strategy? specOrder.waitForUpdate(1000); It doesn't give you guarantee what after timeout this order will be closed. Closing order may take more than 1000 ms. Instead, it is recommended to use specOrder.waitForUpdate(IOrder.State.CLOSED); Then you can be sure that order will be in closed state after waitForUpdate() method. |
Author: | grosskt [ Fri 29 Mar, 2019, 09:02 ] | ||
Post subject: | Re: The latest version, this function (getorders() ) is incorrect | ||
The steps are as follows: 1) Running strategy program 2)On the platform, after many times of manual work, opening a position, after closing a position, This bug will appear!!!! See the print log : --(note : The currency pair running in the program is USD/JPY. On the platform, if the manually operated currency pair is not USD/JPY, such as: open, EUR/USD or GBP/USD ..., this kind of BUG will appear)
|
Author: | SMARTFX [ Wed 03 Apr, 2019, 21:21 ] |
Post subject: | Re: The latest version, this function (getorders() ) is incorrect |
Hi Dukascopy support, I confirm, I am encountering exactly the same issue. To reproduce the issue, create a dummy strategy with following implementation of onMessage method. 1) Start the strategy, then 2) start selling or buying eur/usd manually from JForex platform 3) observe the console, you will see that for each new order filled there are two entries with the same ExtID. One of the entry is broken IOrder object. The broken object has null fields. @Override Please fix ASAP. Best regards, Greg |
Author: | API Support [ Thu 04 Apr, 2019, 14:48 ] |
Post subject: | Re: The latest version, this function (getorders() ) is incorrect |
Fix will be available in next platform release. |
Author: | mtnfx [ Fri 05 Apr, 2019, 21:56 ] |
Post subject: | Re: The latest version, this function (getorders() ) is incorrect |
And ... it would be nice to release updated JForext Client SDK. The latest one was released almost 5 month ago ... |
Page 1 of 1 |