Lucene core is a no-dependencies library. Some of the other Lucene
modules, and the build and tests, have dependencies, but none of them
includes log4j. So sorry, but we won't be making Lucene use log4j
2.17.2; probably you should get your compliance standards changed to
include *forb
Categorization: Unclassified
Hi:
What version of log4j is included in Lucene version 8.11.2? The release notes
for Solr 8.11.2 explicitly states log4j version is upgraded to 2.17.2 to
address security vulnerabilities, but there is no such note for Lucene. I
assume the same is true for Lucene
Ok these are good to know.
thanks
From: Uwe Schindler
Sent: Wednesday, December 15, 2021 5:18 PM
To: java-user@lucene.apache.org ; Ali Akhtar
Cc: Baris Kazar
Subject: Re: Log4j
Hi,
It only has an abstract logging interface inside IndexWriter to track actions
schrieb Ali Akhtar :
>Does Lucene not have any internal logging at all, e.g for debugging?
>
>On Thu, Dec 16, 2021 at 2:49 AM Uwe Schindler wrote:
>
>> Hi,
>>
>> Lucene is an API and does not log with log4j.
>>
>> Only the user interface Luke uses log4j, but
Does Lucene not have any internal logging at all, e.g for debugging?
On Thu, Dec 16, 2021 at 2:49 AM Uwe Schindler wrote:
> Hi,
>
> Lucene is an API and does not log with log4j.
>
> Only the user interface Luke uses log4j, but this one does not do any
> networking. So unless u
Hi,
Lucene is an API and does not log with log4j.
Only the user interface Luke uses log4j, but this one does not do any
networking. So unless user of Luke enters jndi expressions nothing can happen. 😂
Uwe
Am 15. Dezember 2021 21:41:37 UTC schrieb Baris Kazar :
>Hi Folks,-
> Lucene
Hi Folks,-
Lucene is not affected by the latest bug, right?
I saw on Solr News page there are some fixes already made to Solr.
Best regards
9:31:49 AM
Subject: log4j error
Since I upgraded to Lucene 2.3, I started to see some error message
coming
from log4j via Lucene. Has any one ever experienced this? Is this
classloading issue?
javax.ejb.EJBException: EJB Exception: :
java.lang.IllegalStateException:
Current state = FLUSHED
Since I upgraded to Lucene 2.3, I started to see some error message coming
from log4j via Lucene. Has any one ever experienced this? Is this
classloading issue?
javax.ejb.EJBException: EJB Exception: : java.lang.IllegalStateException:
Current state = FLUSHED, new state = CODING
at
