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

Large job repository is blocking deployment

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 23.0.0.Beta1, 23.0.0.Final
    • None
    • Batch
    • None
    • Hide
      • perpare your job repository to have a lot of jobinstances of "job1"
        for an oracle database you can execute:

       

      begin
          for v in 1 .. 100000
          loop
             insert into job_instance (jobinstanceid, jobname)
             values (JOB_INSTANCE_SEQ.nextval, 'job1');
          end loop;
          commit;
      end;
      /

      • deploy the sample application, containg a simple job named 'job1' using java 11+
        mvn wildfly:deploy

       

      You will see a long delay (2 mins) while deploying:

      10:19:29,832 MEZ INFO [org.wildfly.extension.undertow] (ServerService Thread Pool – 358) WFLYUT0021: Registered web context: '/jberet-deploy' for server 'default-server'
      10:21:18,964 MEZ INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "jberet-deploy.war" (runtime-name : "jberet-deploy.war")

       

      Having more different jobs with a lot of job repository entries you will not be able to deploy this little app. This works fine in WildFLy 13.

       

       

       

      Show
      perpare your job repository to have a lot of jobinstances of "job1" for an oracle database you can execute:   begin     for v in 1 .. 100000     loop        insert into job_instance (jobinstanceid, jobname)        values (JOB_INSTANCE_SEQ.nextval, 'job1');     end loop;     commit; end; / deploy the sample application, containg a simple job named 'job1' using java 11+ mvn wildfly:deploy   You will see a long delay (2 mins) while deploying: 10:19:29,832 MEZ INFO [org.wildfly.extension.undertow] (ServerService Thread Pool – 358) WFLYUT0021: Registered web context: '/jberet-deploy' for server 'default-server' 10:21:18,964 MEZ INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0010: Deployed "jberet-deploy.war" (runtime-name : "jberet-deploy.war")   Having more different jobs with a lot of job repository entries you will not be able to deploy this little app. This works fine in WildFLy 13.      
    • Undefined
    • ---
    • ---

    Description

      We are updating from WildFly 13 (jberet 1.2.4) to WildFly 21.0.2 (jberet 1.3.7).

      In our production environment we are running about 50 jobs, some of them in a frequency of 2 or 4 minutes. For documentation reasons we only can delete job information older than 3 months. So we have 20000 and more jobinstances per job in our job repository - an oracle database job repo.

      Deploying of our Job-Module to WildFly 21 is never finished - sometimes a out of memory exception is thrown.

       

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21992 [GSS](7.3.z) WFLY-14275 - Large job repository is blocking deployment

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-21993 [GSS](7.4.z) WFLY-14275 - Large job repository is blocking deployment

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified
          is related to

          Feature Request - Feature requests from customers and/or users WFLY-15525 JBeret: Make it possible to limit number of records retrieved via a JDBC store

          • 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

          Bug - A problem that impairs or prevents the functions of the product. WFLY-14372 Multiple metrics collections

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

          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-14946 More efficient way of getting batch job executions by job name

          • 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
          relates to

          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) JBERET-506 Support retrieving job executions by job name

          • 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.
          • Resolved

          Activity

            People

              cfang@redhat.com Cheng Fang
              gvwolf3d Gunther vw (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: