1

I use jdbc job repository on wildfly. when I kill wildfly process some job execution remain in started state. When I restated wildfly i get running executions by BatchRuntime.getJobOperator().getRunningExecutions and give mentioned job executions. When I use in memory repository it's worked fine. I want to check number of really running execution.

mohammad_1m2
  • 1,571
  • 5
  • 19
  • 38
  • What version of WildFly are you running? Instead of killing the process have you trying something like `$JBOSS_HOME/bin/jboss-cli.sh -c ":shutdown"`? – James R. Perkins Jan 29 '18 at 07:45

1 Answers1

1

You should stop running batch job executions first before stopping WildFly or any application server. To clean up batch jobs stuck in running state after killing application server process, you can manually update the job repository database tables. But this should only be done with great caution so as not to compromise the job repository data.

cheng
  • 1,076
  • 6
  • 6
  • Thanks. How can I access to jobRepository? – mohammad_1m2 Jan 29 '18 at 06:19
  • You can connect to the database that is configured as the WildFly batch jdbc job repository, using the client tool for the database product (e.g., mysql command or mysql workbench). To find info on batch job repository, you can look at WildFly admin console, or WildFly CLI, or view server.xml. – cheng Jan 29 '18 at 12:39