Eugene, Already did that and yes it fixes the problem. Just noticed the number of threads in the eclipse debug pane were growing with successive optimization runs. Thanks, Crichton.
nonlinear5 wrote: >> Eugene, the main optimizer thread pool is not being shutdown in >> OptimizerRunner.java causing >> resource leakage during subsequent optimizations. >> >> > > > > Crichton, how did you diagnose the resource leak? Can you please add > this line to the "finally" clause near the end of OptimizerRunner.java > and see if this fixes the leak: > executor.shutdownNow(); > > Thanks. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
