File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Tomcat and the fly likes Maximum allowed memory for Tomcat 6.0 and Tomcat 7.0 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Maximum allowed memory for Tomcat 6.0 and Tomcat 7.0" Watch "Maximum allowed memory for Tomcat 6.0 and Tomcat 7.0" New topic
Author

Maximum allowed memory for Tomcat 6.0 and Tomcat 7.0

ahmed tanvir
Greenhorn

Joined: Nov 28, 2011
Posts: 1
Currently I am using Tomcat 5.5 but it has a memory limit of 2 GB max. As my application requires more memory, I am thinking of upgrading my tomcat installation.
Can any one tell me the maximum allowed memory for Tomcat 6.0 and Tomcat 7.0? Is there any other benefits of using Tomcat 6.0 or Tomcat 7.0 over Tomcat 5.5?
And what the effect in 64 bit system?
Tim Moores
Rancher

Joined: Sep 21, 2011
Posts: 2408
I don't think that's a Tomcat limitation; it sounds like you're using a 32-bit JVM.
Rob Spoor
Sheriff

Joined: Oct 27, 2005
Posts: 19538
    
  16

Welcome to the Ranch!

A 32-bit JVM will only allow up to 1.5GB. This is a limitation for all 32-bit applications. It doesn't matter if the operating system is 64-bit or not.
If you use a 64-bit JVM (you will also need a 64-bit operating system), you will not have this limit. As a result, Tomcat can use a lot more memory. At my work, we use 3GB for Tomcat at the moment.


SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6
How To Ask Questions How To Answer Questions
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Maximum allowed memory for Tomcat 6.0 and Tomcat 7.0
 
Similar Threads
struts-config parsing error. UnknownHostException
SocketException while uploading File of more than 2GB via Apache HttpClient Object in Websphere
isELIgnored="false"
Setting up contexts somewhere other than webapps
problem with jstl tags