hi all,
Is it possible to deploy 2 instances of geoserver (1.6.4 and 1.7.4 for example) in one tomcat ?
What about memory use ? class loader,....??
do i have to configure some xml files to do that after deployement ?
Thanks
I don't think it would be a problem. Just give the two WAR files different
names and drop them in the webapps folder.
You might have to allocate more memory to the JVM through the -Xmx flag in
Tomcat's startup. You also might need to allocate more PermGen space:
-XX:MaxPermSize=128m or more.
Sébastien Geindre-2 wrote:
hi all,
Is it possible to deploy 2 instances of geoserver (1.6.4 and 1.7.4 for
example) in one tomcat ?
What about memory use ? class loader,....??do i have to configure some xml files to do that after deployement ?
Thanks
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
View this message in context: http://www.nabble.com/2-instance-of-GS-deployed-in-one-tomcat---tp23411351p23411471.html
Sent from the GeoServer - User mailing list archive at Nabble.com.
Hi Sébastien,
There should be no issues. At opengeo we host the same tomcat with many geoserver intances inside of it. I don't know of any additional requirements other than the recommended options listed here:
http://geoserver.org/display/GEOSDOC/2.6+GeoServer+in+Production+Environment
I am sure Arne (our sysadmin) will be happy to share any additional insights.
-Justin
Sébastien Geindre wrote:
hi all,
Is it possible to deploy 2 instances of geoserver (1.6.4 and 1.7.4 for example) in one tomcat ?
What about memory use ? class loader,....??do i have to configure some xml files to do that after deployement ?
Thanks
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
2009/5/6 Justin Deoliveira <jdeolive@anonymised.com>
Hi Sébastien,
There should be no issues. At opengeo we host the same tomcat with many
geoserver intances inside of it.
One thing to watch for is, if you are sharing data directories between different versions, older versions may trash the entries for new features. So if you create a directory dataset in 1.7.x and then go back to 1.6.x everything breaks and you’ll need to recreate the directory datasource in 1.7.x later.
Ian
–
Ian Turton
http://www.geotools.org
http://pennspace.blogspot.com/
Ian Turton wrote:
2009/5/6 Justin Deoliveira <jdeolive@anonymised.com>
Hi Sébastien,
There should be no issues. At opengeo we host the same tomcat with many
geoserver intances inside of it.
One thing to watch for is, if you are sharing data directories between
different versions, older versions may trash the entries for new features.
So if you create a directory dataset in 1.7.x and then go back to 1.6.x
everything breaks and you'll need to recreate the directory datasource in
1.7.x later.Ian
As far as I know, we do not have a decree that GeoServer must play nice with other instaces using the same data directory. I definitely recommend against doing this, I can think of more problematic examples like the one you mention. Storage is cheap, make a copy 
Sébastien:
Memory use is up to the JVM to decide, the only thing you have to do is increase -XX:MaxPermSize=128m (maybe 256). Class loading has always worked fine on Tomcat, as far as I could tell. (We've had some issues with JBoss)
Since you can't set multiple data dirs using environment variables, you have to set it in WEB-INF/web.xml
-Arne
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
According to my knowledge, there's nothing preventing of using several instances of GeoServer in a single Tomcat. Also you can setup more than one Tomcat in one host. I don't have any experience on doing that in a production environment but in development environment I have. I have two Tomcats, one with 5-10 Geoserver instances, another one with other stuff. I have also run a third Tomcat when testing other products, like portal servers (liferay, Jahia etc.) No problems so far after I configured enough memory. I've been using jsvc script to control Tomcats (included in standard distribution).
I have also used naming system which keeps different versions in order. I rename new Geoserver instance before deploying it, like geoserver.war >> gs174.war. After that I create a symbolic link from geoserver to that gs174. When new version is released, I repeat the same procedure, change the link like geoserver >> gs175 and leave the previous version as it is. That keeps downgrading easy.
- mika -
Arne Kepp kirjoitti:
Ian Turton wrote:
2009/5/6 Justin Deoliveira <jdeolive@anonymised.com>
Hi Sébastien,
There should be no issues. At opengeo we host the same tomcat with many
geoserver intances inside of it.
One thing to watch for is, if you are sharing data directories between
different versions, older versions may trash the entries for new features.
So if you create a directory dataset in 1.7.x and then go back to 1.6.x
everything breaks and you'll need to recreate the directory datasource in
1.7.x later.Ian
As far as I know, we do not have a decree that GeoServer must play nice with other instaces using the same data directory. I definitely recommend against doing this, I can think of more problematic examples like the one you mention. Storage is cheap, make a copy
Sébastien:
Memory use is up to the JVM to decide, the only thing you have to do is increase -XX:MaxPermSize=128m (maybe 256). Class loading has always worked fine on Tomcat, as far as I could tell. (We've had some issues with JBoss)Since you can't set multiple data dirs using environment variables, you have to set it in WEB-INF/web.xml
-Arne