I assume the reason for rejection was valid -- the exchange was closed? If so, the way to avoid it is to look up the exchange's holiday schedule.
On Tue, Feb 22, 2011 at 3:15 AM, Victor Martin < [email protected]> wrote: > Hi, from time to time I see in my JBookTrader instance something like this: > > > 1. INFO [17:30:12,963][EventReportLog4j:22] Placing order 80 > 2. INFO [17:30:13,200][EventReportLog4j:22] 201: Order rejected - > reason:Exchange is closed (for id 80) > 3. INFO [21:29:13,211][EventReportLog4j:22] Closing current position. > 4. INFO [21:29:13,212][EventReportLog4j:22] Closing current position. > 5. INFO [21:29:14,211][EventReportLog4j:22] Closing current position. > > > Line 1: At 17:30 CET a simulation strategy tried to close a Nasdaq > position. > Line 2: It seems that market was closed and the order was rejected (so the > position remained open) > Line 3-Infinite: At 21:30 CET finished the TradingSchedule for that > strategy and JBookTrader tried to close the position, running into an > infinite loop > > > any clue on how to avoid that? > > -- > 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. > -- 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.
