New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Job sometimes does not execute #3931
Labels
Comments
tyrng
added
status: waiting-for-triage
Issues that we did not analyse yet
type: bug
labels
Jun 7, 2021
Attached the specific job config that is used in the logs in my original post:
|
Closing this issue as we found that printStackTrace() outputs to STDERR instead of STDOUT, which our script is not able to produce in the log file output. And the printed error seems to be caused by #1448 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
We currently launch our jobs using command line arguments (the main function we used is attached below). We have a collection of Bash scripts that run the jobs separately, hence the job names would not contain human typing error during execution (we have tested each script thoroughly). However, sometimes, and without a clear pattern, some jobs would not be executed at all (refer to the logs attached), nor any new entry inserted into BATCH_JOB_EXECUTION and BATCH_STEP_EXECUTION.
Environment
Spring Batch 2.1.7
Java 1.8
SQL Server 2017
Steps to reproduce
Run the Java application with job name as the command line argument.
Expected behavior
Job should always execute, the execution should be shown in the logs, new entries should be able to be seen in BATCH_JOB_EXECUTION and BATCH_STEP_EXECUTION.
Minimal Complete Reproducible example
Main function:
Log when the job is executed normally:
Log when the job randomly does not execute:
The text was updated successfully, but these errors were encountered: