Diagnostic Agent - SAP JVM - OutOfMemory

[Former Member]

Hi,

I have a huge problem.

I implemented the Solution Manager Diagnastic, the Diagnostic Agent installed on managing sistem (Solution Manager (SLM) with IBM JVM and Diagnostic Agent (SMD) with SAP JVM).

I have replicated the activity on the managed system, in particular, on Enterprise Portal.

Now, when the SMD star on the satellite, and carry out any activity from the Solution Manager, the satellite creates a big heart and many error log file (hs_err_pid303134.log) due to OutOfMemory.

Can you help me?

Best Regards,

Diego Garofalo.

[Former Member]

Diego,

can you post the content of the logfile? What do you mean with "the satellite creates a big heart"?

Regards,

Jaap

[Former Member]

Hi,

I wanted to say a big core file.

I can not insert the text of the log. There is another way to send?

Best regards,

Diego.

[Former Member]

Hi,

I tried an upload the log at this link:

http://www.megafileupload.com/en/file/224164/hs-err-pid872530-log.html

PWD: diagnostic

let me know if you see and what do you think?

Best regards,

Diego.

[Former Member]

Hi Jaap,

you can help me?

Best regards,

Diego.

[Former Member]

Sorry for a link!

#

1. An unexpected error has been detected by SAP Java Virtual Machine:

#

1. java.lang.OutOfMemoryError: requested 64736 bytes for Chunk::new. Out of swap space or heap resource limit exceeded (check with limits or ulimit)?

#

1. Internal Error (allocation.cpp:230), pid=1409216, tid=2571

2. Error: Chunk::new

#

1. Java VM: SAP Java Server VM (5.1.053 Apr 18 2010 11:49:51 - 51_REL - optU - aix ppc64 - 6 - bas2:135531 (mixed mode))

2. If you would like to submit a bug report, please visit:

3. http://service.sap.com/support

4. The crash happened outside the Java Virtual Machine in native code.

5. See problematic frame for where to report the bug.

#

Date: 2010-05-04 Time: 12:34:25

-

---

B u i l d I n f o -

---

compile date/time: Apr 18 2010 11:28:40

sapjvm release: 5

sapjvm flavour: express

sap_platform: rs6000_64

platform: aix

arch: ppc64

codeline: 51_REL

hs bld trgt: "product"

flags: !DEBUG, !ASSERT, PRODUCT

build user: "sapsrc30"

built for: AIX (non-PASE build)

__xlC__: 800

Optimization Level: 3

-

---

N a t i v e C r a s h i n f o -

---

Reporting thread:

Kernel thread id (k-tid): 6238395

Pthread id (tid) : 2571

stack: 0x0000000111598890 - 0x0000000111d98890 sp 0x0000000111d91150 (in)

-

---

current frame:

iar: 0x090000001d20e780 -> libjvm.so::os::pd_print_crashinfo(outputStream,void) + 0x90 (traceback table 0x090000001d20ebec: C++ saves_lr stores_bc gpr_saved:8 fixedparms:2 )Decoded instructions:

0x090000001d20e760: 389f 1a54

0x090000001d20e764: 4808 67dd

0x090000001d20e768: 6000 0000

0x090000001d20e76c: 2c3e 0000

0x090000001d20e770: 4082 0044

0x090000001d20e774: 3bc1 01f0

0x090000001d20e778: 3861 01f0

0x090000001d20e77c: 48bf f525

=>0x090000001d20e780: e841 0028

0x090000001d20e784: 2c03 0000

0x090000001d20e788: 4182 002c

0x090000001d20e78c: e861 04a8

0x090000001d20e790: 389f 1d0c

0x090000001d20e794: 4808 67ad

0x090000001d20e798: 6000 0000

0x090000001d20e79c: e981 0500

0x090000001d20e7a0: 3821 04f0

sp: 0x0000000111d91150 (base - 0x7740)

rtoc: 0x09001000a5fad818

0x090000001d20e9ac: libjvm.so::os::pd_print_crashinfo(outputStream,void) + 0x2bc

0x090000001ddab384: libjvm.so::VMError::report(outputStream*) + 0x5b4

0x090000001ddae0b4: libjvm.so::VMError::report_and_die() + 0x484

0x090000001d224714: libjvm.so::report_vm_out_of_memory(const char,int,unsigned long,const char) + 0xa4

0x090000001d2c1068: libjvm.so::Chunk::operator new(unsigned long,unsigned long) + 0x68

0x090000001d2c35ac: libjvm.so::Arena::grow(unsigned long) + 0x6c

0x090000001d2c4518: libjvm.so::resource_allocate_bytes(unsigned long) + 0x48

0x090000001daf9c4c: libjvm.so::PhaseIdealLoop::Dominators() + 0x16c

0x090000001d780b80: libjvm.so::PhaseIdealLoop::PhaseIdealLoop(PhaseIterGVN&,const PhaseIdealLoop*,bool) + 0x470

0x090000001d758e1c: libjvm.so::Compile::Optimize() + 0x51c

0x090000001d7564d8: libjvm.so::Compile::Compile(ciEnv,C2Compiler,ciMethod*,int,bool) + 0xab8

0x090000001d40a0ac: libjvm.so::C2Compiler::compile_method(ciEnv,ciMethod,int) + 0xcc

0x090000001d2ba9f0: libjvm.so::CompileBroker::invoke_compiler_on_method(CompileTask*) + 0x3d0

0x090000001d2b9ec4: libjvm.so::CompileBroker::compiler_thread_loop() + 0x304

0x090000001d2e7690: libjvm.so::compiler_thread_entry(JavaThread,Thread) + 0x10

0x090000001d2e8ac0: libjvm.so::JavaThread::thread_main_inner() + 0x90

0x090000001d2e7de8: libjvm.so::JavaThread::run() + 0x268

0x090000001d1fcbfc: libjvm.so::java_start(Thread*) + 0x34c

0x0900000000442440: libpthread.a::_pthread_body + 0xe0

0x0000000000000000: -> (invalid)

• end of backchain ***

........................

If you want other sections of the log, try to send,

but the log is very large and do not know how to attack.

Edited by: Diego Garofalo on May 4, 2010 3:26 PM

[Former Member]

Hi Diego,

Have you changed the java settings after j2ee installation? Comparing the currently settings with the following saphelp page you can check that there are some difference that may getting insconsitences like OutOfMemory.

Please read the following:

http://help.sap.com/saphelp_nwpi71/helpdata/en/43/73949862c16fcbe10000000a1553f6/frameset.htm

Also now SAP has the Zero Admin Template option. The main goal of Zero Administration is to simplify the technical configuration within the AS Java. To know more about that please check the following page:

http://help.sap.com/saphelp_nwpi71/helpdata/en/45/b94d64cf2252f8e10000000a1553f7/frameset.htm

Hope this helps you out!

Thanks,

Mark

[Former Member]

Hi Mak,

I have the Enterprise Portal installed on an AIX server with IBM's JVM 1.4.2, and then I installed the Diagnostic Agent, as a separate instance with its SAP JVM 5. Now the SAP JVM has no configtool, how can I change settings?

Best regards.

Diego.

[Former Member]

Hi ,

Did you resolve this error?

I am facing the same issue in solution manager system.

Regards,

Bhavesh

[guilherme_balbinot]

Hello

I assume you are in the same boat since you are both using AIX, am I right?

According to the error displayed in std_smdagent.out file, I think the issue comes from the limits of the <dasid>adm user which do not follow the recommentations described in SAP Note 323816.

May you please apply this SAP Note and restart the agent (do not forget to restart sapstartsrv process as well).

If everything is OK, please upgrade your SAP JVM if possible following #1449879 - SAP JVM Patch Collection 38 (build 5.1.052)

Best regards,

Guilherme Balbinot