[jboss-jira] [JBoss JIRA] (WFLY-4448) Batch creates a JdbcJobRepository per deployment where only one global repository should be used

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059013#comment-13059013 ] 

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 at 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.

> Batch creates a JdbcJobRepository per deployment where only one global repository should be used
> ------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-4448
>                 URL: https://issues.jboss.org/browse/WFLY-4448
>             Project: WildFly
>          Issue Type: Bug
>          Components: Batch
>            Reporter: James Perkins
>            Assignee: James Perkins
>
> When the batch subsystem is configured to use a JDBC job repository a new {{JdbcJobRepository}} is created for each application deployed. A global {{JdbcJobRepository}} should be used.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)