[comixed-dev] Re: Unable to start CX using development builds from comixed-app-0.7.0-0-20200726205635

  • From: "Darryl L. Pierce" <mcpierce@xxxxxxxxx>
  • To: comixed-dev@xxxxxxxxxxxxx
  • Date: Mon, 27 Jul 2020 07:42:22 -0400

That's most likely indicating that, with the new Maven module shuffling,
the H2 JAR file isn't getting bundled in the comixed-app JAR file.

(downloads the artifact)

Yep, that was it. I'll push an update onto develop that fixes it.

On Mon, Jul 27, 2020 at 6:39 AM Guy Incognito <dmarc-noreply@xxxxxxxxxxxxx>
wrote:

Here’s a copy of the CMD log (hopefully appropriately redacted this time):





2020-07-27 21:07:43.665  INFO 13288 --- [           main]
org.comixedproject.ComiXedApp            : Starting ComiXedApp v0.7.0-0 on
(D:\Comics\.comixed\comixed-app-development.jar started by in D:\Comics)

2020-07-27 21:07:43.674 DEBUG 13288 --- [           main]
org.comixedproject.ComiXedApp            : Running with Spring Boot
v2.3.1.RELEASE, Spring v5.2.7.RELEASE

2020-07-27 21:07:43.674  INFO 13288 --- [           main]
org.comixedproject.ComiXedApp            : No active profile set, falling
back to default profiles: default

2020-07-27 21:07:47.356  INFO 13288 --- [           main]
.s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA
repositories in DEFERRED mode.

2020-07-27 21:07:48.225  INFO 13288 --- [           main]
.s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository
scanning in 843ms. Found 15 JPA repository interfaces.

2020-07-27 21:07:49.241  INFO 13288 --- [           main]
trationDelegate$BeanPostProcessorChecker : Bean
'org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler@2e554a3b'
of type
[org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler]
is not eligible for getting processed by all BeanPostProcessors (for
example: not eligible for auto-proxying)

2020-07-27 21:07:49.256  INFO 13288 --- [           main]
trationDelegate$BeanPostProcessorChecker : Bean
'methodSecurityMetadataSource' of type
[org.springframework.security.access.method.DelegatingMethodSecurityMetadataSource]
is not eligible for getting processed by all BeanPostProcessors (for
example: not eligible for auto-proxying)

2020-07-27 21:07:50.002  INFO 13288 --- [           main]
o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s):
7171 (http)

2020-07-27 21:07:50.018  INFO 13288 --- [           main]
o.apache.catalina.core.StandardService   : Starting service [Tomcat]

2020-07-27 21:07:50.018  INFO 13288 --- [           main]
org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache
Tomcat/9.0.36]

2020-07-27 21:07:50.192  INFO 13288 --- [           main]
o.a.c.c.C.[Tomcat].[localhost].[/]       : Initializing Spring embedded
WebApplicationContext

2020-07-27 21:07:50.192  INFO 13288 --- [           main]
w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext:
initialization completed in 6302 ms

2020-07-27 21:07:50.338 DEBUG 13288 --- [           main]
o.c.w.a.ComiXedAuthenticationFilter      : Filter
'comiXedAuthenticationFilter' configured for use

2020-07-27 21:07:50.472 ERROR 13288 --- [           main]
com.zaxxer.hikari.HikariConfig           : Failed to load driver class
org.h2.Driver from HikariConfig class classloader
org.springframework.boot.loader.LaunchedURLClassLoader@bebdb06

2020-07-27 21:07:50.488  WARN 13288 --- [           main]
ConfigServletWebServerApplicationContext : Exception encountered during
context initialization - cancelling refresh attempt:
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'liquibase' defined in class path resource
[org/springframework/boot/autoconfigure/liquibase/LiquibaseAutoConfiguration$LiquibaseConfiguration.class]:
Bean instantiation via factory method failed; nested exception is
org.springframework.beans.BeanInstantiationException: Failed to instantiate
[liquibase.integration.spring.SpringLiquibase]: Factory method 'liquibase'
threw exception; nested exception is
org.springframework.beans.factory.BeanCreationException: Error creating
bean with name 'dataSource' defined in class path resource
[org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]:
Bean instantiation via factory method failed; nested exception is
org.springframework.beans.BeanInstantiationException: Failed to instantiate
[com.zaxxer.hikari.HikariDataSource]: Factory method 'dataSource' threw
exception; nested exception is
org.springframework.boot.context.properties.bind.BindException: Failed to
bind properties under '' to com.zaxxer.hikari.HikariDataSource

2020-07-27 21:07:50.488  INFO 13288 --- [           main]
o.apache.catalina.core.StandardService   : Stopping service [Tomcat]

2020-07-27 21:07:50.535  INFO 13288 --- [           main]
ConditionEvaluationReportLoggingListener :



Error starting ApplicationContext. To display the conditions report re-run
your application with 'debug' enabled.

2020-07-27 21:07:50.535 ERROR 13288 --- [           main]
o.s.b.d.LoggingFailureAnalysisReporter   :



***************************

APPLICATION FAILED TO START

***************************



Description:



Failed to bind properties under '' to com.zaxxer.hikari.HikariDataSource:



    Property: driver-class-name

    Value: org.h2.Driver

    Origin: "driverClassName" from property source "source"

    Reason: Failed to load driver class org.h2.Driver in either of
HikariConfig class loader or Thread context classloader



Action:



Update your application's configuration



-- 
Darryl L. Pierce <mcpierce@xxxxxxxxx>
"Le centre du monde est partout." - Blaise Pascal
"Let's try and find some point of transcendence and leap together." - Gord
Downie

Other related posts: