Hi in application.properties you can configure:
- AsynchronousPool.Size (default 5 for recent versions, was 3 before IIRC) - AsynchronousPool.ShutdownWaitDuration: how many time we wait for tasks to be done when undeploying the app - AsynchronousPool.CorePoolSize - AsynchronousPool.MaximumPoolSize - AsynchronousPool.QueueSize - AsynchronousPool.KeepAliveTime - AsynchronousPool.AllowCoreThreadTimeOut - AsynchronousPool.QueueType: SYNCHRONOUS (SynchronousQueue), LINKED (LinkedBlockingQueue), ARRAY (ArrayBlockingQueue), PRIORITY(PriorityBlockingQueue) - AsynchronousPool.RejectedExecutionHandlerClass: RejectedExecutionHandler implementation, default is org.apache.openejb.util.executor.OfferRejectedExecutionHandler ie retry with a timeout of x seconds (30s by default) - AsynchronousPool.OfferTimeout (if RejectedExecutionHandlerClass not set) I guess you want just a custom RejectedExecutionHandlerClass Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-11-03 10:43 GMT+01:00 Lars-Fredrik Smedberg <[email protected]>: > Hi > > In WebSphere there is a thread pool for serving @Asynchronous EJB method > calls as well as request work queue used when all threads are busy. When > the thread is full the work is placed on the queue and when the queue is > full the policy of BLOCK or FAIL will determine if the thread calling the > method will hang or fail. > > Questions > > - Does TomEE have similar configuration? > > - Is there any way of knowing before calling the @Asynchronous EJB method > if it will wait before beeing processed (or in the WebSphere case hang)? > Combine it with @AccessTimeout perhaps? > > Regards > LF > > -- > Med vänlig hälsning / Best regards > > Lars-Fredrik Smedberg > > STATEMENT OF CONFIDENTIALITY: > The information contained in this electronic message and any > attachments to this message are intended for the exclusive use of the > address(es) and may contain confidential or privileged information. If > you are not the intended recipient, please notify Lars-Fredrik Smedberg > immediately at [email protected], and destroy all copies of this > message and any attachments.
