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.

[Florian]

Hi Mike,

I could imagine, that the backend parameters are just set in a wrong way.

Here's the link to the backend-configuration guide (Section More information).

https://tools.hana.ondemand.com/#abap

I would suggest you start first to check on those and see if it will fix the issue.

~Florian

[pokrakam]

Hi Florian,

Thanks for the input. I doubt it, but checked it anyway and found no discrepancies. Those are all "either it works or it doesn't" settings.

This happens intermittently on two Azure instances, a 7.5 and 7.52 system.

SAPGUI (even inside Eclipse) is rock solid

Running eclipse on a cloud instance is also no problem. The usual deployment setup is a Windows VM alongside a linux VM running SAP in a single virtual network. If I remote-desktop into the Windows VM, Eclipse also works flawlessly.

Over the internet it's as if ADT 'forgets' about the connection and then re-establishes a new session, because it manages to set a lock, which suddenly turns foreign.

Also, this used to work, I've been running this kind of setup for a long time without a hitch, it's in recent months that I've been having this issue. I recently deployed a new instance and when the same thing happened with that one I finally got around to posting this.

[matt]

Over the internet it's as if ADT 'forgets' about the connection and then re-establishes a new session, because it manages to set a lock, which suddenly turns foreign.

I've experienced exactly this, connecting to a non-cloud instance via a VPN but with a shaky connection. Once the ADT/Instance connection gets confused, the only way I got things working again was to restart Eclipse. It's strange though, as I've only encountered this one time. It's like it only happens under very specific circumstances.

[pokrakam]

No restart needed, it keeps the authentication, I just close the class, delete the locks and resume. Then it’s fine, until maybe I go get myself some coffee or write an email and boom, fail on next save, then locked by my other self.