J2EE Engine is not starting

[Former Member]

Hello Gurus,

I have installed SAP ECC 6.0 JAVA IDES , I gave java restart and java is not coming up.

Below are Logs dev_server0 logs

Error occurred during initialization of VM

Could not reserve enough space for object heap

[Thr 4] JLaunchIAbortJava: abort hook is called

[Thr 4] **********************************************************************

• ERROR => The Java VM aborted unexpectedly.

• Please see SAP Note 943602 , section 'Java VM crashes'

I have gone through various threads and SAP notes and found Max heap memory parameter i need to reset.

Currently Value for this parameter is 2048 and i reduced it to 1024 via configtool (RAN CONFIGTOOL VIA ROOT USER ),selected custom value entered 1024M , saved and applied.

After that i gave system restart but when i checked system.properties file still it is coming as 2048M in dev_server0 file

Even i tried to edit file system.properties from OS level but after restart those values are also getting overwritten.

So please let me know how to resolve this issue

[Former Member]

Dear All,

Thanks for you effort i was doing a silly mistake which i caught now.To change parameters using configtool firt we need to stop Dispatcher and SCS and Java Server0 etc using stopsap j2ee command.After that change memory parameters and then stop database and restarted , system changes reflected at OS level and Java came up.

[nirmal_konchada]

Hi,

Te process your following is absolutely correct for your problem.

Make sure you are decreasing the value for parameter "maxHeapSize". Once this is done take a restart of your SAP along with OS.

BTW what is your RAM and OS????

Regards,

Nirmal.K

[Former Member]

@ Nirmal : I have reduced value till 512 M but i got same error

As i can see from instance.properties file Maxheapsize is still 2048 M

pkgqcenv:idjadm 58> cat instance.properties

ID108183400.ClassPath=./bin/boot/boot.jar:./bin/system/bytecode.jar:.

ID108183400.Debuggable=no

ID108183400.JLaunchParameters=

ID108183400.JavaParameters=-Xms256M -verbose:gc -Djava.security.policy=./java.policy

ID108183400.JavaPath=/opt/java1.4

ID108183400.LogName=dispatcher

ID108183400.MainClass=com.sap.engine.boot.Start

ID108183400.MaxHeapSize=256

ID108183400.Name=dispatcher

ID108183400.Parameters=

ID108183400.RootPath=/usr/sap/IDJ/JC10/j2ee/cluster/dispatcher

ID108183400.Type=dispatcher

ID108183450.ClassPath=./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.

ID108183450.DebugMode=no

ID108183450.DebugPort=51021

ID108183450.Debuggable=no

ID108183450.JLaunchParameters=

ID108183450.JavaParameters=-Xms2048M -XX:MaxNewSize=341M -XX:NewSize=341M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:ReservedCodeCacheSize=64M -XX:CodeCacheMinimumFreeSpace=2M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HandlePromotionFailure -XX:UseParNewGC -XX:DisableExplicitGC -XX:UseTLAB -XX:PrintGCTimeStamps -XX:PrintGCDetails -verbose:gc -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Djco.jarm=1 -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom

ID108183450.JavaPath=/opt/java1.4

ID108183450.LogName=server0

ID108183450.MainClass=com.sap.engine.boot.Start

ID108183450.MaxHeapSize=2048ID108183450.Name=server0

ID108183450.Parameters=

ID108183450.RootPath=/usr/sap/IDJ/JC10/j2ee/cluster/server0

ID108183450.Type=server

bootstrap.ClassPath=./bootstrap/launcher.jar

bootstrap.JavaParameters=-Djco.jarm=1

bootstrap.JavaPath=/opt/java1.4

bootstrap.MainClass=com.sap.engine.offline.OfflineToolStart

bootstrap.MaxHeapSize=256

bootstrap.Name=bootstrap

and as per dev_server0 logs

JStartupIReadSection: read node properties [ID108183450]

-> node name : server0

-> node type : server

-> node execute : yes

-> jlaunch parameters :

-> java path : /opt/java1.4

-> java parameters : -XX:MaxNewSize=341M -XX:NewSize=341M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:ReservedCodeCacheSize=64M -XX:CodeCacheMinimumFreeSpace=2M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HandlePromotionFailure -XX:UseParNewGC -XX:DisableExplicitGC -XX:UseTLAB -XX:PrintGCTimeStamps -XX:PrintGCDetails -verbose:gc -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Djco.jarm=1 -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom

-> java vm version : 1.4.2 1.4.2.22-090325-07:06-PA_RISC2.0W PA2.0W (aCC_AP)

-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Hewlett-Packard Company)

-> java vm type : server

-> java vm cpu : PA_RISC2.0W

-> heap size : 2048M

-> init heap size : 2048M

-> root path : /usr/sap/IDJ/JC10/j2ee/cluster/server0

-> class path : ./bin/boot/boot.jar:./bin/boot/jaas.jar:./bin/system/bytecode.jar:.

-> OS libs path : /usr/sap/IDJ/JC10/j2ee/os_libs

-> main class : com.sap.engine.boot.Start

-> framework class : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path : /usr/sap/IDJ/JC10/exe/jstartup.jar:/usr/sap/IDJ/JC10/exe/jvmx.jar

-> shutdown class : com.sap.engine.boot.Start

-> parameters :

-> debuggable : no

-> debug mode : no

-> debug port : 51021

-> shutdown timeout : 120000

so the value which i am chaning is not reflecting at OS level.

Well for my system

RAM size is 8GB

HP UX 11.31

JDK 1.4.2.26

[franz_hiltscher]

Hi,

you are using 1.4.2_22 for your SAP. You can see the version used in the logs. This could be the reason for the error.

HeapSize 2048 is the recommended size.

If you reduce the HeapSize with configtool. Take care where you do that. Global or on Instance level. Instance Settings overwrite Global settings.

After changing you have restart complete. The bootstrap must running that the changes will be synced from db to filesystem.

A possible reason for "Could not reserve enough space for object heap" is that you HP-UX is not configured as recommended.

Check https://service.sap.com/sap/support/notes/1075118 as entry point for Kernel Settings, OS Patch Level an so on.

Regards

Franz

[Former Member]

Dear Franz

I am changing data in Server node which is under CLUSTER DATA so i think it is at Instance level rather then Global

Secondly i have complete system restart after changing parameters

Further Currently swap size is

pkgqcenv:idjadm 113> /usr/sbin/swapinfo -tm
             Mb      Mb      Mb   PCT  START/      Mb
TYPE      AVAIL    USED    FREE  USED   LIMIT RESERVE  PRI  NAME
dev       16384     612   15772    4%       0       -    1  /dev/vg00/lvol2
reserve       -   15772  -15772
memory    15590   13988    1602   90%
total     31974   30372    1602   95%       -       0    -

You are right after changing heap size parameter and complete restart, the bootstrap is running and the changes are synced from db to filesystem

But here is the problem lies even after saving and applying the changes the changes are not being saved in DB.

I can explaint you how i am changing parameter via configtool and let me know in case if i am missing something

1 Ran ./configtool.sh with root user

2 Connecte to DB

3 Selected button " Switch to configuration editor mode "

4 Selected button " switch between edit and view mode " then Yes

5 Navigate to Node Cluster Data ---> Server ---> Instance ID --->Property element.info

6 Selected Parameter : java.max.heap.size ---> selected checkbox under Custom column

7 Entered value 512

8 In Java.parameters entered

-Xms512M -XX:MaxNewSize=512M -XX:NewSize=512M -XX:MaxPermSize=512M -XX:PermSize=512M -XX:ReservedCodeCacheSize=64M -XX:CodeCacheMinimumFreeSpace=2M -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -XX:SoftRefLRUPolicyMSPerMB=1 -XX:HandlePromotionFailure -XX:UseParNewGC -XX:DisableExplicitGC -XX:UseTLAB -XX:PrintGCTimeStamps -XX:PrintGCDetails -verbose:gc -Dsun.io.useCanonCaches=false -Djava.awt.headless=true -Djco.jarm=1 -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom

9 Pressed OK

10 Selected button " Switch b/w view and edit"

11 Selected button " Switch to configuration editor mode "

12 SAVE

13 File --->Apply

Please let me know anything is wrong here

Regards

Kuldeep Tanwar

[franz_hiltscher]

Hello,

iam not a HPUX Expert but i looks like that there is not enough free memory.

Do you running additional sap instances or other applications on the host.

You should execute the configtool as <sid>adm

Regards

Franz

[Jozsó]

Hi,

try to execute java from the commandline like java -Xmx512m then raise the Xmx until you receive the error.

Then you can set the highest possible number either in the configtool under instance -> server...

Or in the offlinecfgeditor at ID108183450.MexHeapSize and ID108183450.javaParameters

btw. the system will be useless if the heap needs to be allocated on the pagefile.

regards,

Jozsef