Log4j 1.x and Log4j 2 are completely different code bases. They have very
little in common. I’m not even sure Log4j 1 had any support for JMX.
Ralph
> On Apr 29, 2020, at 7:33 AM, EDMONDO SENA wrote:
>
> Matt, last question:
>
> Before for log4j 1 the JMX wasn't enabled for default?
>
>
>
I don't know anything about log4j1 as I haven't used that for several
years, sorry.
On Wed, 29 Apr 2020 at 09:33, EDMONDO SENA wrote:
>
> Matt, last question:
>
> Before for log4j 1 the JMX wasn't enabled for default?
>
>
>
> On 2020/04/29 14:30:12, Matt Sicker wrote:
> > Yes, I mean the system
Matt, last question:
Before for log4j 1 the JMX wasn't enabled for default?
On 2020/04/29 14:30:12, Matt Sicker wrote:
> Yes, I mean the system property. I don't know much about PowerMock,
> though I never mock loggers.
>
> On Wed, 29 Apr 2020 at 08:52, EDMONDO SENA wrote:
> >
> > Hi Matt,
Yes, I mean the system property. I don't know much about PowerMock,
though I never mock loggers.
On Wed, 29 Apr 2020 at 08:52, EDMONDO SENA wrote:
>
> Hi Matt,
>
> We've 100 files to change.
> So, in order to speed solution is it disable JMX in log4j2?
> You mean log4j2.disable.jmx=true?
> You th
Hi Matt,
We've 100 files to change.
So, in order to speed solution is it disable JMX in log4j2?
You mean log4j2.disable.jmx=true?
You think that use @PowerMockIgnore("Javax.management.* ") is useless?
On 2020/04/29 13:42:02, Matt Sicker wrote:
> Sounds like you’ll need to configure PowerMock
Also, if you’re trying to mock log4j2 in tests, you can always use the
LoggerContextRule from our test libraries to configure logging at the test
level.
On Wed, Apr 29, 2020 at 08:42 Matt Sicker wrote:
> Sounds like you’ll need to configure PowerMock to ignore the log4j2 JMX
> classes. There’s a
Sounds like you’ll need to configure PowerMock to ignore the log4j2 JMX
classes. There’s also a system property in log4j2 to disable JMX which is
worth a try.
On Wed, Apr 29, 2020 at 08:34 EDMONDO SENA wrote:
> I repeat, we've done some tests and with java 11, Junit 4 and Log4j 1
> everything ha
I repeat, we've done some tests and with java 11, Junit 4 and Log4j 1
everything has worked well.
The only difference is log4j -> log4j 2.13 and we've this problem.
Can you suggest us what's the workaround?
Kind regards.
On 2020/04/29 13:32:17, EDMONDO SENA wrote:
> Matt sorry,
>
> I need a
Matt sorry,
I need a solution!
Before we were Java 8, and Log4j and everything has worked!
Well, now we've java 11 and Log4j 2.
How can we fix it?
Have you any suggest?
On 2020/04/29 13:29:04, Matt Sicker wrote:
> The JMX module isn’t fully compatible with Java 11 as far as I can tell. It
>
The JMX module isn’t fully compatible with Java 11 as far as I can tell. It
doesn’t even compile above 8.
On Wed, Apr 29, 2020 at 07:17 EDMONDO SENA wrote:
> In API Document is reported this phrase:
>
> Enabling JMX
> JMX support is enabled by default. When Log4j initializes, the
> StatusLogger,
In API Document is reported this phrase:
Enabling JMX
JMX support is enabled by default. When Log4j initializes, the StatusLogger,
ContextSelector, and all LoggerContexts, LoggerConfigs and Appenders are
instrumented with MBeans. To disable JMX completely, and prevent these MBeans
from being cr
Any question?
I'm using Log4j 2.13.0...
https://stackanswers.net/questions/powermock-after-log4j2-3-upgrade-could-not-reconfigure-jmx-java-lang-linkageerror
On 2020/04/29 11:55:32, EDMONDO SENA wrote:
> Sorry, we're using Java 11, Junit 4 e Log4j 2!
>
>
> On 2020/04/29 11:49:03, EDMOND
Sorry, we're using Java 11, Junit 4 e Log4j 2!
On 2020/04/29 11:49:03, EDMONDO SENA wrote:
> No It is not so!
>
> PowerMock with java 11 and Log4j old version (1), everything was working.
> Adding Log4j 2 We've that problem...
>
>
>
> On 2020/04/29 11:33:24, Benjamin Asbach wrote:
> > Hel
No It is not so!
PowerMock with java 11 and Log4j old version (1), everything was working.
Adding Log4j 2 We've that problem...
Il giorno mer 29 apr 2020 alle ore 13:33 Benjamin Asbach <
contact-...@impl.it> ha scritto:
> Hello Edmondo,
>
> I don't think this is an log4j related issue.
>
> You
No It is not so!
PowerMock with java 11 and Log4j old version (1), everything was working.
Adding Log4j 2 We've that problem...
On 2020/04/29 11:33:24, Benjamin Asbach wrote:
> Hello Edmondo,
>
> I don't think this is an log4j related issue.
>
> You're using Powermock in combination with JU
Hello Edmondo,
I don't think this is an log4j related issue.
You're using Powermock in combination with JUnit 5 which currently is
not supported [1]. There's some kind of workaround [2] you might try
that out.
Greetings
Benjamin
[1] https://github.com/powermock/powermock/issues/830
[2]
htt
16 matches
Mail list logo
