On Thu, Feb 17, 2011 at 9:50 PM, Justin Deoliveira <[email protected]>wrote:
> Seems fine to me. However just to confirm my understanding. When one sets
> the USE_GLOBAL_RENDERING_POOL to false
> DefaultWebMapService.getRenderingPool() will return null? And this will
> cause the renderer to create its own executor which will then inherit from
> the current thread?
That is the idea, yeah. In that case the streaming renderer will create a
local thread
pool with
localThreadPool = Executors.newSingleThreadExecutor();
which as far as I understand will create threads which are childs of the
current thread.
The global thread pool used otherwise instead is creating threads that are
childs of the
thread that started GeoServer. At least this is my basic understanding of
it,
not sure it's really working like that.
For sure the threads in the global pool are not guaranteed to be childs of
the current
request threads because... well because they are pooled, kept around and
reused
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8128928
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
