hd42 commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2167250756
Adding log4j-to-slf4j has fixed my problem as far as I can see. Thank you
for your help.
An indefinite wait still seems problematic to me, so maybe you should throw
an "N
github-actions[bot] closed pull request #149: Bump
org.springframework:spring-framework-bom from 5.3.35 to 5.3.37
URL: https://github.com/apache/logging-log4j-samples/pull/149
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
rgoers commented on issue #2661:
URL:
https://github.com/apache/logging-log4j2/issues/2661#issuecomment-2166934448
Note that using append="false" on a FileAppender where the same file is
already open on another FileAppender would likely cause serious problems on
Windows if each FileAppende
github-actions[bot] merged PR #34:
URL: https://github.com/apache/logging-log4j-jakarta/pull/34
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifica
grobmeier commented on issue #2540:
URL:
https://github.com/apache/logging-log4j2/issues/2540#issuecomment-2166779765
completed
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comme
grobmeier closed issue #2540: [MS16] Documentation revamp 3/5
URL: https://github.com/apache/logging-log4j2/issues/2540
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsub
ppkarwasz merged PR #2654:
URL: https://github.com/apache/logging-log4j2/pull/2654
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubsc
FreeAndNil merged PR #150:
URL: https://github.com/apache/logging-log4net/pull/150
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubsc
hd42 commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2165775612
Adding log4j-to-slf4j has fixed my problem as far as I can see. Thank you
for your help.
An indefinite wait still seems problematic to me, so maybe you should throw
an "N
taylorThunderbolt opened a new issue, #2661:
URL: https://github.com/apache/logging-log4j2/issues/2661
## Description
Use new FileAppender(the `append` option is set to false, the 'fileName'
option is equivalent to previous FileAppender) to log rest messages after
logging some messag
ppkarwasz opened a new pull request, #2660:
URL: https://github.com/apache/logging-log4j2/pull/2660
Since the Log4j API is independent from the Log4j implementation, the "API"
chapter of the documentation should contain configuration examples for all
major backends that support a certain AP
ppkarwasz commented on PR #2659:
URL: https://github.com/apache/logging-log4j2/pull/2659#issuecomment-2165289271
Part of #2541
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific commen
ppkarwasz commented on PR #2658:
URL: https://github.com/apache/logging-log4j2/pull/2658#issuecomment-2165288746
Part of #2541
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific commen
ppkarwasz opened a new pull request, #2659:
URL: https://github.com/apache/logging-log4j2/pull/2659
This splits the configuration page into:
- a short intro to the "Configuration" chapter,
- a page dedicated entirely to the "Configuration file".
This is the `main` branch vers
github-actions[bot] closed pull request #190: Bump
org.eclipse.jgit:org.eclipse.jgit from 6.9.0.202403050737-r to
6.10.0.202406032230-r
URL: https://github.com/apache/logging-parent/pull/190
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
github-actions[bot] merged PR #192:
URL: https://github.com/apache/logging-parent/pull/192
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications
github-actions[bot] merged PR #50:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/50
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: not
github-actions[bot] merged PR #50:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/50
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: not
dependabot[bot] opened a new pull request, #50:
URL: https://github.com/apache/logging-log4j-audit-sample/pull/50
Bumps
[org.springframework:spring-framework-bom](https://github.com/spring-projects/spring-framework)
from 5.3.36 to 5.3.37.
Release notes
Sourced from https://github.
hd42 commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2165408230
I debugged a working installation and was surprised to see that it didn't
ever call Activator#start. The first call was to ProviderUtil#lazyInit(), which
unlocks even with empty
ppkarwasz commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2165386233
`log4j-core`, `log4j-to-slf4j` and `log4j-to-jul` are Log4j API providers.
There is a simple provider embedded in `log4j-api`, but typically that is
not what you want
hd42 commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2165370953
I see Activator#start gets called but doesn't find any bundle that contains
a provider. I don't see log4j-core installed in the plugins.
log4j seems to block itself from worki
ppkarwasz commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2165330248
This seems related to the order of activation of the OSGi bundles: the
`LogManager` class initialization will block until the `log4j-core` bundle is
started. Log4j does not
github-actions[bot] merged PR #2657:
URL: https://github.com/apache/logging-log4j2/pull/2657
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notificatio
github-actions[bot] merged PR #2656:
URL: https://github.com/apache/logging-log4j2/pull/2656
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notificatio
ppkarwasz opened a new pull request, #2658:
URL: https://github.com/apache/logging-log4j2/pull/2658
This splits the configuration page into:
- a short intro to the "Configuration" chapter,
- a page dedicated entirely to the "Configuration file".
--
This is an automated me
github-actions[bot] merged PR #191:
URL: https://github.com/apache/logging-parent/pull/191
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications
hd42 commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2165262893
As far as I can see, org.apache.logging.log4j.util.Activator#unlockIfReady()
is called a lot but never enters the if block because ProviderUtil.PROVIDERS
remains empty.
--
Th
hd42 commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2165119846
Yes, I am developing an Eclipse Plugin, so the OSGi framework is the one
bundled with Eclipse 2024-03.
--
This is an automated message from the Apache Git Service.
To respond
ppkarwasz commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2165020842
@hd42,
What kind of application are you developing? It seems you are writing an RCP
or an OSGi application?
If so, what kind and version of OSGi framework you are
hd42 commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2164920254
[threaddump2.txt](https://github.com/user-attachments/files/15815945/threaddump2.txt)
Yes, that's what I figured. I'll try to attach a debugger and see when the
initializatio
vy commented on issue #2655:
URL:
https://github.com/apache/logging-log4j2/issues/2655#issuecomment-2164769945
@hd42, this sounds like a deadlock to me. That is, `ProviderUtil` is trying
to acquire the initialization lock that is already acquired. We can improve the
diagnostics by reportin
32 matches
Mail list logo
