2019-06-26 22:19:57.408642475 java.lang.IllegalArgumentException: LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementation (class org.owasp.dependencycheck.maven.slf4j.MavenLoggerFactory loaded from jar:file:/home/admin/samaritan/libs/dependency-check-maven-1.4.3.jar!/). If you are using WebLogic you will need to add 'org.slf4j' to prefer-application-packages in WEB-INF/weblogic.xml: org.owasp.dependencycheck.maven.slf4j.MavenLoggerFactory

2019-06-26 22:19:57.408701383 	at org.springframework.util.Assert.instanceCheckFailed(Assert.java:637)

2019-06-26 22:19:57.408712505 	at org.springframework.util.Assert.isInstanceOf(Assert.java:537)

2019-06-26 22:19:57.408744865 	at org.springframework.boot.logging.logback.LogbackLoggingSystem.getLoggerContext(LogbackLoggingSystem.java:274)

2019-06-26 22:19:57.408753781 	at org.springframework.boot.logging.logback.LogbackLoggingSystem.beforeInitialize(LogbackLoggingSystem.java:99)

2019-06-26 22:19:57.408809318 	at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationStartingEvent(LoggingApplicationListener.java:191)

2019-06-26 22:19:57.408845346 	at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:170)

2019-06-26 22:19:57.408859094 	at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)

2019-06-26 22:19:57.408868002 	at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)

2019-06-26 22:19:57.408877348 	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)

2019-06-26 22:19:57.408923926 	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)

2019-06-26 22:19:57.408936068 	at org.springframework.boot.context.event.EventPublishingRunListener.starting(EventPublishingRunListener.java:68)

2019-06-26 22:19:57.408946296 	at org.springframework.boot.SpringApplicationRunListeners.starting(SpringApplicationRunListeners.java:48)

2019-06-26 22:19:57.408981384 	at org.springframework.boot.SpringApplication.run(SpringApplication.java:313)

2019-06-26 22:19:57.409035943 	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1246)

2019-06-26 22:19:57.409047754 	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1234)

2019-06-26 22:19:57.409076731 	at cn.fraudmetrix.samaritan.AppMain.main(AppMain.java:132)

2019-06-26 22:19:57.409085632 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

2019-06-26 22:19:57.409148074 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

2019-06-26 22:19:57.409170711 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

2019-06-26 22:19:57.409186039 	at java.lang.reflect.Method.invoke(Method.java:498)

2019-06-26 22:19:57.409200844 	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)

2019-06-26 22:19:57.409213367 	at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)

2019-06-26 22:19:57.409228141 	at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)

2019-06-26 22:19:57.409275075 	at org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:587)

2019-06-26 22:19:57.409392972 Exception in thread "main" java.lang.reflect.InvocationTargetException

2019-06-26 22:19:57.409511976 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

2019-06-26 22:19:57.409539209 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

0001-01-01 08:00:00.000000000 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

2019-06-26 22:19:57.409599381 	at java.lang.reflect.Method.invoke(Method.java:498)

2019-06-26 22:19:57.409612149 	at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)

2019-06-26 22:19:57.409625139 	at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)

2019-06-26 22:19:57.409638204 	at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)

0001-01-01 08:00:00.000000000 	at org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:587)

2019-06-26 22:19:57.409742319 Caused by: java.lang.IllegalArgumentException: LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementation (class org.owasp.dependencycheck.maven.slf4j.MavenLoggerFactory loaded from jar:file:/home/admin/samaritan/libs/dependency-check-maven-1.4.3.jar!/). If you are using WebLogic you will need to add 'org.slf4j' to prefer-application-packages in WEB-INF/weblogic.xml: org.owasp.dependencycheck.maven.slf4j.MavenLoggerFactory

2019-06-26 22:19:57.409758932 	at org.springframework.util.Assert.instanceCheckFailed(Assert.java:637)

2019-06-26 22:19:57.409766766 	at org.springframework.util.Assert.isInstanceOf(Assert.java:537)

2019-06-26 22:19:57.409783572 	at org.springframework.boot.logging.logback.LogbackLoggingSystem.getLoggerContext(LogbackLoggingSystem.java:274)

2019-06-26 22:19:57.409805326 	at org.springframework.boot.logging.logback.LogbackLoggingSystem.beforeInitialize(LogbackLoggingSystem.java:99)

2019-06-26 22:19:57.409815018 	at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationStartingEvent(LoggingApplicationListener.java:191)

2019-06-26 22:19:57.409866736 	at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:170)

2019-06-26 22:19:57.409875858 	at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172)

2019-06-26 22:19:57.409897243 	at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165)

0001-01-01 08:00:00.000000000 	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)

2019-06-26 22:19:57.409999701 	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)

0001-01-01 08:00:00.000000000 	at org.springframework.boot.context.event.EventPublishingRunListener.starting(EventPublishingRunListener.java:68)

2019-06-26 22:19:57.410027481 	at org.springframework.boot.SpringApplicationRunListeners.starting(SpringApplicationRunListeners.java:48)

2019-06-26 22:19:57.410039955 	at org.springframework.boot.SpringApplication.run(SpringApplication.java:313)

2019-06-26 22:19:57.410054098 	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1246)

2019-06-26 22:19:57.410073967 	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1234)

0001-01-01 08:00:00.000000000 	at cn.fraudmetrix.samaritan.AppMain.main(AppMain.java:132)

2019-06-26 22:19:57.410092094 	... 8 more

移除掉dependency-check-maven-1.4.3.jar!即可

LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementation的更多相关文章

  1. springboot项目maven报错 LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback

    完整信息如下 SLF4J: Class path contains multiple SLF4J bindings.SLF4J: Found binding in [jar:file:/D:/deve ...

  2. SpringBoot LoggerFactory is not a Logback LoggerContext but Logback is on the classpath

    SpringBoot 在启动项目的时候一起错误: SLF4J: Class path contains multiple SLF4J bindings.SLF4J: Found binding in ...

  3. 解决LoggerFactory is not a Logback LoggerContext but Logback is on the classpath

    因为引用了log4j2同时还引用了logback

  4. 安装springboot时遇到 LoggerFactory is not a Logback LoggerContext but Logback is on the classpath.问题

    将工程外部jar包删除slf4j就可以运行.

  5. logback和log4j比较，前者是后者改良，logback配置详解(转)

    一.logback的介绍 Logback是由log4j创始人设计的另一个开源日志组件,官方网站: http://logback.qos.ch.它当前分为下面下个模块: logback-core:其它两 ...

  6. 2018/2/16 解析Logback的AppenderBase源码，并举一反三的实现Logback扩展功能的思路，以及它的实际业务应用场景

    在学习Logback的过程中,知道了它有一个可以将日志往第三方数据源写的功能,这个功能的实现就是这个AppenderBase类,不禁想看看它的源码. 下面是AppenderBase类的所有子类(也就是 ...

  7. 启动Spring boot项目报错：java.lang.IllegalArgumentException: LoggerFactory is not a Logback

    java.lang.IllegalArgumentException: LoggerFactory is not a Logback LoggerContext but Logback is on t ...

  8. 使用canal分析binlog(一) 入门

    canal介绍 canal是应阿里巴巴存在杭州和美国的双机房部署,存在跨机房同步的业务需求而提出的.早期,阿里巴巴B2B公司因为存在杭州和美国双机房部署,存在跨机房同步的业务需求.不过早期的数据库同步 ...

  9. SSM迁移到Springboot记录

    日志问题 Exception in thread "main" java.lang.IllegalArgumentException: LoggerFactory is not a ...

随机推荐

  1. HTML中设置在浏览器中固定位置fixed定位

    之前的博文 HTML布局排版之制作个人网站的文章列表,中链接到的文章本身,也需要返回到列表主页,可在每个文章页面加导航条,也可以只加个返回到列表主页的链接.刚开始是想在博文最下方,加个返回文章列表的链 ...

  2. vue-cli3使用vue-router 使用动态路由，在刷新页面时报错

    刚发现的一个问题,在使用vue-cli3创建项目之后,使用动=动态路由,demo: { path: '/aa/:id', name: 'aa', component: aa }, 编程式路由: thi ...

  3. 05点睛Spring4.1-国际化

    5.1 ReloadableResourceBundleMessageSource 使用ReloadableResourceBundleMessageSource可获得不同语言的配置 此处是全局配置, ...

  4. 【VS开发】IP地址格式转换（htonl、ntohl；inet_addr、inet_ntoa）

    1.htonl ()和ntohl( ) u_long PASCAL FAR ntohl (u_long netlong); u_short PASCAL FAR ntohs (u_short nets ...

  5. flask 密钥问题

    RuntimeError RuntimeError: The session is unavailable because no secret key was set. Set the secret_ ...

  6. GWAS中的名称概念

    基因: 是指决定生物某一遗传性状的染色体DNA片段 基因型: `基因型`又称`遗传型`,是某一生物个体全部基因组合的总称.它反应生物体的遗传构成,即从双亲获得的全部基因的总和.遗传学中具体使用的基因型 ...

  7. Linux如何查看进程、杀死进程、启动进程

    1.查看进程:ps命令 下面的命令还没实践,仅仅供你参考:可以用man ps查看格式,只不过是一个小工具而已! ps a 显示现行终端机下的所有程序,包括其他用户的程序.    ps -A 显示所有程 ...

  8. php 文字转换成拼音

    <?php //中文字转拼音 $d=array( array("a",-20319), array("ai",-20317), array("a ...

  9. 用 Python 把微信小程序的二维码转化成图片

    官方文档 import cString import requests from tornado.web import authenticated, RequestHandler URL = 'htt ...

  10. Nio学习笔记(大部分网上摘抄)

    Nio与IO的区别 原有的 IO 是面向流的.阻塞的,NIO 则是面向块的.非阻塞的. 1.IO流每次从流中读一个或多个字节,直至读完所有字节,他们没有被缓存在其他地方,并且,IO流不能移动流中的数据 ...