we upgraded the log4j jars from 2.16.0 to 2.17.2. This should fix the
problem. This change will be available with the next iSphere version.
Von: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von David
Gesendet: Montag, 23. Mai 2022 18:57
An: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Betreff: Re: [WDSCI-L] System scan reporting log4j in iSphere
Our firewalls block the install/update of that iSphere component completely
because of log4j -- so we have to uncheck it when doing updates.
---- On Mon, 23 May 2022 09:06:39 -0700 Matt Qualls
<mqualls@xxxxxxxxxxxxxxx> wrote ----
I have uninstalled iSphere Tn5250 and manually deleted the jars. Has anyone
else had the same findings?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.