Skip to Content
0
Former Member
Aug 10, 2006 at 11:02 AM

Allocation failure in portal - Urgent

1177 Views

Hi,

We have installed NW04s with EP as the usage type. The JVM is giving

problems with the garbage collector. I have tuned the JVM settings

according to notes 716927, 893149, 723909 which are relevant to JVM

settings on AIX for Enterprise portal.

The portal runs for some duration after which we get 503 - Service

unavailable error.

The std_server0.log has the following entries:

<AF[4]: Allocation Failure. need 64024 bytes, 15185 ms since last AF or

CON>

<AF[4]: managing allocation failure, action=2 (257761512/966366256)

(107174008/107374032)>

<GC(5): GC cycle started Thu Aug 10 11:35:56 2006

<GC(5): heap layout: (516050552/966366256) (107374032/107374032) /0>

<GC(5): freed 258489064 bytes, 58% free (623424584/1073740288), in

419 ms>

<GC(5): mark: 343 ms, sweep: 76 ms, compact: 0 ms>

<GC(5): In mark: root scan 318 ms>

<GC(5): refs: soft 0 (age >= 32), weak 9, final 2681, phantom 0>

<AF[4]: completed in 421 ms>

I have also tried using -Xgcpolicy:optavgpause option. Following are my

memory parameters which I have set:

-Xms1024M

-Xmx2048M

-Xgcpolicy:optavgpause

-Xloratio0.1

-Xparroot

-Xconmeter2

-Xk30000

-Xp2048K,64K

-Xgcthreads5

-verbose:Xgccon

-Djco.jarm=1

-Djava.security.policy=./java.policy

-Djava.security.egd=file:/dev/urandom

-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-

Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-

Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.Portabl

eRemoteObjectProxy

-verbose:gc

-

Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services

.ts.jts.ots.PortableInterceptor.JTSInitializer

Please recommend a solution since this is hampering our development.

Your urgent response would be highly appreciated.

Thank you very much.