Exceptions when using version 2.20.0 in Eclipse 2022-12 RCP application #1367
Labels
bug
Incorrect, unexpected, or unintended behavior of existing code
Comments
|
I believe this is fixed in Gary's most recent commit. Can you check the As for the reason why the lookup fails, we'll need to investigate further. Can you check if modifying the start level of |
ppkarwasz
added
the
bug
|
Hi @ppkarwasz ! Thanks for a quick response! https://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/ I will see if I can try out modifying the start levels. We are using Fragment-Host to extend both api and core. |
|
Setting start level 2 on the log4j plug-ins actually removed the exceptions! But.. if this requirement can be removed in the upcoming version we would be glad :). We never had to have any start levels set for logging before at all. |
It seems Github Actions stopped publishing snapshots, I'll have to look into it. |
|
I tried with the latest SNAPSHOTS of api/core/slf4j-impl but I see the same problem: |
|
@ppkarwasz @selundqma I'm running into the same issue, it works for me when I set |
N1k145
pushed a commit
to N1k145/logging-log4j2
that referenced
this issue
Apr 13, 2023
N1k145
added a commit
to N1k145/logging-log4j2
that referenced
this issue
Apr 13, 2023
|
I am very grateful for your fix commit! Let us hope it gets accepted and merged soon :). Thanks!!! |
N1k145
added a commit
to N1k145/logging-log4j2
that referenced
this issue
Jul 6, 2023
N1k145
added a commit
to N1k145/logging-log4j2
that referenced
this issue
Jul 6, 2023
ppkarwasz
pushed a commit
to N1k145/logging-log4j2
that referenced
this issue
Jul 7, 2023
ppkarwasz
pushed a commit
that referenced
this issue
Jul 7, 2023
jvz
pushed a commit
to jvz/logging-log4j2
that referenced
this issue
Sep 1, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We have an Eclipse RCP application where we use Log4J 2 (with SLF4J 1.7.36) to do all the logging. Logging using the following dependencies works fine:
But.. when we update the dependencies to 2.20.0, we get a log list of exceptions. I think I have tracked down the difference in behavior to the ServiceLoaderUtil class:
...
if (OsgiServiceLocator.isAvailable()) {
services = Stream.concat(services, OsgiServiceLocator.loadServices(serviceType, lookup, verbose));
}
...
In 2.19.0 the OsgiServiceLocator.isAvailable() returns false, but with 2.20.0 it returns true and executes the row below the check. Here the exceptions are logged in the try/catch clauses.
Configuration
Version: 2.20.0
Operating system: Windows Enterprise 10.0.19044
JDK: JDK 17.0.6.10.1
Logs
The text was updated successfully, but these errors were encountered: