Linux Notes 3 Centos7 tomcat under the JVM

Testing the CMIs Discovery CMIs occasionally times out when the case is in progress.

App\common\components\cmis\cmisruntimeexception:curl Error code:28, url:http://cmis:8180/cmis/atom/pf1tyl4r% 3adefault/id?id=d20ddc94-06ac-47ff-8828-c5f43efdb9cc&f

Troubleshooting Procedures

1. The start of CMIs is launched under Tomcat, so go to the Tomcat startup program

[email protected] tomcat]# which Tomcat
/usr/sbin/tomcat
[Email protected] tomcat]# Vi/usr/sbin/tomcat

2. Discover that there is a java_opts JVM in the launcher is typically added to this place, but this variable is not defined under the current shell and should be referenced by other files.

3. Continue to see that there's a place

Tomcat_cfg= "/etc/tomcat/tomcat.conf"
Go on,/etc/tomcat/tomcat.conf.

Found a java_opts variable inside.

Change it to the value we need.

Java_opts= "-xms2048m-xmx6144m"

Appendix:

http://blog.csdn.net/ye1992/article/details/9344807

The initial memory allocated by the JVM is specified by-XMS, the default is physical memory 1/64;JVM the maximum allocated memory is specified by-XMX, which defaults to 1/4 of the physical memory. When the default free heap memory is less than 40%, the JVM increases the heap until the maximum limit of-xmx, and when the free heap memory is greater than 70%, the JVM reduces the heap until the minimum limit of-XMS. So the server generally sets-xms,-xmx equal to avoid resizing the heap after each GC. You can make heap memory settings with options such as the-XMN-XMS-XMX provided by the JVM, generally to set the-XMS and-XMX options to the same, and the-XMX value of-xmn to 1/4, the recommended maximum value for the heap is set to 80% of the maximum available memory.

Linux Notes 3 Centos7 tomcat under the JVM