DBusConnection - RejectedExecutionException

[swiesend]

DBusConnection - RejectedExecutionException

[swiesend]

version 1.2.3:

[main] INFO org.freedesktop.secret.ServiceTest - isRemote()
Exception in thread "DBusConnection" java.util.concurrent.RejectedExecutionException: Task org.freedesktop.dbus.connections.AbstractConnection$3@5a0fc9cb rejected from java.util.concurrent.ThreadPoolExecutor@1f0d4cee[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
	at java.base/java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2057)
	at java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:827)
	at java.base/java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1357)
	at org.freedesktop.dbus.connections.AbstractConnection.executeInWorkerThreadPool(AbstractConnection.java:946)
	at org.freedesktop.dbus.connections.AbstractConnection.handleMessage(AbstractConnection.java:920)
	at org.freedesktop.dbus.connections.AbstractConnection.handleMessage(AbstractConnection.java:709)
	at org.freedesktop.dbus.connections.IncomingMessageThread.run(IncomingMessageThread.java:43)

[infeo]

This looks like a race condition, e.g. the DBus object is already disconnected, but still need to handle some messages. After analyzing this isssue I believe the error lies within the dbus-java project. For a more in depth analysis, have a look at the linked issue: hypfvieh/dbus-java#123

[infeo]

@swiesend can you try to reproduce the issue with the current HEAD of dbus-java? The maintainer applied some changes that possibly fix the problem.

[swiesend]

I published a secret-service 1.2.4-SNAPSHOT and documented the test results over here:
cryptomator/integrations-linux#2 (comment)