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

Add batch-jberet subsystem to replace the original batch subsystem

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 10.0.0.Beta1
    • None
    • Batch
    • None

    Description

      The original batch subsystem will not work well with capabilities and requirements. It's also fairly limited in the validation it can offer for the job repositories.

      Current model:

      {
    "outcome" => "success",
    "result" => {
        "job-repository-type" => "in-memory",
        "job-repository" => {"jdbc" => {"jndi-name" => undefined}},
        "thread-factory" => undefined,
        "thread-pool" => {"batch" => {
            "keepalive-time" => {
                "time" => 30L,
                "unit" => "SECONDS"
            },
            "max-threads" => 10,
            "name" => "batch",
            "thread-factory" => undefined
        }}
    }
}

      The job-repository-type will be removed as well as the job-repository=jdbc. A new jdbc-job-repository and in-memory-job-repository resource will be added. There will also be a default-job-repository which will accept a name from one of the defined job repositories.

      The jndi-name will no longer be used and a data-source name will be used for the JDBC job repository. For example resource value might be ExampleDS.

      A new deployment descriptor will be added to allow a user to defined a job repository configured on the subsystem.

      Due to these changes the persisted XML will likely need some small alterations. Mainly ensuring a name attribute is persisted and multiple repositories are allowed to be defined.

      The current batch subsystem will remain. It will allow the server to boot with old configurations, but the default with be the new batch-jberet subsystem.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users WFLY-4628 Add ability to restart and stop batch jobs

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-4634 Cannot start JDBC storage for Batch subsystem with the Driver in a deployment

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-4773 CLI pretends that it's possible to change JDBC job repository JNDI name even for in-memory repository type

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-4776 Missing batch JDBC job repository JNDI name validation

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is blocked by

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-4825 Add capabilities and requirements for data sources

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              jperkins-rhn James Perkins
              jperkins-rhn James Perkins
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: