Bug 4798 - SPEC - document concurrency and thread-safetyness requirement in JobOperator
SPEC - document concurrency and thread-safetyness requirement in JobOperator
Status: ASSIGNED
Product: jbatch
Classification: Unclassified
Component: SPEC
1
PC Mac OS
: P5 enhancement
: ---
Assigned To: cvignola
future
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-15 03:28 UTC by cf126330
Modified: 2014-02-13 13:12 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description cf126330 2013-03-15 03:28:18 UTC
Should have some javadoc in JobOperator to cover concurrency and thread-safety aspect.

For example, is it supported if multiple client threads access the same JobOperator instance, starting/stopping/restarting the same or different job?
Comment 1 ScottKurz 2013-03-15 17:50:32 UTC
For what it's worth we're not doing a whole lot in the RI.. even in the Glassfish environment where we've introduced a purge.

The burden of consistency and synchronization is on the end user / batch admin... though we took another pass fixing our RI tables and at least have some DB-level consistency.

We won't have time to code anything else here.. so probably you'll have to use loose language (i.e. up to implementation) here.
Comment 2 cvignola 2013-03-16 21:23:55 UTC
I need to think this one over a little more.
Comment 3 ScottKurz 2014-02-13 13:12:33 UTC
Not committing to address in future, just listing as candidates and pointing out they're excluded from current Maintenance Rel.