at the root of the issue is that logging uses a static logger:
static Logger log = LoggerFactory.getLogger(SolrCore.class);
i don't know of any minimally invasive way to get get around this...
On Dec 17, 2008, at 10:22 AM, Marc Sturlese wrote:
I am thinking in doing a hack to specify the log path of the solr
cores in
solr.xml.
Would like to do something like:
<cores adminPath="/admin/cores">
<core name="core_name" instanceDir="core_dir"
configName="solrconfig.xml" schemaName="schema.xml"
logPath="log_file_path">
<property name="dataDir" value="data" />
</core>
...
</core>
Any advice about how should I start?
Thanks in advance
ryantxu wrote:
As is, the log classes are statically bound to the class, so they are
configured for the entire VM context.
Off hand i can't think of any good work around either. The only
thing
to note is that most core specific log messages include the core name
as a prefix: [core0] ...
ryan
On Dec 17, 2008, at 6:07 AM, Marc Sturlese wrote:
Hey there,
My original app (before getting into Solr) use to have 3 index in
the same
web app. I used log4j with a log file per index.
Now in Solr I have different cores and I am trying to set a log file
per
core via slf4 but don't know how to do it.
As I understood this thread:
http://www.nabble.com/Details-on-logging-in-Solr-td21027267.html#a21027540
You can just instantiate a log file per sol web_app and not per
core?
Thanks in advance
--
View this message in context:
http://www.nabble.com/setting-a-log-file-per-core-with-slf4-tp21051199p21051199.html
Sent from the Solr - User mailing list archive at Nabble.com.
--
View this message in context:
http://www.nabble.com/setting-a-log-file-per-core-with-slf4-tp21051199p21054558.html
Sent from the Solr - User mailing list archive at Nabble.com.
