简体   繁体   English

Spring Cloud DataFlow组成的任务无法启动

[英]Spring Cloud DataFlow Composed Task doesn't start

I'm trying to run SCDF Composed Task. 我正在尝试运行SCDF组合任务。 Any composed tasks that I create does the same thing: executes SQL script: 我创建的所有组合任务都执行相同的操作:执行SQL脚本:

Executing SQL script from class path resource [org/springframework/cloud/task/schema-h2.sql]` 从类路径资源[org / springframework / cloud / task / schema-h2.sql]中执行SQL脚本`

And on that point execution pauses. 在这一点上,执行暂停。 In Executions tab of SCDF Dashboard at Start time and End time I see N/A . Start timeEnd time的SCDF仪表板的“ Executions选项卡中,我看到N/A

I'm using Spring Cloud DataFlow 1.2.3.RELEASE and Composed Task Runner 1.0.0.RELEASE. 我正在使用Spring Cloud DataFlow 1.2.3.RELEASE和Composed Task Runner 1.0.0.RELEASE。

Here's the output from logs: 这是日志的输出:

2017-08-18 18:20:09.455 INFO 828 --- [ main] cccConfigServicePropertySourceLocator : Fetching config from server at: http://localhost:8888 2017-08-18 18:20:10.528 WARN 828 --- [ main] cccConfigServicePropertySourceLocator : Could not locate PropertySource: I/O error on GET request for " http://localhost:8888/composedtaskrunner-task/default ": Connection refused: connect; 2017-08-18 18:20:09.455信息828-[[main] cccConfigServicePropertySourceLocator:从以下位置的服务器获取配置: http:// localhost:8888 2017-08-18 18:20:10.528 WARN 828-[主要] cccConfigServicePropertySourceLocator:无法找到PropertySource:“ http:// localhost:8888 / composedtaskrunner -task / default ”的GET请求上的I / O错误:连接被拒绝:connect; nested exception is java.net.ConnectException: Connection refused: connect 2017-08-18 18:20:10.530 INFO 828 --- [ main] .tacComposedtaskrunnerTaskApplication : No active profile set, falling back to default profiles: default 2017-08-18 18:20:10.567 INFO 828 --- [ main] scaAnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@61a52fbd: startup date [Fri Aug 18 18:20:10 EEST 2017]; 嵌套异常是java.net.ConnectException:连接被拒绝:connect 2017-08-18 18:20:10.530 INFO 828 --- [main] .tacComposedtaskrunnerTaskApplication:未设置活动配置文件,回退到默认配置文件:默认2017-08- 18 18:20:10.567 INFO 828-[main] scaAnnotationConfigApplicationContext:刷新org.springframework.context.annotation.AnnotationConfigApplicationContext@61a52fbd:启动日期[2017年8月18日星期五18:20:10]; parent: org.springframework.context.annotation.AnnotationConfigApplicationContext@3b95a09c 2017-08-18 18:20:10.903 INFO 828 --- [ main] osbfsDefaultListableBeanFactory : Overriding bean definition for bean 'transactionManager' with a different definition: replacing [Root bean: class [null]; 父级:org.springframework.context.annotation.AnnotationConfigApplicationContext@3b95a09c 2017-08-18 18:20:10.903 INFO 828 --- [main] osbfsDefaultListableBeanFactory:使用不同的定义覆盖bean'transactionManager'的bean定义:替换[root bean :class [null]; scope=; 范围=; abstract=false; 抽象= FALSE; lazyInit=false; lazyInit = FALSE; autowireMode=3; autowireMode = 3; dependencyCheck=0; dependencyCheck = 0; autowireCandidate=true; autowireCandidate = TRUE; primary=false; 初级= FALSE; factoryBeanName=org.springframework.batch.core.configuration.annotation.SimpleBatchConfiguration; factoryBeanName = org.springframework.batch.core.configuration.annotation.SimpleBatchConfiguration; factoryMethodName=transactionManager; factoryMethodName = transactionManager的; initMethodName=null; initMethodName = NULL; destroyMethodName=(inferred); destroyMethodName =(推断); defined in class path resource [org/springframework/batch/core/configuration/annotation/SimpleBatchConfiguration.class]] with [Root bean: class [null]; 在类路径资源[org / springframework / batch / core / configuration / annotation / SimpleBatchConfiguration.class]中定义,并带有[Root bean:class [null]; scope=; 范围=; abstract=false; 抽象= FALSE; lazyInit=false; lazyInit = FALSE; autowireMode=3; autowireMode = 3; dependencyCheck=0; dependencyCheck = 0; autowireCandidate=true; autowireCandidate = TRUE; primary=false; 初级= FALSE; factoryBeanName=org.springframework.cloud.task.configuration.SimpleTaskConfiguration; factoryBeanName = org.springframework.cloud.task.configuration.SimpleTaskConfiguration; factoryMethodName=transactionManager; factoryMethodName = transactionManager的; initMethodName=null; initMethodName = NULL; destroyMethodName=(inferred); destroyMethodName =(推断); defined in class path resource [org/springframework/cloud/task/configuration/SimpleTaskConfiguration.class]] 2017-08-18 18:20:11.150 INFO 828 --- [ main] oscloud.context.scope.GenericScope : BeanFactory id=03034f55-14f0-32fd-9b4a-577a14282248 2017-08-18 18:20:11.161 WARN 828 --- [ main] oscaConfigurationClassEnhancer : @Bean method ScopeConfiguration.stepScope is non-static and returns an object assignable to Spring's BeanFactoryPostProcessor interface. 在类路径资源中定义[org / springframework / cloud / task / configuration / SimpleTaskConfiguration.class] 2017-08-18 18:20:11.150 INFO 828-[[main] oscloud.context.scope.GenericScope:BeanFactory id = 03034f55-14f0-32fd-9b4a-577a14282248 2017-08-18 18:20:11.161 WARN 828 --- [main] oscaConfigurationClassEnhancer:@Bean方法ScopeConfiguration.stepScope是非静态的,并返回可分配给Spring的BeanFactoryPostProcessor接口的对象。 This will result in a failure to process annotations such as @Autowired, @Resource and @PostConstruct within the method's declaring @Configuration class. 这将导致无法在方法的声明@Configuration类中处理诸如@ Autowired,@ Resource和@PostConstruct之类的注释。 Add the 'static' modifier to this method to avoid these container lifecycle issues; 在此方法中添加“静态”修饰符可避免这些容器生命周期问题; see @Bean javadoc for complete details. 有关完整的详细信息,请参见@Bean javadoc。 2017-08-18 18:20:11.167 WARN 828 --- [ main] oscaConfigurationClassEnhancer : @Bean method ScopeConfiguration.jobScope is non-static and returns an object assignable to Spring's BeanFactoryPostProcessor interface. 2017-08-18 18:20:11.167警告828 --- [main] oscaConfigurationClassEnhancer:@Bean方法ScopeConfiguration.jobScope是非静态的,并返回可分配给Spring的BeanFactoryPostProcessor接口的对象。 This will result in a failure to process annotations such as @Autowired, @Resource and @PostConstruct within the method's declaring @Configuration class. 这将导致无法在方法的声明@Configuration类中处理诸如@ Autowired,@ Resource和@PostConstruct之类的注释。 Add the 'static' modifier to this method to avoid these container lifecycle issues; 在此方法中添加“静态”修饰符可避免这些容器生命周期问题; see @Bean javadoc for complete details. 有关完整的详细信息,请参见@Bean javadoc。 2017-08-18 18:20:11.218 INFO 828 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$591cf5d8] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2017-08-18 18:20:11.224 INFO 828 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$3d02f2db] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2017-08-18 18:20:11.250 INFO 828 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.task.batch.configuration.TaskBatchAutoCo 2017-08-18 18:20:11.218信息828-[[主要] trationDelegate $ BeanPostProcessorChecker:类型[org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration $$ EnhancerBySpringCGLIB $的Bean'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' $ 591cf5d8]不符合所有BeanPostProcessor的处理要求(例如:不符合自动代理的条件)2017-08-18 18:20:11.224信息828-[[main] trationDelegate $ BeanPostProcessorChecker:Bean'org.springframework类型为[org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration $$ EnhancerBySpringCGLIB $$ 3d02f2db]的.transaction.annotation.ProxyTransactionManagementConfiguration'不符合所有BeanPostProcessor的处理条件(例如:不符合自动代理资格)2017-08- 18 18:20:11.250信息828-[main] trationDelegate $ BeanPostProcessorChecker:Bean'org.springframework.cloud.task.batch.configuration.TaskBatchAutoCo nfiguration' of type [org.springframework.cloud.task.batch.configuration.TaskBatchAutoConfiguration$$EnhancerBySpringCGLIB$$c2729e67] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2017-08-18 18:20:11.258 INFO 828 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.task.batch.listener.BatchEventAutoConfiguration' of type [org.springframework.cloud.task.batch.listener.BatchEventAutoConfiguration$$EnhancerBySpringCGLIB$$ac8a86a] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2017-08-18 18:20:11.655 INFO 828 --- [ main] osjdbc.datasource.init.ScriptUtils : Executing SQL script from class path resource [org/springframework/cloud/task/schema-h2.sql]` 类型为[org.springframework.cloud.task.batch.configuration.TaskBatchAutoConfiguration $$ EnhancerBySpringCGLIB $$ c2729e67]的nfiguration不适合所有BeanPostProcessor处理(例如:不符合自动代理资格)2017-08-18 18:20:11.258信息828-[main] trationDelegate $ BeanPostProcessorChecker:类型为[org.springframework.cloud.task.batch.listener.BatchEventAutoConfiguration'的Bean'org.springframework.cloud.task.batch.listener.BatchEventAutoConfiguration'类型$ EnhancerBySpringCGLIB $$ ac8a86a]不适合所有BeanPostProcessor处理(例如:不符合自动代理资格)2017-08-18 18:20:11.655 INFO 828 --- [main] osjdbc.datasource.init。 ScriptUtils:从类路径资源[org / springframework / cloud / task / schema-h2.sql]中执行SQL脚本`

And in server logs I see a lot of different characters changing over time, for ex.: "[0x0][0x0][0x8][0x8][0x0][0xfa]CaJ[\\r]3[0x99][0xd4]}[0x3][0x0][0x0][0x87][0x6][0x0][0x0]3[0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0xa4][0x81] c[\\n]" 在服务器日志中,我看到许多不同的字符随时间变化,例如: "[0x0][0x0][0x8][0x8][0x0][0xfa]CaJ[\\r]3[0x99][0xd4]}[0x3][0x0][0x0][0x87][0x6][0x0][0x0]3[0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0x0][0xa4][0x81] c[\\n]"

Sorry for formatting, cannot properly format output 很抱歉格式化,无法正确格式化输出

Solved. 解决了。 The problem was in h2 versions incompatibility in Composed Task Runner and SCDF. 问题出在组成任务运行程序和SCDF中的H2版本不兼容。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 Spring Cloud DataFlow多次运行组合任务 - Spring Cloud DataFlow run Composed Task multiple times 组成的任务运行器在Spring Cloud Dataflow Kubernetes服务器中失败 - Composed task runner failing in spring cloud dataflow kubernetes server Spring Cloud Dataflow Local Using dockerized Task - Spring Cloud Dataflow Local Using dockerized Task 在数据流服务器中运行时出现spring cloud task taskLifecycleListener错误 - spring cloud task taskLifecycleListener error when running in dataflow server 升级到Spring Cloud Dataflow任务的Spring Boot 2.0后无法反序列化执行上下文 - Unable to deserialize the execution context after upgrading to spring boot 2.0 for a spring cloud dataflow task Spring Cloud DataFlow自动运行 - Spring Cloud DataFlow automated run Spring Cloud Task Launcher 不响应发送到 Rabbit 的新事件 - Spring Cloud Task Launcher doesn't respond to new events sent to Rabbit Spring Cloud DataFlow 在 AWS S3 存储桶源中的新文件后使用启动任务 - Spring Cloud DataFlow using launch task after new file in AWS S3 Bucket source Spring Cloud Dataflow 无法启动 bean 'taskLifecycleListener'; 嵌套异常是 java.lang.IllegalArgumentException: Invalid TaskExecution - Spring cloud Dataflow Failed to start bean 'taskLifecycleListener'; nested exception is java.lang.IllegalArgumentException: Invalid TaskExecution 如何在 Spring Cloud Dataflow “Cloudfoundry”服务器启动时引用本地 Kafka 和 Zookeeper 配置 - How to reference local Kafka and Zookeeper config on Spring Cloud Dataflow “Cloudfoundry” server start
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM