Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.18.5
->5.18.6
2.23.1
->2.24.3
2.22.0
->2.24.3
9.5.0
->9.7.0
2.8.2
->2.8.4
0.9.0
->0.9.1
Release Notes
apache/activemq (apache-activemq)
v5.18.6
Compare Source
apache/logging-log4j2 (apache-log4j)
v2.24.3
: 2.24.3Compare Source
Release Notes
This release fixes two minor bugs.
ConcurrentModificationException
, if multiple threads modify loggers concurrently.This bug affects users that modify logger levels programmatically. (#3234)
PropertiesUtil
against property sources that callPropertiesUtil
recursively.In some cases such a property source can even cause deadlocks. (#3252)
v2.24.2
: 2.24.2Compare Source
Release Notes
This release fixes a critical bug in Log4j API initialization code, which can cause
LogManager.getLogger()
to returnnull
under certain conditions. See #3143 for details.Fixed
Logger
s inLoggerRegistry
. (#3143)ArrayIndexOutOfBoundsException
in JSON Template Layout truncated exception resolver (#3216)v2.24.1
: 2.24.1Compare Source
This release contains mainly bug fixes of problems encountered with the thread context map, logger registry and configuration reloading.
It also enhances integration tests to use Docker images of the most recent releases of MongoDB and Elastic Search.
Changed
LoggerRegistry
to make itMessageFactory
-namespaced.This effectively allows loggers of same name, but different message factory. (#2936)
Fixed
putAll()
in the default thread context map implementation (#2942)Updated
org.apache.logging:logging-parent
to version11.3.0
v2.24.0
: 2.24.0Compare Source
The
2.24.0
version of Log4j API has been enhanced with changes from the3.x
branch and will be used by both Log4j 2 Core and Log4j 3 Core releases. The changes include:ThreadContextMap
.Check your configuration for typos.
Documentation
The Apache Log4j 2 website has been almost entirely rewritten to provide improved documentation and faster access to the information you need.
Bridges
The JUL-to-Log4j API and Log4j 1-to-Log4j API bridges will no longer be able to modify the configuration of Log4j Core by default.
If such a functionality is required, it must be explicitly enabled.
Modules
The following Log4j Core additional modules have been removed:
log4j-flume-ng
The module is no longer part of the release process and will follow its own release lifecycle.
Please manage your dependencies using
log4j-bom
to always use its latest version.log4j-kubernetes
The module has been moved to the Fabric8.io Kubernetes project and follows the Fabric8.io release lifecycle.
log4j-mongodb3
The module based on MongoDB Java client version 3.x has been removed.
Please migrate to
log4j-mongodb
(client version 5.x) orlog4j-mongodb4
(client version 4.x).JMX changes
Starting in version 2.24.0, JMX support is disabled by default and can be re-enabled via the
log4j2.disableJmx=false
system property.Added
DefaultThreadContextMap
implementation. (#2330)log4j-slf4j-impl
andlog4j-slf4j2-impl
.Users can enable it by setting the property
log4j2.messageFactory
toorg.apache.logging.slf4j.message.ThrowableConsumingMessageFactory
. (#2363)GcpLayout.json
(#2498)org.apache.logging:logging-parent:11.0.0
Changed
log4j-api
in GraalVM without additional reachability data. (#1539)PropertiesUtil
and fixDuration
parser. (#1936)Provider
class and deprecatelog4j2.loggerContextFactory
property. (#2374)log4j-kubernetes
lookup. User should migrate toio.fabric8:kubernetes-log4j
. (#2412)log4j2.disableJmx
to be set tofalse
to enable JMX support. (#2462)DateTimeFormatter#toString()
withDateTimeFormatter#formatTo(StringBuilder)
to cut down on allocations(#2515)
log4j1.compatibility
isfalse
. (#2778)log4j2.enableThreadLocals
,log4j2.garbagefreeThreadContextMap
andlog4j2.shutdownHookEnabled
over the value of
log4j.isWebapp
. (#2517)log4j2.defaultStatusLevel
property in Log4j Core in favor oflog4j2.statusLoggerLevel
(#2481)Deprecated
Message#getFormat()
due to unclear semantics andinconsistent implementations (#2773)org.apache.logging.log4j.EventLogger
for removal (#2665)org.apache.logging.log4j.core.appender.rolling.action.Duration
class for removal (#2425)log4j-mongodb4
module in favor oflog4j-mongodb
(#2486)Fixed
log4j2.messageFactory
andlog4j2.flowMessageFactory
properties (#2505)PropertiesUtil
(#2414)log4j2.debug
. (#2703)%F
and%file
keys in Pattern Layout (#2781)JsonLayout
failure under JPMS. (#2814)TruncatingBufferedWriter
(#2609)didn't replace the '{}' sequence. The behavior changed in 2.21.0 and should be restored for backward compatibility. (#2380)
ClassCastException
in LMAX Disruptor 3 initialization (#2768)java.management
module when JMX is disabled, which is the default (#2775)Removed
Updated
com.fasterxml.jackson:jackson-bom
to version2.17.2
(#2719)com.github.luben:zstd-jni
to version1.5.6-5
(#2901)commons-codec:commons-codec
to version1.17.1
(#2741)commons-logging:commons-logging
to version1.3.4
(#2864)github/codeql-action
to version3.25.1
(#2483)io.fabric8:docker-maven-plugin
to version0.45.0
(#2776)org.apache.cassandra:cassandra-all
to version3.11.17
(#2479)org.apache.commons:commons-compress
to version1.27.1
(#2869)org.apache.commons:commons-csv
to version1.11.0
(#2565)org.apache.commons:commons-lang3
to version3.17.0
(#2907)org.apache.kafka:kafka-clients
to version3.8.0
(#2777)org.apache.logging:logging-parent
to version11.2.0
org.eclipse.jetty:jetty-bom
to version9.4.55.v20240627
(#2709)org.jctools:jctools-core
to version4.0.5
(#2637)org.mongodb:*
from4.11.1
to4.11.2
(#2409)org.mongodb:bson
to version5.1.3
(#2823)org.slf4j:slf4j-api
to version2.0.16
(#2829)org.springframework:spring-framework-bom
to version5.3.39
(#2840)apache/solr (apache-solr)
v9.7.0
Compare Source
v9.6.1
Compare Source
v9.6.0
Compare Source
composer/composer (custom-composer)
v2.8.4
Compare Source
audit
command not being meaningful (now 1 for vulnerabilities and 2 for abandoned, 3 for both) (#12203)bump-after-update
failing when using inline constraints (#12223)create-project
command to now disable symlinking when used with a path repo as argument (#12222)validate --no-check-publish
to hide publish errors entirely as they are irrelevant (#12196)audit
command returning a failing code when composer audit fails as this should not trigger build failures, but running audit as standard part of your build is probably a terrible idea anyway (#12196)v2.8.3
Compare Source
dbmdz/solr-ocrhighlighting (solr-ocrhighlighting)
v0.9.1
: : Solr 9.7 compatibility, fixesCompare Source
Changed
two, this is in preparation for the S3 storage backend, where we don't have the luxury
of relying on a page cache to paper over our inefficencies.
Fixed
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.