cancel
Showing results for 
Search instead for 
Did you mean: 
Subscribe

Hello,

On our SAP PI apps, J2ee process restarts automatically with  "Fatal: Caught outofmemoryError! Node will exit with exit code 666 java.lang.outofmemoryError".  It has been working fine for sometime. But now, I am not sure for what reason, it restarts by itself. I find huge entries like this in our developer trace file of J2ee process..

[Unloading class jsp._sapportalsjsp_NavigationForms]

[Unloading class sun.reflect.GeneratedMethodAccessor250]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor232]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor179]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor299]

[Unloading class sun.reflect.GeneratedMethodAccessor313]

[Unloading class sun.reflect.GeneratedMethodAccessor306]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor107]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor6]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor393]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor14]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor255]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor104]

[Unloading class sun.reflect.GeneratedSerializationConstructorAccessor451]

These are the JVM parameters for our server process..

-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.PortableRemoteObjectProxy

-Djco.jarm=1

-XX:MaxPermSize=256M

-XX:PermSize=512M

-Xms1024M

-XX:NewSize=320M

-XX:MaxNewSize=171M

-XX:+DisableExplicitGC

-verbose:gc

-Xloggc:GC.log

-XX:+PrintGCDetails

-XX:+PrintGCTimeStamps

-Djava.awt.headless=true

-Dsun.io.useCanonCaches=false

-XX:SoftRefLRUPolicyMSPerMB=1

-XX:SurvivorRatio=2

-XX:TargetSurvivorRatio=90

-XX:+UseParNewGC

-XX:+HandlePromotionFailure

-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer

-Djava.io.tmpdir=C:\WINDOWS\Temp

-Dcm.tmpdir=C:\WINDOWS\Temp

We are currently on Windows 2003 SP2 version (64 bit version), J2ee 7.0 SP18 and Oracle 11.2.0.2 version. We have JDK 1.4.2_17 ver installed on our servers.

Physical RAM 8GB, Swap space 20GB

I tried increasing the max heap size (-Xmx) and initial heap size (-Xms) to 2GB and other relevant Perm and New size according to SAP note 723909, at this point the java server0 process starts but the SAP PI repository page is displayed only half, i can view only the top layer i.e. Tools and Administration, i cannot view Integration Directory, Integration Repository, RWB and SLD.

The page is just Plain, with no error in the std_server0, dev_server0, defaulttrace.

Please let me know your thoughts on this issue.

Regards

Hemang

0 Likes
View Entire Topic
Former Member
0 Likes

Hi,

Please increase heap memory if you have sufficient memory on the server.

Thanks

Sunny

Former Member
0 Likes

Hi Sunny,

Thanks for your quick reply, i tried increasing the heap memory but it did not help.

Any other JVM parameters to look for?

Thanks & Regards

Hemang

Former Member
0 Likes

What is the version of your system ?

Also, please paste error logs from default trace.

Thanks

Sunny

Former Member
0 Likes

Hi Sunny,

We are currently on Windows 2003 SP2 version (64 bit version), SAP Netweaver PI 7.0 SP18 Kernel Level 344 and Oracle 11.2.0.2 version. We have JDK 1.4.2_17 ver installed on our server.

Physical RAM 8GB, Swap space 20GB

Please find the attached defaulttrace snap.

Thanks & Regards

Hemang

Former Member
0 Likes

Please check SAP note 1285490.

Thanks

Sunny

Former Member
0 Likes

Hi Sunny,

We are getting the error while starting the SAP PI application itself. The ABAP is started fine, and the SAP J2ee SDM and Dispatcher also comes up fine, but the Server0 process fails with the OutofmemoryError 666.

Thanks & Regards

Hemang