Please read below
Quoting Andrea Aime andrea.a...@geo-solutions.it:
On Sat, Mar 26, 2011 at 4:17 PM, christian.muel...@nvoe.at wrote:
What you are describing here would work, but this is the poor man solution
with many disadvantages. Let us assume a cluster with 32 nodes.
a) In the worst
Hi, please read below
Quoting Andrea Aime andrea.a...@geo-solutions.it:
On Fri, Mar 25, 2011 at 5:00 PM, christian.muel...@nvoe.at wrote:
4) I hope you are aware that you can cluster geoserver instances only for
not authenticated access. If you want to cluster with user authentication,
you
On Sat, Mar 26, 2011 at 4:17 PM, christian.muel...@nvoe.at wrote:
What you are describing here would work, but this is the poor man solution
with many disadvantages. Let us assume a cluster with 32 nodes.
a) In the worst case, you have 32 individual authentication processes. The
geoserver
On Fri, Mar 25, 2011 at 3:01 PM, Martin Zeller tor...@torres.at wrote:
Hi,
I encountered a new problem with GeoServer2.1-RC3 which does not exist on
RC2:
When I use a shared geoserver_data_dir it's not possible to start another
geoserver instance
on the same data dir.
Please let me know
Andrea, what can we expect of the next versions regarding
clusters/shared data?
I mean, I tried a shared datadir on a cluster with RC2 - it does not
work, because getGeoServer().reload() throws an error
(see my other post
Hallo Martin, about your clustering problems.
1) I hope you assigned a different log file for each of your geoserver
instances
2) Disable GWC as described by Martin to avoid problems
3) About the reload. A quick look into the source code shows me a
potential for race conditions.
The reload
On Fri, Mar 25, 2011 at 5:00 PM, christian.muel...@nvoe.at wrote:
4) I hope you are aware that you can cluster geoserver instances only for
not authenticated access. If you want to cluster with user authentication,
you need an authentication cluster concept, a single sign on for the
cluster.
