From: ClintFoster <cf...@us...> - 2006-12-28 23:57:45
|
I tried using the ThreadPool class under extras (which extends the Java 5 ThreadPoolExecutor class). However, something now seems to be blocking internally in Jetty. I can connect successfully, but my servlet's doPost() method is never getting called. I tried tinkering with the pool size and BlockingQueue parameters without success. I'm using rc0. I can try it with rc2, but since I don't really need to replace the thread pool implementation, I'm a little more comfortable sticking with BoundedThreadPool. I assume it is the most thoroughly tested. The only downside is that I have to modify the source to change the inner PoolThread class to extend my specialization of Thread. Clint Jan Bartel wrote: > > Clint, > > Take a look in $jetty.home/extras/threadpool, which has an impl of > the java5 concurrent thread pool. So you can plug that in instead of > the BoundedThreadPool. The impl has a constructor that takes a > ThreadFactory, so you should be able to do your customizations there. > > regards > Jan > > ClintFoster wrote: >> Has any thought been given to the possibility of using the Java 5 >> ThreadFactory interface? To quote from the Javadoc, "Using thread >> factories >> removes hardwiring of calls to new Thread, enabling applications to use >> special thread subclasses, priorities, etc." Currently I am modifying >> the >> source code for BoundedThreadPool and AbstractConnector to specify a >> custom >> Thread subclass. But it would be much cleaner to do this by configuring >> Jetty to use a custom ThreadFactory. >> >> Clint Foster > > -- View this message in context: http://www.nabble.com/ThreadFactory-tf2866214.html#a8081998 Sent from the Jetty Discuss mailing list archive at Nabble.com. |