cancel
Showing results for 
Search instead for 
Did you mean: 

NW2004s portal , dispatcher and server0 not start

Former Member
0 Kudos

Hello,

I have made an exact copy of our production server to create a development server. I have installed it but the dev server not start. The jcontrol.exe stay yellow and the dispatcher and the server0 stay on "Starting framework". No error in the dump stack trace.

The developer trace for the dispatcher and the server0 has :

...

[Thr 38588] JLaunchISetClusterId: set cluster id 18813800

[Thr 38588] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 38588] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

and nothing after.

I have checked the files std_dispatcher.out and std_server0.out, and i have the same thing:

...

Loading : ClusterManager ... 154ms

Loading : LockingManager ...

I have wait 1 day and no change.

Somebody could help me? Please.

View Entire Topic
Former Member
0 Kudos

Is your Java id pointing to the correct server? You can check it in the configtool. Also, check if note 757692 is applicable to your situation.

RSB

Former Member
0 Kudos

I already check my java vm settingd and all is correct. Comcerning the note. It's note for me because the DEV server is an exact copy of the PRD server. So it's the same name of computer. The only difference is the dev server is not on the network because if we connect it, we could have a conflict with the name of the PRD Computer.

Former Member
0 Kudos

Hi,

Did you check your java settings like JAVA_HOME, PATH etc.

Also i can observe that the VM settings may not be right.

It should be 2048m for the server nodes, both -Xms and -Xmx.

For Bootstrap you can set 545 and dispatcher can be 512m.

Also add -Xss2m in the server nodes. Save after each change and then finally restart the cluster.

Hope it will work.

reward with points.!!!!!

Former Member
0 Kudos

Hello,

Please archive the whole instance work directory - /usr/sap/<SID>/<instance-no>/work/* plus the last modified version of the /usr/sap/<SID>/<instance-no>/j2ee/cluster/server0/log/defaultTrace.X.trc. Upload the archive somewhere (http://www.rapidshare.com/, etc.).

Regards, Ventsi

former_member255800
Discoverer
0 Kudos

Hi,

we run into the same problem with getting stucked in

"Reference Handler" daemon prio=10 tid=0x01063390 nid=0x22a0 in Object.wait()

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

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

"main" prio=5 tid=0x003d7358 nid=0x26b0 in Object.wait()

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

- waiting on <0x1ad2ca70> (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 <0x1ad2ca70> (a com.sap.engine.boot.StartFrame)

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

"VM Thread" prio=5 tid=0x01062988 nid=0x1ffc runnable

"VM Periodic Task Thread" prio=10 tid=0x00f87960 nid=0x1710 waiting on condition

"Suspend Checker Thread" prio=10 tid=0x00f82d78 nid=0x2738 runnable

3264.018: [Full GC 3264.018: 80700K->54552K(1005056K), , 0.3969853 secs]

Wed Apr 30 07:06:50 2008

So I guess the Suspend Checker Thread is the condition it's waiting for. Any hint what the problem is? Or how did you solve this at that time?

Regards

Yüksel Tiryaki