Issue with switching active database because of Wrong lock passed.

System information:

• Windows 10 Pro Version 2004 (Build 19041.153)
• DBeaver 7.0.1.202003211804

Connection specification:

PostgreSql 9.6 PostgreSQL standard driver Do you use tunnels or proxies (SSH, SOCKS, etc) : SSH

Describe the problem you’re observing:

When trying to switch to another database, Dbeaver spends long time on Excessive lock and fails with the error message: Wrong exclusive lock passed.

Steps to reproduce, if exist:

1. With active connection on databse_a, Open New Sql Editor through shortcut.
2. In newly opened sql editor, try to change default object to databse_b
3. DBeaver will try to connect for a while and fail with aforementioned message.

Include any warning/errors/backtraces from the logs

Log:

!ENTRY org.jkiss.dbeaver.model 4 0 2020-04-02 12:59:05.707
!MESSAGE Wrong exclusive lock passed
!STACK 0
java.lang.IllegalArgumentException: Wrong exclusive lock passed
	at org.jkiss.dbeaver.model.impl.SimpleExclusiveLock.releaseTaskLock(SimpleExclusiveLock.java:90)
	at org.jkiss.dbeaver.model.impl.SimpleExclusiveLock.releaseExclusiveLock(SimpleExclusiveLock.java:78)
	at org.jkiss.dbeaver.model.impl.jdbc.JDBCExecutionContext.connect(JDBCExecutionContext.java:162)
	at org.jkiss.dbeaver.model.impl.jdbc.JDBCRemoteInstance.openIsolatedContext(JDBCRemoteInstance.java:123)
	at org.jkiss.dbeaver.ui.editors.sql.SQLEditor$OpenContextJob.run(SQLEditor.java:581)
	at org.jkiss.dbeaver.model.runtime.AbstractJob.run(AbstractJob.java:103)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

Screenshot:

[xyluet]

Same with ubuntu 18.04 dbeaver version Version 7.0.1.202003211804

After a long sleep, it happened, but it’s intermittent. When you close the app then reopen, it said cannot lock workspace <home>/.local/share/workspace6 …, it’s recommended to shutdown previous instance …

[uslss]

verified