Lock errors using eclipse over the internet

[pokrakam]

Update 1: I found out how to reproduce the issue fairly reliably, see end of post.

Update 2: I found the root cause involves a dump and does seems to originate from Azure/SAP combination, see my answer below.

When I use my local eclipse to connect to a cloud instance (Azure), I often see timeout and locking errors. There is no problem with the connection, via SAPGUI it is perfectly stable and when it works Eclipse is also generally quick. But then very randomly I'll hit a bump that goes something like:

Save -> spinning wheel for a while > message "Timeout getting a lock"

If I try again I see the message "Object could not be locked / User DEVELOPER is currently editing ZCL..."

I have to manually remove the lock via SM12 to continue working.

It seems to happen more often when I've left the system idle for a couple of minutes - but not always.

I have 200MB fibre broadband and experience no other internet issues. SAPGUI and remote desktop to the same instance is perfectly fine. I use VPN both inbound and outbound to work remotely all day long, there are no issues whatsoever other than using ADT.

---Edit---:

I've been trying to observe a pattern, it seems to mainly happen on generation and code changes, but NOT save. The following procedure reproduces it quite often:

1. Open SM12, view locks
2. Open a class, make a change, activate.
3. Make another change. You should now see the padlock and the * (change indicator) in the tab to indicate that it is locked and changed.
4. Leave it for 10-15 minutes
5. SM12 should still show it's locked
6. Save the class -> success. The * is no longer in the tab but the padlock is still there.
7. SM12 should still show it's locked
8. Ctrl-F3 to activate -> spinny wheel -> Object could not be locked, locked by <your userid>

If you close and re-open, the last change is still there, so it definitely saved under the existing lock. But you can no longer edit until you remove the lock in SM12.

Something is definitively fishy and it's not at my end.

I'm using the latest Eclipse Oxygen with latest ADT on a Mac. I will try it on a Windows VM when I have some more time.

[Wozza]

I know this is an old thread, but wanted to say for users working on ABAP Cloud (BTP) there is a user sessions Fiori app, you can use that to kill your sessions and release the locks.

[Former Member]

Hi,

Has anyone a recent update on this blogpost? Still looking for a solution.

Eclipse Version: 2019-06 (4.12.0)；

SAP S/4HANA 1709

[Armin_Beil]

Hello Hai Bo Shen,

Sorry that there was no further progress or update on this topic recently. I'll try to use your feedback as a new trigger to get more awareness and dev capactiy within the ADT teams for this issue.

Next release of ADT (planned for 01.08.19) will fix a bug that may cause lock issues during activation (without waiting time; a popup tells you immediately that your own user already edits the object), while a second attempt to activate usually just works and you don't have to use SM12.

For the issue discussed in this thread (where you get a frozen UI for 20+ seconds and have to use SM12), we added a mitigation for the subvariant discribed by Kjetil. The main issue however is unfortunately not fixed and currently there is no known workaround.

If you would like to support us getting it fixed, it would be great if you could create a customer incident (component BC-DWB-AIE), describe the issue and link this thread.

If it is not possible for you to create an incident, it would be also helpful if you could answer the questions:

- Is the issue rather reproducible or does it occur only sporadically?
- Is there a UI freeze and you have to wait 20s+?
- Do you have to use SM12 to get rid of the lock or is the issue temporary and disappear after 2-3 seconds?
- Do you also use Azure?

Best regards,
Armin