Ok, so I think I understand the issue better. What's really happening is a dead lock between the two threads, simply because they're both locking on the same object. The second thread is derived from the first, so the lock never gets cleared.

Yes, Tomcat is started from within AfterDeploymentValidation notification when the lock is already held.

Thoughts?

Hm yes, we would have either to delay @Initialized(ApplicationScoped.class) or change the lock object.