After running a GeoServer war file installation in Tomcat for some time in Windows Server 2008 x64, I've become increasingly unhappy with Tomcat's chronic memory issues and leaks. Now that the GeoServer Windows installer appears to run in a 64-bit environment as a Windows service when used in tandem with a 32-bit JVM, I'm looking into abandoning the war file in favor of the Windows installer. What are the pros and cons of the Windows installer versus the war file in a 64-bit Windows environment?


I would go with the binary (OS Independent) download rather than the installer. This will let you use a 64bit JDK (and probably JRE) while giving you more flexibility about your set up. The installer can get very confused about permissions (well it's windows that gets confused) and generally be more hassle to set up than you save.

However in either case you can just point JAVA_HOME to a 64 bit VM and it will work out fine.

  • Thanks for putting the binary back on my radar screen. I'm giving Tomcat another shot after upgrading it and my JVM, but the binary will be the next thing I try if Tomcat doesn't work out this time. – Roger D. Aug 17 '10 at 3:09

We have attempted to install Geoserver using the windows installer but had issues getting it running. I never could get it configured properly. We then started using the WAR file with greater success.

Before giving up on the WAR file I would echo the previous posts. We ran Tomcat on a x64 bit windows 2008 machine and it was a problem. We had much better luck when I uninstalled 32 bit java and only installed the 64 bit flavor. Everything seems to like defaulting to 32 bit. I believe that in the past year tomcat has added support for 64 bit as well. I also noticed it is now up to version 7.

Lastly, I believe that Geoserver can run with Jetty, although I have never used it, it might be worth investigating.

  • So far so good with the war file in a 64-bit version of Tomcat plus a 64-bit JVM. I've checked into Jetty, but getting it up and running as a service in a 64-bit OS appears problematic from what I gather. – Roger D. Aug 17 '10 at 16:21
  • I was not sure about it, I happened to see it in the docs. It stuck because I was concerned about 64bit tomcat. I have had good luck with it and 64 bit java. One work of warning though, you may want to turn off java updates. In some cases I have seen a comp update to the 32 bit java rather than 64bit. – wilsongis Aug 17 '10 at 17:20
  • The Windows installer uses Jetty by default. – R.K. Feb 7 '12 at 16:03

I think that war file is for who has already an Apache Tomcat installation.

Note that you should see if the windows installer has the 64 bit JRE on it.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.