<p data-start=”0″ data-end=”200″>We have applied the Cloverleaf 2022.09.04 patch in our build and test environments on RHEL, and so far the results are satisfactory. We are planning to apply the same patch in production this weekend.</p>
<p data-start=”202″ data-end=”343″>We have not observed any significant functional changes, apart from the resolution of a few vulnerabilities reported by our IT Security team.</p>
<p data-start=”345″ data-end=”434″ data-is-last-node=”” data-is-only-node=””>We had also reported the below issue to Infor and have received the recommended solution.</p>
Issue: Xlates fail to open in the IDE, throwing a <code>NoSuchMethodError</code> related to <code>jackson-core</code> (missing <code>releaseToPool()</code> method). Initial findings suggest multiple conflicting Jackson library versions in the environment.
Solution provided by Infor:
We must use jackson-core version 2.19.4 and remove earlier versions from both client and server. Please see below:
./server/tomcat/cloverapps/clapi/WEB-INF/lib/jackson-core-2.19.4.jar -> KEEP
./CAA/ws/lib/GJDWS_lib/jackson-core-2.14.0.jar -> REMOVE
./CAA/ws/lib/GJDWS_lib/jackson-core-2.19.4.jar -> KEEP
./CAA/datafabric/lib/CAADataFabric_lib/jackson-core-2.16.2.jar -> REMOVE
./CAA/datafabric/lib/CAADataFabric_lib/jackson-core-2.20.1.jar -> KEEP
./clgui/lib/jackson-core-2.19.4.jar -> KEEP
./clgui/lib/ext/caawsggc_lib/jackson-core-2.19.4.jar -> KEEP
./clgui/lib/ext/caawsggc_lib/jackson-core-2.14.0.jar -> REMOVE
I’d be curious as to your experience on how far behind you stay in terms of Cloverleaf and server updates. We’re currently on RHEL 8.10 on CIS2022.09.03. We should have really updated to RHEL 9 but it was “too soon” when we started this migration to Cloverleaf. now that we’re done we’re looking at the upgrades, and I was looking at possibly staying one patch behind in Cloverleaf, and we’d stay current with RHEL.
We’re kind of stuck as our network security team is on top of a lot of stuff, and we’re already getting side-eyed with RHEL 8.0. This also applies to some of the cryptos that Cloverleaf uses (and tends to be behind on).
Hi Jason, We were running 9.1 with 2022.09.03 and everything was running great. Then the server admin applied ‘patches’ that brought the engine up to RHEL 9.7. It has been an absolute living hell since then. The server admin says 9.7 can’t be backed out so we trying to avoid a server rebuilt and hoping that 2022.09.04, being one minor version from certified, will be more stable.
The biggest issue we are seeing is hcienginestop does not work. Migrating to hcienginerestart has helped but there is still massive instability.
This is a rely from Infor I got a couple weeks ago:
Based on KB2282305, RHEL 9.1 is the latest authorized version for Cloverleaf 2022.09.03. For Cloverleaf 2022.09.04, the authorized version is RHEL 9.6. For more information, please refer to the attached KB article.
That’s interesting. We’re on 8.10, looking to go to 2025, then jump to 10, we’ll have to double-verify we’re on a certified version when we go. However, we’ll be rebuilding from scratch when we go to 10 so it will be a full upgrade. Got some considerations with HA pairs, but that’s a different story. .
.
.