server0 won't start

[Former Member]

Hi All,

I have BW 7.

some reason in MMC server0 won't start. I checked \usr\sap\SID\DVEBMGS00\j2ee\configtool file, lot of thing there, but I don't know how to fix ?

Is anyone tell me steps...

Thanks a lot in Advanced

Angeline

[Former Member · Accepted solution]

Hi,

Post the server0 log file. It will be located in usr/sap/sid/j2ee/cluster/server0/log. Did you install any java version in your server recently? Also check the bootstrap.properties file.

Regards,

Vamshi.

[Former Member · Accepted solution]

ok let me found out that fine first and I can post it

[Former Member · Accepted solution]

This is Server0.log file

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed

Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR partner '127.0.0.1:sapgw00' not reached

TIME Wed Jul 01 12:16:00 2009

RELEASE 700

COMPONENT NI (network interface)

VERSION 38

RC -10

MODULE nixxi.cpp

LINE 2823

DETAIL NiPConnect2

SYSTEM CALL connect

ERRNO 10061

ERRNO TEXT WSAECONNREFUSED: Connection refused

COUNTER 1

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)

at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)

at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)

at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)

at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)

... 6 more

I think proble is define is localhost not application server name.... where may i go to change that value...

Thanks in Advanced

[Former Member · Accepted solution]

update your hosts file with the application server name and its IP

Regards,

Pavan

[Former Member · Accepted solution]

Hi,

Have you set the parameter: icm/host_name_full . This should be some thing like abc.xyz.com

Then you need to restart the server. Also you have make the above entry in the host file at the os level.

Are you sure your server0.log file is this small? Any other info?

Regards,

Vamshi.

[Former Member · Accepted solution]

Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1

Did you try use server name instead of just localhost? For some reason gateway is not reachable or connections can not be made. Check your firewall rules, disable antivirus and give a go. Also check settings in services file for sapgw00

ERRNO 10061
ERRNO TEXT WSAECONNREFUSED: Connection refused

[http://msdn.microsoft.com/en-us/library/ms740668(VS.85).aspx]

[Former Member · Accepted solution]

Hello Vamshi and Manoj

Thanks for reply, I checked default profile, start profile, and instance profile, everying is looks same, and I see SMICM services are fine too in QA system when I run Tr: SMGW, no entry listed there

I checked SICF to found some clue... but no luck

Manoj, I disable firewall on server, but same thing...

thats look like gateway is not reachable

How to change localhost name to full server name ? where should I go and what is the Tcode?

Thanks for you help

Angeline

[JPReyes · Accepted solution]

check std_server0.out and std_dispatcher.out and post the errors here

Regards

Juan

[Former Member · Accepted solution]

STD_SERVER0.OUT

-

---

node name : server0

pid : 22355

system name : BQA

system nr. : 00

started at : Wed Jul 22 07:18:25 2009

[Thr 34484] MtxInit: -2 0 0

Error occurred during initialization of VM

Could not reserve enough space for object heap

STD_DISPATCHER.OUT

-

---

Loading: LogManager ... 281 ms.

Loading: PoolManager ... 0 ms.

Loading: ThreadManager ... 47 ms.

Loading: IpVerificationManager ... 16 ms.

Loading: ConnectionsManipulator ... 0 ms.

Loading: ClassLoaderManager ... 15 ms.

Loading: ClusterManager ... 94 ms.

Loading: PortsManager ... 0 ms.

Loading: LockingManager ... 31 ms.

Loading: ConfigurationManager ... 0.0188029 secs]

1235 ms.

Loading: LicensingManager ... 15 ms.

Loading: CacheManager ... 94 ms.

Loading: ServiceManager ...

Loading services.:

Service security started. (16 ms).

Service sld started. (31 ms).

Service httptunneling started. (31 ms).

Service licensing started. (32 ms).

Service r3startup started. (47 ms).

Service memory started. (47 ms).

Service timeout started. (47 ms).

Service jmx_notification started. (47 ms).

Service webservices started. (47 ms).

Service keystore started. (47 ms).

Service iiop started. (62 ms).

Service shell started. (94 ms).

Service ssl started. (63 ms).

Service telnet started. (62 ms).0.0372559 secs]

Service p4 started. (297 ms).

Service classload started. (0 ms).

Service jmx started. (219 ms).

Service log_configurator started. (1188 ms).

Service configuration started. (0 ms).

[Full 0.1150354 secs]

Service basicadmin started. (282 ms).

Service adminadapter started. (16 ms).

Service http started. (344 ms).

Service jms_provider started. (344 ms).

Service tc.monitoring.logviewer started. (563 ms).

ServiceManager started for 2531 ms.

Framework started for 4609 ms.

SAP J2EE Engine Version 7.00 is running!

>

Login :

[Former Member · Accepted solution]

Error occurred during initialization of VM
Could not reserve enough space for object heap

Increase heapsize (config tool) if you enough memory. Also check your operating system paging file size is 3 to 4 times of your RAM.

Check Note 723909 - Java VM settings for J2EE 6.40/7.0

[Former Member · Accepted solution]

Hi, Manoj

I was tyring to found paramaters to see Heap size in ConfigTool, but I didn't found any heapsize paramaters, please can you tell me what is the paramater ?

2nd I checked profile there is one paramaters: Jstartup/max_heap_size = 64MB, our server has phisical 12GB memory and when i check memory through OS level it shows only 1GB left / available

I mean can we change that one through Tr: RZ10 or default profile or instanace profile someting like that...

Thanks

[Former Member · Accepted solution]

Hi,

Just double click on the server_IDXXXX you will find the java parameters on the right hand side of the window.

I am not sure about the note number but can find in the market place. It tells the jvm parameters to me maintained.

Regards,

Vamshi.

[Former Member · Accepted solution]

check these notes,

Note 710146 - How to change J2EE Engine JVM Settings

Note 1303953 - SAP JVM memory parameters and their names in the Config Tool

Regards,

Ravi

[Former Member · Accepted solution]

Hi, Vamshi

You are so helpful, you know I already checked complete ConfigTools, there is no paramaters such as jvm. I do found out server_ID no.... even i checked under the tree managers and services as well

[Former Member · Accepted solution]

Hi,

Minimum Heap memory parameters is (Xms)

and Maximum Heap memory parameters. (Xmx).

In the same way u can find other parameters also in the config tool.

Just login to ur config tool---> cluster data->instance_IDXXX---->server_IDXXX

on the right side u can see general tab below that u can see all Java parameters.

change the heap values (or any other Java parameters)there. save them.

Regards,

Ravi

[Former Member · Accepted solution]

Hi, Vashmi

wowoowow! I got that screen thanks you

Before you read this one I want to tell one one thing, I have 12GB memory in QAS server, and it said Maximum HeapSize = 1024MB...

and Physical memory is available in QAS system 5100000 KB like 51MB

Now please tell me what I have to change in blow:

-Djco.jarm=1

-XX:MaxPermSize=512M THis one

-XX:PermSize=512M This one

-Xms2048M

-Xmx2048M

-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

[Former Member · Accepted solution]

If ur system is EP6

refer this note.

Note 696410 - Java VM settings for EP6 on J2EE 6.20

4. Heap Size

4.1 For the server node the minimum value for -Xmx is 512m.

4.2 In productive environments we recommend 1.5 GB (*) for 32-bit

and 2.5 GB for 64-bit machines. AIX, HP and Solaris need special patches/tuning to enable this heap size, see Note 492222 and chapter 10 below.

For Solaris 8 and higher no extra settings are needed and one can use even 3 GB heap.

Please refer to note 748713 for Startup Framework restrictions.

4.3 The -Xms value should be equal to -Xmx

4.4 The heap size of all Java server nodes must fit completely into the physical memory in order to avoid heavy paging on OS level. You must also consider the space needed for OS and other processes. For each Java VM on the server, all Java memory must fit completely into physical memory (no paging)!

Regards,

Ravi

[Former Member · Accepted solution]

Hi,

Note 723909 - Java VM settings for J2EE 6.40/7.0 Refer this note it says what's the recommended value.

Set the values accordingly by going through the note.

Regards,

Vamshi.

[Former Member · Accepted solution]

hi,

i guess manoj has already given note above refer it,

Increase heapsize (config tool) if you enough memory. Also check your operating system paging file size is 3 to 4 times of your RAM.

Check Note 723909 - Java VM settings for J2EE 6.40/7.0

[Former Member · Accepted solution]

Hi Ravi and Vashmi

As you know I am running under Windows 2003 server NW7, physical memory 12GB under oracle db

1. I tried to change heap size 1024 to 2048 save it and strat server just stop and start sap, not physical machine... Nothing happend

2. Open ConfigTool and return back heap size 2048 to 1024

3. In Instance_ID Servers General Tab: I change value XX:MaxNewSize=640m to 1024m also changed XX:MaxNewSize 640M to 1024M and saved it and stop and start sap server nothing happend

I am sending current value agian please let me know what i should change

I really appricate your time

Servers General

-

---

-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

-Dorg.xml.sax.driver=com.sap.engine.lib.xml.parser.SAXParser

-verbose:gc

-Xmx2048m

-Xms2048m

-Djco.jarm=1

-XX:PermSize=1024m

-XX:MaxPermSize=1024m

-XX:NewSize=1024m

-XX:MaxNewSize=1024m

-XX:SurvivorRatio=2

-XX:TargetSurvivorRatio=90

-XX:+PrintGCTimeStamps

-XX:+UseTLAB

-XX:SoftRefLRUPolicyMSPerMB=1

-Dsun.io.useCanonCaches=false

-Djava.awt.headless=true

-Xss2m

-XX:+UseParNewGC

-

---

IN MESSAGE SERVER & BOOTSTARUP

Max Heap size (in MB) 2GB selected

Edited by: T A on Jul 22, 2009 11:24 PM

[Former Member · Accepted solution]

Hi,

Now check and post what you server0 log file says. This time post the log file completely.

I assume your SDM and Dispatcher start and only the server0 doesnt start. Post the server0 log file completely.

Regards,

Vamshi.

[Former Member · Accepted solution]

Hi Vamshi

How are you today, sorry late reply, you konw what I did, just change heap memory it was selected 2048M now I put it back 1024M and its goes green ( now problem has been resolved), thanks you very very much for your help and time....

but I have one small thing, after BI guy trying to get some BEX Reporting through potols, it take toooooooo long time to get report, why is that like, is that issue i changed memory...

And what is the easy way to checks memory issues... where the first step i have to check memory or performance issues...

becuase J2EE goes yellow, and after 5 munites goes green

Take care

[Former Member · Accepted solution]

Hi,

Really not sure some times the java stack behaves very wiered. General recommendation would be as Java stack would occupy much memory, Always a standalone portal system is suggested which will reduce the load on the BI system.

I understand it all depends on how client wants to proceed.

Have a good day!!!

Regards,

Vamshi.

[Former Member · Accepted solution]

Hi, Vamshi,

The last time I having problem in Server0 J2EE wasn't start and I increase Heap memory as you guys siad, thanks a lot, and in BI server J2EE engine is running and working fine... here is old URL related that...

BUT now in PI Development server having same problem, I changed hip memory size, it keep tyring to start framworks and stopped again!!!

Server has 4GB memory and I increased Heap size using configTools...

Heap size: 2048MB

-XX:MaxPermSize=512M

-XX:PermSize=512M

-Xms2048M

-Xmx2048M

-XX:NewSize=320M

-XX:MaxNewSize=320M

-XX:+DisableExplicitGC

Ok here is story:

When I right click on J2EE server and tyring to start or Enable its become yellow and start framworks, in windows task manager it shows Jcontrol + Jlunch start 3 times, and getting lot of memory!!!

I am not sure is that problem or what?

I checked the following:

There is log of logs, I am not sure which logs i have to check it

usr/sap/SID/DEVBMGSID/J2ee/cluster System.log ( I didn't understand that logs btw what does it do?)

usr\sap\SID\DVEBMGS00\j2ee\cluster\dispatcher\log (there are some default trace logs)

usr\sap\SID\DVEBMGS00\j2ee\cluster\server0 (dev_jrfc.trc logs blow)

LCRBEAN_GET_PROFILE_PARAMETERnot found on host PI-DEV, ProgId =LCRSAPRFC_PRD: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/LCRBEAN_GET_PROFILE_PARAMETER.

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:138)

at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

I checkd dev_server0 trace

Please tell me where and which logs i shoud check?

Thanks in Advanced

Edited by: T A on Aug 17, 2009 7:13 PM

[Former Member]

Post New Thread

[Former Member]

This is same question, but different server

Edited by: T A on Aug 17, 2009 7:30 PM

[Former Member]

Can you please paste the defaultrace.trc file too. You can fnd this file in Drive Letter:/usr/sap/<SID>/JC or DV/j2ee/cluster/server0/log

[sunny_pahuja2]

Hi,

Could you please paste std_server0 and dev_server0 logs here ?

Thanks

Sunny