Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

jlaunch memory leak

Hi,

I m using Netweaver AS with Oracle Database 10g Enterprise Edition. Recently i have observed that the jlaunch.exe is consuming lots of system memory and keeps on growing until we force a restart of the AS. The gc parameters are as reccommended in SAP notes. Can any body help please??

regards

Rajath

Former Member
Former Member replied

JLaunch process is a wrap of the java process within SAP J2EE cluster. it could be one of your server node in your case. you can find more information about jlaunch at:

[http://help.sap.com/saphelp_nw70/helpdata/EN/a2/852aca5cd96f4796e51ba0f7a28926/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/EN/a2/852aca5cd96f4796e51ba0f7a28926/frameset.htm]

it's depending on your JVM configuration, the process could use memory up to the total of maximum heap size + Maximum perm space + native/java stack size.

if you follow SAP recommendation for the initial setup, normally one server node process could use up to around 2.3GB memory.

So it might be a configuration rather than memory leak.

If you still think it's suspected memory leaking issue,you should start with GC analysis, find a good GC graphic viewer or using Wily introscope will help you a lot.

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question