You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
异常信息如下:
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class org.apache.logging.log4j.util.PropertiesUtil
at org.apache.logging.log4j.status.StatusLogger.(StatusLogger.java:71)
at org.apache.logging.log4j.LogManager.(LogManager.java:60)
at org.apache.commons.logging.LogFactory$Log4jLog.(LogFactory.java:199)
at org.apache.commons.logging.LogFactory$Log4jDelegate.createLog(LogFactory.java:166)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:109)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:99)
at org.springframework.boot.SpringApplication.(SpringApplication.java:198)
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Yes I am willing to submit a pull request on my own!
The text was updated successfully, but these errors were encountered:
Search before asking
AREX Test Service
AREX Java Agent (arextest/arex-agent-java)
Current Behavior
Springboot项目启动
不加载arex-agent启动正常
加载agent:0.4.4启动正常
加载agent:0.4.6启动异常
项目依赖信息如下:
Expected Behavior
不产生异常
Steps To Reproduce
异常信息如下:
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class org.apache.logging.log4j.util.PropertiesUtil
at org.apache.logging.log4j.status.StatusLogger.(StatusLogger.java:71)
at org.apache.logging.log4j.LogManager.(LogManager.java:60)
at org.apache.commons.logging.LogFactory$Log4jLog.(LogFactory.java:199)
at org.apache.commons.logging.LogFactory$Log4jDelegate.createLog(LogFactory.java:166)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:109)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:99)
at org.springframework.boot.SpringApplication.(SpringApplication.java:198)
Anything else
No response
Are you willing to submit a pull request to fix on your own?
The text was updated successfully, but these errors were encountered: