File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Tomcat and the fly likes 32-bit development vs 64-bit deployment Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Tomcat
Bookmark "32-bit development vs 64-bit deployment" Watch "32-bit development vs 64-bit deployment" New topic

32-bit development vs 64-bit deployment

John Halupka

Joined: Nov 05, 2010
Posts: 4
I have a Tomcat-hosted web app developed in NetBeans 6.7 using Visual JSF.

Development and operational computers have 32-bit OS (XP Pro for development, Windows 2003 SBS for operational) use Tomcat 6.0.16, MySQL 5.0.51b, and JDK 6.

Web app works fine but last major release is putting "pressure" on operational computer (web app more than doubled in size with twice as many simultaneous users).

To offload Windows 2003 server, I want to get a dedicated computer for the web app.

I am considering Windows 7 64-bit system so I can get 4GB of memory.

Should I install 32-bit or 64-bit version of Tomcat on new operational computer?

If 64-bit, will there be issues deploying web app from 32-bit development environment to 64-bit operational one?

Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 17417

Welcome to the JavaRanch, John!

While I personally avoid Windows for production webapp servers (at least ones accessible from the open internet), I have clients who are braver than I am.

I'd recommend using the 64-bit version of Tomcat. You do not have to build 64-bit webapps. Every Java executable is 64-bit at the virtual level, so the important part is to be using the 64-bit JVM, on platforms where that's an option.

An IDE is no substitute for an Intelligent Developer.
I agree. Here's the link:
subject: 32-bit development vs 64-bit deployment
jQuery in Action, 3rd edition