|
Attention! Read the forum rules carefully before posting a topic.
Try to find an answer in Wiki before asking a question. Submit programming questions in this forum only. Off topics are strictly forbidden.
Any topics which do not satisfy these rules will be deleted.
Simple Logger configuration on linux console standalone API |
hyperscalper
|
Post subject: Simple Logger configuration on linux console standalone API |
Post rating: 0
|
Posted: Sun 12 Jan, 2014, 22:13
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
Linux server console standalone API, how do I configure log4j.properties to suppress these messages? I believe I should place log4j.properties in the default directory. Does my code need to call any Logger functions on startup at all? Thanks, HyperScalper 2014-01-12 21:07:42.991 WARN LocalCacheManager - Some or all of the requested data was not found, instrument [EUR/JPY], period [Ticks], side [null], chunk from [2014.01.12 20:00:00 000], chunk to [2014.01.12 21:00:00 000] 2014-01-12 21:07:42.991 WARN LocalCacheManager - Some or all of the requested data was not found, instrument [EUR/JPY], period [Ticks], side [null], chunk from [2014.01.12 21:00:00 000], chunk to [2014.01.12 22:00:00 000] 2014-01-12 21:07:43.030 WARN LocalCacheManager - Some or all of the requested data was not found, instrument [GBP/JPY], period [Ticks], side [null], chunk from [2014.01.12 21:00:00 000], chunk to [2014.01.12 22:00:00 000] 2014-01-12 21:07:43.076 WARN LocalCacheManager - Some or all of the requested data was not found, instrument [EUR/JPY], period [Ticks], side [null], chunk from [2014.01.12 21:00:00 000], chunk to [2014.01.12 22:00:00 000] 2014-01-12 21:07:43.122 WARN LocalCacheManager - Some or all of the requested data was not found, instrument [GBP/JPY], period [Ticks], side [null], chunk from [2014.01.12 20:00:00 000], chunk to [2014.01.12 21:00:00 000]
|
|
|
|
 |
API Support
|
Post subject: Re: Simple Logger configuration on linux console standalone API |
Post rating: 0
|
Posted: Tue 14 Jan, 2014, 08:15
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17 Posts: 6139
|
simply set com.dukascopy.charts.data.datacache.LocalCacheManager level to ERROR.
|
|
|
|
 |
hyperscalper
|
Post subject: Re: Simple Logger configuration on linux console standalone API |
Post rating: 0
|
Posted: Wed 15 Jan, 2014, 04:31
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
Do you have fully qualified class names for all of the logger messages, for example:
CurvesJsonProtocolHandler
I assume the fully qualified class name needs to be used to influence the logging level...
HyperScalper
|
|
|
|
 |
hyperscalper
|
Post subject: Re: Simple Logger configuration on linux console standalone API |
Post rating: 0
|
Posted: Wed 15 Jan, 2014, 06:03
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
So I put this in log4j.properties com.dukascopy.charts.data.datacache.LocalCacheManager=ERROR But I still get these messages: 2014-01-15 05:00:12.863 WARN LocalCacheManager - Some or all of the requested data was not found, instrument [EUR/USD], period [Ticks], side [null], chunk from [2014.01.15 05:00:00 000], chunk to [2014.01.15 06:00:00 000] 2014-01-15 05:00:12.970 WARN LocalCacheManager - Some or all of the requested data was not found, instrument [EUR/USD], period [Ticks], side [null], chunk from [2014.01.15 05:00:00 000], chunk to [2014.01.15 06:00:00 000] 2014-01-15 05:00:13.082 WARN LocalCacheManager - Some or all of the requested data was not found, instrument [EUR/USD], period [Ticks], side [null], chunk from [2014.01.15 05:00:00 000], chunk to [2014.01.15 06:00:00 000] 2014-01-15 05:00:13.183 WARN LocalCacheManager - Some or all of the requested data was not found, instrument [EUR/USD], period [Ticks], side [null], chunk from [2014.01.15 05:00:00 000], chunk to [2014.01.15 06:00:00 000]
What should I try next, to suppress these messages? Thanks, HyperScalper
|
|
|
|
 |
API Support
|
Post subject: Re: Simple Logger configuration on linux console standalone API |
Post rating: 0
|
Posted: Wed 15 Jan, 2014, 08:19
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17 Posts: 6139
|
hyperscalper wrote: Do you have fully qualified class names for all of the logger messages, for example:
CurvesJsonProtocolHandler You can locate the class also by searching the type (e.g., in Eclipse the command is Ctrl+Shift+T). hyperscalper wrote: I assume the fully qualified class name needs to be used to influence the logging level... You can also set the level for a package or package group. For instance, see JForex-SDK/rc/log4j.properties - the default level for our logs is: #Filter for dukascopy logs log4j.category.com.dukascopy=INFO In this case you work with a package group. hyperscalper wrote: What should I try next, to suppress these messages? Did you make sure that the log4j.properties file is in your classpath? If you, for instance, set all logs to ERROR, does anything change? If not, please see how logging is configured in our downloadable JForex-SDK maven project.
|
|
|
|
 |
hyperscalper
|
Post subject: Re: Simple Logger configuration on linux console standalone API |
Post rating: 0
|
Posted: Wed 15 Jan, 2014, 12:42
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
Thanks.
I prepended ".:" to the linux classpath jar list since possibly the current directory folder including the log4j.properties file was not on the java classpath, which may be a big part of the solution.
HyperScalper
|
|
|
|
 |
|
Pages: [
1
]
|
|
|
|
|