The Essential Project Forum

Hello Team,

My tomcat services refuse to start after setting the memory max pool to 2048. Even though I have 12gig memory.

Below is the content of the log files that got updated after restarting the tomcat services:


commons-daemon.2024-08-29


7648] Apache Commons Daemon procrun (1.3.4.0 32-bit) started.
[2024-08-29 10:31:34] [info] [ 7648] Running Service 'Tomcat9'...
[2024-08-29 10:31:34] [info] [ 9616] Starting service...
[2024-08-29 10:38:00] [info] [ 9436] Apache Commons Daemon procrun (1.3.4.0 32-bit) started.
[2024-08-29 10:38:00] [info] [ 9436] Running Service 'Tomcat9'...
[2024-08-29 10:38:00] [info] [ 7392] Starting service...
[2024-08-29 10:41:33] [info] [ 4160] Apache Commons Daemon procrun (1.3.4.0 32-bit) started.
[2024-08-29 10:41:33] [info] [ 4160] Running Service 'Tomcat9'...
[2024-08-29 10:41:33] [info] [10220] Starting service...


tomcat9-stderr.2024-08-29



2024-08-29 10:31:34 Apache Commons Daemon procrun stderr initialized.

2024-08-29 10:38:00 Apache Commons Daemon procrun stderr initialized.

2024-08-29 10:41:33 Apache Commons Daemon procrun stderr initialized.



tomcat9-stdout.2024-08-29



2024-08-29 10:31:34 Apache Commons Daemon procrun stdout initialized.

2024-08-29 10:38:00 Apache Commons Daemon procrun stdout initialized.

2024-08-29 10:41:33 Apache Commons Daemon procrun stdout initialized.

Your log indicates that the Apache Commons Daemon is running as a 32-bit process (procrun (1.3.4.0 32-bit)).
A 32-bit JVM has a hard limit on the amount of memory it can allocate, usually around 1.5 to 2 GB.

Setting a -Xmx value (maximum heap size) of 2048 MB may be too close to or exceed this limit, causing the JVM to fail to start.

Confirm that you are running a 64-bit JVM. You can run java -version from the command line to verify this.

Hi,

That sounds right. Ensure you have the 64bit version of Tomcat and a 64 bit JVM.

https://tomcat.apache.org/download-90.cgi

32-bit/64-bit Windows Service Installer

Also, is there anything in the catalina.out log? It may also be called catalina.SOMEDATE.log

That log can often provide more useful information

Cheers

Neil

Hello Team,

This is the version of java:

U:\>java -version
java version "1.8.0_411"
Java(TM) SE Runtime Environment (build 1.8.0_411-b09)
Java HotSpot(TM) Client VM (build 25.411-b09, mixed mode, sharing)

U:\>


Regarding apache version, the file I installed is actually a 64bit file, how do I approach this? even if I uninstall it, and install it again I will still have this 32 bit service running.

Can you post the details of the catalina.out file?