Do I get it right understanding it as work manager = HTTP pool? if so there is a language "conflict" between Weblo work manager and JCA (the specification) one. In Tomcat/TomEE world it is the executor service associated to a Connector which is associated to a Service which has in some nested tags the Context which are the webapps. Rarely saw multiple services in tomcat - never actually - but it is theorically possible even if it makes the socket configuration harder.
If I got it wrong and you really speak about JCA work manager it is configurable through system properties. Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-12-03 16:27 GMT+01:00 seenu.atluri <[email protected]>: > Thanks for the reply Romain. > > I agree with you that work manager can be created in > tomee.xml/resources.xml > and can get it using @Resource. But, weblogic automatically assigns the > inbound request to appropriate work manager queue based on WL dispatch > policy specified. So weblogic does dispatch the inbound requests > automatically. > > Does TomEE has ability route inbound requests to specified work manger? > > Thanks & Regards, > Srinivas Atluri. > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Work-Manager-and-dispatch-policy-in-TomEE-tp4677117p4677121.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
