manage-async

Asynchronous execution in OFBiz separates transaction boundaries by deferring operations. It differentiates between concurrent execution and later execution, ensuring background tasks do not interfere with the main transaction's commit or rollback processes.

For high-volume data imports in OFBiz, synchronous batching is recommended over excessive async calls. This approach prevents system instability and resource exhaustion by avoiding the creation of massive numbers of persisted async jobs.

Creating massive numbers of persisted jobs in the OFBiz JobSandbox bottlenecks the system. This accumulation causes performance degradation and resource exhaustion because the system struggles to manage the high volume of background tasks.

To decide between synchronous and asynchronous execution for nightly data synchronization in OFBiz, evaluate transaction boundaries and potential deadlocks. Use the decision-making framework to avoid deadlocks and performance degradation based on service invocation modes.

Using async job scheduling in OFBiz for batch processing risks system bottlenecks if it creates excessive persisted jobs. To prevent system instability, synchronous batching is advised instead of scheduling high-volume background tasks asynchronously.

Avoid using mode="async" for service invocation in OFBiz when processing large data imports or batch tasks. Excessive asynchronous calls create massive persisted jobs that bottleneck the JobSandbox and exhaust system resources.