123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172 |
- [2m2021-07-05 10:04:19.005[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Starting GpExpServerApplication on caiwx with PID 19424 (C:\Users\weiyf\IdeaProjects\gp-exp-server\target\classes started by weiyf in C:\Users\weiyf\IdeaProjects\gp-exp-server)
- [2m2021-07-05 10:04:19.010[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m The following profiles are active: pro
- [2m2021-07-05 10:04:20.781[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Multiple Spring Data modules found, entering strict repository configuration mode!
- [2m2021-07-05 10:04:20.784[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Bootstrapping Spring Data repositories in DEFAULT mode.
- [2m2021-07-05 10:04:20.968[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Finished Spring Data repository scanning in 168ms. Found 0 repository interfaces.
- [2m2021-07-05 10:04:21.455[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mtrationDelegate$BeanPostProcessorChecker[0;39m [2m:[0;39m Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$7e413749] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- [2m2021-07-05 10:04:22.089[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.b.w.embedded.tomcat.TomcatWebServer [0;39m [2m:[0;39m Tomcat initialized with port(s): 8080 (http)
- [2m2021-07-05 10:04:22.126[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.apache.catalina.core.StandardService [0;39m [2m:[0;39m Starting service [Tomcat]
- [2m2021-07-05 10:04:22.127[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36morg.apache.catalina.core.StandardEngine [0;39m [2m:[0;39m Starting Servlet engine: [Apache Tomcat/9.0.24]
- [2m2021-07-05 10:04:22.393[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.a.c.c.C.[Tomcat].[localhost].[/] [0;39m [2m:[0;39m Initializing Spring embedded WebApplicationContext
- [2m2021-07-05 10:04:22.394[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.web.context.ContextLoader [0;39m [2m:[0;39m Root WebApplicationContext: initialization completed in 2819 ms
- [2m2021-07-05 10:04:23.248[0;39m [33m WARN[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.a.r.c.CachingConnectionFactory [0;39m [2m:[0;39m ***
- Automatic Recovery was Enabled in the provided connection factory;
- while Spring AMQP is generally compatible with this feature, there
- are some corner cases where problems arise. Spring AMQP
- prefers to use its own recovery mechanisms; when this option is true, you may receive
- 'AutoRecoverConnectionNotCurrentlyOpenException's until the connection is recovered.
- It has therefore been disabled; if you really wish to enable it, use
- 'getRabbitConnectionFactory().setAutomaticRecoveryEnabled(true)',
- but this is discouraged.
- [2m2021-07-05 10:04:23.362[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.RedisConfig [0;39m [2m:[0;39m JedisPool注入成功!!
- [2m2021-07-05 10:04:23.362[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.RedisConfig [0;39m [2m:[0;39m redis地址:r-uf6s2bntltbncgcxtf.redis.rds.aliyuncs.com:6379
- [2m2021-07-05 10:04:23.697[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Initializing ExecutorService
- [2m2021-07-05 10:04:23.699[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Initializing ExecutorService 'taskExecutor'
- [2m2021-07-05 10:04:23.707[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.XxlJobConfig [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job config init.
- [2m2021-07-05 10:04:23.716[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.xxl.job.core.executor.XxlJobExecutor [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job register jobhandler success, name:guoanJobHandle, jobHandler:com.parksong.job.GuoanJobHandle@54f2df29
- [2m2021-07-05 10:04:23.760[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.x.r.r.provider.XxlRpcProviderFactory [0;39m [2m:[0;39m >>>>>>>>>>> xxl-rpc, provider factory add service success. serviceKey = com.xxl.job.core.biz.ExecutorBiz, serviceBean = class com.xxl.job.core.biz.impl.ExecutorBizImpl
- [2m2021-07-05 10:04:25.258[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.b.w.embedded.tomcat.TomcatWebServer [0;39m [2m:[0;39m Tomcat started on port(s): 8080 (http) with context path ''
- [2m2021-07-05 10:04:25.264[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Started GpExpServerApplication in 8.334 seconds (JVM running for 11.368)
- [2m2021-07-05 10:04:25.267[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Spring boot启动初始化了 305 个 Bean
- [2m2021-07-05 10:04:25.304[0;39m [32m INFO[0;39m [35m19424[0;39m [2m---[0;39m [2m[ Thread-19][0;39m [36mcom.xxl.rpc.remoting.net.Server [0;39m [2m:[0;39m >>>>>>>>>>> xxl-rpc remoting server start success, nettype = com.xxl.rpc.remoting.net.impl.netty_http.server.NettyHttpServer, port = 2336
- [2m2021-07-05 11:18:16.992[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Starting GpExpServerApplication on caiwx with PID 16788 (C:\Users\weiyf\IdeaProjects\gp-exp-server\target\classes started by weiyf in C:\Users\weiyf\IdeaProjects\gp-exp-server)
- [2m2021-07-05 11:18:16.995[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m The following profiles are active: pro
- [2m2021-07-05 11:18:18.386[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Multiple Spring Data modules found, entering strict repository configuration mode!
- [2m2021-07-05 11:18:18.390[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Bootstrapping Spring Data repositories in DEFAULT mode.
- [2m2021-07-05 11:18:18.596[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Finished Spring Data repository scanning in 184ms. Found 0 repository interfaces.
- [2m2021-07-05 11:18:19.051[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mtrationDelegate$BeanPostProcessorChecker[0;39m [2m:[0;39m Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$20d554e] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- [2m2021-07-05 11:18:19.631[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.b.w.embedded.tomcat.TomcatWebServer [0;39m [2m:[0;39m Tomcat initialized with port(s): 8080 (http)
- [2m2021-07-05 11:18:19.666[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.apache.catalina.core.StandardService [0;39m [2m:[0;39m Starting service [Tomcat]
- [2m2021-07-05 11:18:19.667[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36morg.apache.catalina.core.StandardEngine [0;39m [2m:[0;39m Starting Servlet engine: [Apache Tomcat/9.0.24]
- [2m2021-07-05 11:18:19.903[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.a.c.c.C.[Tomcat].[localhost].[/] [0;39m [2m:[0;39m Initializing Spring embedded WebApplicationContext
- [2m2021-07-05 11:18:19.903[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.web.context.ContextLoader [0;39m [2m:[0;39m Root WebApplicationContext: initialization completed in 2649 ms
- [2m2021-07-05 11:18:20.796[0;39m [33m WARN[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.a.r.c.CachingConnectionFactory [0;39m [2m:[0;39m ***
- Automatic Recovery was Enabled in the provided connection factory;
- while Spring AMQP is generally compatible with this feature, there
- are some corner cases where problems arise. Spring AMQP
- prefers to use its own recovery mechanisms; when this option is true, you may receive
- 'AutoRecoverConnectionNotCurrentlyOpenException's until the connection is recovered.
- It has therefore been disabled; if you really wish to enable it, use
- 'getRabbitConnectionFactory().setAutomaticRecoveryEnabled(true)',
- but this is discouraged.
- [2m2021-07-05 11:18:20.951[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.RedisConfig [0;39m [2m:[0;39m JedisPool注入成功!!
- [2m2021-07-05 11:18:20.952[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.RedisConfig [0;39m [2m:[0;39m redis地址:r-uf6s2bntltbncgcxtf.redis.rds.aliyuncs.com:6379
- [2m2021-07-05 11:18:21.442[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Initializing ExecutorService
- [2m2021-07-05 11:18:21.446[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Initializing ExecutorService 'taskExecutor'
- [2m2021-07-05 11:18:21.458[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.XxlJobConfig [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job config init.
- [2m2021-07-05 11:18:21.473[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.xxl.job.core.executor.XxlJobExecutor [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job register jobhandler success, name:guoanJobHandle, jobHandler:com.parksong.job.GuoanJobHandle@590013c7
- [2m2021-07-05 11:18:21.520[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.xxl.rpc.util.NetUtil [0;39m [2m:[0;39m >>>>>>>>>>> xxl-rpc, port[2336] is in use.
- [2m2021-07-05 11:18:21.521[0;39m [33m WARN[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mConfigServletWebServerApplicationContext[0;39m [2m:[0;39m Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xxlJobExecutor' defined in class path resource [com/parksong/basics/util/configurations/XxlJobConfig.class]: Invocation of init method failed; nested exception is com.xxl.rpc.util.XxlRpcException: xxl-rpc provider port[2336] is used.
- [2m2021-07-05 11:18:21.523[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Shutting down ExecutorService 'taskExecutor'
- [2m2021-07-05 11:18:21.530[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.apache.catalina.core.StandardService [0;39m [2m:[0;39m Stopping service [Tomcat]
- [2m2021-07-05 11:18:21.554[0;39m [32m INFO[0;39m [35m16788[0;39m [2m---[0;39m [2m[ main][0;39m [36mConditionEvaluationReportLoggingListener[0;39m [2m:[0;39m
- Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
- [2m2021-07-05 11:19:25.129[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Starting GpExpServerApplication on caiwx with PID 14364 (C:\Users\weiyf\IdeaProjects\gp-exp-server\target\classes started by weiyf in C:\Users\weiyf\IdeaProjects\gp-exp-server)
- [2m2021-07-05 11:19:25.133[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m The following profiles are active: pro
- [2m2021-07-05 11:19:26.786[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Multiple Spring Data modules found, entering strict repository configuration mode!
- [2m2021-07-05 11:19:26.794[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Bootstrapping Spring Data repositories in DEFAULT mode.
- [2m2021-07-05 11:19:27.024[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Finished Spring Data repository scanning in 212ms. Found 0 repository interfaces.
- [2m2021-07-05 11:19:27.504[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mtrationDelegate$BeanPostProcessorChecker[0;39m [2m:[0;39m Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$3d9ae477] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- [2m2021-07-05 11:19:28.105[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.b.w.embedded.tomcat.TomcatWebServer [0;39m [2m:[0;39m Tomcat initialized with port(s): 8080 (http)
- [2m2021-07-05 11:19:28.138[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.apache.catalina.core.StandardService [0;39m [2m:[0;39m Starting service [Tomcat]
- [2m2021-07-05 11:19:28.139[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36morg.apache.catalina.core.StandardEngine [0;39m [2m:[0;39m Starting Servlet engine: [Apache Tomcat/9.0.24]
- [2m2021-07-05 11:19:28.382[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.a.c.c.C.[Tomcat].[localhost].[/] [0;39m [2m:[0;39m Initializing Spring embedded WebApplicationContext
- [2m2021-07-05 11:19:28.382[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.web.context.ContextLoader [0;39m [2m:[0;39m Root WebApplicationContext: initialization completed in 2921 ms
- [2m2021-07-05 11:19:29.278[0;39m [33m WARN[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.a.r.c.CachingConnectionFactory [0;39m [2m:[0;39m ***
- Automatic Recovery was Enabled in the provided connection factory;
- while Spring AMQP is generally compatible with this feature, there
- are some corner cases where problems arise. Spring AMQP
- prefers to use its own recovery mechanisms; when this option is true, you may receive
- 'AutoRecoverConnectionNotCurrentlyOpenException's until the connection is recovered.
- It has therefore been disabled; if you really wish to enable it, use
- 'getRabbitConnectionFactory().setAutomaticRecoveryEnabled(true)',
- but this is discouraged.
- [2m2021-07-05 11:19:29.390[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.RedisConfig [0;39m [2m:[0;39m JedisPool注入成功!!
- [2m2021-07-05 11:19:29.391[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.RedisConfig [0;39m [2m:[0;39m redis地址:r-uf6s2bntltbncgcxtf.redis.rds.aliyuncs.com:6379
- [2m2021-07-05 11:19:29.707[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Initializing ExecutorService
- [2m2021-07-05 11:19:29.709[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Initializing ExecutorService 'taskExecutor'
- [2m2021-07-05 11:19:29.718[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.XxlJobConfig [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job config init.
- [2m2021-07-05 11:19:29.728[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.xxl.job.core.executor.XxlJobExecutor [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job register jobhandler success, name:guoanJobHandle, jobHandler:com.parksong.job.GuoanJobHandle@11d2714a
- [2m2021-07-05 11:19:29.766[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.xxl.rpc.util.NetUtil [0;39m [2m:[0;39m >>>>>>>>>>> xxl-rpc, port[2336] is in use.
- [2m2021-07-05 11:19:29.767[0;39m [33m WARN[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mConfigServletWebServerApplicationContext[0;39m [2m:[0;39m Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'xxlJobExecutor' defined in class path resource [com/parksong/basics/util/configurations/XxlJobConfig.class]: Invocation of init method failed; nested exception is com.xxl.rpc.util.XxlRpcException: xxl-rpc provider port[2336] is used.
- [2m2021-07-05 11:19:29.768[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Shutting down ExecutorService 'taskExecutor'
- [2m2021-07-05 11:19:29.774[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.apache.catalina.core.StandardService [0;39m [2m:[0;39m Stopping service [Tomcat]
- [2m2021-07-05 11:19:29.785[0;39m [32m INFO[0;39m [35m14364[0;39m [2m---[0;39m [2m[ main][0;39m [36mConditionEvaluationReportLoggingListener[0;39m [2m:[0;39m
- Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
- [2m2021-07-05 11:22:42.014[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Starting GpExpServerApplication on caiwx with PID 21200 (C:\Users\weiyf\IdeaProjects\gp-exp-server\target\classes started by weiyf in C:\Users\weiyf\IdeaProjects\gp-exp-server)
- [2m2021-07-05 11:22:42.022[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m The following profiles are active: pro
- [2m2021-07-05 11:22:43.762[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Multiple Spring Data modules found, entering strict repository configuration mode!
- [2m2021-07-05 11:22:43.767[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Bootstrapping Spring Data repositories in DEFAULT mode.
- [2m2021-07-05 11:22:43.973[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Finished Spring Data repository scanning in 188ms. Found 0 repository interfaces.
- [2m2021-07-05 11:22:44.517[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mtrationDelegate$BeanPostProcessorChecker[0;39m [2m:[0;39m Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$bb91dd47] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- [2m2021-07-05 11:22:45.209[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.b.w.embedded.tomcat.TomcatWebServer [0;39m [2m:[0;39m Tomcat initialized with port(s): 8080 (http)
- [2m2021-07-05 11:22:45.273[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.apache.catalina.core.StandardService [0;39m [2m:[0;39m Starting service [Tomcat]
- [2m2021-07-05 11:22:45.274[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36morg.apache.catalina.core.StandardEngine [0;39m [2m:[0;39m Starting Servlet engine: [Apache Tomcat/9.0.24]
- [2m2021-07-05 11:22:45.582[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.a.c.c.C.[Tomcat].[localhost].[/] [0;39m [2m:[0;39m Initializing Spring embedded WebApplicationContext
- [2m2021-07-05 11:22:45.583[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.web.context.ContextLoader [0;39m [2m:[0;39m Root WebApplicationContext: initialization completed in 3229 ms
- [2m2021-07-05 11:22:46.516[0;39m [33m WARN[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.a.r.c.CachingConnectionFactory [0;39m [2m:[0;39m ***
- Automatic Recovery was Enabled in the provided connection factory;
- while Spring AMQP is generally compatible with this feature, there
- are some corner cases where problems arise. Spring AMQP
- prefers to use its own recovery mechanisms; when this option is true, you may receive
- 'AutoRecoverConnectionNotCurrentlyOpenException's until the connection is recovered.
- It has therefore been disabled; if you really wish to enable it, use
- 'getRabbitConnectionFactory().setAutomaticRecoveryEnabled(true)',
- but this is discouraged.
- [2m2021-07-05 11:22:46.651[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.RedisConfig [0;39m [2m:[0;39m JedisPool注入成功!!
- [2m2021-07-05 11:22:46.651[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.RedisConfig [0;39m [2m:[0;39m redis地址:r-uf6s2bntltbncgcxtf.redis.rds.aliyuncs.com:6379
- [2m2021-07-05 11:22:47.020[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Initializing ExecutorService
- [2m2021-07-05 11:22:47.021[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Initializing ExecutorService 'taskExecutor'
- [2m2021-07-05 11:22:47.030[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.XxlJobConfig [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job config init.
- [2m2021-07-05 11:22:47.039[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.xxl.job.core.executor.XxlJobExecutor [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job register jobhandler success, name:guoanJobHandle, jobHandler:com.parksong.job.GuoanJobHandle@7afe0e67
- [2m2021-07-05 11:22:47.083[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.x.r.r.provider.XxlRpcProviderFactory [0;39m [2m:[0;39m >>>>>>>>>>> xxl-rpc, provider factory add service success. serviceKey = com.xxl.job.core.biz.ExecutorBiz, serviceBean = class com.xxl.job.core.biz.impl.ExecutorBizImpl
- [2m2021-07-05 11:22:48.609[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.b.w.embedded.tomcat.TomcatWebServer [0;39m [2m:[0;39m Tomcat started on port(s): 8080 (http) with context path ''
- [2m2021-07-05 11:22:48.613[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Started GpExpServerApplication in 7.385 seconds (JVM running for 10.42)
- [2m2021-07-05 11:22:48.617[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Spring boot启动初始化了 305 个 Bean
- [2m2021-07-05 11:22:48.689[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[ Thread-17][0;39m [36mcom.xxl.rpc.remoting.net.Server [0;39m [2m:[0;39m >>>>>>>>>>> xxl-rpc remoting server start success, nettype = com.xxl.rpc.remoting.net.impl.netty_http.server.NettyHttpServer, port = 2336
- [2m2021-07-05 11:24:52.011[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[rRegistryThread][0;39m [36mc.x.r.r.i.reference.XxlRpcReferenceBean [0;39m [2m:[0;39m >>>>>>>>>>> xxl-rpc, invoke error, address:http://xxljob.fengzhan100.com/xxl-job-admin/api, XxlRpcRequestXxlRpcRequest{requestId='4a3d5606-24ca-430b-9c78-adae771c1be9', createMillisTime=1625455489004, accessToken='', className='com.xxl.job.core.biz.AdminBiz', methodName='registry', parameterTypes=[class com.xxl.job.core.biz.model.RegistryParam], parameters=[RegistryParam{registGroup='EXECUTOR', registryKey='gp-exp-server', registryValue='192.168.2.6:2336'}], version='null'}
- [2m2021-07-05 11:24:52.020[0;39m [32m INFO[0;39m [35m21200[0;39m [2m---[0;39m [2m[rRegistryThread][0;39m [36mc.x.j.c.thread.ExecutorRegistryThread [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job registry error, registryParam:RegistryParam{registGroup='EXECUTOR', registryKey='gp-exp-server', registryValue='192.168.2.6:2336'}
- com.xxl.rpc.util.XxlRpcException: xxl-rpc, request timeout at:1625455492011, request:XxlRpcRequest{requestId='4a3d5606-24ca-430b-9c78-adae771c1be9', createMillisTime=1625455489004, accessToken='', className='com.xxl.job.core.biz.AdminBiz', methodName='registry', parameterTypes=[class com.xxl.job.core.biz.model.RegistryParam], parameters=[RegistryParam{registGroup='EXECUTOR', registryKey='gp-exp-server', registryValue='192.168.2.6:2336'}], version='null'}
- at com.xxl.rpc.remoting.net.params.XxlRpcFutureResponse.get(XxlRpcFutureResponse.java:117)
- at com.xxl.rpc.remoting.invoker.reference.XxlRpcReferenceBean$1.invoke(XxlRpcReferenceBean.java:219)
- at com.sun.proxy.$Proxy142.registry(Unknown Source)
- at com.xxl.job.core.thread.ExecutorRegistryThread$1.run(ExecutorRegistryThread.java:48)
- at java.lang.Thread.run(Thread.java:748)
- [2m2021-07-05 14:59:13.999[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Starting GpExpServerApplication on caiwx with PID 24428 (C:\Users\weiyf\IdeaProjects\gp-exp-server\target\classes started by weiyf in C:\Users\weiyf\IdeaProjects\gp-exp-server)
- [2m2021-07-05 14:59:14.005[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m The following profiles are active: pro
- [2m2021-07-05 14:59:15.583[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Multiple Spring Data modules found, entering strict repository configuration mode!
- [2m2021-07-05 14:59:15.586[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Bootstrapping Spring Data repositories in DEFAULT mode.
- [2m2021-07-05 14:59:15.787[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.d.r.c.RepositoryConfigurationDelegate[0;39m [2m:[0;39m Finished Spring Data repository scanning in 184ms. Found 0 repository interfaces.
- [2m2021-07-05 14:59:16.326[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mtrationDelegate$BeanPostProcessorChecker[0;39m [2m:[0;39m Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$94d4f57c] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- [2m2021-07-05 14:59:17.051[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.b.w.embedded.tomcat.TomcatWebServer [0;39m [2m:[0;39m Tomcat initialized with port(s): 8080 (http)
- [2m2021-07-05 14:59:17.084[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.apache.catalina.core.StandardService [0;39m [2m:[0;39m Starting service [Tomcat]
- [2m2021-07-05 14:59:17.085[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36morg.apache.catalina.core.StandardEngine [0;39m [2m:[0;39m Starting Servlet engine: [Apache Tomcat/9.0.24]
- [2m2021-07-05 14:59:17.328[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.a.c.c.C.[Tomcat].[localhost].[/] [0;39m [2m:[0;39m Initializing Spring embedded WebApplicationContext
- [2m2021-07-05 14:59:17.328[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.web.context.ContextLoader [0;39m [2m:[0;39m Root WebApplicationContext: initialization completed in 2986 ms
- [2m2021-07-05 14:59:18.206[0;39m [33m WARN[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.a.r.c.CachingConnectionFactory [0;39m [2m:[0;39m ***
- Automatic Recovery was Enabled in the provided connection factory;
- while Spring AMQP is generally compatible with this feature, there
- are some corner cases where problems arise. Spring AMQP
- prefers to use its own recovery mechanisms; when this option is true, you may receive
- 'AutoRecoverConnectionNotCurrentlyOpenException's until the connection is recovered.
- It has therefore been disabled; if you really wish to enable it, use
- 'getRabbitConnectionFactory().setAutomaticRecoveryEnabled(true)',
- but this is discouraged.
- [2m2021-07-05 14:59:18.323[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.RedisConfig [0;39m [2m:[0;39m JedisPool注入成功!!
- [2m2021-07-05 14:59:18.323[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.RedisConfig [0;39m [2m:[0;39m redis地址:r-uf6s2bntltbncgcxtf.redis.rds.aliyuncs.com:6379
- [2m2021-07-05 14:59:18.729[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Initializing ExecutorService
- [2m2021-07-05 14:59:18.732[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.s.concurrent.ThreadPoolTaskExecutor [0;39m [2m:[0;39m Initializing ExecutorService 'taskExecutor'
- [2m2021-07-05 14:59:18.744[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.p.b.util.configurations.XxlJobConfig [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job config init.
- [2m2021-07-05 14:59:18.754[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.xxl.job.core.executor.XxlJobExecutor [0;39m [2m:[0;39m >>>>>>>>>>> xxl-job register jobhandler success, name:guoanJobHandle, jobHandler:com.parksong.job.GuoanJobHandle@1c2d63f0
- [2m2021-07-05 14:59:18.800[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mc.x.r.r.provider.XxlRpcProviderFactory [0;39m [2m:[0;39m >>>>>>>>>>> xxl-rpc, provider factory add service success. serviceKey = com.xxl.job.core.biz.ExecutorBiz, serviceBean = class com.xxl.job.core.biz.impl.ExecutorBizImpl
- [2m2021-07-05 14:59:20.312[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mo.s.b.w.embedded.tomcat.TomcatWebServer [0;39m [2m:[0;39m Tomcat started on port(s): 8080 (http) with context path ''
- [2m2021-07-05 14:59:20.317[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Started GpExpServerApplication in 7.285 seconds (JVM running for 9.993)
- [2m2021-07-05 14:59:20.322[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ main][0;39m [36mcom.parksong.GpExpServerApplication [0;39m [2m:[0;39m Spring boot启动初始化了 305 个 Bean
- [2m2021-07-05 14:59:20.488[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[ Thread-16][0;39m [36mcom.xxl.rpc.remoting.net.Server [0;39m [2m:[0;39m >>>>>>>>>>> xxl-rpc remoting server start success, nettype = com.xxl.rpc.remoting.net.impl.netty_http.server.NettyHttpServer, port = 2336
- [2m2021-07-05 15:29:13.266[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[nio-8080-exec-1][0;39m [36mo.a.c.c.C.[Tomcat].[localhost].[/] [0;39m [2m:[0;39m Initializing Spring DispatcherServlet 'dispatcherServlet'
- [2m2021-07-05 15:29:13.267[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[nio-8080-exec-1][0;39m [36mo.s.web.servlet.DispatcherServlet [0;39m [2m:[0;39m Initializing Servlet 'dispatcherServlet'
- [2m2021-07-05 15:29:13.283[0;39m [32m INFO[0;39m [35m24428[0;39m [2m---[0;39m [2m[nio-8080-exec-1][0;39m [36mo.s.web.servlet.DispatcherServlet [0;39m [2m:[0;39m Completed initialization in 16 ms
|