Hi all,
Currently the gwc module does its configuration in a separate thread. This
is problematic for dbconfig because during that configuration gwc must
access the catalog. The way session management is set up currently is that
it is thread local based. So this leads to issues.
Describing the issue a bit more... the way the hibernate dao is setup is
that its proxy will allow methods to be called on the catalog and create a
session on demand... howver that session is closed after the method called.
Which prevents any sort of lazy initialization. So what we do on startup is
create a thread local session and keep it around until geoserver startup is
complete. And so if gwc did its config in the main startup thread there
would be no issue... but since it does not ... kaboom.
So... thoughts on this issue? It would be easy enough to patch the gwc
TileLayerDispatcher to load in the current thread... but i don't know enough
about gwc to know if that is a good idea.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security
easier or more difficult to achieve? Read this whitepaper to separate the
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
