CODEWITHSUNDEEP
javamultithreadingsynchronization
Eager Learner
Eager Learner

Reputation: 559

Schedule periodic job in Java with depedent thread workers?

Here is simplified version of my requirement

I have a java class say Processor that contains a method say bigProcess() all it does is connect to a file server, download a specified file once that is done save the file in DB and after that update some of the DB fields in different tables.

For each of the subtasks like download file, save in DB, update fields in t1 etc it uses different methods.

The processor class is invoked every 2 hours and it has to process say around 30 to 40 requests for each invocation. To improve the perfromance I am planning to span a new thread for each request (30 to 40 threads here) and each thread calls the bigProcess method.

Now my question is do I need to synchronize any of the code blocks in bigProcess() method (here I am worried about update fields methods. Some of the update methods are do lock a row like selecte f1,f2,f3 from t1 for update, sets the values for fields f1,f2 & f3 and issue commit)

NOTE : The method bigProcess() does not use any instance variables of class Processor.

Upvotes: 1

Views: 434

Answers (2)

cletus
cletus

Reputation: 625007

Make BigProcess a Callable. When you submit it to an Executor or ExecutorService you get back a Future. If you do future.get() in the 30-40 threads, those threads will block until the Callable completes. Or if the Callable has completed, they will return the result immediately.

An alternative way to do this (that I quite like) is to create a thread pool, submit all the work to the thread pool. Once all the work is submitted, shutdown and await termination. It looks something like this:

ExecutorService threadPool = Executors.newFixedThreadPool(40);
// submit work
threadPool.shutdown();
try {
  threadPool.awaitTermination(Long.MAX_VALUE, TimeUnit.NANOSECONDS);
} catch (InterruptedException e) {
  // do something
}

If you have dependent work (like task B cannot be done until task A completes) then create task B with a Future from task A and so on.

I like this approach because everything is transient. For a single load from the database, all the processes will be created, run and thrown away. When you start creating persistent thread pool you introduce another potential problem and it's harder to work out what's going on.

Upvotes: 3

Bombe
Bombe

Reputation: 83847

Whether you need to synchronize your methods depends on what these methods actually do. Generally you need to synchronize if there are resources that are used from multiple threads, such as a single file or a single table in a database (that you are actually writing to and reading from). If all the processes you’re running do not interefere with one another there’s no need for synchronization.

Upvotes: 1

Related Questions