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. vue 静态资源文件夹src下的assets 和static的区别

    static下的静态资源在项目打包的时候,直接在dist文件夹下直接把static文件夹打包进去src下的assets,在打包时,vue是按照模块来引入里面的静态资源,一般使用这种方式

  2. LeetCode：三数之和【15】

    LeetCode:三数之和[15] 题目描述 给定一个包含 n 个整数的数组 nums,判断 nums 中是否存在三个元素 a,b,c ,使得 a + b + c = 0 ?找出所有满足条件且不重复的 ...

  3. TCP/IP学习笔记7--TCP/IP模型通信例子学习

    "一位如蝴蝶般美丽的女子向我飞来,翩翩的舞姿如同云端轻盈的叶儿." -------------------------------------------------------- ...

  4. Ubuntu 中改变文件的默认打开方式(转)

     源自:Ubuntu 中改变文件的默认打开方式 1. 相关配置文件 全局配置 /etc/gnome/defaults.list /usr/share/applications/mimeinfo.cac ...

  5. mogodb数据库简单的权限分配

    mongdb数据库默认不需要权限认证,但为了安全起见,最好设置下需要权限认证,启动的时候设置auth=true即可. 推荐通过mongodb.conf配置文件的形式启动mongodb   进入mong ...

  6. 循环（数组循环、获取json数据循环）、each()循环详解

    return; // 退出循环(不满足,退出此次循环.下次满足条件,依然会走此循环)return false; //退出函数(退出所有) 一. 数组循环: html: <div class=&q ...

  7. Jenkins+maven+gitlab自动化部署之docker发布sprint boot项目(七)

    Jenkins发布docker应用与发布java应用配置基本一致,需要配置Dockerfile及构建的步骤,步骤如下: 1.jenkins主机构建应用为jar包 2.jenkins主机把生产的jar包 ...

  8. Spring之3：ListableBeanFactory

    ListableBeanFactory在BeanFactory的位置见<Spring源码阅览——BeanFactory体系结构> ListableBeanFactory:同样扩展BeanF ...

  9. 数组模拟循环队列（java实现）

    1.front变量的含义:front就指向队列的第一个元素,也就是说arr[front]就是队列的第一个元素front的初始值=0. 2.rear变量的含义:rear指向队列的最后一个元素的后一个位置 ...

  10. （一）Shiro，久闻其名，而今初相识

    文章目录 shiro简介 功能介绍 从外部看 Shiro 架构 从内部看 Shiro 架构 多说一句,在学习shiro之前,我觉得应该先用 filter ,自己动手写过粗粒度的权限系统,而不要一上来就 ...