This update for log4j fixes the following issue:
{
"binaries": [
{
"log4j-slf4j": "2.16.0-4.10.1",
"log4j-javadoc": "2.16.0-4.10.1",
"disruptor-javadoc": "3.4.4-3.3.1",
"jakarta-servlet": "5.0.0-5.3.1",
"log4j-jcl": "2.16.0-4.10.1",
"log4j": "2.16.0-4.10.1",
"jakarta-servlet-javadoc": "5.0.0-5.3.1",
"disruptor": "3.4.4-3.3.1"
}
]
}
{
"binaries": [
{
"log4j-slf4j": "2.16.0-4.10.1",
"log4j-javadoc": "2.16.0-4.10.1",
"disruptor-javadoc": "3.4.4-3.3.1",
"jakarta-servlet": "5.0.0-5.3.1",
"log4j-jcl": "2.16.0-4.10.1",
"log4j": "2.16.0-4.10.1",
"jakarta-servlet-javadoc": "5.0.0-5.3.1",
"disruptor": "3.4.4-3.3.1"
}
]
}
{
"binaries": [
{
"log4j-slf4j": "2.16.0-4.10.1",
"log4j-javadoc": "2.16.0-4.10.1",
"disruptor-javadoc": "3.4.4-3.3.1",
"jakarta-servlet": "5.0.0-5.3.1",
"log4j-jcl": "2.16.0-4.10.1",
"log4j": "2.16.0-4.10.1",
"jakarta-servlet-javadoc": "5.0.0-5.3.1",
"disruptor": "3.4.4-3.3.1"
}
]
}