Hmm, does this mean we will have no problem in running threads in J2EE environments ? Hmm, if thats the case, this is a good idea. ( this doesn't mean we should pop up threads here and there ;-) ). . The two scenarios we are using threads are in invoke non-blocking case and Async Message Receivers. So this will not be a problem with thread pools.
Chamil, can you please create a JIRA on this, IF people here agree ? Thanks, Chinthaka Chamil Thanthrimudalige wrote: > hi all, > > Axis2 at present implements a very simple ThreadPool concept. If we > can come up with a way of using an external thread pool we can let the > axis2 users use a more robust ThreadPool of their choice if need be. > If an external ThreadPool is not set we can do the same thing that we > are doing now. Providing a method like in Jetty 6, which is > setThreadPool(ThreadPool tp) with the ThreadPool implementing > execute(Runnable r) method will be an ideal method to do this. > > Best Regards, > Chamil Thanthrimudalige. > >
