Community
Participate
Working Groups
I'm running into a deadlock while Framework.close() is occuring. What's happening is that another thread logging various shutdown events ends up calling methods that boils down to a Framework.getAdminPermission() which uses the same Framework lock. The Framework.getAdminPermissions(...) method is synchronized to protect the "adminPermissions" cache. To prevent this deadlock I believe the lock can safely have its scope reduced to just the "adminPermissions" object instead of the Framework. I've done some analysis and don't think this will have any undesirable side-effects but would definitely appreciate someone else taking a look.
Created attachment 36436 [details] change to adminpermissions lock scope
Good catch. Thanks Simon. I have reviewed and released the fix. [contributed patch applied]
adding "contributed" keyword to patches contributed by the community.