Fetching orders and non balances?

[Desrever Nu]

Maybe it is just a logging problem but

0:01:08.927 c.n.n.s.S.StrategySecondaryPegUtils - Initial walls placed
10:01:09.709 c.n.n.s.OrderManager - Fetching active orders ...
10:01:15.150 c.n.n.s.OrderManager - Fetching active orders ...
10:01:19.903 c.n.n.s.OrderManager - Fetching active orders ...
10:01:25.098 c.n.n.s.OrderManager - Fetching active orders ...
10:01:29.719 c.n.n.s.OrderManager - Fetching active orders ...
10:01:35.163 c.n.n.s.OrderManager - Fetching active orders ...

[Benjamin Cordes]

yes, bad debug message. we can trace it (BalanceManager it is traced)

[Desrever Nu]

I am more in favour of debugging both , and also debug all calls to server routes. We need to find agreement because I am setting debug and you always undo it by setting it to trace from time to time

[Desrever Nu]

restored DEBUG level for fetching Balances and the routes in ConfigController.

The only route with a trace level should be the dumplogs.

We need to know exactly what is going on when something goes wrong and a custodians send us the verbose logs.

[Desrever Nu]

Resolve when ACKd @benjyc

[Benjamin Cordes]

makes sense. alternatively we could also add a logger on trace level (very easy to do - just add a few lines in XML). reading this info in the UI is not going to be very informative. on the other hand if we trace everything log files could get very large after long runs.

[Desrever Nu]

I agree, that is why verbose is optional and should be default to false, I do not expect custodians to set it to true