Hi,

it seems that in onStop() orderStates are not getting updated anymore. Is this correct?

When onStop() is triggered when a PLACE_BID- or PLACE_OFFER-order is still in the state CREATED, trying to close that order leads to an error.
Waiting for a state change to OPENED with Thread.sleep(..) doesn't work, the status won't change. At the same time the position is already listed as PENDING in the JForex-client.

What would be the best procedure to close an order with state CREATED in onStop()?

Best regards,
RR.

Hi,
unfortunately, there is no workaround. You must close them manually.

Dear support,

thank you for your reply.

ok, this means the order would have to have the status "OPENED" before onStop is getting called?
In this case it might help to wait to issue a context.stop() until no order is in state CREATED anymore?

would it then help to replace context.stop()-calls by the following code?

   public void contextStop()
   {
      boolean bStatusOK = false;
      int nLoop = 0;
      try
      {
         while (bStatusOK && nLoop < 5)
         {
            bStatusOK = true;
            for (IOrder order: engine.getOrders())
            {
               if (order.getState() == IOrder.State.CREATED)
               {
                     bStatusOK = false;
                      Thread.currentThread();
                      Thread.sleep(2000,0);   //wait 2 seconds and then test again for the state...
                      break;
               }
            }
            nLoop++;
         }
      }
      catch (Exception e)
      {
         //...
      }
      finally
      {
         context.stop();
      }
   }

Best, RR.

Hello SupportTeam,

if I understand correctly, the order states get updated in onMessage().
Would it be possible for you to update the order states during onStop?
Something like an internal onMessage(.., bOnStop=true) that is still triggered during onStop() and does process the order-messages?

Thanks a lot for considering,
RR.

Yes, i think it would. Try it