Hi Pooja,
On Fri, Mar 4, 2022 at 10:32 AM Pooja Pandey
wrote:
> We are calling
> Logger.getLogger(, )
>
> And in AppenderAttachableImpl aai;, this is returning AppenderWrapper, which
> we are trying to cast to FileAppender as we were doing when we were using
> log4j1.x.
That will not work,
On Fri, Mar 4, 2022 at 7:32 PM Ralph Goers wrote:
> I am a little surprised though as it looks like Gary added the Log4j 1.2
> FileAppender to log4j-1.2-api but he didn’t remove the builder. If he had it
> would have created org.apache.log4j.FileAppender as you want.
The
Hello Pooja,
On Mon, Mar 7, 2022 at 11:23 AM Pooja Pandey
wrote:
> I think there is something wrong with Log4j1.x bridge level handling when
> migrating from log4j1.x to log4j2.x.
>
> Issue: In my config file, log level is set to "Error", but with log4j1.x
> bridge log level is getting
Hello Pooja,
On Mon, Mar 7, 2022 at 1:40 PM Pooja Pandey
wrote:
>
> -> If I recall correctly, you are using a custom `Logger` class. My guess is
> that you overrode the `getEffectiveLevel()` with some custom logic.
>
> Yes Piotr, you are correct. I am overriding this method in my custom logger
Hi Pooja,
On Sat, Mar 5, 2022 at 3:01 AM Pooja Pandey
wrote:
> @Override
> public Appender getAppender(final String name) {
> AppenderWrapper appenderWrapper = (AppenderWrapper)
> super.getAppender(name);
> return
>
Hi Pooja,
On Sat, Mar 5, 2022 at 1:48 PM Pooja Pandey
wrote:
> Hi Piotr,
>
> I don’t understand what is the bug?? Can you please help me with JIRA
> ticket summary and description.
The bug is that if you use a native Log4j 1.2 appender (a derivative
class of org.apache.log4j.FileAppender for
Hello,
On Mon, Mar 7, 2022 at 3:15 PM Pooja Pandey
wrote:
>
> From the questions you posted up to now, you use a lot of custom code
> extending Log4j 1.x capabilities. In my personal opinion you'll spend more
> time trying to adapt your code to use the Log4j 1.x bridge, than it would
>
Ralph,
On Sat, Mar 5, 2022 at 6:21 PM Ralph Goers wrote:
> Even if getAppender() were to bypass the AppenderWrapper it would still return
> org.apache.logging.log4j.core.appender.FileAppender, not
> org.apache.log4j.FileAppender.
> Are you proposing that getAppender return a proxy for
>
On Sat, Mar 5, 2022 at 10:50 PM Gary Gregory wrote:
> This is a bit tricky, the API is typed to return an Appender and that's
> what we do, not only that but it is an Appender that behaves properly IIRC.
> If we returned the wrapped Log4j 1 Appender and you call it, the wrong
> thing will happen
Hi,
On Tue, Mar 8, 2022 at 7:48 AM Pooja Pandey
wrote:
> I am trying to migrate from log4j1.x to log4j2.17.2 using log4j1.x bridge
> approach. I am getting below ClassCastException error message. Please let me
> know if you have any idea how to fix this.
>
> 2022-03-08 01:41:17,023
Hello Fred,
On Fri, Mar 11, 2022 at 1:29 AM Fred Eisele wrote:
> I would like something similar.
> Maybe a way to initialize a builder with the current configuration?
An already initialized `AbstractConfiguration` can no longer be used
to initialize a configuration builder. However you can use
Hello Pavithra,
The class "org.apache.log4j.rolling.RollingFileAppender" is not part
of the `log4j` artifact, but it is part of `apache-log4j-extras`
(https://mvnrepository.com/artifact/log4j/apache-log4j-extras/1.2.17).
Can you try your original configuration:
On Mon, Feb 21, 2022 at 11:16 AM
Hello Arulkumar,
What method are you using to change the logger's level? The
`Configurator.setLevel` methods are probably the most appropriate
ones.
Can you provide a minimal example of code that does not work?
Piotr
On Wed, 23 Mar 2022 at 06:43, Arulkumar Ponnusamy wrote:
>
> Hi all,
> I am
Hi Arulkumar,
On Thu, 24 Mar 2022 at 07:30, Arulkumar Ponnusamy
wrote:
> However, What i noticed is, the Configurator.setLevel() method's
> Logger.getContext has a different reference id whereas the actual class's
> LoggerFactory.getLogger(class) has a different context id. I guess, because
>
Hello Juan,
On Tue, 29 Mar 2022 at 23:00, Juan Jose Silupú Maza
wrote:
> So, is my project affected by the LOG4J vulnerability? How do I mitigate it?
The Log4Shell vulnerability (CVE-2021-44228) concerned only the
`log4j-core` artifact developed by the Apache Logging Services
project. The
Hello Pablo,
On Tue, 29 Mar 2022 at 19:58, Pablo Rogina wrote:
> However this warning appears (application launched with -Dlog4j2.debug=true):
> WARN StatusLogger Unable to load plugin class name
> com.mycompany.log4j.CustomAppender with key
> com.mycompany.log4j.customappender
This is an
Hello Stamatis,
I posted a working solution on SO:
logger.t1.filter.M.type = Filters
logger.t1.filter.M.f1.type = RegexFilter
logger.t1.filter.M.f1.regex = .*SQL.*
logger.t1.filter.M.f1.onMatch = NEUTRAL
logger.t1.filter.M.f1.onMismatch = DENY
logger.t1.filter.M.f2.type = RegexFilter
On Sun, 3 Apr 2022 at 21:53, Ralph Goers wrote:
> Bugs?
>
> When it was first implemented it followed a standard format (which should
> still work). Almost immediately folks started “simplifying” it since the
> standard
> format is cumbersome. But being cumbersome is not a bug.
>
> The biggest
Hi Ralph,
On Sun, 3 Apr 2022 at 19:00, Ralph Goers wrote:
> The enhancement you suggest would make the properties configuration different
> than
> the other configuration formats as they all require the Filters element. This
> is yet another
> example of why most (or all) of the log4j 2
Hi Ralph,
On Thu, 7 Apr 2022 at 07:50, Ralph Goers wrote:
> Second, putting the property in log4j2.component.properties is correct.
> However, it must only be on the classpath of the web app that needs it, not
> in a shared directory.
If there is no `log4j-api` in the web app classpath, I
On Mon, 6 Nov 2023 at 23:14, Piotr P. Karwasz wrote:
>
> In order to concentrate our limited resources on the remaining modules,
> the PMC decided to deprecate the following modules/features in 2.x and
> to remove them in 3.x:
> * `log4j-cassandra`,
> * CouchDB appender,
In order to concentrate our limited resources on the remaining modules,
the PMC decided to deprecate the following modules/features in 2.x and
to remove them in 3.x:
* `log4j-cassandra`,
* CouchDB appender,
* GELF appender,
* Kafka appender,
* jeroMQ appender,
* `log4j-jpa`,
*
Hi all,
On Thu, 28 Sept 2023 at 09:35, Piotr P. Karwasz wrote:
> We know that statistics are not everything and that is why we would
> like to hear your opinion on these modules. The discussion will be
> open for a month, after which the PMC will announce a definitive list
> of
Hi all,
We always strive to only release industrial-strength components.
Following an internal discussion and looking at statistics from
several sources, the PMC plans to deprecate in the 2.x version several
components for removal in 3.x.
We know that statistics are not everything and that is
Apache Log4j team is pleased to announce the 2.21.1
release. Apache Log4j is a versatile, industrial-strength
Java logging framework composed of an API, its implementation,
and components to assist the deployment for various use cases.
For further information (support, download, etc.) see the
Hello Stephen,
On Wed, 20 Apr 2022 at 20:03, Stephen Johns
wrote:
> Configurator.initialize(configurationBuilder.build());
>
This only works if the `LoggerContext` has not been initialized yet. Since
every call to a `LogManager` method initializes a `LoggerContext`, it is
almost certainly too
Hello Karthik,
On Tue, 19 Apr 2022 at 14:45, KARTHIK SHIVAKUMAR
wrote:
> I need log4j2 to log all of the info/debug objects across the project.
> If i add log4j2-core & log4j2-api to the project library, the packages
> do not recognise the log4j objects unless there is a entry to
>
Hi Dave,
Thank you for bringing this subject up.
On Thu, 12 May 2022 at 13:16, Dave Piper (HE/HIM)
wrote:
> We've been using log4j for over a decade to produce logs for various
> webapps within a single tomcat instance. Some of our loggers and file
> appenders are defined within the tomcat/lib
Hi Alain,
On Thu, 7 Jul 2022 at 11:35, Alain Désilets wrote:
> If you look at my pom, you can see that there is a filter in the
> configuration of the shade plugin that remove the Log4j2Plugins.dat files.
> This seems to work because
>
> jar -tf iutools-core-1.0.2-jar-with-dependencies.jar |
Hi, Björn,
On Wed, 13 Apr 2022 at 17:46, Björn Kautler wrote:
>
> I'm currently using ListAppender from log4j2-core-test, to test that
> the logging of the project does what it should do.
> For that I configured a ListAppender in the log4j2 config file that is
> used for the tests.
> In a custom
Hi René,
On Fri, 10 Jun 2022 at 16:36, Schindler, René
wrote:
> Therefore we came up with this workaround:
>
> @PreDestroy
> public static void shutDown() {
> org.apache.logging.log4j.LogManager.shutdown();
>
> Configurator.reconfigure(new NullConfiguration());
>
Hi Rick,
I gave a longer answer about this a couple of months ago on StackOverflow:
https://stackoverflow.com/q/71862896/11748454
Basically the delayed lookup `$${date:...}` uses the current time,
when the rollover occurs, while the pattern `%d{...}` uses the date of
the previous rollover.
A
Hi Clayton,
On Fri, 14 Oct 2022 at 17:32, Clayton Wohl wrote:
>
> I've heard rumors that the log4j devs are working on a Java 11+ JPMS native
> version of log4j. This would help end users use jlink to package/distribute
> their applications. Is this still happening? Is there a ballpark time
>
Hi Joan,
> After making a lot of tests trying to get this working again, we had to
> change the line below:
>
> this.systemLog = LogManager.getLogger("LOGGER_SYSTEM");
>
> �
>
> By this:
>
> this.systemLog = LogManager.getContext().getLogger("LOGGER_SYSTEM");
This looks like a
Hi Joan,
On Sun, 16 Oct 2022 at 00:45, Joan ventusproxy
wrote:
> The " log4j.configurationFile " variable is set in this way:
> System.setProperty("log4j.configurationFile",
> "/opt/ventusproxy/app/proxy/ROOT/WEB-INF/log4j.xml");
For some unknown reason this is executed too late (after Log4j2
Hi Stig,
On Fri, 18 Nov 2022 at 11:03, Stig Døssing
wrote:
> Is there a way to disable this “permanent substitution” and get log4j to do
> the system property lookup for every log event, even if there is a default
> value? If not, should there be? System properties can be changed from inside
Hi Jeff,
On Fri, 11 Nov 2022 at 15:58, wrote:
> I just discovered the Junit hooks and have been using them out in my test
> code - nice way of testing logging with a clean context.
Can you provide an example on how you use the JUnit extensions in your
application test code?
The JUnit
Hi Chris,
On Tue, 28 Feb 2023 at 20:04, Christopher Schultz
wrote:
> What is the recommended technique for changing a single logger's
> threshold in log4j2? I realize that the best thing to do would be to
> "just configure it correctly the first time" but in reality, you
> sometimes just have to
Hi Ganesh,
On Tue, 2 May 2023 at 04:12, Ganesh S wrote:
> I'm trying to implement remote logging for my application which is running
> in a docker container.
> The remote server provider is Papertrail.
> I want to specify a custom local host name, currently it is taking
> container id, which I
Hi Jason,
On Sat, 3 Jun 2023 at 00:13, Jason Guild wrote:
> The application currently uses log4j-web to get the all the essential
> setup for initializing log4j 2 under an application container. The
> log4j-web library appears to have a hard dependency on log4j-core.
The `log4j-web` module is
Hi Nishu,
Sorry for the delay,
On Wed, 24 May 2023 at 06:47, Nishu Gupta
wrote:> I did the set the `log4j1.compatibility` to `true` in the
custom properties.
>
> Do I need to use the log4j.xml while using the bridge jar? or I need to
> convert to log4j2.xml as well?
My rule of thumb on this is
Hi Danish,
On Tue, 1 Aug 2023 at 20:10, Danish Arif wrote:
> My use case is that my application uses the above mentioned method to get
> logger and log. Appender and Logger have been set in log4j2.xml file. We
> stop the Logger by getting all core appenders , removing them , then
> stopping them
Hi Ralph,
On Tue, 1 Aug 2023 at 20:58, Ralph Goers wrote:
> 2. Partition your application so that the main application and each batch job
> use their own ClassLoader. The ClassLoaderContextSelector (the default) will
> then create a LoggerContext for each ClassLoader and each can have its own
Hi Nishu,
On Tue, 16 May 2023 at 07:25, Nishu Gupta wrote:
> Currently I am using log4j 1.x version. I am trying to migrate from 1.x to =
> 2.x using bridge jar.
>
> we are using below category in log4j1.xml
> eAppender">
>
> (...)
>
> I am trying to convert into logj2.xml and we have custom
The Apache Log4j 2 team is pleased to announce the Apache Log4j
Transformation Tools 0.1.0 release!
Apache Log4j Transformation Tools is a subproject of Apache Log4j that
provides binary manipulation tools for Log4j-enabled software.
In this first release you'll find:
• A Maven plugin to
The Apache Log4j team is pleased to announce the 2.23.0
release. Apache Log4j is a versatile, industrial-strength
Java logging framework composed of an API, its implementation,
and components to assist the deployment for various use cases.
For further information (support, download, etc.) see the
The Apache Log4j team is pleased to announce the 3.0.0-beta2
release. Apache Log4j is a versatile, industrial-strength
Java logging framework composed of an API, its implementation,
and components to assist the deployment for various use cases.
For further information (support, download, etc.)
Hi Mickael,
On Wed, 10 Jan 2024 at 15:53, Mickael Maison wrote:
> I see that log4j3 is about to release, so I'm wondering what are the
> plans regarding future development and maintenance of log4j2? Do you
> expect to keep releasing new 2.X versions? How long do you expect to
> still maintain
The Apache Log4j team is pleased to announce the 2.22.1
release. Apache Log4j is a versatile, industrial-strength
Java logging framework composed of an API, its implementation,
and components to assist the deployment for various use cases.
For further information (support, download, etc.) see the
The Apache Log4j Kotlin API team is pleased to announce the 1.4.0
release. This project contains a Kotlin-friendly interface to log
against the Log4j API. For further information (support, download,
etc.) see the project website[1].
[1] https://logging.apache.org/log4j/kotlin/
=== Release Notes
Hi Joan,
On Thu, 25 Jan 2024 at 12:06, wrote:
> My application has been using async logging for years by setting this env
> variable on tomcat 8.5.x running on java 11 with log4j-2.15/6/7/8/9:
> -DLog4jContextSelector=org.apache.logging.log4j.core.async.BasicAsyncLoggerContextSelector
>
> Now
Hi Christopher,
On Fri, 2 Feb 2024 at 23:54, Christopher Schultz
wrote:
> I'm using log4j 2.17.1.
There have been tons of bug fixes in `log4j-1.2-api`, especially in
version 2.17.2:
https://logging.apache.org/log4j/2.x/release-notes.html#release-notes-2-17-2
Can you check with the latest
Joan,
On Fri, 26 Jan 2024 at 13:33, wrote:
> Issue fixed. The problem was in the disruptor library, which we also migrated
> from 3.4.4 to 4.0.0. Downgrading again to 3.4.4. fixed the problem.
Thank you for sharing your solution with us. Since nobody was able to
diagnose this problem from your
Hi all,
For Q3-Q4 we plan to introduce native GraalVM support in Log4j Core.
This can be implemented in at least two ways:
* you can have slim binaries with only the Log4j Core components
necessary for your configuration,
* you can have larger binaries, but be able to digest any valid Log4j
Hi Piers,
On Thu, 14 Mar 2024 at 14:08, Piers Uso Walter wrote:
> However, what I was trying to achieve by using a servlet context listener was
> to be able to set the location of the log4j configuration file at run time.
> I’m trying to make the app compatible with different app servers where
Hi Jeff,
On Fri, 15 Mar 2024 at 02:43, wrote:
> Our builds are now ***full*** of deprecation warnings. The IDE shows
> deprecation highlighting everywhere. Also, CI builds i.e. with Sonar evaluate
> use of deprecated API as Code Smells and Quality Gates fail. When SQ quality
> gates fail
Hi Jeff,
On Fri, 15 Mar 2024 at 02:43, wrote:
> One of the great new features of Log4j2 is the lambda lazy logging.
>
> Since we migrated to Log4j2 we have liberally been trying to take advantage
> of this where we can.
>
> In the last few releases though, in preparation for Log4j 3.x the Log4j
Hi Jeff,
On Fri, 15 Mar 2024 at 07:50, wrote:
> Yes the Javadoc did a fine job of explaining the reason for the change and I
> understood it, but there are so many side-effects from deprecating those
> APIs. My question was more of a "why do this in advance?"
The deprecation was introduced
Hi Piers,
On Wed, 13 Mar 2024 at 22:29, Piers Uso Walter wrote:
> 2024-03-13T19:49:02.609143Z Catalina-utility-1 INFO
> Log4jServletContextListener triggered a Log4j context initialization.
>
> Case 2:
> However, if I stop and restart the Tomcat service (with the war file having
> been
Hi Piers,
On Wed, 20 Mar 2024 at 17:09, Piers Uso Walter wrote:
> Am I trying something unusual here when I attempt to make the app decide
> where the log4j configuration file is located?
> Is there any other way in which I can achieve this?
> Is there an API for this?
Sorry for the late
Hi Piers,
On Sun, 31 Mar 2024 at 22:37, Piers Uso Walter wrote:
>
> Thad,
>
>
> Thanks so much. This looks exactly what I want to do.
> But somehow I never got your code to work.
>
> ...
>
> I made these changes to your code:
>
> 1.
> LogListener is now a subclass of Log4jServletContextListener,
Hi Ralph,
On Thu, 4 Apr 2024 at 21:01, Ralph Goers wrote:
> I really have no idea why but this is the first time I have heard someone ask
> for the ability to filter based on the Exception class.
This came out at least once before: see the SO "Log4j - How to log
specific exception into a
Hi Jasmine,
On Thu, 28 Mar 2024 at 12:12, JASMINE DASH wrote:
> Please find the below log4j2.properties file.
>
> rootLogger.level = INFO, STDOUT appender = Console
> appender.console.name = STDOUT
> appender.console.type = Console appender.console.layout.type = PatternLayout
>
>
63 matches
Mail list logo
