cancel
Showing results for 
Search instead for 
Did you mean: 

Content update in solution manager

Former Member
0 Kudos

Hi,

I am updating CR content in solution manager before solution manager upgrade. Java hangs in between and then we need to restart java. When i checked server0 log i see following:

Allocation Failure. need 110616 bytes, 5064 ms since last AF>
<AF[35]: managing allocation failure, action=2 (447458384/1073740288)>

Mon Aug 24 16:40:33 2015
  <GC(35): freeing class sun.reflect.GeneratedSerializationConstructorAccessor24(700000071ec0360)>
  <GC(35): freeing class sun.reflect.GeneratedSerializationConstructorAccessor29(700000079dd2fa0)>
  <GC(35): freeing class sun.reflect.GeneratedSerializationConstructorAccessor30(70000007b5cbdf0)>
  <GC(35): unloaded and freed 3 classes>
  <GC(35): GC cycle started Mon Aug 24 16:40:33 2015
  <GC(35): freed 225234608 bytes, 62% free (672692992/1073740288), in 242 ms>
  <GC(35): mark: 201 ms, sweep: 41 ms, compact: 0 ms>
  <GC(35): refs: soft 2982 (age >= 32), weak 1264, final 2539, phantom 0>
<AF[35]: completed in 244 ms>

Any suggestions?

Regards,

SJ

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello SJ,

Please check Heap dump.

It might have been full. Remove it from Work directory of J2ee.

Else increase Heap size in config tool.

Regards

Anand

Former Member
0 Kudos

Thanks!

Former Member
0 Kudos

Shall I increase it for instance or just the server? Right now for instance its 256MB, dispatcher has 374 and server has 2048.

Matt_Fraser
Active Contributor
0 Kudos

Hi SJ,

It is only the server instance that matters, but you can set it at the instance level under the Servers General tab (you are probably looking at the Bootstrap java heap -- don't change that). Set it under Servers General in the Max heap size field, then find the server instance and check that the same value is set there in the general java settings.

For a NW 7.0x 64-bit system, though, a 2048 MB heap size is usually sufficient.

I assume this is SLD CR content that you are updating? Are you carefully following the directions in Note 669669 (Update of SAP System Component Repository in SLD)? It's very important to import everything in the correct order and not ignore any warnings. Also, there are some older CR content imports that are quite large (identified in the Note), so you may need to follow the directions in Note 1326081 (SLD import error: "Posted content length exceeds limit"), though this doesn't seem to be the error you're getting at the moment.

Cheers,

Matt

Former Member
0 Kudos

Thanks Matt! Yes, i am following 669669 and 1326081.

Answers (0)