When handling the Tomcat problem, Tomcat could not start to view the log as follows
[2018-08-17 14:47:01] [info] Invalid maximum heap size: -Xmx4096m
[2018-08-17 14:47:01] [info] The specified size exceeds the maximum representable size. # The specified size exceeds the maximum representable.
[2018-08-17 14:47:01] [395 javajni.c] [error] CreateJavaVM Failed
View JDK version 
If it is 64 bit, the last line will be displayed
Java HotSpot(TM) 64-Bit Server VM
Since Tomcat has installed services, you can only change the relevant configuration in the registry. Check the original configuration as follows: 
. You can see that the maximum memory of jvmmx is set to 4096m, which is not supported by 32 bits. If you modify the parameter value, you can start normally. 
Similar Posts:
- tomcat PermGen space
- [Solved] Spring Boot Error: The field file exceeds its maximum permitted size of 1048576 bytes
- How to Solve JAVA Error: “Too small initial heap”
- [Solved] CDH6.3.2 Hive on spark Error: is running beyond physical memory limits
- Tomcat java.lang.OutOfMemoryError: PermGen space
- Investigation on the error caused by: java.lang.outofmemoryerror: Java heap space of Tomcat Java application in production environment
- [Solved] Too large catalina.out file of Tomcat (logrotate mode)
- [Solved] 0xC0000374: A heap has been corrupted !
- JAVA package Run Error: Java hotspot (TM) 64 bit server VI warning: Info: OST; The ‘eror’ page file is too small to complete the operation
- Tuning and setting of memory and CPU on yarn cluster