Mixing
How to stop Job in Spring Batch remote chunking, when slaves are completed?
0
I am using this example as a starting point for a spring batch app, using remote chunking:
https://github.com/benas/spring-batch-remote-chunking-sample/blob/master/src/main/java/io/github/benas/MasterConfiguration.java
Over this example, I've added my custom readers/writers, but I didn't changed any configuration. The example works fine, except that I can not stop the job after all slaves are completed.
I've tried using a JobListner, to stop the job inside 'afterJob' method, but no results.
public class MyJobExecutionListener implements JobExecutionListener {
@Override
public void beforeJob(JobExecution jobExecution) {
// TODO Auto-generated method stub
}
@Override
public void afterJob(JobExecution jobExecution) {
System.out.println("afterJob start~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
System.out.println(jobExecution.getExitStatus().getExitCode());
System.out.println(jobExecution.getExitStatus().getExitDescription());
System.out.println(jobExecution.getStartTime());
System.out.println(jobExecution.getEndTime());
System.out.println(jobExecution.isRunning());
System.out.println(jobExecution.isStopping());
jobExecution.stop();
System.out.println("!!!!!!!!!");
System.out.println(jobExecution.isRunning());
System.out.println(jobExecution.isStopping());
System.out.println(jobExecution.getEndTime());
System.out.println("afterJob end~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
}
}
jobExecution.getExitStatus().getExitCode() is COMPLETED
jobExecution.isStopping() is true, but the app is still running.
To run the app, I'm using SpringBoot (instead running it as unit test, as it is in the example)
@SpringBootApplication
@EnableAutoConfiguration(exclude={DataSourceAutoConfiguration.class})
public class AppStarter {
public static void main(String args) {
System.out.println("!!!!!!!!!!!!!!!!!!!!!!!!!!! start");
SpringApplication.run(AppStarter.class, args);
}
}
Is there a way to stop the app when completed ?
java spring-batch
edited Jan 2 at 20:56
Mahmoud Ben Hassine
5,4051717
asked Jan 2 at 20:31
AdrianAdrian
156
add a comment |
0
I am using this example as a starting point for a spring batch app, using remote chunking:
https://github.com/benas/spring-batch-remote-chunking-sample/blob/master/src/main/java/io/github/benas/MasterConfiguration.java
Over this example, I've added my custom readers/writers, but I didn't changed any configuration. The example works fine, except that I can not stop the job after all slaves are completed.
I've tried using a JobListner, to stop the job inside 'afterJob' method, but no results.
public class MyJobExecutionListener implements JobExecutionListener {
@Override
public void beforeJob(JobExecution jobExecution) {
// TODO Auto-generated method stub
}
@Override
public void afterJob(JobExecution jobExecution) {
System.out.println("afterJob start~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
System.out.println(jobExecution.getExitStatus().getExitCode());
System.out.println(jobExecution.getExitStatus().getExitDescription());
System.out.println(jobExecution.getStartTime());
System.out.println(jobExecution.getEndTime());
System.out.println(jobExecution.isRunning());
System.out.println(jobExecution.isStopping());
jobExecution.stop();
System.out.println("!!!!!!!!!");
System.out.println(jobExecution.isRunning());
System.out.println(jobExecution.isStopping());
System.out.println(jobExecution.getEndTime());
System.out.println("afterJob end~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
}
}
jobExecution.getExitStatus().getExitCode() is COMPLETED
jobExecution.isStopping() is true, but the app is still running.
To run the app, I'm using SpringBoot (instead running it as unit test, as it is in the example)
@SpringBootApplication
@EnableAutoConfiguration(exclude={DataSourceAutoConfiguration.class})
public class AppStarter {
public static void main(String args) {
System.out.println("!!!!!!!!!!!!!!!!!!!!!!!!!!! start");
SpringApplication.run(AppStarter.class, args);
}
}
Is there a way to stop the app when completed ?
java spring-batch
edited Jan 2 at 20:56
Mahmoud Ben Hassine
5,4051717
asked Jan 2 at 20:31
AdrianAdrian
156
The master should be stopped automatically. There is something else preventing the application context from stopping (either aThreadPoolTaskExecutoror some Spring Integration components that need to be explicitly stopped). Do you have one of those in your app? I know you said you didn't changed any configuration but since you are using Spring Boot, it might have added a couple of things implicitly. Can you share your repo?
– Mahmoud Ben Hassine
Jan 2 at 21:16
The code is local, on a VM, so I can not publish it on a public repo. In the master configuration class, I have: ` @Configuration @EnableBatchProcessing @EnableIntegration @PropertySource("classpath:application.properties") `
– Adrian
Jan 2 at 21:19
I am also using JMS to communicate between master and slaves:@Bean public IntegrationFlow outboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(masterRequests()) .handle(Jms.outboundAdapter(jmsConnectionFactory).destination("requests")) .get(); } @Bean public IntegrationFlow masterInboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(Jms.messageDrivenChannelAdapter(jmsConnectionFactory).destination("replies")) .channel(masterReplies()) .get(); }
– Adrian
Jan 2 at 21:26
sorry for formatting, I'm still getting used with it
– Adrian
Jan 2 at 21:26
add a comment |
0
0
0
I am using this example as a starting point for a spring batch app, using remote chunking:
https://github.com/benas/spring-batch-remote-chunking-sample/blob/master/src/main/java/io/github/benas/MasterConfiguration.java
Over this example, I've added my custom readers/writers, but I didn't changed any configuration. The example works fine, except that I can not stop the job after all slaves are completed.
I've tried using a JobListner, to stop the job inside 'afterJob' method, but no results.
public class MyJobExecutionListener implements JobExecutionListener {
@Override
public void beforeJob(JobExecution jobExecution) {
// TODO Auto-generated method stub
}
@Override
public void afterJob(JobExecution jobExecution) {
System.out.println("afterJob start~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
System.out.println(jobExecution.getExitStatus().getExitCode());
System.out.println(jobExecution.getExitStatus().getExitDescription());
System.out.println(jobExecution.getStartTime());
System.out.println(jobExecution.getEndTime());
System.out.println(jobExecution.isRunning());
System.out.println(jobExecution.isStopping());
jobExecution.stop();
System.out.println("!!!!!!!!!");
System.out.println(jobExecution.isRunning());
System.out.println(jobExecution.isStopping());
System.out.println(jobExecution.getEndTime());
System.out.println("afterJob end~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
}
}
jobExecution.getExitStatus().getExitCode() is COMPLETED
jobExecution.isStopping() is true, but the app is still running.
To run the app, I'm using SpringBoot (instead running it as unit test, as it is in the example)
@SpringBootApplication
@EnableAutoConfiguration(exclude={DataSourceAutoConfiguration.class})
public class AppStarter {
public static void main(String args) {
System.out.println("!!!!!!!!!!!!!!!!!!!!!!!!!!! start");
SpringApplication.run(AppStarter.class, args);
}
}
Is there a way to stop the app when completed ?
java spring-batch
edited Jan 2 at 20:56
Mahmoud Ben Hassine
5,4051717
asked Jan 2 at 20:31
AdrianAdrian
156
I am using this example as a starting point for a spring batch app, using remote chunking:
https://github.com/benas/spring-batch-remote-chunking-sample/blob/master/src/main/java/io/github/benas/MasterConfiguration.java
Over this example, I've added my custom readers/writers, but I didn't changed any configuration. The example works fine, except that I can not stop the job after all slaves are completed.
I've tried using a JobListner, to stop the job inside 'afterJob' method, but no results.
public class MyJobExecutionListener implements JobExecutionListener {
@Override
public void beforeJob(JobExecution jobExecution) {
// TODO Auto-generated method stub
}
@Override
public void afterJob(JobExecution jobExecution) {
System.out.println("afterJob start~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
System.out.println(jobExecution.getExitStatus().getExitCode());
System.out.println(jobExecution.getExitStatus().getExitDescription());
System.out.println(jobExecution.getStartTime());
System.out.println(jobExecution.getEndTime());
System.out.println(jobExecution.isRunning());
System.out.println(jobExecution.isStopping());
jobExecution.stop();
System.out.println("!!!!!!!!!");
System.out.println(jobExecution.isRunning());
System.out.println(jobExecution.isStopping());
System.out.println(jobExecution.getEndTime());
System.out.println("afterJob end~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~");
}
}
jobExecution.getExitStatus().getExitCode() is COMPLETED
jobExecution.isStopping() is true, but the app is still running.
To run the app, I'm using SpringBoot (instead running it as unit test, as it is in the example)
@SpringBootApplication
@EnableAutoConfiguration(exclude={DataSourceAutoConfiguration.class})
public class AppStarter {
public static void main(String args) {
System.out.println("!!!!!!!!!!!!!!!!!!!!!!!!!!! start");
SpringApplication.run(AppStarter.class, args);
}
}
Is there a way to stop the app when completed ?
java spring-batch
java spring-batch
edited Jan 2 at 20:56
Mahmoud Ben Hassine
5,4051717
asked Jan 2 at 20:31
AdrianAdrian
156
edited Jan 2 at 20:56
Mahmoud Ben Hassine
5,4051717
asked Jan 2 at 20:31
AdrianAdrian
156
edited Jan 2 at 20:56
Mahmoud Ben Hassine
5,4051717
edited Jan 2 at 20:56
Mahmoud Ben Hassine
5,4051717
edited Jan 2 at 20:56
Mahmoud Ben Hassine
5,4051717
5,4051717
asked Jan 2 at 20:31
AdrianAdrian
156
asked Jan 2 at 20:31
AdrianAdrian
156
asked Jan 2 at 20:31
AdrianAdrian
156
156
The master should be stopped automatically. There is something else preventing the application context from stopping (either aThreadPoolTaskExecutoror some Spring Integration components that need to be explicitly stopped). Do you have one of those in your app? I know you said you didn't changed any configuration but since you are using Spring Boot, it might have added a couple of things implicitly. Can you share your repo?
– Mahmoud Ben Hassine
Jan 2 at 21:16
The code is local, on a VM, so I can not publish it on a public repo. In the master configuration class, I have: ` @Configuration @EnableBatchProcessing @EnableIntegration @PropertySource("classpath:application.properties") `
– Adrian
Jan 2 at 21:19
I am also using JMS to communicate between master and slaves:@Bean public IntegrationFlow outboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(masterRequests()) .handle(Jms.outboundAdapter(jmsConnectionFactory).destination("requests")) .get(); } @Bean public IntegrationFlow masterInboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(Jms.messageDrivenChannelAdapter(jmsConnectionFactory).destination("replies")) .channel(masterReplies()) .get(); }
– Adrian
Jan 2 at 21:26
sorry for formatting, I'm still getting used with it
– Adrian
Jan 2 at 21:26
add a comment |
The master should be stopped automatically. There is something else preventing the application context from stopping (either aThreadPoolTaskExecutoror some Spring Integration components that need to be explicitly stopped). Do you have one of those in your app? I know you said you didn't changed any configuration but since you are using Spring Boot, it might have added a couple of things implicitly. Can you share your repo?
– Mahmoud Ben Hassine
Jan 2 at 21:16
The code is local, on a VM, so I can not publish it on a public repo. In the master configuration class, I have: ` @Configuration @EnableBatchProcessing @EnableIntegration @PropertySource("classpath:application.properties") `
– Adrian
Jan 2 at 21:19
I am also using JMS to communicate between master and slaves:@Bean public IntegrationFlow outboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(masterRequests()) .handle(Jms.outboundAdapter(jmsConnectionFactory).destination("requests")) .get(); } @Bean public IntegrationFlow masterInboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(Jms.messageDrivenChannelAdapter(jmsConnectionFactory).destination("replies")) .channel(masterReplies()) .get(); }
– Adrian
Jan 2 at 21:26
sorry for formatting, I'm still getting used with it
– Adrian
Jan 2 at 21:26
The master should be stopped automatically. There is something else preventing the application context from stopping (either a
ThreadPoolTaskExecutor or some Spring Integration components that need to be explicitly stopped). Do you have one of those in your app? I know you said you didn't changed any configuration but since you are using Spring Boot, it might have added a couple of things implicitly. Can you share your repo?– Mahmoud Ben Hassine
Jan 2 at 21:16
The master should be stopped automatically. There is something else preventing the application context from stopping (either a
ThreadPoolTaskExecutor or some Spring Integration components that need to be explicitly stopped). Do you have one of those in your app? I know you said you didn't changed any configuration but since you are using Spring Boot, it might have added a couple of things implicitly. Can you share your repo?– Mahmoud Ben Hassine
Jan 2 at 21:16
The code is local, on a VM, so I can not publish it on a public repo. In the master configuration class, I have: ` @Configuration @EnableBatchProcessing @EnableIntegration @PropertySource("classpath:application.properties") `
– Adrian
Jan 2 at 21:19
The code is local, on a VM, so I can not publish it on a public repo. In the master configuration class, I have: ` @Configuration @EnableBatchProcessing @EnableIntegration @PropertySource("classpath:application.properties") `
– Adrian
Jan 2 at 21:19
I am also using JMS to communicate between master and slaves:
@Bean public IntegrationFlow outboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(masterRequests()) .handle(Jms.outboundAdapter(jmsConnectionFactory).destination("requests")) .get(); } @Bean public IntegrationFlow masterInboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(Jms.messageDrivenChannelAdapter(jmsConnectionFactory).destination("replies")) .channel(masterReplies()) .get(); }– Adrian
Jan 2 at 21:26
I am also using JMS to communicate between master and slaves:
@Bean public IntegrationFlow outboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(masterRequests()) .handle(Jms.outboundAdapter(jmsConnectionFactory).destination("requests")) .get(); } @Bean public IntegrationFlow masterInboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(Jms.messageDrivenChannelAdapter(jmsConnectionFactory).destination("replies")) .channel(masterReplies()) .get(); }– Adrian
Jan 2 at 21:26
sorry for formatting, I'm still getting used with it
– Adrian
Jan 2 at 21:26
sorry for formatting, I'm still getting used with it
– Adrian
Jan 2 at 21:26
add a comment |
1 Answer
1
active
oldest
votes
0
You can stop the application context of the master explicitly with something like:
ConfigurableApplicationContext context = SpringApplication.run(YourMasterApp.class, args);
context.close();
This will ensure the master side has finished running the job and then close the application context.
A couple of notes though:
- You can find the same sample in the official samples repo here: https://github.com/spring-projects/spring-batch/tree/master/spring-batch-samples#remote-chunking-sample. The personal repo you used as a starting point may be deleted at any time
- Using
jobExecution.stop()in theafterJobmethod of the listener make no sense because thisafterJobmethod is almost the last statement before ending the job anyway. Moreover, thisjobExecution.stop()will be removed in a future version (see https://jira.spring.io/browse/BATCH-1987)
Hope this helps.
answered Jan 2 at 21:48
Mahmoud Ben HassineMahmoud Ben Hassine
5,4051717
Yep, works great. Thank you!
– Adrian
Jan 2 at 22:03
Also, I've received some updates and I have to start the Job from a controller. Better for me, since it can be started using something likejobLauncher.run(job, new JobParameters());So, I'll have access to the JobLauncher and have easier control (at least for me).
– Adrian
Jan 2 at 22:06
Glad it helped!
– Mahmoud Ben Hassine
Jan 2 at 22:34
add a comment |
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54012777%2fhow-to-stop-job-in-spring-batch-remote-chunking-when-slaves-are-completed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
You can stop the application context of the master explicitly with something like:
ConfigurableApplicationContext context = SpringApplication.run(YourMasterApp.class, args);
context.close();
This will ensure the master side has finished running the job and then close the application context.
A couple of notes though:
- You can find the same sample in the official samples repo here: https://github.com/spring-projects/spring-batch/tree/master/spring-batch-samples#remote-chunking-sample. The personal repo you used as a starting point may be deleted at any time
- Using
jobExecution.stop()in theafterJobmethod of the listener make no sense because thisafterJobmethod is almost the last statement before ending the job anyway. Moreover, thisjobExecution.stop()will be removed in a future version (see https://jira.spring.io/browse/BATCH-1987)
Hope this helps.
answered Jan 2 at 21:48
Mahmoud Ben HassineMahmoud Ben Hassine
5,4051717
Yep, works great. Thank you!
– Adrian
Jan 2 at 22:03
Also, I've received some updates and I have to start the Job from a controller. Better for me, since it can be started using something likejobLauncher.run(job, new JobParameters());So, I'll have access to the JobLauncher and have easier control (at least for me).
– Adrian
Jan 2 at 22:06
Glad it helped!
– Mahmoud Ben Hassine
Jan 2 at 22:34
add a comment |
0
You can stop the application context of the master explicitly with something like:
ConfigurableApplicationContext context = SpringApplication.run(YourMasterApp.class, args);
context.close();
This will ensure the master side has finished running the job and then close the application context.
A couple of notes though:
- You can find the same sample in the official samples repo here: https://github.com/spring-projects/spring-batch/tree/master/spring-batch-samples#remote-chunking-sample. The personal repo you used as a starting point may be deleted at any time
- Using
jobExecution.stop()in theafterJobmethod of the listener make no sense because thisafterJobmethod is almost the last statement before ending the job anyway. Moreover, thisjobExecution.stop()will be removed in a future version (see https://jira.spring.io/browse/BATCH-1987)
Hope this helps.
answered Jan 2 at 21:48
Mahmoud Ben HassineMahmoud Ben Hassine
5,4051717
Yep, works great. Thank you!
– Adrian
Jan 2 at 22:03
Also, I've received some updates and I have to start the Job from a controller. Better for me, since it can be started using something likejobLauncher.run(job, new JobParameters());So, I'll have access to the JobLauncher and have easier control (at least for me).
– Adrian
Jan 2 at 22:06
Glad it helped!
– Mahmoud Ben Hassine
Jan 2 at 22:34
add a comment |
0
0
0
You can stop the application context of the master explicitly with something like:
ConfigurableApplicationContext context = SpringApplication.run(YourMasterApp.class, args);
context.close();
This will ensure the master side has finished running the job and then close the application context.
A couple of notes though:
- You can find the same sample in the official samples repo here: https://github.com/spring-projects/spring-batch/tree/master/spring-batch-samples#remote-chunking-sample. The personal repo you used as a starting point may be deleted at any time
- Using
jobExecution.stop()in theafterJobmethod of the listener make no sense because thisafterJobmethod is almost the last statement before ending the job anyway. Moreover, thisjobExecution.stop()will be removed in a future version (see https://jira.spring.io/browse/BATCH-1987)
Hope this helps.
answered Jan 2 at 21:48
Mahmoud Ben HassineMahmoud Ben Hassine
5,4051717
You can stop the application context of the master explicitly with something like:
ConfigurableApplicationContext context = SpringApplication.run(YourMasterApp.class, args);
context.close();
This will ensure the master side has finished running the job and then close the application context.
A couple of notes though:
- You can find the same sample in the official samples repo here: https://github.com/spring-projects/spring-batch/tree/master/spring-batch-samples#remote-chunking-sample. The personal repo you used as a starting point may be deleted at any time
- Using
jobExecution.stop()in theafterJobmethod of the listener make no sense because thisafterJobmethod is almost the last statement before ending the job anyway. Moreover, thisjobExecution.stop()will be removed in a future version (see https://jira.spring.io/browse/BATCH-1987)
Hope this helps.
answered Jan 2 at 21:48
Mahmoud Ben HassineMahmoud Ben Hassine
5,4051717
answered Jan 2 at 21:48
Mahmoud Ben HassineMahmoud Ben Hassine
5,4051717
answered Jan 2 at 21:48
Mahmoud Ben HassineMahmoud Ben Hassine
5,4051717
answered Jan 2 at 21:48
Mahmoud Ben HassineMahmoud Ben Hassine
5,4051717
5,4051717
Yep, works great. Thank you!
– Adrian
Jan 2 at 22:03
Also, I've received some updates and I have to start the Job from a controller. Better for me, since it can be started using something likejobLauncher.run(job, new JobParameters());So, I'll have access to the JobLauncher and have easier control (at least for me).
– Adrian
Jan 2 at 22:06
Glad it helped!
– Mahmoud Ben Hassine
Jan 2 at 22:34
add a comment |
Yep, works great. Thank you!
– Adrian
Jan 2 at 22:03
Also, I've received some updates and I have to start the Job from a controller. Better for me, since it can be started using something likejobLauncher.run(job, new JobParameters());So, I'll have access to the JobLauncher and have easier control (at least for me).
– Adrian
Jan 2 at 22:06
Glad it helped!
– Mahmoud Ben Hassine
Jan 2 at 22:34
Yep, works great. Thank you!
– Adrian
Jan 2 at 22:03
Yep, works great. Thank you!
– Adrian
Jan 2 at 22:03
Also, I've received some updates and I have to start the Job from a controller. Better for me, since it can be started using something like
jobLauncher.run(job, new JobParameters()); So, I'll have access to the JobLauncher and have easier control (at least for me).– Adrian
Jan 2 at 22:06
Also, I've received some updates and I have to start the Job from a controller. Better for me, since it can be started using something like
jobLauncher.run(job, new JobParameters()); So, I'll have access to the JobLauncher and have easier control (at least for me).– Adrian
Jan 2 at 22:06
Glad it helped!
– Mahmoud Ben Hassine
Jan 2 at 22:34
Glad it helped!
– Mahmoud Ben Hassine
Jan 2 at 22:34
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54012777%2fhow-to-stop-job-in-spring-batch-remote-chunking-when-slaves-are-completed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The master should be stopped automatically. There is something else preventing the application context from stopping (either a
ThreadPoolTaskExecutoror some Spring Integration components that need to be explicitly stopped). Do you have one of those in your app? I know you said you didn't changed any configuration but since you are using Spring Boot, it might have added a couple of things implicitly. Can you share your repo?– Mahmoud Ben Hassine
Jan 2 at 21:16
The code is local, on a VM, so I can not publish it on a public repo. In the master configuration class, I have: ` @Configuration @EnableBatchProcessing @EnableIntegration @PropertySource("classpath:application.properties") `
– Adrian
Jan 2 at 21:19
I am also using JMS to communicate between master and slaves:
@Bean public IntegrationFlow outboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(masterRequests()) .handle(Jms.outboundAdapter(jmsConnectionFactory).destination("requests")) .get(); } @Bean public IntegrationFlow masterInboundFlow(ActiveMQConnectionFactory jmsConnectionFactory) { return IntegrationFlows.from(Jms.messageDrivenChannelAdapter(jmsConnectionFactory).destination("replies")) .channel(masterReplies()) .get(); }– Adrian
Jan 2 at 21:26
sorry for formatting, I'm still getting used with it
– Adrian
Jan 2 at 21:26