server0 getting restarted when i access UME config...

Hai experts,

i have changed UME configuration for ABAP , and for testing the sap system I.e ( through system configuration )when i click on UME configuration tab my server0 is getting restarted , before restart it ends with exit code 666 and starts again. i logged in through sap* to access this.

kindly help me where to modify or any changes has to be done.

thanks in advance..

regards

Arun

SAP Managed Tags:
NW AS Java Administrator (NWA)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (5)

Hi All:

i tried to double those settings of memory, and it works.

parameters:

java heap size

xms

xmr

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Dear Arun

As many other folk advised you about the memory setting problem. Please go through the below link to findout the solution of your problem.!

https://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P19

Regards

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

HI Anwer Waseem,

i tried by changing the value of heap memory upto 2.5 GB where Memory is only upto 3GB is available.

when i try to access UME configuration or webdynpro component , server0 gets restarted.

tried by changing values in all the cases..

Java Parameters -- server is

-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=512M

-XX:PermSize=512M

-Xms1024M

-XX:NewSize=171M

-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

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

the above parameters is set to server ID--.

Logs from std_server0 :

FATAL: Caught OutOfMemoryError! Node will exit with exit code 666

================================================================================

java.lang.OutOfMemoryError.

Any more changes has to be followed for java paramter?

Kindly

Regards

Arun

Hello Arun,

Set following parameters,

-XX:MaxPermSize=256M

-XX:PermSize=256M

-Xms1024M

-Xmx1024M

-XX:NewSize=170M

-XX:MaxNewSize=170M

Regards

Pramod

Hello Promod,

I changed the parameters as you specified , still getting restarted when i access the ume configuration.

any more changes...

Regards

Arun

Hello Arun,

I know this is very basic thing, but as you have tried most things, after changing VM parameters via configtool, you are restarting your J2EE system right?

When system is starting or after system is started, have you checked default trace before loging to system and accessing UME link?

May be there is some problem with UME application starting.

Also please let us know is your system on 32 bit hardware or 64 bit hardware?

Regards,

Abhay

Hello Abhay

I know this is very basic thing, but as you have tried most things, after changing VM parameters via configtool, you are restarting your J2EE system right?

After changing the parameters, restarting the server and then i try to other operation.

When system is starting or after system is started, have you checked default trace before loging to system and accessing UME link?

May be there is some problem with UME application starting.

Not only server restarts when i access UME comfiguration, it restarts when accessing content administration also.i dont think the problem is in UME application.

Also please let us know is your system on 32 bit hardware or 64 bit hardware?

system is 32bit Hard

regards

Arun

Hello Arun,

As per your reply, I am assuming below things.

1. Your system is standalone J2EE portal, with one server node.

2. You have set Max heap size as 1 GB (1024 MB) which is correct and should only be set for 32 bit system for one server node (As per SAP standard, you can check note for VM parameters)

3. Problem is not specific to UME.

Hence as per me, there is memory leak in your system,

Just try to start your system in safe mode (option is available in config tool), this will start system with minimum required applications.

Once system is started , check for above problem by accessing UME or content admin.

Running system in safe mode is just for checking, once checking is done, revert to normal mode.

Let us know the output.

Regards,

Abhay

hi abhay,

Thanks a lot , i changed the same and started in safe mode , now i am not facing the problem.

after reverting back from safe mode , i will check the same and reply the status....

Since some login problem with my account , i couldnt make it earlier....

Regards

Arun Rajan

Hi,

plz provide the std_server* files and dev_server* files with the default trace files during the time the server nodes restart happens.

regards,

sreekanth

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

std_server0

getThreadDump : Thu Aug 27 10:08:54 2009

FATAL: Caught OutOfMemoryError! Node will exit with exit code 666

================================================================================

java.lang.OutOfMemoryError

Full thread dump Java HotSpot(TM) Server VM (1.4.2_11-b06 mixed mode):

"Thread-113" daemon prio=5 tid=0x05ef7118 nid=0x1c4c in Object.wait() [0x5d84f000..0x5d84fd94]

at java.lang.Object.wait(Native Method)

- waiting on <0x270dffc8> (a java.lang.ref.ReferenceQueue$Lock)

at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)

- locked <0x270dffc8> (a java.lang.ref.ReferenceQueue$Lock)

at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)

at com.sap.engine.cache.util.ReferenceQueueRunnable.run(ReferenceQueueRunnable.java:43)

at java.lang.Thread.run(Thread.java:534

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

dev_server0

Thu Aug 27 10:13:02 2009

1280 ! com.sapportals.portal.prt.util.AutoClassLoader$ClassPath::_createLocation (290 bytes)

Thu Aug 27 10:13:31 2009

1281 ! com.sapportals.portal.application.applicationrepository.ApplicationRepositoryService::__getTechnicalUser (66 bytes)

1282 com.sap.security.core.srvUser.imp.ServiceUserFactory::checkForServiceUser (243 bytes)

1283 ! com.sap.security.core.util.cache.BaseTechCacheWrapper::get (86 bytes)

1284 java.util.Arrays$ArrayList::size (6 bytes)

1285 java.util.Arrays$ArrayList::get (7 bytes)

Thu Aug 27 10:13:33 2009

1286 EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap$HashIterator::nextElement (5 bytes)

Thu Aug 27 10:13:41 2009

1287 ! com.sapportals.portal.pcd.pl.PlAttribute::cloneKeepReadOnlyFlag (97 bytes)

1288 com.sapportals.portal.pcd.pl.PlAttribute::clone (12 bytes)

Thu Aug 27 10:13:45 2009

64% ! java.lang.ref.Finalizer$FinalizerThread::run @ 0 (21 bytes)

Thu Aug 27 10:13:50 2009

1289 java.util.HashMap$Values::iterator (8 bytes)

1290 s oracle.jdbc.driver.OraclePreparedStatement::clearParameters (29 bytes)

Thu Aug 27 10:13:51 2009

1291 com.sap.sql.sqlparser.SQLLexer::makeToken (7 bytes)

1292 com.sap.sql.sqlparser.CheckGroupVisitor$WhereChecker::visitColumnReference (32 bytes)

1293 ! com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl::commonCleanup (84 bytes)

1294 com.sap.engine.services.dbpool.cci.ConnectionHandle::<init> (81 bytes)

1295 com.sapportals.portal.pcd.pl.AttributeValuesTable::readAttributeValue (662 bytes)

1296 oracle.sql.CharacterSet::conv3ByteUTFtoUTF16 (71 bytes)

1297 com.sapportals.portal.pcd.pl.PlFactory::getInteger (72 bytes)

1298 oracle.sql.CharacterSet::conv2ByteUTFtoUTF16 (36 bytes)

1299 oracle.sql.CharacterSet::isHiSurrogate (16 bytes)

1300 oracle.jdbc.driver.T4CClobAccessor::processIndicator (156 bytes)

1301 com.sapportals.portal.pcd.pl.PlAttribute::setInternalNoEmptyLocaleMapping (114 bytes)

1302 s com.sapportals.portal.pcd.pl.PlBiDirectionalCache::getObject2 (54 bytes)

1303 ! com.sapportals.portal.pcd.pl.PlAttribute::readTextValue (102 bytes)

1304 ! com.sapportals.portal.pcd.pl.AttributeHeadersTable::selectSubtreeObjectsAttributeHeaders (145 bytes)

Thu Aug 27 10:13:52 2009

1305 com.sapportals.portal.pcd.pl.PlFactory::composeAttributeString (96 bytes)

1306 oracle.jdbc.driver.T4C8TTIClob::read (297 bytes)

1307 com.sapportals.portal.pcd.pl.PlAttribute::setInternalNoEmptyLocaleMapping (114 bytes)

1308 com.sapportals.portal.pcd.pl.PlLocaleCache::getLocale (118 bytes)

1309 com.sapportals.portal.pcd.pl.PlFactory::isLazyReadLocale (40 bytes)

1310 ! com.sapportals.portal.pcd.pl.AttributeValuesTable::selectSubtreeObjectsAttributeValues (145 bytes)

1311 java.lang.Long::hashCode (14 bytes)

1312 oracle.jdbc.driver.T4CTTIoer::processError (187 bytes)

Thu Aug 27 10:13:53 2009

1313 ! com.sapportals.portal.pcd.pl.AttributeValuesTable::selectById (91 bytes)

1314 s java.util.Hashtable::size (5 bytes)

1315 java.lang.Integer::equals (29 bytes)

1316 java.util.Hashtable$Entry::clone (41 bytes)

1317 ! com.sapportals.portal.prt.util.AutoClassLoader::loadClassLocally (127 bytes)

1318 com.sun.naming.internal.ResourceManager::getInitialEnvironment (131 bytes)

Thu Aug 27 10:13:54 2009

1319 com.sap.security.core.srvUser.imp.ServiceUserFactory::getUniqueNameMapping (36 bytes)

Thu Aug 27 10:13:58 2009

1320 com.sapportals.portal.prt.deployment.descriptor.ServiceList::getService (72 bytes)

1321 com.sapportals.portal.prt.deployment.descriptor.PropertyList::load (102 bytes)

1322 com.sapportals.portal.prt.deployment.descriptor.FilteredNodeList::getLength (17 bytes)

Logs at the time of restart....

Edited by: Arun Rajan on Aug 27, 2009 7:17 AM

Edited by: Arun Rajan on Aug 27, 2009 7:19 AM

Edited by: Arun Rajan on Aug 27, 2009 7:20 AM

Hi sreekanth,

dev_server log .....

"SAPEngine_Application_Thread[impl:3]_0" prio=5 tid=0x05ab2658 nid=0x2c9c in Object.wait() [0x067af000..0x067afd94]

at java.lang.Object.wait(Native Method)

- waiting on <0x1ab12cf0> (a com.sap.engine.lib.util.WaitQueue)

at java.lang.Object.wait(Object.java:429)

at com.sap.engine.lib.util.WaitQueue.dequeue(WaitQueue.java:238)

- locked <0x1ab12cf0> (a com.sap.engine.lib.util.WaitQueue)

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

"Thread-1" prio=5 tid=0x011fe830 nid=0x2700 in Object.wait() [0x05b3f000..0x05b3fd94]

at java.lang.Object.wait(Native Method)

- waiting on <0x1ab14480> (a com.sap.engine.core.Framework)

at java.lang.Object.wait(Object.java:429)

at com.sap.engine.core.Framework.start(Framework.java:203)

- locked <0x1ab14480> (a com.sap.engine.core.Framework)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.boot.FrameThread.run(FrameThread.java:61)

at java.lang.Thread.run(Thread.java:534)

"Signal Dispatcher" daemon prio=10 tid=0x011b8a48 nid=0x2d60 waiting on condition [0x00000000..0x00000000]

"Finalizer" daemon prio=9 tid=0x003cfa58 nid=0x1f50 in Object.wait() [0x0573f000..0x0573fd94]

at java.lang.Object.wait(Native Method)

- waiting on <0x1ab14858> (a java.lang.ref.ReferenceQueue$Lock)

at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)

- locked <0x1ab14858> (a java.lang.ref.ReferenceQueue$Lock)

at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)

at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)

"Reference Handler" daemon prio=10 tid=0x003cf6d8 nid=0x299c in Object.wait() [0x010ef000..0x010efd94]

at java.lang.Object.wait(Native Method)

- waiting on <0x1ab132c0> (a java.lang.ref.Reference$Lock)

at java.lang.Object.wait(Object.java:429)

at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)

- locked <0x1ab132c0> (a java.lang.ref.Reference$Lock)

"main" prio=5 tid=0x003c4ca0 nid=0xa14 in Object.wait() [0x61acf000..0x61acfe1c]

at java.lang.Object.wait(Native Method)

- waiting on <0x1ab148c0> (a com.sap.engine.boot.StartFrame)

at java.lang.Object.wait(Object.java:429)

at com.sap.engine.boot.StartFrame.work(StartFrame.java:106)

- locked <0x1ab148c0> (a com.sap.engine.boot.StartFrame)

at com.sap.engine.boot.Start.main(Start.java:34)

"VM Thread" prio=5 tid=0x003ced68 nid=0x2274 runnable

"Suspend Checker Thread" prio=10 tid=0x011b8078 nid=0x1660 runnable

[Thr 8820] JLaunchIExitJava: exit hook is called (rc = 666)

[Thr 8820] **********************************************************************

ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.

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

[Thr 8820] JLaunchCloseProgram: good bye (exitcode = 666)

server gets restarted....

if any parameters value should be modified.

Regards

Arun.

This looks like a problem with the memory settings..

Read,

[SAP Note 723909 - Java VM settings for J2EE 6.40/7.0|https://service.sap.com/sap/support/notes/723909] and related notes

Regards

Juan

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Juan,

As per Note 723909 , heap size is set to -Xmx1024m and -Xms1024m. But still when i supposed to use UME configuration tab to verify the sap system ,server0 gets restarted.

regards

Arun Rajan.

Check developer traces/log files as mentioned in throubleshooting guide (link in earlier post)

Hi manoj,

checked the trace files , error occurred due to java.lang.outofmemory.

so i increased the premsize and maxpremsize from 128m to 256m. but still i am getting the same , server0 gets restarted when accessing the UME configuration.

Regards

Arun.

hi manoj,

checked the log/traces file and found the error: java.lang.outofmemory.

so i changed the permsize and maxpermsize from 128M to 256M . But the probelm remains still.

server0 gets restarted when accessing the UME configuration.

Regards

Arun.

Hi Arun,

How many server nodes do you have in the cluster. What is the heap size that you have set. . Can you please attache the dev_server* files and std_ser* files .

Regards,

Karthick.

Hope you have enough RAM. Try to configure swap/virtual memory 3 to 4 times of your RAM if it is not done already.

Please find attached troubleshooting guide.

[https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e09e4a5e-8280-2a10-ca98-a59dd47d396d&overridelayout=true]

Do you have the enough swap space assigned on this system and heap memory ?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Ask a Question

Top Q&A Solution Author

User

Count