I noticed on a WF16 that when I redeploy an application, ExecutorService-submitted tasks are sometimes left hanging around and then complain that @ApplicationScoped beans are not available when they try to do their work (probably because they've lost contact with their deployed application). Are the tasks supposed to be persistent like that?
Maybe it has something to do with WFLY-11678 or possibly WFLY-11846. If not I would say that's a bug as I'd think the old class loader should stick around until the thread is complete.
--
James R. Perkins