Error-Idea:Process finished with exit code 1
| ylbtech-Error-Idea:Process finished with exit code 1 |
| 1.返回顶部 |
log4j:WARN No appenders could be found for logger (org.springframework.boot.devtools.settings.DevToolsSettings).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Users/Administrator/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/C:/Users/Administrator/.m2/repository/org/slf4j/slf4j-log4j12/1.7.25/slf4j-log4j12-1.7.25.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
Application Version: 1.0.0
Spring Boot Version: 2.0.5.RELEASE
███████╗██╗ ██╗██╗███╗ ██╗███████╗██╗ ██╗ ██████╗ ██████╗
██╔════╝██║ ██║██║████╗ ██║██╔════╝╚██╗ ██╔╝██╔═══██╗██╔═══██╗
███████╗███████║██║██╔██╗ ██║█████╗ ╚████╔╝ ██║ ██║██║ ██║
╚════██║██╔══██║██║██║╚██╗██║██╔══╝ ╚██╔╝ ██║ ██║██║ ██║
███████║██║ ██║██║██║ ╚████║███████╗ ██║ ╚██████╔╝╚██████╔╝
╚══════╝╚═╝ ╚═╝╚═╝╚═╝ ╚═══╝╚══════╝ ╚═╝ ╚═════╝ ╚═════╝
17:52:17.811 [restartedMain] INFO o.a.s.c.e.EhCacheManager - [getCache,158] - Cache with name 'com.shineyoo.framework.shiro.realm.UserRealm.authorizationCache' does not yet exist. Creating now.
17:52:17.817 [restartedMain] INFO o.a.s.c.e.EhCacheManager - [getCache,165] - Added EhCache named [com.shineyoo.framework.shiro.realm.UserRealm.authorizationCache]
17:52:19.950 [restartedMain] INFO o.a.s.c.e.EhCacheManager - [getCache,169] - Using existing EHCache named [loginRecordCache]
17:52:21.277 [restartedMain] INFO o.a.c.h.Http11NioProtocol - [log,180] - Initializing ProtocolHandler ["http-nio-80"]
17:52:21.296 [restartedMain] INFO o.a.c.c.StandardService - [log,180] - Starting service [Tomcat]
17:52:21.296 [restartedMain] INFO o.a.c.c.StandardEngine - [log,180] - Starting Servlet Engine: Apache Tomcat/8.5.34
17:52:21.300 [localhost-startStop-1] INFO o.a.c.c.AprLifecycleListener - [log,180] - The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [C:\Program Files\Java\jdk1.8.0_151\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\VisualSVN Server\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Users\Administrator\AppData\Local\BypassRuntm;.]
17:52:21.538 [localhost-startStop-1] INFO o.a.c.c.C.[.[.[/] - [log,180] - Initializing Spring embedded WebApplicationContext
17:52:22.454 [restartedMain] INFO c.a.d.p.DruidDataSource - [init,930] - {dataSource-1} inited
17:52:22.938 [restartedMain] INFO o.q.i.StdSchedulerFactory - [instantiate,1208] - Using default implementation for ThreadExecutor
17:52:22.957 [restartedMain] INFO o.q.c.SchedulerSignalerImpl - [<init>,61] - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
17:52:22.957 [restartedMain] INFO o.q.c.QuartzScheduler - [<init>,229] - Quartz Scheduler v.2.3.0 created.
17:52:22.970 [restartedMain] INFO o.q.c.QuartzScheduler - [initialize,294] - Scheduler meta-data: Quartz Scheduler (v2.3.0) 'nnzScheduler' with instanceId 'CN-20190525ESPU1560160342941'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 20 threads.
Using job-store 'org.springframework.scheduling.quartz.LocalDataSourceJobStore' - which supports persistence. and is clustered.
17:52:22.971 [restartedMain] INFO o.q.i.StdSchedulerFactory - [instantiate,1362] - Quartz scheduler 'nnzScheduler' initialized from an externally provided properties instance.
17:52:22.971 [restartedMain] INFO o.q.i.StdSchedulerFactory - [instantiate,1366] - Quartz scheduler version: 2.3.0
17:52:22.975 [restartedMain] INFO o.q.c.QuartzScheduler - [setJobFactory,2287] - JobFactory set to: org.springframework.scheduling.quartz.AdaptableJobFactory@2b16ef70
17:52:23.038 [restartedMain] DEBUG c.s.q.m.S.selectJobAll - [debug,159] - ==> Preparing: select job_id, job_name, job_group, method_name, method_params, cron_expression, misfire_policy, status, create_by, create_time, remark from sys_job
17:52:23.065 [restartedMain] DEBUG c.s.q.m.S.selectJobAll - [debug,159] - ==> Parameters:
17:52:23.101 [restartedMain] DEBUG c.s.q.m.S.selectJobAll - [debug,159] - <== Total: 1
17:52:23.163 [restartedMain] INFO o.q.c.QuartzScheduler - [shutdown,666] - Scheduler nnzScheduler_$_CN-20190525ESPU1560160342941 shutting down.
17:52:23.164 [restartedMain] INFO o.q.c.QuartzScheduler - [standby,585] - Scheduler nnzScheduler_$_CN-20190525ESPU1560160342941 paused.
17:52:23.164 [restartedMain] INFO o.q.c.QuartzScheduler - [shutdown,740] - Scheduler nnzScheduler_$_CN-20190525ESPU1560160342941 shutdown complete.
17:52:23.175 [restartedMain] INFO c.a.d.p.DruidDataSource - [close,1825] - {dataSource-1} closed
17:52:23.182 [restartedMain] INFO o.a.c.c.StandardService - [log,180] - Stopping service [Tomcat]
Process finished with exit code 1
| 2.返回顶部 |
Z:我意思是你先与他们的版本保持一致试试看,你当前装个maven2一定会死的
Z:因为2和3的机制都不一样
Z:你们这些日志都是应用自己的类文件日志,也不知道具体代表什么意思
Z:现在看现象是应用初始化上下文的时候,初始化了一个定时任务,然后查了下库,查了后就中止了
Z:初始化的时候,还加载了一个缓存,丢到ehcache了
| 3.返回顶部 |
| 4.返回顶部 |
| 5.返回顶部 |
| 6.返回顶部 |
![]() |
作者:ylbtech 出处:http://ylbtech.cnblogs.com/ 本文版权归作者和博客园共有,欢迎转载,但未经作者同意必须保留此段声明,且在文章页面明显位置给出原文连接,否则保留追究法律责任的权利。 |
Error-Idea:Process finished with exit code 1的更多相关文章
- spring boot 运行提示:Process finished with exit code 1
spring boot 运行提示:Process finished with exit code 1 经检查发现是由于在application.properties配置文件中将某些自定义配置项移除了, ...
- pycharm 调试Django 奇葩问题:Process finished with exit code -1073741819
想自己整个BLOG,发现python+Django好像还不错,尝试一下.在使用过程中,突然pycharm不能调试django工程.网上搜索也没解决,是google哦.好像记得启动pycharm时,看到 ...
- pycharm报错:Process finished with exit code -1073741819 (0xC0000005)解决办法
这个是几个月前的问题了,有小伙伴在CSDN问我咋解决的,那我今天在这边把这个问题解决办法分享下吧,免得大家把很多时间都浪费在安装排坑上面,有些坑虽然解决了还真不知道啥原因. 我的pycharm一直用的 ...
- python跑机器学习时报错:Process finished with exit code -1073740791 (0xC0000409)
emmm...第二次遇到这个错误了,好好的好好的卷积神经网络突然就跑不起了.就弹出一堆信息也不报那行代码错了... 记录一下: 两次解决方法相同,删h5py包 Process finished wit ...
- IDEA:Process finished with exit code -1073741819 (0xC0000005)
出门左转:https://www.cnblogs.com/virgosnail/p/10335224.html
- 启动总是提示:Process finished with exit code 0
1.端口冲突检查端口号 2.缺少web启动依赖 <dependency> <groupId>org.springframework.boot</groupId> & ...
- odoo Windows10启动debug模式报错(Process finished with exit code -1073740940 (0xC0000374))
之前用win10系统,安装odoo总是启动debug模式启动不起来很恼火. 报错问题:Process finished with exit code -1073740940 (0xC0000374) ...
- [报错] Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
今天下午做python的作业,我用PyQt5 中 利用QWebEngineView打开外部网页. 但是一直闪退,一运行就闪退. 显示报错:Process finished with exit code ...
- Android-AndroidStudio-AVD启动不了-emulator: Process finished with exit code 1
注意:解决此错误目前只针对Windows系统的电脑: 1.AndroidStudio-->AVDManager(Create Virtual Device): 2.提示AVD启动不了,同时Eve ...
随机推荐
- 牛客D-Where are you /// kruskal+tarjan找无向图内的环
题目大意: https://ac.nowcoder.com/acm/contest/272/D 在一个无向图中,给定一个起点,从起点开始走遍图中所有点 每条边有边权wi,表示第一次经过该道路时的花费( ...
- 【Java】Appache Flume 中文介绍
Flume 是什么 Apache Flume是一个高可靠.高可用的分布式的海量日志收集.聚合.传输系统.它能够从不同的日志源採集数据并集中存储. Flume也算是Hadoop生态系 ...
- Vue项目如何关闭Eslint检测
找到build/webpack.base.config.js文件,修改如下 将图中第二个红色框的内容 "createLintingRule()" 清空,然后保存重新启动项目即可.
- vue created与activated的区别
搬运自:https://www.cnblogs.com/goloving/p/9256212.html 使用<keep-alive>会将数据保留在内存中,如果要在每次进入页面的时候获取最新 ...
- [转载]Spring AOP 深入剖析
转载自 http://www.cnblogs.com/digdeep/p/4528353.html 多谢@digdeep AOP是Spring提供的关键特性之一.AOP即面向切面编程,是OOP编程的有 ...
- uboot 的启动过程及工作原理
启动模式介绍 大多数 Boot Loader 都包含两种不同的操作模式:"启动加载"模式和"下载"模式,这种区别仅对于开发人 员才有意义.但从最终用户的角度看, ...
- 随笔记录 MBR扇区故障系统备份与还原 2019.8.7
系统备份: [root@localhost ~]# mkdir /abc [root@localhost ~]# mount /dev/sdb1 /abc [root@localhost ~]# dd ...
- stelller插件与background-attachment配合使用,制作滚动页面
stelller插件与background-attachment:fixed配合使用,制作滚动页面
- Laravel Illuminate\Http\Exceptions\PostTooLargeException
出错原因是: 请求的post的数据比 php.ini设定的 post_max_size大的原因 解决方法: 增加php.ini中 post_max_size和upload_max_filesize的设 ...
- thinkphp 变量输出
在模板中输出变量的方法很简单,例如,在控制器中我们给模板变量赋值: 大理石平台支架 $name = 'ThinkPHP'; $this->assign('name',$name); $this- ...
