ConcurrentUpdateExcpetion on paymentGroup Stops Commerce Pipeline Processing
Last updated on JANUARY 17, 2017
Applies to:Oracle Commerce Platform - Version 10.0 and later
Information in this document applies to any platform.
After an order has been submitted, if there are any updates to the paymentGroup data they can potentially overlap in time with remote Fulfillment processing. Fulfillment is normally the loser of the race, hitting a ConcurrentUpdateException. It can come as a surprise that the payment group is being updated since the purchase process code only reads the payment group data after it is first defined. It raises the question why read access to this kind of data led to an update and then to a concurrent update where it is used.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms