Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- APÓS EXECUTAR O COMANDO para subir aplicação: heroku logs --tail a aplicação está retornando o erro abaixo. Parece ser problema de versão de migração. Sou Analista Trainee linguagem Java, algum colega tem a solução para isso?
- 2019-02-07T11:47:07.434320+00:00 heroku[web.1]: State changed from starting to crashed
- 2019-02-07T11:47:07.418115+00:00 heroku[web.1]: Process exited with status 1
- 2019-02-07T12:14:40.873242+00:00 heroku[web.1]: State changed from crashed to starting
- 2019-02-07T12:14:45.383136+00:00 heroku[web.1]: Starting process with command `java -Dserver.port=43501 $JAVA_OPTS -jar target/algamoney-api-1.0.0-SNAPSHOT.jar`
- 2019-02-07T12:14:47.749459+00:00 app[web.1]: Create a Procfile to customize the command used to run this process: https://devcenter.heroku.com/articles/procfile
- 2019-02-07T12:14:47.775919+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
- 2019-02-07T12:14:47.784958+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8
- 2019-02-07T12:14:50.122312+00:00 app[web.1]:
- 2019-02-07T12:14:50.122362+00:00 app[web.1]: . ____ _ __ _ _
- 2019-02-07T12:14:50.122457+00:00 app[web.1]: /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
- 2019-02-07T12:14:50.122547+00:00 app[web.1]: ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
- 2019-02-07T12:14:50.122641+00:00 app[web.1]: \\/ ___)| |_)| | | | | || (_| | ) ) ) )
- 2019-02-07T12:14:50.122749+00:00 app[web.1]: ' |____| .__|_| |_|_| |_\__, | / / / /
- 2019-02-07T12:14:50.122895+00:00 app[web.1]: =========|_|==============|___/=/_/_/_/
- 2019-02-07T12:14:50.129548+00:00 app[web.1]: :: Spring Boot :: (v1.5.3.RELEASE)
- 2019-02-07T12:14:50.129654+00:00 app[web.1]:
- 2019-02-07T12:14:50.495267+00:00 app[web.1]: 2019-02-07 12:14:50.488 INFO 4 --- [ main] c.e.a.api.AlgamoneyApiApplication : Starting AlgamoneyApiApplication v1.0.0-SNAPSHOT on 01743a0a-5e65-4861-8cf0-7edb3fcc38a3 with PID 4 (/app/target/algamoney-api-1.0.0-SNAPSHOT.jar started by u11286 in /app)
- 2019-02-07T12:14:50.495725+00:00 app[web.1]: 2019-02-07 12:14:50.495 INFO 4 --- [ main] c.e.a.api.AlgamoneyApiApplication : No active profile set, falling back to default profiles: default
- 2019-02-07T12:14:50.733954+00:00 app[web.1]: 2019-02-07 12:14:50.733 INFO 4 --- [ main] ationConfigEmbeddedWebApplicationContext : Refreshing org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@4b9af9a9: startup date [Thu Feb 07 12:14:50 UTC 2019]; root of context hierarchy
- 2019-02-07T12:14:58.369894+00:00 app[web.1]: 2019-02-07 12:14:58.369 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$3d2de98f] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.511452+00:00 app[web.1]: 2019-02-07 12:14:58.511 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration' of type [org.springframework.security.config.annotation.configuration.ObjectPostProcessorConfiguration$$EnhancerBySpringCGLIB$$d5dbb1c9] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.528710+00:00 app[web.1]: 2019-02-07 12:14:58.528 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'objectPostProcessor' of type [org.springframework.security.config.annotation.configuration.AutowireBeanFactoryObjectPostProcessor] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.535694+00:00 app[web.1]: 2019-02-07 12:14:58.535 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.security.access.expression.method.DefaultMethodSecurityExpressionHandler@240237d2' of type [org.springframework.security.oauth2.provider.expression.OAuth2MethodSecurityExpressionHandler] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.592007+00:00 app[web.1]: 2019-02-07 12:14:58.591 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean '(inner bean)#23282c25' of type [org.springframework.beans.factory.config.PropertiesFactoryBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.592722+00:00 app[web.1]: 2019-02-07 12:14:58.592 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean '(inner bean)#23282c25' of type [java.util.Properties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.602715+00:00 app[web.1]: 2019-02-07 12:14:58.602 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean '(inner bean)#4b168fa9' of type [org.springframework.data.repository.core.support.PropertiesBasedNamedQueries] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.610082+00:00 app[web.1]: 2019-02-07 12:14:58.609 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean '(inner bean)#3b2cf7ab' of type [org.springframework.data.repository.query.ExtensionAwareEvaluationContextProvider] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.688780+00:00 app[web.1]: 2019-02-07 12:14:58.688 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$$EnhancerBySpringCGLIB$$67a780f9] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.766142+00:00 app[web.1]: 2019-02-07 12:14:58.765 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'stringOrNumberMigrationVersionConverter' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$StringOrNumberToMigrationVersionConverter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.822448+00:00 app[web.1]: 2019-02-07 12:14:58.822 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'flyway-org.springframework.boot.autoconfigure.flyway.FlywayProperties' of type [org.springframework.boot.autoconfigure.flyway.FlywayProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.851184+00:00 app[web.1]: 2019-02-07 12:14:58.850 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jdbc.DataSourceConfiguration$Tomcat' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceConfiguration$Tomcat] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:58.911171+00:00 app[web.1]: 2019-02-07 12:14:58.910 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.datasource-org.springframework.boot.autoconfigure.jdbc.DataSourceProperties' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:59.467932+00:00 app[web.1]: 2019-02-07 12:14:59.467 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'dataSource' of type [org.apache.tomcat.jdbc.pool.DataSource] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:59.482877+00:00 app[web.1]: 2019-02-07 12:14:59.482 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceAutoConfiguration$$EnhancerBySpringCGLIB$$1f218cef] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:59.513333+00:00 app[web.1]: 2019-02-07 12:14:59.512 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'dataSourceInitializer' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceInitializer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:59.523381+00:00 app[web.1]: 2019-02-07 12:14:59.522 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$FlywayConfiguration' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$FlywayConfiguration$$EnhancerBySpringCGLIB$$bd2bb72f] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:59.581750+00:00 app[web.1]: 2019-02-07 12:14:59.581 INFO 4 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'flyway' of type [org.springframework.boot.autoconfigure.flyway.FlywayAutoConfiguration$SpringBootFlyway] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
- 2019-02-07T12:14:59.595499+00:00 app[web.1]: 2019-02-07 12:14:59.595 INFO 4 --- [ main] o.f.core.internal.util.VersionPrinter : Flyway 3.2.1 by Boxfuse
- 2019-02-07T12:15:00.165601+00:00 app[web.1]: Thu Feb 07 12:15:00 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
- 2019-02-07T12:15:01.396500+00:00 app[web.1]: Thu Feb 07 12:15:01 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
- 2019-02-07T12:15:01.516709+00:00 app[web.1]: Thu Feb 07 12:15:01 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
- 2019-02-07T12:15:01.654272+00:00 app[web.1]: Thu Feb 07 12:15:01 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
- 2019-02-07T12:15:01.855673+00:00 app[web.1]: Thu Feb 07 12:15:01 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
- 2019-02-07T12:15:01.973316+00:00 app[web.1]: Thu Feb 07 12:15:01 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
- 2019-02-07T12:15:02.245497+00:00 app[web.1]: Thu Feb 07 12:15:02 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
- 2019-02-07T12:15:02.333848+00:00 app[web.1]: Thu Feb 07 12:15:02 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
- 2019-02-07T12:15:02.404247+00:00 app[web.1]: Thu Feb 07 12:15:02 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
- 2019-02-07T12:15:02.428653+00:00 app[web.1]: Thu Feb 07 12:15:02 UTC 2019 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
- 2019-02-07T12:15:02.739875+00:00 app[web.1]: 2019-02-07 12:15:02.739 INFO 4 --- [ main] o.f.c.i.dbsupport.DbSupportFactory : Database: jdbc:mysql://axxb6a0z2kydkco3.cbetxkdyhwsb.us-east-1.rds.amazonaws.com:3306/tr6kyeactg7juy8g (MySQL 5.7)
- 2019-02-07T12:15:03.023285+00:00 app[web.1]: 2019-02-07 12:15:03.023 INFO 4 --- [ main] o.f.core.internal.command.DbValidate : Validated 4 migrations (execution time 00:00.127s)
- 2019-02-07T12:15:03.173493+00:00 app[web.1]: 2019-02-07 12:15:03.173 INFO 4 --- [ main] o.f.core.internal.command.DbMigrate : Current version of schema `tr6kyeactg7juy8g`: 03
- 2019-02-07T12:15:03.184064+00:00 app[web.1]: 2019-02-07 12:15:03.183 WARN 4 --- [ main] ationConfigEmbeddedWebApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'resourceServerFilterChainOrderProcessor' defined in class path resource [org/springframework/boot/autoconfigure/security/oauth2/resource/OAuth2ResourceServerConfiguration.class]: BeanPostProcessor before instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'metaDataSourceAdvisor': Cannot resolve reference to bean 'methodSecurityMetadataSource' while setting constructor argument; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.security.config.annotation.method.configuration.GlobalMethodSecurityConfiguration': Unsatisfied dependency expressed through method 'setMethodSecurityExpressionHandler' parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'resourceServiceConfig': Unsatisfied dependency expressed through field 'userDetailsService'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'appUserDetailsService': Unsatisfied dependency expressed through field 'usuarioRepository'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'usuarioRepository': Cannot create inner bean '(inner bean)#5ad851c9' of type [org.springframework.orm.jpa.SharedEntityManagerCreator] while setting bean property 'entityManager'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)#5ad851c9': Cannot resolve reference to bean 'entityManagerFactory' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.api.FlywayException: Schema `tr6kyeactg7juy8g` contains a failed migration to version 03 !
- 2019-02-07T12:15:03.236831+00:00 app[web.1]: 2019-02-07 12:15:03.232 ERROR 4 --- [ main] o.s.b.f.s.DefaultListableBeanFactory : Destroy method on bean with name 'dataSourceInitializer' threw an exception
- 2019-02-07T12:15:03.236835+00:00 app[web.1]:
- 2019-02-07T12:15:03.236838+00:00 app[web.1]: java.lang.IllegalStateException: ApplicationEventMulticaster not initialized - call 'refresh' before multicasting events via the context: org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@4b9af9a9: startup date [Thu Feb 07 12:14:50 UTC 2019]; root of context hierarchy
- 2019-02-07T12:15:03.236848+00:00 app[web.1]: at org.springframework.context.support.AbstractApplicationContext.getApplicationEventMulticaster(AbstractApplicationContext.java:404) [spring-context-4.3.8.RELEASE.jar!/:4.3.8.RELEASE]
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement