[jira] [Commented] (SOLR-4129) Solr doesn't support log4j
[ https://issues.apache.org/jira/browse/SOLR-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507352#comment-13507352 ] David Smiley commented on SOLR-4129: +1 Patch looks good. Solr doesn't support log4j --- Key: SOLR-4129 URL: https://issues.apache.org/jira/browse/SOLR-4129 Project: Solr Issue Type: Bug Components: SolrCloud Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0 Reporter: Raintung Li Labels: log Fix For: 4.1, 5.0 Attachments: patch-4129.txt For many project use the log4j, actually solr use slf logger framework, slf can easy to integrate with log4j by design. Solr use log4j-over-slf.jar to handle log4j case. This jar has some issues. a. Actually last invoke slf to print the logger (For solr it is JDK14.logging). b. Not implement all log4j function. ex. Logger.setLevel() c. JDK14 log miss some function, ex. thread.info, day rolling Some dependence project had been used log4j that the customer still want to use it. JDK14 log has many different with Log4j, at least configuration file can't reuse. The bad thing is log4j-over-slf.jar conflict with log4j. If use solr, the other project have to remove log4j. I think it shouldn't use log4j-over-slf.jar, still reuse log4j if customer want to use it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4129) Solr doesn't support log4j
[ https://issues.apache.org/jira/browse/SOLR-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507489#comment-13507489 ] Shawn Heisey commented on SOLR-4129: I've been trying to work out what is being said here and I'm finding it hard to follow. I'm especially confused by the part about log4j-over-slf4j. If this means that I will be able to change logging levels for log4j within the GUI, I'm all for it. I'm less concerned about being able to view the log within the GUI, but that would be a nice addition. I use log4j with Solr, and I've included log4j-over-slf4j. To make it a lot easier to build that way, I patched solr/build.xml, that patch is attached to SOLR-3918. I have the following jars in jetty's lib/ext: jcl-over-slf4j-1.7.2.jar log4j-1.2.17.jar log4j-over-slf4j-1.7.2.jar slf4j-api-1.7.2.jar slf4j-log4j12-1.7.2.jar Solr doesn't support log4j --- Key: SOLR-4129 URL: https://issues.apache.org/jira/browse/SOLR-4129 Project: Solr Issue Type: Bug Components: SolrCloud Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0 Reporter: Raintung Li Labels: log Fix For: 4.1, 5.0 Attachments: patch-4129.txt For many project use the log4j, actually solr use slf logger framework, slf can easy to integrate with log4j by design. Solr use log4j-over-slf.jar to handle log4j case. This jar has some issues. a. Actually last invoke slf to print the logger (For solr it is JDK14.logging). b. Not implement all log4j function. ex. Logger.setLevel() c. JDK14 log miss some function, ex. thread.info, day rolling Some dependence project had been used log4j that the customer still want to use it. JDK14 log has many different with Log4j, at least configuration file can't reuse. The bad thing is log4j-over-slf.jar conflict with log4j. If use solr, the other project have to remove log4j. I think it shouldn't use log4j-over-slf.jar, still reuse log4j if customer want to use it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4129) Solr doesn't support log4j
[ https://issues.apache.org/jira/browse/SOLR-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507496#comment-13507496 ] David Smiley commented on SOLR-4129: Shawn, how could you have both log4j-over-slf4 and log4j itself on the classpath? That doesn't make sense and SLF4J will probably complain; if it doesn't it's still an error. If your intent is to use Log4j then remove log4j-over-slf4. Solr doesn't support log4j --- Key: SOLR-4129 URL: https://issues.apache.org/jira/browse/SOLR-4129 Project: Solr Issue Type: Bug Components: SolrCloud Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0 Reporter: Raintung Li Labels: log Fix For: 4.1, 5.0 Attachments: patch-4129.txt For many project use the log4j, actually solr use slf logger framework, slf can easy to integrate with log4j by design. Solr use log4j-over-slf.jar to handle log4j case. This jar has some issues. a. Actually last invoke slf to print the logger (For solr it is JDK14.logging). b. Not implement all log4j function. ex. Logger.setLevel() c. JDK14 log miss some function, ex. thread.info, day rolling Some dependence project had been used log4j that the customer still want to use it. JDK14 log has many different with Log4j, at least configuration file can't reuse. The bad thing is log4j-over-slf.jar conflict with log4j. If use solr, the other project have to remove log4j. I think it shouldn't use log4j-over-slf.jar, still reuse log4j if customer want to use it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4129) Solr doesn't support log4j
[ https://issues.apache.org/jira/browse/SOLR-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507511#comment-13507511 ] Shawn Heisey commented on SOLR-4129: bq. Shawn, how could you have both log4j-over-slf4 and log4j itself on the classpath? That doesn't make sense and SLF4J will probably complain; if it doesn't it's still an error. If your intent is to use Log4j then remove log4j-over-slf4. I did this because I didn't know any better. I'm a bit of a beginner in the Java universe. I added the slf4j things included in the standard WAR except for the JUL binding, then added the log4j binding and log4j. There are no complaints about it in my log. It's probably not complaining because alphabetically, the real log4j jar comes before the slf4j one, so when the import is done, the right class gets loaded. After removing log4j-over-slf4j, Solr still seems fine. Both before and after the removal, logging at WARN, the only log entry I get is Log watching is not yet implemented for log4j. I would like to have short logs saying that each core has been started and that Solr is fully started. Would it be reasonable to file a jira asking for this to happen at WARN, or would I just have to figure out which class(es) to set to INFO in my log4j config? Solr doesn't support log4j --- Key: SOLR-4129 URL: https://issues.apache.org/jira/browse/SOLR-4129 Project: Solr Issue Type: Bug Components: SolrCloud Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0 Reporter: Raintung Li Labels: log Fix For: 4.1, 5.0 Attachments: patch-4129.txt For many project use the log4j, actually solr use slf logger framework, slf can easy to integrate with log4j by design. Solr use log4j-over-slf.jar to handle log4j case. This jar has some issues. a. Actually last invoke slf to print the logger (For solr it is JDK14.logging). b. Not implement all log4j function. ex. Logger.setLevel() c. JDK14 log miss some function, ex. thread.info, day rolling Some dependence project had been used log4j that the customer still want to use it. JDK14 log has many different with Log4j, at least configuration file can't reuse. The bad thing is log4j-over-slf.jar conflict with log4j. If use solr, the other project have to remove log4j. I think it shouldn't use log4j-over-slf.jar, still reuse log4j if customer want to use it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4129) Solr doesn't support log4j
[ https://issues.apache.org/jira/browse/SOLR-4129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13507518#comment-13507518 ] David Smiley commented on SOLR-4129: bq. I would like to have short logs saying that each core has been started and that Solr is fully started. Would it be reasonable to file a jira asking for this to happen at WARN, or would I just have to figure out which class(es) to set to INFO in my log4j config? Using WARN for an informational message just seems wrong to me, albeit I've seen it in some projects at work. Simply setting only one class to INFO and others higher (e.g. WARN) wouldn't work because this would probably go in SolrCore which has plenty of other INFO messages to say. Too much IMO. I think the right solution is to log an announcement message to a special name like org.apache.solr.announcement. Yeah, file an issue for that. Solr doesn't support log4j --- Key: SOLR-4129 URL: https://issues.apache.org/jira/browse/SOLR-4129 Project: Solr Issue Type: Bug Components: SolrCloud Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0 Reporter: Raintung Li Labels: log Fix For: 4.1, 5.0 Attachments: patch-4129.txt For many project use the log4j, actually solr use slf logger framework, slf can easy to integrate with log4j by design. Solr use log4j-over-slf.jar to handle log4j case. This jar has some issues. a. Actually last invoke slf to print the logger (For solr it is JDK14.logging). b. Not implement all log4j function. ex. Logger.setLevel() c. JDK14 log miss some function, ex. thread.info, day rolling Some dependence project had been used log4j that the customer still want to use it. JDK14 log has many different with Log4j, at least configuration file can't reuse. The bad thing is log4j-over-slf.jar conflict with log4j. If use solr, the other project have to remove log4j. I think it shouldn't use log4j-over-slf.jar, still reuse log4j if customer want to use it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
