1.8GB Heap Limit in ColdFusion MX
Macromedia's Recent Technote: Maximum JVM heap size greater than 1.8GB will prevent ColdFusion MX from starting points out the limitations of a the JVM on a 32 bit architecture.
Wondering where the number 1.8GB comes from? Moazam Raja's recent blog entry explains. 32 bit processes can only address 4GB of memory, windows reserves 2GB for the kernel. So where's the other .2 GB? It is allocated to the the JVM's
permanent generation (this stores meta data for the JVM). Many people increase the size of the permanent generation (for CFM or JSP apps) using the jvm startup option
-XX:MaxPermSize. If you increase the perm generation (and you may want to) keep in mind your Max heap size will be less than 1.8GB.
Of course if you have these problems you should consider upgrading to a 64 bit architecture which have much larger limits.
- ColdFusion Memory Usage Stats - March 15, 2004
- Getting Size of Heap and Non Heap Memory in CFML - July 17, 2013
- Robi Sen on Hung Servers, java.lang.OutOfMemory errors and Tuning CF JVM - November 19, 2004
- Server Memory Flash Remoting Tool - August 30, 2004
- ColdFusion Garbage - June 3, 2004
- Updating Java on ColdFusion or Lucee
- ColdFusion returning empty response with server-error: true
- Careful applying CF11u16, CF2016u8, CF2018u2
- Sessions don't work in Chrome but do in IE
- csrfVerifyToken does not invalidate the token
- The cf_sql_ is optional in cfqueryparam
- Cookie Expires / Max-Age 1969-12-31T23:59:59.000Z
- Burst Throttling on AWS API Gateway Explained