FATAL: Caught OutOfMemoryError! Node will exit with exit code 666

[Former Member]

Hi, we have Portal 7.0 on NW04s SP12, our server is DEV, 2 CPUs (64 bit) and 8 GB of memory, we are facing a problem, and that is, the J2EE engine restarts every 30 min or so, looking at the default trace, we see the error:

FATAL: Caught OutOfMemoryError! Node will exit with exit code 666

I already modified Heap Size values to:

-Xmx2048m

-Xms2048m

-XX:PermSize=2048m

-XX:MaxPermSize=2048m

-XX:NewSize=320m

-XX:MaxNewSize=320m

but even with that, the portal is restarting and we still get the same error, any clue on how to increase size?, according to note 723909 it is not recommended to have a heap size higher than 2048 MB.

Could it be that the Garbage collector is not running frequently as to release memory? Is it possible to change the Garbage Collector Frequency?

Any help is highly appreciated.

Jorge Flores

[Former Member]

HI Jorge,

Can you please brief on, what is the difference between 'applying parameters at instance level and applying parameters at server level'. I'm bit confused with it.

Thanks in advace.

[Former Member]

It was basically a matter of tuning up the parameters. Initial problem is that I was applying the parameters at the instance level and has to be applied at server level.

[Former Member]

Hi,

I am also getting the same error. I updated the parameter through configtool. This is the menu:

1) Connect to DB

-

---

6) Global dispatcher configuration ...

7) Global server configuration ...

😎 Instance ID85944 ...

9) Create new server

-

---

12) Message server settings

13) Bootstrap settings

14) General servers settings

15) Debug servers settings

-

---

17) Dispatcher ID8594400 ...

18) Server ID8594450 ...

-

---

20) Back to the previous menu

21) Back to the main menu

-

---

23) Exit

I updated under at menu number 18 (Server ID8594450 ...). But iam still getting this error. Did i do anything wrong.

[kohlerm]

Hi Jorge,

> Hi, we have Portal 7.0 on NW04s SP12, our server is

> DEV, 2 CPUs (64 bit) and 8 GB of memory, we are

> facing a problem, and that is, the J2EE engine

> restarts every 30 min or so, looking at the default

> trace, we see the error:

>

> FATAL: Caught OutOfMemoryError! Node will exit with

> exit code 666

>

> I already modified Heap Size values to:

>

> -Xmx2048m

> -Xms2048m

> -XX:PermSize=2048m

> -XX:MaxPermSize=2048m

> -XX:NewSize=320m

> -XX:MaxNewSize=320m

MaxPermSize of 2 Gbyte should not be necessary.

>

> but even with that, the portal is restarting and we

> still get the same error, any clue on how to increase

> size?, according to note 723909 it is not recommended

> to have a heap size higher than 2048 MB.

On 64 bit you could increase the size, but you a full GC could take long to execute.

>

> Could it be that the Garbage collector is not running

> frequently as to release memory? Is it possible to

> change the Garbage Collector Frequency?

No. The GC will run automatically.

I would recommend you to add the option XX:+HeapDumpOnOutOfMemory.

This should generate a .hprof heap dump File, that can be analysed with the SAP Memory Analyzer.

You can find several tips of how to use the SAP Memory Analyzer at my blog here :

/people/markus.kohler/blog

Regards,

Markus

>

> Any help is highly appreciated.

>

> Jorge Flores

[Former Member]

Hi Markus, thanks a lot, I will go to add the parameter to generate the log.

About the MaxPermSize, so, what number do you recomend?

Regards!!

[Former Member]

Problem solved.

Problem was that was applying the parameters at the instance level, applied the parameters at Server level and working like a charm.

Regards, point to you two.

[kohlerm]

Hi,

1024m for the perm size is usually enough.

Check note 723909 for the recommended JVM settings.

Regards,

Markus

[Former Member]

Hello,

which jdk and which os system have you?

regards,

alexander

[Former Member]

Hi Alexander, we have Windows Server 2003 64 bit edition Support Pack 2, as for JDK, it is j2sdk1.4.2_13-x64.

Regards!!

[Former Member]

Sorry, in this case i can't help you. I have only knowledge regarding aix.

alexander

[Former Member]

Hello Jorge,

maybe I have an idea.

a) Could you reduce the value for the following parameters

-XX:PermSize=2048m

-XX:MaxPermSize=2048m

to 256.

b) Make sure the j2ee never must use the swap space.

b) patch the sp12 with the newest patches. some performance bugs in the standard stack.

alexander tuerk

[Former Member]

Hi Alexander, that is precisely the value it has at the very beginning, will try, but don't think it may help.

Regards!!