Wildfly 20 and batch SubSystem jberet

[Massimo Furnari]

Hi, 

i have an instance of Wildfly 20.0.1.Final with this subsystem

        <subsystem xmlns="urn:jboss:domain:batch-jberet:2.0">
            <default-job-repository name="jobpersistence"/>
            <default-thread-pool name="batch"/>
            <job-repository name="jobpersistence">
                <jdbc data-source="PostgresDS"/>
            </job-repository>
            <thread-pool name="batch">
                <max-threads count="10"/>
                <keepalive-time time="30" unit="seconds"/>
            </thread-pool>
        </subsystem>

there is a way to set a cleanup strategy or i have to delete manually the rows on job_execution and job_instance tables ?

[James Perkins]

Hello,

I think what you want is the PurgeBatchlet. This might be helpful https://issues.redhat.com/browse/JBERET-130.

[Massimo Furnari]

Hi, 

I don't understand if the PurgeBatchlet is included i  WildFly or not

consider that I never installed jberet in wildfly, i use WildFly 20.0.1 like downloaded

searching for jberet in wildlfy folder i found 

\wildfly-20.0.1.Final\modules\system\layers\base\org\jberet\jberet-core\main\jberet-core-1.3.6.Final.jar

\wildfly-20.0.1.Final\modules\system\layers\base\org\wildfly\extension\batch\jberet\main\wildfly-batch-jberet-20.0.1.Final.jar

Thank you

[James Perkins]

It is part of JBeret which is the Batch implementation in WildFly. You should be able to use the PurgeBatchlet in WildFly.

[Massimo Furnari]

Hi, sorry for delay... i discovered that application using information stored in jobexecution table... and i cannot delete rows

so.. the question is.. is possible avoid that wildfly ( on startup ) scan jobexecution id like i described in  https://groups.google.com/g/wildfly/c/kH7MslcXBac/m/jm2J9C2yAAAJ   ?

i don't found nothing on this topic

[James Perkins]

I don't think there is a way to do it via any kind of startup command. I'm not sure I follow why you can't add the batchlet though.

[Massimo Furnari]

i cannot add batchlet ( in this moment ) because there is other services in application that use data stored in job_executions, so if i delete rows from that table, the application get errors

if possibile in future, i will try to remove this dependeny but for now... cannot delete