[ https://issues.jboss.org/browse/WFLY-4448?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-4448: ------------------------------------- The resources to display batch jobs from the console will live on the deployment. In CLI the path is {{/deployment=my.war/subsystem=batch/}}. This is where jobs will be displayed by the job name. {code:title=Example CLI output} [standalone@localhost:9990 /] /deployment=batch-chunk.war/subsystem=batch:read-resource(include-runtime=true,recursive=true) { "outcome" => "success", "result" => {"job" => {"chunkPartition" => { "instance-count" => 1, "running-executions" => 0, "execution" => {"1" => { "batch-status" => "COMPLETED", "create-time" => "2015-04-14T11:29:39.008-0700", "end-time" => "2015-04-14T11:29:39.033-0700", "exit-status" => "COMPLETED", "instance-id" => 1L, "last-updated-time" => "2015-04-14T11:29:39.033-0700", "start-time" => "2015-04-14T11:29:39.008-0700" }} }}} } {code} If a deployment uses a shared JDBC data source (the only current option) they could see all jobs from all applications using the same data source. The management operations will limit the available jobs to those allowed to be seen by the deployment. We may be able to add that constraint by overriding the {{JobOperator}}. I'm not sure we want to go there at this point though. -- This message was sent by Atlassian JIRA (v6.3.11#6341)