Error after Jira DC 9.10.1 upgrade and eazyBI 7.0.1

Questions & Answers
1

Testing upgrade of Jira DC to 9.10.1 (which has completed without issue). However, after upgrading to eazyBI 7.0.1, attempting to navigate to the eazyBI app throws an error

a].[localhost].[/]] ERROR: initialization failed
org.jruby.rack.RackInitializationException: cannot link Java class com.eazybi.mondrian.aggregator.NoneAggregator (java.lang.NoClassDefFoundError: Could not initialize class org.apache.logging.log4j.core.config.LoggerConfig)
from org/jruby/javasupport/JavaPackage.java:253:in method_missing' from /var/atlassian/application-data/jira/plugins/.osgi-plugins/felix/felix-cache/bundle316/version0.0/plugin.9873687496211588711.eazybi-jira-7.0.1_1692043699091.jar-lib/0/META-INF/rails.root/vendor/gems/eazy_cube/lib/eazy_cube.class:38:in register_custom_aggregators’
from /var/atlassian/application-data/jira/plugins/.osgi-plugins/felix/felix-cache/bundle316/version0.0/plugin.9873687496211588711.eazybi-jira-7.0.1_1692043699091.jar-lib/0/META-INF/rails.root/vendor/gems/eazybi/config/initializers/mondrian.class:56:in <main>' from org/jruby/RubyKernel.java:1059:in load’

Caused by: org.jruby.exceptions.NameError: (NameError) cannot link Java class com.eazybi.mondrian.aggregator.NoneAggregator (java.lang.NoClassDefFoundError: Could not initialize class org.apache.logging.log4j.core.config.LoggerConfig)
at org.jruby.javasupport.JavaPackage.method_missing(org/jruby/javasupport/JavaPackage.java:253)
at RUBY.register_custom_aggregators(/var/atlassian/application-data/jira/plugins/.osgi-plugins/felix/felix-cache/bundle316/version0.0/plugin.9873687496211588711.eazybi-jira-7.0.1_1692043699091.jar-lib/0/META-INF/rails.root/vendor/gems/eazy_cube/lib/eazy_cube.class:38)

Have already reached out to support.
Have disabled, cleared caches, uninstalled, reinstalled 6.6.0, reupgraded to 7.0.1, and everything in between.
Deployed new nodes to my test environment, building local home directory after removing the hidden plugin caches.

Wondering if anyone else has experienced this. Sort of looks like an issue with log4j which I know was updated for jira 9.x somewhere.

Running on openjdk 17

TYIA

2

An update to the issue if anyone faces a similar issue - the error was related to the Datadog Java agent.
The Datadog engineers have found the issue and could release a fixed version soon.
Meanwhile, there is a workaround - to use an additional parameter -Ddd.trace.classloaders.exclude=org.jruby.util.JRubyClassLoader
( DD_TRACE_CLASSLOADERS_EXCLUDE=org.jruby.util.JRubyClassLoader as an environment variable). This will exclude the class-loader org.jruby.util.JRubyClassLoader from the Datadog monitoring.