|
#1
|
|||
|
|||
|
Hello Folks,
in a JEE project we are using TaskExecutor to run background processes. These background-processes are started from "normal" request-actions (JSF). Inside the Task Runnable we are accessing session-scoped Beans. Now we have a problem with "cached" request objects (tested with jetty). If the task code call a session-scoped bean then the aop-proxy try to load the "current" session from request attribute. This will not always work ... i.e. if the Webcontainer "reused" request objects (i.e. for performance improvment). Is there a "best practise" to use TaskExecutor inside JEE? Regards Andreas |
|
#2
|
|||
|
|||
|
|
![]() |
| Tags |
| taskexecutor |
| Thread Tools | |
| Display Modes | |
|
|