Talk:Log4j

Image:Nuvola apps important.svg

:Image:Log4j.jpg is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.

Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.BetacommandBot 23:41, 5 June 2007 (UTC)

It doesn't look outdated to me. I'll remove it, but if I'm missing something let me know.

The Log4j 1.3 and 2.0 branches should probably be discussed. Some 1.3 alpha versions were released, but development has been abandoned. From http://logging.apache.org/log4j/:

:Apache log4j has three development branches: a stable branch, 1.2, a discontinued branch, 1.3 and an experimental branch 2.0.

:Apache log4j 1.2 releases are widely deployed. Development on the 1.2 branch is generally limited to bug fixing and minor enhancements.

:Apache log4j 1.3 alpha releases are in limited use. Apache log4j 1.3 added many interesting features, but was compatibility with log4j 1.2 was problematic. Many features original developed for log4j 1.3 have been back-ported as companions for log4j 1.2. No further development is anticipated.

:Apache log4j 2.0 is an experimental development branch for logging services designed for Java 5 and later.

-- Ernstdehaan 07:52, 3 September 2007 (UTC)

Someone put "outdated" on the log4cxx link again. I don't think it is outdated. If there is a reason for putting "outdated" on the log4cxx link, please indicate what it is. —Preceding unsigned comment added by 132.228.195.206 (talk) 14:27, 16 October 2007 (UTC)

:I confirm that, according to answer received on log4j users mailing list, log4cxx isn't outdated. --Arnauld (talk) 19:02, 16 October 2007 (UTC)

Just Adding log4j.properties & logger statement in java code doesn't generate log files in the case of

the Application Server such as Tomcat.

Following method can be added in the Main class & should be called via suitable methods

public void initLogging(){

try{

URL fl = this.getClass().getClassLoader().getResource("log4j.properties");

PropertyConfigurator.configure(fl);

logger.debug("Reloading log4j.properties file.");

}

catch(Exception e)

{

logger.error(e);

}

}

Following should be added in the log4j.properties is also needed.

log4j.logger.=

• This is not the recommended initialization procedure for an application server such as tomcat. This is a very helpful link: [http://logging.apache.org/log4j/1.2/manual.html]. Check out the section named "Default Initialization under Tomcat" - basically you define a servlet that runs upon application startup

We should remove all direct links to external web site selling softwares and so on...

May be also: add PatternLayout chapter integrating a TTCC subsection

Oliver H (talk) 17:10, 2 July 2010 (UTC)

I just wanted to say how helpful the TTCC section is. Adding links to it in my log4j.xml config files :) Here's hoping the link doesn't get removed!

--Brilong87 (talk) 16:08, 28 February 2011 (UTC)

Log4j —Preceding unsigned comment added by 219.65.191.106 (talk) 08:21, 7 October 2010 (UTC)

It is not very clear to me how to specify where the output file is to be located. Description of the defaults (if any) would be appreciated too.

Dan Aquinas (talk) 23:31, 7 November 2012 (UTC)

The log4j Levels should be ordered logically, not like posted. It should say ALL , DEBUG, INFO , WARN , ERROR , FATAL, OFF (in this order)

137.30.122.155 (talk) 23:16, 10 January 2015 (UTC)

It is not clear what "NLog" is. Does it refer to JSNLog (probably not)? --Mortense (talk) 21:38, 15 May 2017 (UTC)

Hello fellow Wikipedians,

I have just modified one external link on Log4j. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive https://archive.is/20121225133348/http://log4r.rubyforge.org/ to http://log4r.rubyforge.org/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

{{sourcecheck|checked=false|needhelp=}}

Cheers.—InternetArchiveBot (Report bug) 04:55, 5 January 2018 (UTC)

{{Archive top|status=Merged|result=There was consensus and sufficient arguments that Reload4j is not a notable project on its own and should be merged into Log4j, specifically lacking quality sources that address the topic. Notability is established by the quantity and quality of sources, not by metrics of usage or importance to some. Projects which are important enough will naturally have reliable secondary sources. SWinxy (talk) 22:10, 16 August 2022 (UTC)}}

My (non-expertise) search did not find reliable sources that justify a standalone article on Reload4j and seems to make sense as part of the Log4j article. Singularity42 (talk) 17:31, 14 January 2022 (UTC)

:{{u|Man thinking}} [https://en.wikipedia.org/w/index.php?title=User_talk:Singularity42&diff=1065665267&oldid=1065621337 replied on my talk page] that Reload4j is a fork of Log4j he created for the purpose of trademark protection and to give the Reload4j its own identify. Of course, that is not a valid reason for a stand-alone article, and further supports that this should be merged, and the purpose of Wikipedia is not to help products, etc. obtain notability. Singularity42 (talk) 18:11, 14 January 2022 (UTC)

Comment by {{u|Man thinking}}: I apologize if it is not proper etiquette to reply below a comment. The reload4j article is expanding. It will evolve if you give it half a chance. I would also like to observe that there is an unmet need to offer users a migration path from log4j 1.x and reload4j does that. — Preceding unsigned comment added by Man thinking (talk • contribs) 18:37, 14 January 2022 (UTC)

• Merge. Not notable by any measure (see the general notability guideline). The content might be due as a section of the Log4j article to the extent that some reliable source exists, although none is present in the current Reload4j article. MarioGom (talk) 10:21, 15 January 2022 (UTC)

Reload4j is being adopted by more and more Java projects as a drop-in replacement for log4j 1.x. The pressure is very high on everyone to address log4shell vulnerability and by ricochet the more minor log4j1.x vulnerabilities. Reload4j significantly alleviates the pain of such mitigation. --Man thinking (talk) 13:50, 19 January 2022 (UTC)

I also note that there is no Wikipedia article on logback. It is the most widely used logging framework in the Java ecosystem. --Man thinking (talk) 15:34, 19 January 2022 (UTC)

:{{u|Man thinking}}: Please, see the general notability guideline. We assess notability based on coverage in reliable sources. How much a piece of software is used is not really relevant. MarioGom (talk) 13:34, 12 February 2022 (UTC)

• Merge per nom. ―Jochem van Hees (talk) 11:58, 13 February 2022 (UTC)

Regarding notability of reload4j, please read https://www.linkedin.com/pulse/log4j-1x-reload4j-rescue-michaela-elschner/ --Man thinking (talk) 09:48, 14 February 2022 (UTC)

• reload4j does not address any issues related to log4shell - in fact, log4j1 was never affected by log4shell. Instead, log4j1 and also reload4j does share the same problems, like concurrency problems which can cause serious harm to your applications. They are all known and tracked in Bugzilla. Several other CVEs were raised for reload4j since. All unrelated to log4shell and easy to migitate. The whole reload4j project is obsolete and there is no need to introduce problems like classpath crashes using it. That said, I don't think it's worth mentioning it on the log4j wikipedia. Cy23 (talk) 18:54, 19 February 2022 (UTC)

Indeed, log4j 1.x was not affected by log4shell. If concurrency problems affecting reload4j are qualified as "seriously harmful" how should CVEs be qualified? What about log4shell? --Alain madak (talk) 16:46, 21 February 2022 (UTC)

{{Archive bottom}}