jsr352 | Implementation of Jakarta Batch Specification and API | Continuous Deployment library

In JSR352 batch, I am running a partitioned step to create multiple JSON objects. Each thread, reads some data from oracle and write as JSON object. In some cases, the resultSet.next() getting timed out and throws an exception and going to close() method of ItemReader and ItemWriter class to cleanup any resources. which is perfectly fine. However I have some dao calls on close() method of writer. which needs to be executed when the writer gets completed. But when there's an exception on ItemReader, I am not sure how to get the exception details on close() method. If the exception occured on ItemReader, close() method should not execute the DAO call. Is there anyway to identify ItemReader exception in ItemWriter class.

I'd like to write some generic batch listeners to log out some useful information of all batches configured in my application. To do so I'd like to get the configured skippable/retryable exceptions from batch configuration. However I did not find any API for that. Is there a way to retrieve this configuration independant of the jsr352 implementation?

I am running java batch(jsr352) using liberty server. The datasource configured in server.xml. I would like to load server.xml based on the region(like dev, sit, prod). How can I pass arguments to start liberty server and load the datasource dynamically There could be possiblity with server.env file and bootstrap.properties. since new to this.. can anyone help on this.

I have a batch implemented with JSR-352 (using jberet on wildfly).

I have a chunk with item-count 15 and java.lang.Exception is configured as retryable and skippable exception.

When there are many exceptions, most of the items will be processed multiple times. In this extreme case all items would throw an exception in the writer:

• First 15 items are read
• Exception occurs on first item
• Chunk is rolled back and configured with item-count = 1
• First item is read
• Exception occurs again, item is skipped
• Proceed with the other 14 items, exception may occur on every item, every item is skipped
• After the first 15 items the chunk is back with item-count = 15
• Items 16-30 are read
• Exception occurs again
• Reader is rolled back to latest checkpoint

At this point there is still no checkpoint because there was no successful processed item yet. Hence the reader starts with the first item again. All 30 items are processed with item-count = 1. etc.

If there are many such failures the batch would process all items again and again.

I think the checkpoint needs to be set also for skipped items because a skipped item should not be processed again.

I think this is a bug in the specification so I already opened an issue there: https://github.com/WASdev/standards.jsr352.batch-spec/issues/15 Or am I wrong and have misunderstood the implementation?

How is this implemented in Spring Batch?

My JSR352 batch job needs to read from a database, and then depending on the result flows to one of two pathways, each of which involves some more if/else scenarios. I wonder what the pros and cons between writing a single step with a large batchlet and several steps consisting of smaller batchlets would be. This job does not involves chunk steps with chunk size larger than 1, as it needs to persists the read result immediately in case there is any before proceeding to other logic. The job will be run using Control-M, I wonder if using multiple smaller steps provides more control points.

In a project I'm working on we are reading a file in which every item (a record) read represents a variable number of items to be written in a destination database. This apparently seems to break the pattern of JSR352 by inflating a single chunk more than expected.

Does anyone has ever experienced this kind of problem? If yes, how has it been solved?

I've already deployed an OSGi maven application with many OSGi bundles under Glassfish 4.1.2. This bundles are activated with a webapp that makes some calls with Jobs defined on it. All this is actually working in the expected way.

The web app executes the jobs and jobs make the calls to the OSGi bundles. The problem comes when I try to get the Batch Status from outside.

The purpose is to deploy other web application with REST webservices, so I can query the batch status on demmand. When I run:

I have developed a java batch program using the JSR352 implementation (javax.batch.api.*)

What is the best way to run this java batch program in a Java SE environment ?

ps: We can deploy this program to a JEE server having JSR352 implementation but, we are looking for methods to run in a Java SE environment, where i can run the java program as a simple console application.

ps2: i have the javaee-api-7.0.jar in my project classpath.

I have written a Java batch application using the JSR352 implementation from JavaSE. I have a Reader, Processor and Writer.

Since am running this java app from console in a JavaSE environment, I use the following code in my main(String[] args) method to start the job.