1 Reply Latest reply on Mar 22, 2019 6:59 PM by jamezp

    ExecutorService thread outliving deployment


      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?