Skip to Content
author's profile photo Former Member
Former Member

server0 keeps standing with yellow color

Dear experts,

My J2EE engine keep the status Start Apps on the Console Management for a long time, instead of changing to Running. I cover the log file and have some confused thing, pls help me to find the solution.

"SAPJarResourceCloseTimeoutThread" daemon prio=5 tid=0x07b99b10 nid=0x1594 in Object.wait() [9c4f000..9c4fd94]

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

- waiting on <0x17810138> (a com.sap.engine.frame.core.load.res.JarThread)

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

at com.sap.engine.frame.core.load.res.JarThread.run(JarThread.java:32)

- locked <0x17810138> (a com.sap.engine.frame.core.load.res.JarThread)

"Thread-14" daemon prio=5 tid=0x07cd8410 nid=0x157c in Object.wait() [9c0f000..9c0fd94]

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

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

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

- locked <0x17812350> (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)

"Background Jobs Internal Thread" daemon prio=5 tid=0x078b44e0 nid=0x15a8 in Object.wait() [9bcf000..9bcfd94]

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

- waiting on <0x17812378> (a java.lang.Object)

at com.sap.engine.cache.job.impl.BackgroundExactImpl.run(BackgroundExactImpl.java:134)

- locked <0x17812378> (a java.lang.Object)

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

"Timeout Service Integrity Watcher Thread" daemon prio=10 tid=0x080f5008 nid=0x1648 runnable [9b8f000..9b8fd94]

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

- waiting on <0x178123e0> (a com.sap.engine.cache.job.impl.IntegrityWatcher)

at com.sap.engine.cache.job.impl.IntegrityWatcher.run(IntegrityWatcher.java:54)

- locked <0x178123e0> (a com.sap.engine.cache.job.impl.IntegrityWatcher)

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

"Background Jobs Internal Thread" daemon prio=5 tid=0x07fccad8 nid=0x1644 in Object.wait() [9b4f000..9b4fd94]

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

- waiting on <0x17812420> (a java.lang.Object)

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

at com.sap.engine.cache.job.impl.BackgroundExactImpl.run(BackgroundExactImpl.java:115)

- locked <0x17812420> (a java.lang.Object)

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

"Timeout Service Integrity Watcher Thread" daemon prio=10 tid=0x07c786e8 nid=0x1640 runnable [9b0f000..9b0fd94]

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

- waiting on <0x17812468> (a com.sap.engine.cache.job.impl.IntegrityWatcher)

at com.sap.engine.cache.job.impl.IntegrityWatcher.run(IntegrityWatcher.java:54)

- locked <0x17812468> (a com.sap.engine.cache.job.impl.IntegrityWatcher)

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

....

"Finalizer" daemon prio=9 tid=0x010f06a0 nid=0x1304 in Object.wait() [34bf000..34bfd94]

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

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

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

- locked <0x17816680> (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=0x010efa88 nid=0x1300 in Object.wait() [347f000..347fd94]

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

- waiting on <0x178137f8> (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 <0x178137f8> (a java.lang.ref.Reference$Lock)

"main" prio=5 tid=0x003d49b0 nid=0x1408 in Object.wait() [619af000..619afe1c]

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

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

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

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

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

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

Pls help!!!

Thanks in advance,

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jun 30, 2008 at 10:43 PM

    Have you tried restarting the AS-JAVA instance?

    During restart, use the logviewer and monitor the j2ee\cluster\server0\log\defaultrace.trc file. This file contants 80% of all errors from my experiences.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 01, 2008 at 08:21 AM

    Hi Pham,

    I am not sure whether this will help or not, but can you check whether the server service is running or not?

    Go to services.msc in the run command and start the service named server if it is in stopped state.

    Bye

    Ankur

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 25, 2008 at 02:15 PM

    Hi Pham

    Look in MMC under server0, are there any numbers under the restars or errors columns? Also have a look at your std_server.out log file in your work directory. That will tell you where the startup is failing and the reasons for it.

    Regards

    Fayzal

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 26, 2008 at 05:23 PM

    Hi Pham Nguyen Vu,

    once check your sdm,and dispacther then restart the server0 node. In MMC you check all these,check the log file for any errors, i hope this might solve your problem.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.