tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Crowther <>
Subject Re: Best Tomcat O.S. and Server Configuration
Date Tue, 20 Oct 2009 16:17:22 GMT
2009/10/20 beppe_c <>:
> I've just bought a dedicated server, and I'm looking 4 the best
> configuration. I need to run Java (Struts2-hibernate+mysql) applications
> through Tomcat.
> Motherboard supports till 8GB RAM
> CPU Intel 2,6GHz Pentium Dual Core
> 4GB RAM DDR2 667 MHz

That's not large for 5 virtual servers.

> 2HD SATA 500GB 7200rpm in RAID 1 software
> I'm thinking to create 4 virtual servers:
> 1) Developing Environment. It contains repository (svn) and Trac application
> (a project management web app.)
> 2) Test Environment. Identical to Production.
> 3) Production Environment. Must run Struts2+Hibernate apps.
> 4) Parking Environment. Dedicated to simple static sites and parked domains.
> 5) Mysql Environment. To be used and not duplicated from the other
> virtualizations.
> I'd create also a virtual shared storage.
> I'm going to use XenServer to virtualize, I'm almost sure about it.
> Yet, I still don't know which O.S. is better to use on the virtualizations..
> over of all, on test and production environments.
> Please, tell me some advice about it.. or about the right strategy in
> virtualizing the system.

I'll use my usual quote: "It depends on what you're trying to do".
How heavy is the traffic to your machine?  Why do you want the
boundaries you have drawn - what is the benefit to you of each of
those boundaries?

Unless you have very strong reasons to keep them separate, I would
suggest combining the production and parking environments into one
virtual server.  The overhead of an entire OS and Web server for
parking and static sites will be high compared to the overhead of just
running them on the production server.

If you only have one MySQL instance, then your test environment is
*not* identical to your production environment as you must use
different instances or databases for the "test" and "production"
systems.  It's very easy to forget to change the configuration as you
move between the two.  I would install MySQL on "test" and on
"production".  If you feel you can't afford the RAM to do this... you
probably need to add more RAM.  You might want a third instance on
"developing" as well, and just get rid of the separate MySQL

So I'd go for at most three VMs: "test", "production" and possibly
"developing" if you don't want to merge your svn repository and trac
onto your production server.

OS-wise, I would pick the one that you're familiar with.  The cost of
learning a new OS is far higher than the cost of the RAM to run your
preferred OS on the virtual machines - though if you're most familiar
with Windows, I'd beware of paying for 5 x Windows licenses!

- Peter

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message