Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-9658

Batch jobs in a sub-deployment can be started but not queried

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 13.0.0.Final
    • Component/s: Batch
    • Labels:
      None

      Description

      In an EAR deployment that contains a multiple batch deployments each sub-deployment can start jobs from other sub-deployments, but the job information cannot be queried. For example a job can be started from a WAR that is in an EJB, however you cannot execute JobOperator.getJobInstance() from the WAR on the same job.

      Visibility should be consistent for starting and querying batch jobs.

      More details on https://github.com/jberet/jsr352/issues/105.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jamezp James Perkins
                  Reporter:
                  jamezp James Perkins
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: