Fair enough, Gavin. Thanks. Lots learned here since then, and plenty for many to consider if they ever hit such a memory issue.
The âJava Heap Spaceâ error youâre seeing indicates that your script is exhausting the maximum heap memory allocated to the JVM running Lucee. Even though the same script previously worked with Lucee 5.3.8.189, there are a few factors that could explain why it fails now. First, your Tomcat memory settings (-Xms512m -Xmx1024m) are quite low for a heavy script. Only 1 GB of maximum heap is available. A change in Lucee version, JDK (moving to JDK 18), or even the way Windows allocates memory can increase overhead, leaving less memory for your script. Reinstalling Lucee and Tomcat may also have reset or altered JVM parameters that were implicitly helping before. Also you know, any difference in JDK versions (Java 8 vs. Java 18) will also affect the garbage collection behavior and memory pressure.
To resolve this, you should increase the JVM heap settings in Tomcatâs configuration (for example, -Xmx2048m or higher depending on your systemâs RAM). Ensure that youâre using a 64-bit JDK, since a 32-bit JVM cannot allocate large heaps. Itâs also a good idea to monitor the scriptâs memory usage using Luceeâs Server Administrator or external tools, to confirm how much memory it requires. If upgrading heap alone doesnât help, you may need to review whether the script is loading very large datasets into memory at once and consider optimizing it (e.g., processing in smaller batches). The major issue should be the Java heap being too small for the workload. Trying to adjust the JVM memory parameters can help to overcome this âJava Heap Spaceâ error.
You can check out this blog How to Solve OutOfMemoryError: Java heap space to understand more about this Java Heap Space error.
1 Like