Potentially there could be a 2nd message flow sending messages to the same adapter (different BO) and updating the same table
Why do you need to have a different BOs for the same table? You need to have only 1 BO per table. The first flow can send requests with Verb as Create and second flow can send requests with Verb as Update.
Quote:
Is there a possibility that we could run into table/row lock issues or other potential issues?
Yes. If the connector tries to do 2 updates to the same row simultaneously. Or if the connector tries to update a row that is not yet inserted etc.
Quote:
Any suggestion?
There is a property jms.NumConcurrentRequests in the connector configuration file under Standard Properties. If you set this to 1, then the connector will process only one request at a time. So you would not have to worry about row locks.
By default, this property has a value of 10, meaning the connector will process up to 10 requests simultaneously. We can specify a higher value for this property when there are a lot of requests coming in and you just have to insert all the requests into the table.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum