Exchange Plan Between Central base and Several sub bases

Hi,

I have some questions related with exchange plan and data lock.

While DeleteChangeRecords of exchange plan or while executing ExchangeMessageWriter or ExchangeMessageReader methods is data objects (for example "catalogRef. item example") are locked?

Why I ask it, I have at the moment such situation:
For example: I have central base and 3 sub bases.
On central base created a node for each sub base. for that we can see witch changes are related on witch base.
On sub bases there is background job witch access to central base web service and read and write own changes.

So sometimes I got an error such as:

question is Is it possible to realize data exchange with several bases on one object at same time?

Murat Yazlıyev,
It is possible.
To lower the risk of deadlocks and time-outs:
1) "Default transaction data lock control mode"  for configuration must be "Managed"
2) When you are reading\writing changes - set up a node property "Number of data element processed in a single transaction" is equal to 100-200.

When reading changes from exchange plan or when writing changes to exchange plan or when deleting changes from exchange plan is related object is locked by that proccess or session?

Murat Yazlıyev,
Depends on "Default transaction data lock control mode" behavior is a bit different.
Generally speaking, all modified and read data\objects in transaction are locked to the end of transaction.
This is not some 1C feature. Check out 'transaction locking' in google.