All,

A few updates to this thread.  After some additional testing, we've 
discovered that upgrading to log4j version 2.25.1 *does solve the logging 
issues*.   (The prior mentioned fix of downgrading to version 2.24.3 also 
works -- either is perfectly OK to patch the issue)

If you want to upgrade to log4j 2.25.1, the fix is the small one-line 
change in this PR: https://github.com/DSpace/DSpace/pull/11028   

Simply update your root "pom.xml" to have:
<log4j.version>2.25.1</log4j.version>

After that change, you'd have to rebuild the DSpace backend (mvn -U clean 
package) and reinstall (ant update).

I've also updated the 7.6.4 Release Notes to include a warning about this 
log4j 
issue: 
https://wiki.lyrasis.org/display/DSDOC7x/Release+Notes#ReleaseNotes-7.6.4ReleaseNotes

We are also working on a very quick DSpace 7.6.5 release to fix this 
issue.  I think this should be out either today or tomorrow. 7.6.5 will be 
a very small release which only includes a few dependency updates 
(including this very important log4j one). So it will be a simple upgrade 
for anyone running 7.6.4.

Tim

On Tuesday, July 22, 2025 at 1:26:17 AM UTC-5 [email protected] wrote:

> Hi,
>
> This is what I did and it actually works as expected. Thank you all for 
> your help.
>
> Regards,
> Mariusz
>
> poniedziałek, 21 lipca 2025 o 18:18:44 UTC+2 DSpace Technical Support 
> napisał(a):
>
>> Hi Mariusz,
>>
>> Since it appears log4j 2.25.x is being problematic, I'd recommend anyone 
>> impacted currently *downgrade* to log4j 2.24.3.
>>
>> It should be possible to do so by just updating your root "pom.xml" to 
>> have:
>> <log4j.version>2.24.3</log4j.version>
>>
>> After that change, you'd have to rebuild the DSpace backend (mvn -U clean 
>> package) and reinstall (ant update).
>>
>> I'm not yet sure what could have changed in log4j to cause this.  We've 
>> never hit this sort of incompatibility in a log4j minor release before.  
>> I'm also hoping we can find a way to detect in automated tests whether 
>> logging is working (to avoid this occurring again in the future).
>>
>> Tim
>> On Monday, July 21, 2025 at 1:02:30 AM UTC-5 [email protected] wrote:
>>
>>> So we have a problem with log4j. Just what next since upgrading to 
>>> 2.25.1 as Sean checked doesn't solve the problem?
>>>
>>> Regards,
>>> Mariusz
>>>
>>> piątek, 18 lipca 2025 o 19:29:38 UTC+2 Brian Keese napisał(a):
>>>
>>>> I just commented on the ticket. There was a version bump of log4j that 
>>>> broke tomcat logging but not CLI logging.
>>>>
>>>> https://github.com/DSpace/DSpace/commit/230bf80b5fcde55a2abdf916c282c3439e49654b
>>>>
>>>>
>>>> On Friday, July 18, 2025 at 12:10:36 PM UTC-5 Brian Keese wrote:
>>>>
>>>>> Me too. I am running a fork of the dspace-7_x branch that I made a 
>>>>> week ago or so. 
>>>>> Last commit was 
>>>>> https://github.com/DSpace/DSpace/commit/a9546055f4d0aa2d91dc545e97d559c989744dae
>>>>>
>>>>> -Brian
>>>>>
>>>>>
>>>>> On Friday, July 18, 2025 at 11:17:20 AM UTC-5 Sean Carte wrote:
>>>>>
>>>>>> Hi Tim
>>>>>>
>>>>>> I created a ticket: https://github.com/DSpace/DSpace/issues/11046
>>>>>>
>>>>>> Seems strange that it's just the two of us though.
>>>>>>
>>>>>> Sean
>>>>>>
>>>>>> On Fri, 18 Jul 2025 at 16:00, DSpace Technical Support <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Hi Mariusz or Sean,
>>>>>>>
>>>>>>> Could one of you create a bug ticket in 
>>>>>>> https://github.com/DSpace/DSpace/issues and also let us know what 
>>>>>>> version you are upgrading from?  That way I can try and locate a 
>>>>>>> volunteer 
>>>>>>> to investigate what may be going on.  I'm not recalling any logging 
>>>>>>> changes 
>>>>>>> that occurred in 7.6.4 (but maybe something had a side effect).  
>>>>>>>  Obviously, though, in 7.6.3 we did update the log4j configuration to 
>>>>>>> add 
>>>>>>> the new "dspace-cli.log" file. 
>>>>>>>
>>>>>>> If you can provide us with any more details in the bug ticket, that 
>>>>>>> might help someone to track down the issue more quickly.
>>>>>>>
>>>>>>> Tim
>>>>>>>
>>>>>>> On Friday, July 18, 2025 at 6:40:24 AM UTC-5 [email protected] wrote:
>>>>>>>
>>>>>>>> Then I’m not alone with this issue. Thanks for the information.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Mariusz
>>>>>>>>
>>>>>>>> piątek, 18 lipca 2025 o 13:34:14 UTC+2 Sean Carte napisał(a):
>>>>>>>>
>>>>>>>>> Yes, here too.
>>>>>>>>>
>>>>>>>>> I just checked and I have loglevel.dspace set to INFO in 
>>>>>>>>> config/log4j2.xml but it looks like only WARN-level messages are 
>>>>>>>>> being 
>>>>>>>>> logged.
>>>>>>>>>
>>>>>>>>> Sean
>>>>>>>>>
>>>>>>>>> On Fri, 18 Jul 2025 at 13:27, Technologiczny Informator <
>>>>>>>>> [email protected]> wrote:
>>>>>>>>>
>>>>>>>>>> Hi everyone,
>>>>>>>>>>
>>>>>>>>>> Has anyone already tried upgrading their DSpace to version 7.6.4?
>>>>>>>>>> I did it on my test instance and unfortunately I noticed that 
>>>>>>>>>> there are no entries in the dspace.log file.
>>>>>>>>>> However, dspace-cli.log works normally.
>>>>>>>>>> Has anyone encountered this issue?
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>> Mariusz
>>>>>>>>>>
>>>>>>>>>> -- 
>>>>>>>>>> All messages to this mailing list should adhere to the Code of 
>>>>>>>>>> Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>>>>>>>>>> --- 
>>>>>>>>>> You received this message because you are subscribed to the 
>>>>>>>>>> Google Groups "DSpace Technical Support" group.
>>>>>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>>>>>> send an email to [email protected].
>>>>>>>>>> To view this discussion visit 
>>>>>>>>>> https://groups.google.com/d/msgid/dspace-tech/eb5d064a-50bc-46b4-90ef-4d10b9d07cd0n%40googlegroups.com
>>>>>>>>>>  
>>>>>>>>>> <https://groups.google.com/d/msgid/dspace-tech/eb5d064a-50bc-46b4-90ef-4d10b9d07cd0n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>>>> .
>>>>>>>>>>
>>>>>>>>> -- 
>>>>>>> All messages to this mailing list should adhere to the Code of 
>>>>>>> Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>>>>>>> --- 
>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>> Groups "DSpace Technical Support" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>>> send an email to [email protected].
>>>>>>>
>>>>>> To view this discussion visit 
>>>>>>> https://groups.google.com/d/msgid/dspace-tech/574677fb-88b3-4728-b6b5-b13e9fafc40fn%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/dspace-tech/574677fb-88b3-4728-b6b5-b13e9fafc40fn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>>
>>>>>>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/dspace-tech/f620175e-d05a-4e0b-93ef-af492bc68b0cn%40googlegroups.com.

Reply via email to