Java Server Node memory problems

[iprieto]

Hi all,

We are having problems with the memory of my development enviroment of SAP PI Java Stack. At a given time the memory grows and the performance decreases.

I have generated a head dump file. I have analized it and I was raised different issues, one of then is the following:

J "HTTP Worker " cpu=11247.84 ms allocated=1117036016 B (1.04 GB)

J io= file i/o: 54730/443492 B, net i/o: 18315332/15043554 B, files opened:81, socks opened:0

J user="" prio=7 tid=0x6000000002aff460 nid=0x1c45 waiting for monitor entry

J java.lang.Thread.State: BLOCKED (on object monitor)

J at com.sap.bc.proj.jstartup.fca.FCAServer.accept()Lcom/sap/bc/proj/jstartup/fca/FCAConnection;(FCAServer.java:111)

J - waiting to lock <0x87fffffed5f5f568> (a com.sap.bc.proj.jstartup.fca.FCAServer)

J at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run()V(Processor.java:198)

J at com.sap.engine.core.thread.impl3.ActionObject.run()Ljava/lang/Object;(ActionObject.java:37)

J at java.security.AccessController.doPrivileged(Ljava/security/PrivilegedAction;Ljava/security/AccessControlContext;)Ljava/lang/Object;(Native Method)

J at com.sap.engine.core.thread.impl3.SingleThread.execute(Lcom/sap/engine/core/thread/ThreadContextImpl;)V(SingleThread.java:152)

J at com.sap.engine.core.thread.impl3.SingleThread.run()V(SingleThread.java:247)

J

J Locked ownable synchronizers:

J - None

I have a doubt because I don't know what is the meaning of *ms allocated=1117036016 B (1.04 GB) *.

Could somebody help me with this issue?

I will be grateful if somebody show me more information (help.sap, blogs or articles) related about this question.

Thank you and best regards.

Ivá

[Former Member]

I believe this is

J "HTTP Worker [6]" cpu=11247.84 http://reset 11247.84 ms

allocated=1117036016 B (1.04 GB) http://reset 1117036016 B (1.04 GB)

and not

what is the meaning of *ms allocated=1117036016 B (1.04 GB) *.

You may need to tune the system.Consider heap memory, number of application and dispatcher threads etc.

[Former Member]

implement note 723909 note. it might helps you for memory related issues.

[nirmal_konchada]

Hi,

This dump occurs when the heap memory is over utilized.

Increase the Heap Memory to avoid this.

Regards,

Nirmal.K