Yikes .. no matter how much memory you allocate, it'll eventually consume it?
I ran into this problem a few times and I reviewed the application
code looking for the cause through testing.
A memory profiler can work, but I've found them to be somewhat
unwieldy and difficult. Dumps can also give
On 22.12.18 22:58, Dhaval Jaiswal wrote:
> Application built in such a way that it consum memory and hence, it's
> exhaust all memory and results in crashing Java. Probably GC is not running
> when it reaches to its threshold. Is there a way I can call GC explicitly
> without affecting running
If you use large heaps you should use G1 garbage collector
And if you use that then I would set the min and Max to the same values
*-server -Xms13G -Xmx13G **-XX:+UseG1GC*
*To fully initialize the memory at once (g1 will figure it into compartments)*
Op za 22 dec. 2018 13:35 schreef Dhaval
Application built in such a way that it consum memory and hence, it's
exhaust all memory and results in crashing Java. Probably GC is not running
when it reaches to its threshold. Is there a way I can call GC explicitly
without affecting running application. I believe need to identify the
memory
On 22.12.18 20:17, Dhaval Jaiswal wrote:
> System has allocated all mentioned RAM.
>
> I assume 13 would be fine.
Adding to John's question, what I forgot earlier: Another rule of thumb
is to identify the *minimum* amount of memory that the application can
run with, then add a bit of headroom.
Why are you requiring so much memory?
On 12/22/18, Dhaval Jaiswal wrote:
> System has allocated all mentioned RAM.
>
> I assume 13 would be fine.
>
> On Sat 22 Dec, 2018, 11:44 PM John Dale
>> I agree with this tactic .. I do the same thing.
>>
>> Cheers.
>>
>> On 12/22/18, Olaf Kock wrote:
System has allocated all mentioned RAM.
I assume 13 would be fine.
On Sat 22 Dec, 2018, 11:44 PM John Dale I agree with this tactic .. I do the same thing.
>
> Cheers.
>
> On 12/22/18, Olaf Kock wrote:
> >
> > On 22.12.18 13:35, Dhaval Jaiswal wrote:
> >> I am facing issue of crashing JAVA
I agree with this tactic .. I do the same thing.
Cheers.
On 12/22/18, Olaf Kock wrote:
>
> On 22.12.18 13:35, Dhaval Jaiswal wrote:
>> I am facing issue of crashing JAVA process and log files attached for
>> the same.
>>
>> Server total RAM is 16 GB.
>>
>> catalina.sh having following setting.
On 22.12.18 13:35, Dhaval Jaiswal wrote:
> I am facing issue of crashing JAVA process and log files attached for
> the same.
>
> Server total RAM is 16 GB.
>
> catalina.sh having following setting.
> export JAVA_MEM_OPTS="-Xms1g -Xmx15g -XX:MaxPermSize=1536m"
>
> Can some one help where could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Leon,
On 12/22/18 08:19, Leon Rosenberg wrote:
> You should provide at least Java version. Out of the blue you
> should have at least 2Gb for the OS, so if your server is having 16
> Gb, your Xmx and MaxPermSize shouldn't be more then 14 G
Java version 8
On Sat 22 Dec, 2018, 6:49 PM Leon Rosenberg You should provide at least Java version.
> Out of the blue you should have at least 2Gb for the OS, so if your server
> is having 16 Gb, your Xmx and MaxPermSize shouldn't be more then 14 G
> TOGETHER. Of course this only applies to
You should provide at least Java version.
Out of the blue you should have at least 2Gb for the OS, so if your server
is having 16 Gb, your Xmx and MaxPermSize shouldn't be more then 14 G
TOGETHER. Of course this only applies to versions of java below 1.8,
because there is no permspace in modern
12 matches
Mail list logo
