Forum

Hi,

While trying to write an object, if I receive such an error message:

How I understand it means that an object which I want to write to db is locked from another session or process? Am I right?

So, I prefer to control lock situation of an object in this case. In onject there exists a method named IsLocked(). In syntax written as:
So this method does not control even if data is locked from another session or process?

So how can I control if data is locked by another session or process? And how can I Unlock the data that locked by another session or process?

Or I need to use common method named UnlockDataForEdit(<Key>,<Fo rmIdentifier>) ??

Hi, Murat.

You are rigth. You can not control locked data or not from another session.

You can only try to lock and wait when a data will be free.

Not exactly. It means that you and someone else are mutually blocking each other - you wait until he releases a resource you need, while he wait for you to release a resource he needs. This type of conflict is called deadlock and it's one of the most complicated errors to deal with.
This method has nothing to do with this type of locks. The thing is that there are two different types of locks in 1C: object locks (see Developer Guide, 9.1) and transaction locks. Deadlocks occur in connection with transaction locks while IsLocked() method works with object locks only.

Transaction locks are used by DBMS and 1C to prevent data loss or inconsistency as a result of concurrent user activity (for example these locks do no allow two users to write the same database table record concurrently). This locks are acquired mostly automatically on almost every action you perform on data and you have very limited options to control them.
You cannot. All transaction locks are released automatically (in most cases when transaction is over). There is no way to unlock anything by 1C script and there is a good reason for that. You cannot just unlock whatever you want because it can cause data loss or inconsistency.

OK, let's get back to you deadlock.

Basically, a deadlock is an error in script (most probably in 1C application script). In other words there is something wrong with data processing sequence in you configuration. There are at least 4 different lines of scriptwhose running in this particular order in two different sessions caused the deadlock. We need to find them out and fix the sequence.

To be able to do that we need to collect a technological log containing TLOCK and TDEADLOCK events. Please copy the attached logcfg.xml file into "\bin\conf" folder on 1C server where "\bin" - is a folder 1C cluster runs from. Wait for a minute and make sure that the folder "C:\1C\logs" appeared on the server and there are subfolders looking like "rphost_XXX" inside.

After that you have to wait until at least one deadlock is happened, archive all content of "C:\1C\logs" folder and upload it to the forum.

Please be advised that tech log collecting can cause system slow-down. To switch the tech log off just delete or rename the logcgf.xml file.