[ 
https://issues.apache.org/jira/browse/SOLR-7887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386500#comment-16386500
 ] 

Shawn Heisey commented on SOLR-7887:
------------------------------------

bq. Are you talking about one of the log4j2.xml files? 

I also noticed that there were multiple files, so I wanted to sanity check 
which xml file was being used for Solr startup.  I made a little change to the 
fileName parameter in what I assumed was the right one.  The filename in the 
exception didn't change.  What finally changed the exception message was 
modifying server/scripts/cloud-scripts/log4j2.xml, which was definitely a 
surprise.

Solr 8.0-SNAPSHOT *does* start even with the multiple exceptions, and when it 
starts, the dashboard doesn't show a sysprop definition for the log4j config 
file.  I'm assuming it should be there.  It is there on my 6.6.2 dev server:

-Dlog4j.configuration=file:/index/solr6/log4j.properties


> Upgrade Solr to use log4j2 -- log4j 1 now officially end of life
> ----------------------------------------------------------------
>
>                 Key: SOLR-7887
>                 URL: https://issues.apache.org/jira/browse/SOLR-7887
>             Project: Solr
>          Issue Type: Task
>    Affects Versions: 5.2.1
>            Reporter: Shawn Heisey
>            Assignee: Varun Thacker
>            Priority: Major
>         Attachments: SOLR-7887-WIP.patch, SOLR-7887-eoe-review.patch, 
> SOLR-7887-eoe-review.patch, SOLR-7887.patch, SOLR-7887.patch, 
> SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, 
> SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch, SOLR-7887.patch
>
>
> The logging services project has officially announced the EOL of log4j 1:
> https://blogs.apache.org/foundation/entry/apache_logging_services_project_announces
> In the official binary jetty deployment, we use use log4j 1.2 as our final 
> logging destination, so the admin UI has a log watcher that actually uses 
> log4j and java.util.logging classes.  That will need to be extended to add 
> log4j2.  I think that might be the largest pain point to this upgrade.
> There is some crossover between log4j2 and slf4j.  Figuring out exactly which 
> jars need to be in the lib/ext directory will take some research.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to