sonatype/nexus — comment on commit 3f280cc4096feeabe99fac3614e0f0bffbb7fe41
File:  line 0
By mhansen-sonatype:

Possibly something to contend with in the new design approach... When the event handling is performed by threads from the ThreadPoolExecutor pool, the locks currently the thread firing the events are not an issue (e.g. the DefaultNexusConfiguration lock). However, if the threads in the pool are exhausted (or -- unlikely -- the pool has been shutdown) the execution of the handler will be done in the context of the thread calling DefaultEventInspectorHost.processEvent(). If the design assumes that asynchronously handled events will always be free of any prior synchronization locks, there is no guarantee that will be the case.

This is not an issue if the order of lock acquisition is always consistent, but this rare circumstance seemed like a subtlety worth pointing out. Perhaps it has already been considered.