> Sure, probably the exchange was closed, but the problem here is not the > remaining opened position, is the dead lock state that causes JBookTrader to > "freeze" (for example it does not update UI table). > > Maybe the solution is to get market's rejection callback and leave that > position opened, going on with the the regular execution without interfering > with other strategies. > > Are you sure there is a dead lock? If the exchange was closed, there is no market data, so the JBT UI would *seem* frozen, when in fact it's simply reflecting the last available market data.
If you look in the EventReport, you'd notice that the API is reporting the exchange hours for the day. A nice enhancement for JBT would be to parse that information, and warn the user about the holiday hours, if any. -- You received this message because you are subscribed to the Google Groups "JBookTrader" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jbooktrader?hl=en.
