-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Suvendu,
On 1/11/18 10:06 AM, Suvendu Sekhar Mondal wrote:
> On Tue, Jan 9, 2018 at 10:53 AM, Leon Rosenberg
> wrote:
>> On Mon, Jan 8, 2018 at 10:26 AM, Mark Thomas
>> wrote:
>>
>>> On 08/01/18
On Tue, Jan 9, 2018 at 10:53 AM, Leon Rosenberg
wrote:
> On Mon, Jan 8, 2018 at 10:26 AM, Mark Thomas wrote:
>
>> On 08/01/18 15:16, Christopher Schultz wrote:
>>
>>
>>
>> >> Therefore, the first time that the GC runs, the process can take
>> >>
On Mon, Jan 8, 2018 at 10:26 AM, Mark Thomas wrote:
> On 08/01/18 15:16, Christopher Schultz wrote:
>
>
>
> >> Therefore, the first time that the GC runs, the process can take
> >> longer. Also, the heap is more likely to be fragmented and require
> >> a heap compaction. To
On Mon, Jan 8, 2018 at 10:16 AM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Suvendu,
>
> On 1/5/18 6:46 AM, Suvendu Sekhar Mondal wrote:
> > I really never found any explanation behind this "initial=max" heap
> > size theory
On 08/01/18 15:16, Christopher Schultz wrote:
>> Therefore, the first time that the GC runs, the process can take
>> longer. Also, the heap is more likely to be fragmented and require
>> a heap compaction. To avoid that, till now my strategy is to: -
>> Start application with the minimum heap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Suvendu,
On 1/5/18 6:46 AM, Suvendu Sekhar Mondal wrote:
> I really never found any explanation behind this "initial=max" heap
> size theory until I saw your mail; although I see this type of
> configuration in most of the places. It will be
On 05.01.2018 12:46, Suvendu Sekhar Mondal wrote:
I really never found any explanation behind this "initial=max" heap size
theory until I saw your mail; although I see this type of configuration in
most of the places. It will be awesome if you can tell more about benefits
of this
On Jan 4, 2018 11:14 PM, "Rainer Jung" wrote:
Am 04.01.2018 um 18:20 schrieb Christopher Schultz:
> -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
]
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 applicati
Am 04.01.2018 um 18:20 schrieb Christopher Schultz:
-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
-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
elGC
3.203: [GC (Allocation Failure) 31744K->6311K(121856K), 0.0097261 secs]
3.578: [GC (Allocation Failure) 38055K->12368K(121856K), 0.0089875 secs]
3.756: [GC (Allocation Failure) 44112K->19589K(121856K), 0.0100339 secs]
3.897: [GC (Allocation Failure) 51333K->25872K(153600K), 0.00
HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/opt/apache/ancillariesmonitoring/logs/
-XX:InitialHeapSize=128985152 -XX:MaxHeapSize=268435456 -XX:+PrintGC
-XX:+PrintGCTimeStamps -XX:+UseCompressedClassPointers
-XX:+UseCompressedOops -XX:+UseParallelGC
3.203: [GC (Allocation Failure) 31744K->6
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
3.203: [GC (Allocation Failure) 31744K->
14 matches
Mail list logo