New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
运行example 报告无法找到日志类: org.apache.logging.log4j.core.Logger #145
Comments
db.num=2 |
独立模式或群集模式 你能提供更多信息吗? standalone mode or cluster mode can you provide more info? |
默认模式 我直接拉master的代码 exmaple跑一下就error就报错了 怀疑是依赖问题 但是不知道为什么 。 |
loss log impl , i fix it. thx! |
* feature: add namespace api * feat: add configuration history api * retranslation history configuration api description * update history configuration api description
我试着使用现在的版本尝试跑一下 example 下的configexample 得到了如下报错 :
Tue Oct 23 19:22:54 CST 2018 sun.misc.Launcher$AppClassLoader@18b4aac2 JM.Log:WARN Init JM logger with NopLoggerFactory, pay attention. sun.misc.Launcher$AppClassLoader@18b4aac2
java.lang.ClassNotFoundException: org.apache.logging.log4j.core.Logger
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at com.alibaba.nacos.client.logger.log4j2.Log4j2LoggerFactory.(Log4j2LoggerFactory.java:33)
at com.alibaba.nacos.client.logger.LoggerFactory.(LoggerFactory.java:59)
at com.alibaba.nacos.client.config.utils.LogUtils.(LogUtils.java:50)
at com.alibaba.nacos.client.config.NacosConfigService.(NacosConfigService.java:53)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at com.alibaba.nacos.api.config.ConfigFactory.createConfigService(ConfigFactory.java:43)
at com.alibaba.nacos.api.NacosFactory.createConfigService(NacosFactory.java:44)
at com.alibaba.nacos.example.ConfigExample.main(ConfigExample.java:40)
似乎与依赖有关系 - -..........
The text was updated successfully, but these errors were encountered: