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
The getBinder method in the DefaultBinderFactory class is marked as synchronized. However, the use of synchronized can be detrimental to performance when using Virtual Threads in Java, as it can introduce deadlocks that negatively affect concurrency and performance.
The getBinder method can be invoked multiple times during the life cycle of the application:
During initialisation: When the application starts and configures the different message channels.
At runtime: Every time a new binder is needed for a specific message channel.
So it would be nice to replace synchronized with a more suitable concurrency mechanism, like ReentrantLock.
If you think it's right, we can contribute it.
The text was updated successfully, but these errors were encountered:
The getBinder method in the DefaultBinderFactory class is marked as synchronized. However, the use of synchronized can be detrimental to performance when using Virtual Threads in Java, as it can introduce deadlocks that negatively affect concurrency and performance.
The getBinder method can be invoked multiple times during the life cycle of the application:
So it would be nice to replace synchronized with a more suitable concurrency mechanism, like ReentrantLock.
If you think it's right, we can contribute it.
The text was updated successfully, but these errors were encountered: