Thank you. I will make initial and max heap to be same value. Ambica Sanka Sr J2EE IV Developer office 703.661.7928
atpco.net linkedIn / twitter @atpconews 45005 Aviation Drive Dulles, VA 20166 -----Original Message----- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Thursday, January 04, 2018 12:20 PM To: users@tomcat.apache.org Subject: Re: GC allocation failure -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Ambica, On 1/4/18 11:17 AM, Sanka, Ambica wrote: > I am seeing below highlighted errors in native_err logs in all my > tomcat applications. I also increased memory for the VM from 4GB to > 8GB. Still seeing those. When do we get that errors? I am reading > online that when program asks for memory and java cannot give, that's > when we see them. Please suggest. Java HotSpot(TM) 64-Bit Server VM > (25.20-b23) for linux-amd64 JRE (1.8.0_20-b26), built on Jul 30 2014 > 13:13:52 by "java_re" with gcc 4.3.0 20080428 (Red Hat > 4.3.0-8) Memory: 4k page, physical 8061572k(2564740k free), swap > 4063228k(4063228k free) > > CommandLine flags: -XX:+HeapDumpOnOutOfMemoryError > -XX:HeapDumpPath=/opt/apache/ancillariesmonitoring/logs/ > -XX:InitialHeapSize=128985152 -XX:MaxHeapSize=268435456 -XX:+PrintGC > -XX:+PrintGCTimeStamps -XX:+UseCompressedClassPointers > -XX:+UseCompressedOops -XX:+UseParallelGC Others have commented on those messages you received, but nobody mentioned your heap configuration. In the above command-line arguments, you have specified both the minimum and maximum heap memory. You have expressed those values in bytes which makes it somewhat hard to read what they actually are, but this is what you have in readable units: - -XX:InitialHeapSize=128M -XX:MaxHeapSize=256M So you aren't using an 8GiB heap. You aren't even using a 4GiB heap. You are using a 256 *megabyte* heap. If you really want an 8GiB heap, you'll need to set it properly in your command-line arguments. Note that setting the initial heap size to anything other than the maximum heap size just makes the JVM take longer to get the heap generations sized appropriately. For a long-running server process, I think it never makes any sense to set initial < max heap size. Always set them to the same value so that the heap itself does not have to be expanded/resized during heap allocations. Hope that helps, - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJRBAEBCAA7FiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlpOYkMdHGNocmlzQGNo cmlzdG9waGVyc2NodWx0ei5uZXQACgkQHPApP6U8pFjKfBAAikZ9mfKhO5VcEGyd spKC8m4Ot1N+qtkR02ftBf7Sh0CQRjMBFsQUzd2Y+F2w7lPT8bpCnxThKfrkjrkk ySrF7mVF82aVUM72Abh65tK+E4HJhbZWzGAx7NtSx5XDS5ga9nFvJ42Ea/+pzqUf ZQmnRIXhj4gWf+q8mk1bIeR0siSc9J7e575CxMkJWji4gIgLgVMMJTZ1Euwya83W ohTe1Bi355kKiiX3ikRutFgv91fX5kSdNkf+u4huvEBccyDJRaK2MapJ+KOMVUbJ OodFqlO4eFkeL/KxyclWr8OnAgPj4VaNfaq7jNzZyI5MpZymKhuy8uKnUN10XN8r tZO/ZFroeEmLDpM6imPIj1eHcgq/emFg1gT9QW8G08WfWFkSF7fm60Xi3U+4/8si uB3zCFXq9g5EjQ5p2MdpNyQPsHXm5E/J4iS5XyBKkjcuNkVfYneEMP+alOMHIIGI SxS1Hb54VgV+//etPHgycVVoomw5JFW3erRkiMd6edQL5K9m/j+xHJhbr5nbcYKe Nj3lPFPQ5hP02qySf+flZQYayX3HNgCXqhFfDDCANKejU7I4ZC2bSySrWrPkuTfc Dgk+TXlvLRvZ5xWzyM8F1NlsJ/OV+mk23WIyGX7Riyqw9lPghzO+i1mHtyZzg2g8 8zBZXehds+nzTCCBP6MUNqH+I50= =DPai -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
