J2EE Framworks keep Restarting

[Former Member]

Hi All,

In NW2004s under Windows 2003, Oracle 10g I am getting problem in J2EE server0

its start framworks and start application then its restart it again

I have BI and PI server. both server has 4GB memory and virtual memory size 12260MB

so I setup all xxmemory paramaters same like BI in configTools

ABAP Trace log:

[Thr 6996] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 6996] JLaunchRequestQueueInit: create pipe listener thread

[Thr 7080] JLaunchRequestFunc: Thread 7080 started as listener thread for np messages.

[Thr 268] WaitSyncSemThread: Thread 268 started as semaphore monitor thread.

[Thr 6996] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)

[Thr 6996] CPIC (version=700.2006.09.13)

[Thr 6996] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx.c 2604]

[Thr 6996] [Node: server0] java home is set by profile parameter

Java Home: C:\j2sdk1.4.2_16-x64

[Thr 6996] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

******************************************

JStartupIReadSection: read node properties [ID3795650]

-> node name : server0

-> node type : server

-> node execute : yes

-> jlaunch parameters :

-> java path : C:\j2sdk1.4.2_16-x64

-> java parameters : -Djco.jarm=1 -XX:MaxPermSize=512M -XX:PermSize=512M -XX:NewSize=320M -XX:MaxNewSize=320M -XX:DisableExplicitGC -verbose:gc -XX:PrintGCDetails -XX:+PrintGCTimeStamps -Djava.awt.headless=true -Dsun.io.useCanonCaches=false -XX:SoftRefLRUPolicyMSPerMB=1 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=90 -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

-> java vm version : 1.4.2_16-b05

-> java vm vendor : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)

-> java vm type : server

-> java vm cpu : amd64

-> heap size : 2048M

-> init heap size : 2048M

-> root path : D:\usr\sap\PID\DVEBMGS00\j2ee\cluster\server0

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

-> OS libs path : D:\usr\sap\PID\DVEBMGS00\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 : D:\usr\sap\PID\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

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

-> parameters :

-> debuggable : no

-> debug mode : no

-> debug port : 50021

-> shutdown timeout : 120000

**********************************************************************

[Thr 6996] JLaunchISetDebugMode: set debug mode [no]

[Thr 5368] JLaunchIStartFunc: Thread 5368 started as Java VM thread.

[Thr 5368] [JHVM_PrepareVMOptions] use java parameters set by profile parameter

Java Parameters: -Xss2m

**********************************************************************

JHVM_LoadJavaVM: VM Arguments of node [server0]

-> stack : 1048576 Bytes

-> arg[ 0]: exit

-> arg[ 1]: abort

-> arg[ 2]: vfprintf

-> arg[ 3]: -Djco.jarm=1

-> arg[ 4]: -XX:MaxPermSize=512M

-> arg[ 5]: -XX:PermSize=512M

-> arg[ 6]: -XX:NewSize=320M

-> arg[ 7]: -XX:MaxNewSize=320M

-> arg[ 8]: -XX:+DisableExplicitGC

-> arg[ 9]: -verbose:gc

-> arg[ 10]: -XX:+PrintGCDetails

-> arg[ 11]: -XX:+PrintGCTimeStamps

-> arg[ 12]: -Djava.awt.headless=true

-> arg[ 13]: -Dsun.io.useCanonCaches=false

-> arg[ 14]: -XX:SoftRefLRUPolicyMSPerMB=1

-> arg[ 15]: -XX:SurvivorRatio=2

-> arg[ 16]: -XX:TargetSurvivorRatio=90

-> arg[ 17]: -Djava.security.policy=./java.policy

-> arg[ 18]: -Djava.security.egd=file:/dev/urandom

-> arg[ 19]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-> arg[ 20]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-> arg[ 21]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-> arg[ 22]: -Dsys.global.dir=D:\usr\sap\PID\SYS\global

-> arg[ 23]: -Dapplication.home=D:\usr\sap\PID\DVEBMGS00\exe

-> arg[ 24]: -Djava.class.path=D:\usr\sap\PID\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.

-> arg[ 25]: -Djava.library.path=C:\j2sdk1.4.2_16-x64\jre\bin\server;C:\j2sdk1.4.2_16-x64\jre\bin;C:\j2sdk1.4.2_16-x64\bin;D:\usr\sap\PID\DVEBMGS00\j2ee\os_libs;C:\j2sdk1.4.2_16-x64\bin;D:\oracle\PID\102\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files\Microsoft SQL Server\100\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files\Microsoft SQL Server\100\DTS\Binn\;D:\usr\sap\PID\SYS\exe\uc\NTAMD64

-> arg[ 26]: -Dmemory.manager=2048M

-> arg[ 27]: -Xmx2048M

-> arg[ 28]: -Xms2048M

-> arg[ 29]: -DLoadBalanceRestricted=no

-> arg[ 30]: -Djstartup.mode=JCONTROL

-> arg[ 31]: -Djstartup.ownProcessId=6808

-> arg[ 32]: -Djstartup.ownHardwareId=U1903088766

-> arg[ 33]: -Djstartup.whoami=server

-> arg[ 34]: -Djstartup.debuggable=no

-> arg[ 35]: -Xss2m

-> arg[ 36]: -DSAPINFO=PID_00_server

-> arg[ 37]: -DSAPSTART=1

-> arg[ 38]: -DCONNECT_PORT=3367

-> arg[ 39]: -DSAPSYSTEM=00

-> arg[ 40]: -DSAPSYSTEMNAME=PID

-> arg[ 41]: -DSAPMYNAME=pidev_PID_00

-> arg[ 42]: -DSAPPROFILE=D:\usr\sap\PID\SYS\profile\PID_DVEBMGS00_pidev

-> arg[ 43]: -DFRFC_FALLBACK=ON

-> arg[ 44]: -DFRFC_FALLBACK_HOST=localhost

-> arg[ 45]: -DSAPSTARTUP=1

-> arg[ 46]: -DSAPSYSTEM=00

-> arg[ 47]: -DSAPSYSTEMNAME=PID

-> arg[ 48]: -DSAPMYNAME=pidev_PID_00

-> arg[ 49]: -DSAPDBHOST=pidev

-> arg[ 50]: -Dj2ee.dbhost=pidev

**********************************************************************

Thank in Advanced

[shyam_dontamsetty · Accepted solution]

Hi Angeline,

1.Can you review your Java memory parameters or post the parameters.

• WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) - using -Xmx2048M [jstartxx.c 2604*

Can you check this parameter(max Heap Size) -Xmx=2048 in your system

2. check the file jvmx.jar file in this path D:\usr\sap\PID\DVEBMGS00\exe\jvmx.jar

Best Regards,

Shyam Dontamsetty

[Former Member · Accepted solution]

Hi,

Thank for reply,

Current setting is like this:

heap memory using \usr\sap\SID\DVEBMGS00\J2ee\configtool\configtool.bat

4GB Physical memory

Under Instance_ID9999

Max heap size MB 256

Under Server General

Max heap size MB = 2048

-Xmx1024m

-Xms1024m

-XX:PermSize=512m

-XX:NewSize=320m

-XX:MaxNewSize=320

Under Instance -> server_ID9999

Max heap size MB 1024

-XX:MaxPermSize=512M

-XX:PermSize=512M

-Xms2048m

-Xmx2048m

-XX:NewSize=320m

-XX:MaxNewSize=320

Its fixed last night and works fine, but at this mornning same now its stoped -2 error

Regards,

[Former Member · Accepted solution]

well there are many reasons for undefined loops of java startup/ framework

for example, if configtool has different 'Driver Location' (i.e ConfigurationManager) then you find this behavior.

so similar, recollect if had made any changes and revert back or make it correct.

-sekhar

[Former Member · Accepted solution]

Last night was worked fine, not it stopped with -2 and sometime -4

As you said change Xms and Xmx value, but in ConfigTool has 2 place to put that value

one is "Instance_ID9999" and Server_ID9999, where should I goto change that value Instance_ID or Server_ID

Please advise

[Former Member · Accepted solution]

additionally, refer Note 997510 - Troubleshooting J2EE Engine 6.40/7.0 Bootstrap Issues

-sekhar

Edited by: sekhar on Mar 5, 2010 7:15 PM

[Former Member · Accepted solution]

login to configtool, click on Find button

type string 'drive' ->choose start

Select one entry -> then choose Go

now put the correct value - Choose 'Add'

similarly repeat the same all the entries (in your case 2 times)

click on 'Save' (if require 2 times)

restart your Java

-sekhar

[Former Member · Accepted solution]

Hi there,

Please kindly tell me anyone which memory I have to increase, because J2ee engine keep restarting...

ConfigTools:

Instance_ID

Xmx:1024M

Xms:1024M

Server_ID

Xmx:2048M

Xms:2048M

here is some screenshot, where sould I add these entry please verify, i really appricaited your time...

http://www.flickr.com/photos/38842895@N04/4408666423/sizes/o/

http://www.flickr.com/photos/38842895@N04/4408666401/sizes/o/in/photostream/

http://www.flickr.com/photos/38842895@N04/4409432738/sizes/o/in/photostream/

Please help

Thanks

Edited by: AngelinePurnama on Mar 5, 2010 11:50 PM

[Former Member · Accepted solution]

I don't see any issue with your current configuraton as per your post.

But for your knowledge, you can go through this link that helps you in determining the size of memory according different parameters.

http://help.sap.com/saphelp_nwce10/helpdata/en/f0/cec51dabd1461b87e4db9e3958710e/frameset.htm

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

-sekhar

Edited by: sekhar on Mar 6, 2010 6:34 AM

[Former Member · Accepted solution]

Hi,

The parameter settings seem to be fine.....Can you repeat the issue and post recent lines of std_server<x>.out file ?

Cheers....,

Raghu

[Former Member · Accepted solution]

Hi All,

ok here is current configuration for J2EE (Remember I have 4GB memory and visual memory 12GB setup)

Instance_ID - Message Server & bootstartup TAB

Max heap size in BM 750

Instance_ID - Server General TAB

Max heap size in BM 750

-Xmx512m

-Xms512m

-XX:PermSize=512m

-XX:MaxPermSize=512m

-XX:NewSize=320m

-XX:MaxNewSize=320m

Server_ID - General TAB

Max heap size in BM 750

-XX:MaxPermSize=512M

-XX:PermSize=512M

-Xms512M

-Xmx512M

-XX:NewSize=320M

-XX:MaxNewSize=320M

-XX:+DisableExplicitGC

-verbose:gc

-XX:+PrintGCDetails

-XX:+PrintGCTimeStamps

I really appricaited your all time... but I really want to fix that problem...

Thank

[Former Member · Accepted solution]

Hi my friend

It looks like lack of main memory, the symptom is that server0 restarts itself sometimes but bootstrap and dispatcher remain running.

Usually AS Java instance requires at least 6GB physical memory, a little more for 64bit. I think in your case it's a 32bit Windows 2003, isn't it? So basically main memory will shared by: 0.8-1GB by OS kernel, Oracle DB (you didn't indicate), bootstrap(you didn't indicate, I guess it should be 256MB), 512MB by dispatcher and 512MB by server0. Server0 requires enough physical memory when being started or current insufficient resource for new activities, regardless of 12GB page file.

Please refer to note 723909 and 716604 to configure your JVM and your current 4GB physical memory is obviously insufficient. So if adding memory is not an option for you, then you have to try decrease memory allocated for Oracle, but it might turn into another bottleneck of performance.

Regards,

Effan

[Former Member · Accepted solution]

Thank you so much Effan, for you time...

ok as you said Java startup need more memory, I have 4GB memory and I try to increase Heap memory 512 to 1024 even I treid 2048 as well

I have 64bit windows 2003 server... I know 4GB memory is not good for server... but for the time being we have to start Java instance...

could you please guide me where should I change these value...

one dispatcher and instance_Id and server_ID, bootstartup tab, boot-startup general TAB, ???

Thank

[Former Member · Accepted solution]

I don't see an ideal option here because of your 4GB memory, my friend. Let's do a math: ideally 1GB(OS) + 2GB(Oracle) + 256MB(bootstrap) + 512MB(dispatcher) + 2GB(each server node)= 5.75GB.

But in your case let's assume there's no much DB activities and decrease to like: 1GB for Oracle, 200MB for bootstrap, 256MB for dispatcher and 1536MB for server0; see if it can get any better. You can find details in note 723909 and 716604.

Regards,

Effan

[Former Member · Accepted solution]

I got your math , thats really good calculation, basically our database has no load...

But I am still little confouse, basically dispatcher is works fine... so we just looking server0

Where should I put and change value... there is 3 location

Displatcher

Instance_ID

Server_ID

Everyting has heap memory size where should I change... ok I am sending some screen shot one by one please look at it and give me advised please

Instance

http://www.flickr.com/photos/38842895@N04/4418088260/sizes/o/in/photostream/

Dispatcher

http://www.flickr.com/photos/38842895@N04/4418088404/sizes/o/in/photostream/

Server

http://www.flickr.com/photos/38842895@N04/4418088504/sizes/o/in/photostream/

Thank in Advance

[Former Member · Accepted solution]

> But I am still little confouse, basically dispatcher is works fine... so we just looking server0

Dispatcher in AS Java is like disp+work in AS ABAP, it doesn't do heavy work but communicating with message server and enqueue server, server nodes do.

Your changes look fine, please give it a restart to take effect and see how it's going. If server0 still restarts itself, try increase server0 memory to 2048 as my last shot.

Regards,

Effan

[Former Member · Accepted solution]

Hi all,

Basically problem was one of messages stick in que xi_af_msg table... and trying to pull out when I start instance... simply in SQL delete that messages from the table....

delete from xi_af_msg where status = 'FAIL' someting like that...