Sometimes (perhaps once a day, on average), "IEngine.submitOrder(...)" throws "JFException: Not subscribed to the instrument [EUR/USD]" even though the platform is subscribed to EURUSD.

A contiguous snippet from the console, in reverse chronological order:

11:00:10 TRACE: Currently subscribed to [EUR/USD]
11:00:10 ERROR: JfOrderManager: Thrown in trySubmitOrder, com.dukascopy.api.JFException: Not subscribed to the instrument [EUR/USD]
11:00:07 TRACE: MessageType : INSTRUMENT_STATUS Instument : EUR/USD Tradable : true

Code fragment that produced the above snippet:

        try {
            order = engine.submitOrder(
                labelPrefix + orderIndex++,
                instrument,
                orderCommand,
                orderManager.getAmount(),
                orderManager.getEntry(),
                orderManager.getAllowedSlip(),
                orderManager.getSl(),
                orderManager.getTp(),
                orderManager.getGoodTillTime(),
                comment);
        } catch (JFException ex) {
            Debug.error("JfOrderManager: Thrown in trySubmitOrder, " + ex);
            Debug.trace("Currently subscribed to " + context.getSubscribedInstruments()); // for debugging
        }

(I can provide implementations of Debug.error and Debug.trace, orderManager.getAmount etc on request.)

FURTHER INFORMATION:
When this issue occurs, it is consistent: Even if the order is submitted repeatedly, this exception is thrown repeatedly. When this happens, I have noticed in the past that opening a new EURUSD chart makes the problem go away.

UPDATE: I have confirmed what the above paragraph says many times and further noticed that subscribing the platform to a new instrument also makes the problem go away.

Did you receive any error or warning messages between the moment when the IEngine.submitOrder worked fine, and when it failed with the exception?

No, there is no warning or error message (I confirmed).
I also confirmed that opening a new EURUSD chart makes the problem go away temporarily.

In the posts above, the engine seems to "unsubscribe", and resubscribe when a new chart of that instrument is opened. I've noticed some similar (possibly related problems). Sometimes...

• ... one of the charts would stop charting (producing flats), and would resume charting when I open (another) new chart of the same instrument.
• ... one of the strategies would stop receiving ticks (onTick not called), and would resume receiving ticks when I open a new chart of the same instrument.

This usually seems to happen after long periods of inactivity.

BEGIN SPECULATION
It seems as if components of the system (engine, strategy, chart) sometimes become "unsubscribed" (for no apparent reason) from the client's central tick feed, and that their subscriptions are "refreshed" when a new component subscribes.
END SPECULATION

Please provide full stack trace for the exception.

ex.getCause() == null

We launched the following program for 3 days on an account where both other strategies were ran and multiple instrument subscriptions/unsubscriptions were carried out:
We could not replicate the case. Also no other standalone user has reported such case, although there are many who run their strategies over multiple days in a row. Could you please try to recall what other actions you had carried out on the same account both in standalone and platform before this JFException was thrown?

Thank you.

I could be mistaken, but I think this tends to happen mostly (but not necessarily) after long periods of inactivity. For example, a strategy left to idle overnight (or over a weekend) might throw this exception first thing in the morning. Also, I have never noticed this happening while the platform is subscribed to more than one instrument; but that is just anecdotal evidence.


I don't know whether this bug occurs in standalone usage, but I have only been testing with a strategy in the platform. Perhaps it is a bug in the platform then? Is there a possibility that components of the platform (engine, charts, strategies) become unsubscribed from an instrument while IContext.getSubscribedInstruments() returns that instrument?


I did not encounter the bug in the last 3 days either. But it comes and goes.

IMO the bug is not induced by actions such as subscribing/unsubscribing instruments, but more likely caused by disruptions in connectivity. Quite often, it has occurred without any user-actions other than:
1. Starting the platform (which is already by default subscribed to (only) the required instrument)
2. Starting the strategy in the platform
3. Waiting until the strategy tries to place its first order, at which point the exception is thrown (consistently). (The period waited has been anything from a few minutes to a weekend.)