You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have run into a deadlock while running tests with the TestMsbAdapterFactory as brokerAdapterFactory. In our case it happened when we had a responder server that handed off the work to another thread that then tried to send a response with the responder that it got from the response context.
The problem seems to be that multiple threads access methods on the TestMsbStorageForAdapterFactory instance of that factory concurrently and everything is synchronized, so the entire thing deadlocks.
It looks like this could be solved by using java.util.concurrent.ConcurrentMap instances.
The text was updated successfully, but these errors were encountered:
sebastiaansamyn-tc
changed the title
Deadlocks using TestMsbStorageForAdapterFactory
Deadlocks using TestMsbAdapterFactory
May 15, 2017
We have run into a deadlock while running tests with the TestMsbAdapterFactory as brokerAdapterFactory. In our case it happened when we had a responder server that handed off the work to another thread that then tried to send a response with the responder that it got from the response context.
The problem seems to be that multiple threads access methods on the TestMsbStorageForAdapterFactory instance of that factory concurrently and everything is synchronized, so the entire thing deadlocks.
It looks like this could be solved by using java.util.concurrent.ConcurrentMap instances.
The text was updated successfully, but these errors were encountered: