[GitHub] [incubator-shardingsphere] cielswift commented on issue #3993: Start error with yml
cielswift commented on issue #3993: Start error with yml URL: https://github.com/apache/incubator-shardingsphere/issues/3993#issuecomment-575496207 @KomachiSion Yes, I see 4 in the official documentation, I think 3 is no longer maintained https://shardingsphere.apache.org/document/current/cn/manual/sharding-jdbc/usage/sharding/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-shardingsphere] cielswift commented on issue #3993: Start error with yml
cielswift commented on issue #3993: Start error with yml URL: https://github.com/apache/incubator-shardingsphere/issues/3993#issuecomment-575495337 @terrymanu 2020-01-17 14:34:43.348 ERROR 7196 --- [ restartedMain] o.s.b.web.embedded.tomcat.TomcatStarter : Error starting Tomcat context. Exception: org.springframework.beans.factory.BeanCreationException. Message: Error creating bean with name 'servletEndpointRegistrar' defined in class path resource [org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration$WebMvcServletEndpointManagementContextConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]: Factory method 'servletEndpointRegistrar' threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'healthEndpoint' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: Unsatisfied dependency expressed through method 'healthEndpoint' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'healthContributorRegistry' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.health.HealthContributorRegistry]: Factory method 'healthContributorRegistry' threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.boot.actuate.autoconfigure.jdbc.DataSourceHealthContributorAutoConfiguration': Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in class path resource [com/alibaba/druid/spring/boot/autoconfigure/DruidDataSourceAutoConfigure.class]: Invocation of init method failed; nested exception is org.springframework.boot.autoconfigure.jdbc.DataSourceProperties$DataSourceBeanCreationException: Failed to determine a suitable driver class 2020-01-17 14:34:43.375 INFO 7196 --- [ restartedMain] o.apache.catalina.core.StandardService : Stopping service [Tomcat] 2020-01-17 14:34:43.388 WARN 7196 --- [ restartedMain] o.a.c.loader.WebappClassLoaderBase : The web application [producer] appears to have started a thread named [RxIoScheduler-1 (Evictor)] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.base@13.0.1/jdk.internal.misc.Unsafe.park(Native Method) java.base@13.0.1/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:235) java.base@13.0.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123) java.base@13.0.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182) java.base@13.0.1/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899) java.base@13.0.1/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054) java.base@13.0.1/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114) java.base@13.0.1/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) java.base@13.0.1/java.lang.Thread.run(Thread.java:830) 2020-01-17 14:34:43.389 WARN 7196 --- [ restartedMain] o.a.c.loader.WebappClassLoaderBase : The web application [producer] appears to have started a thread named [lettuce-eventExecutorLoop-1-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.base@13.0.1/jdk.internal.misc.Unsafe.park(Native Method) java.base@13.0.1/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:235) java.base@13.0.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123) java.base@13.0.1/java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:458) app//io.netty.util.concurrent.SingleThreadEventExecutor.takeTask(SingleThreadEventExecutor.java:289) app//io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:64) app//io.netty.util.concurrent.SingleThreadEventExecutor$6.run(SingleThreadEventExecutor.java:1050) app//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
[GitHub] [incubator-shardingsphere] cielswift commented on issue #3993: Start error with yml
cielswift commented on issue #3993: Start error with yml URL: https://github.com/apache/incubator-shardingsphere/issues/3993#issuecomment-575494939 @terrymanu    This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [incubator-shardingsphere] cielswift commented on issue #3993: Start error with yml
cielswift commented on issue #3993: Start error with yml URL: https://github.com/apache/incubator-shardingsphere/issues/3993#issuecomment-574990293 4.0 version does not support mysql8? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
