WAS v8.5 > Develop applications > Develop EJB applications > Develop session beans > Configure EJB 3.1 session bean methods to be asynchronousEJB container work manager for asynchronous methods
The default work manager used by the EJB container to dispatch asynchronous methods is not configurable. The following configuration information is provided to help understand the limits imposed by this work manager. Remember, one EJB container work manager exists for all asynchronous methods running in the application server process.
The EJB container work manager has the following thread pool settings:
- Minimum number of threads = 1
- Maximum number of threads = 5
- Work request queue size = 0 work objects
- Action taken when buffer overflows = Block
- Remote Future object duration = 86400 seconds
Work request queue size is the maximum number of asynchronous method requests that can be queued while waiting for a thread to become available. If we specify a value of 0 (the default) or blank is specified, the queue size is managed by the run time..
Additionally, the EJB container work manager has configuration settings that specify which service contexts are propagated from the client thread to the work manager thread that runs the asynchronous method. The global transaction service context and the activity session service context are not propagated. The security context, and all of the WebSphere extension contexts, such as work area, internationalization, and so on, are propagated for use on the execution thread.
Related concepts:
EJB 3.1 asynchronous methods
Client programming model for EJB asynchronous methods
Bean implementation programming model for EJB asynchronous methods
Related
Configure EJB 3.1 session bean methods to be asynchronous