Impacts of Removing Oracle Commerce Fulfillment
(Doc ID 2311917.1)
Last updated on SEPTEMBER 27, 2017
Applies to:Oracle Commerce Platform - Version 10.0 and later
Information in this document applies to any platform.
What is the impact of removing Oracle Commerce (ATG) Fulfillment?
ConcurrentUpdateException is occurring because backend systems are sending an updateOrder request to update the order's status while OrderFufiller is running. It was found that the reason this occurs is because the fulfillment process obtains and releases the order lock multiple times as its running, the updateOrder request is able to get a lock, update the order status and release the lock while the fulfillment is running and thus causes the ConcurrentUpdateException. The fulfillment is handled by other backend systems which simply return the updated status when they are ready to let Oracle Commerce know of its new status. In order to avoid ConcurrentUpdateException, you are contemplating on removing Oracle Commerce Fulfillment module.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document