SAPMMC disp+work.EXE in yellow :-(

[Former Member]

Hello,

I can't found why now the process is in yellow.

In the "J2EE Process Table" the "dispatcher" and "server0" are in yellow !

In the std_server0.out file :

SAP J2EE Engine Version 7.00 PatchLevel is starting...

Loading: LogManager ... 1969 ms.

Loading: PoolManager ... 15 ms.

Loading: ApplicationThreadManager ... 266 ms.

Loading: ThreadManager ... 62 ms.

Loading: IpVerificationManager ... 63 ms.

Loading: ClassLoaderManager ... 62 ms.

Loading: ClusterManager ... 844 ms.

Loading: LockingManager ...

Can you help me please !

Best Regards,

Mathieu

[Former Member · Accepted solution]

HI Mathieu,

Check what messages do you have in jvm_server0.out, dev_server0.out and bootstrap traces,

Regards,

Mike

[Former Member · Accepted solution]

Hi Mike,

In the the jvm_server0.out file is empty.

I haven't the dev_server0.out but in the std_server0.out file :

SAP J2EE Engine Version 7.00 PatchLevel is starting...

Loading: LogManager ... 1969 ms.

Loading: PoolManager ... 15 ms.

Loading: ApplicationThreadManager ... 266 ms.

Loading: ThreadManager ... 62 ms.

Loading: IpVerificationManager ... 63 ms.

Loading: ClassLoaderManager ... 62 ms.

Loading: ClusterManager ... 844 ms.

Loading: LockingManager ...

And in the bootstrap folder, which file ?

Regards,

Mathieu

[Former Member · Accepted solution]

Hi,

in the MMC the server0 and dispatcher have the status :

starting framework.

[Former Member · Accepted solution]

Hi,

How can I restore or reinstall the J2EE Server and dispatcher ?

I need your help please.

Regards,

Mathieu

[Former Member · Accepted solution]

Hi,

problem solved by SAP Support :

"The first problem was that in the SCS instance there was no running

enqueue server as its starting line had no line break at the end in the

start profile. Without this NT cannot parse the line. After adding the

line break the enqueue server could start.

The second problem was that in the global dispatcher configuration for

the LockingManager the en.port was set to 3201 instead of 3200 (which

is correct as the SCS instance has the intance number 00).

After correcting these problems the J2EE engine could be started fine."

[Former Member]

Hello.

I had the problem too.

Only importing the SAP profiles in SAP transaction RZ10:

Utilities - Import profiles - of Active Server

has the problem solved.

I hope it can be useful.

Alberto

[Former Member]

Dear Alberto,

Mi name is Daniel and I have the same problem, disp+work status is yellow, then stop.

As you said the solution is to import the profile from RZ10, but as the problem is that disp+work isn't running, I can't start SAP.

We installed Sap netweaver BI in one server, and copy all datafiles, \usr folder, \sapmnt folder from old server to the new server. (previosly we changed hostname to be the same as before)

When we try to start Sap in managemnet console, all proccess starts, but disp+work begins with yellow and the its stop.

And it say the error with j2ee unreachable.

I saw your solution but we can't start sap in order to import the profile, could you give me a solution please, as i'm in another country till tomorrow and I wish I coluld finish this before I leave!...

Thanks in advance.

Regards,

Daniel.

[Former Member]

I apologize for the inconvenience, finally we could start SAP, but java didn't, probably because de variables where different as it tooks the ones from the old server, now we're trying to change them, not using Tx AL11 because the wrong variables are from Java not sap!..

Best Reagards,

Daniel!.

[Former Member]

Hi Gurus,

Sorry for my long mail, but wanna give more details.

The dispatcher is yellow in MMC with a message J2EE status not available.

I checked the dev_jcontrol file and it did give some error. Please find the file contents below.

I also checked the instance.properties file which has the same error entries which was given in dev_jcontrol file.

The last entry in dev_bootstrap was made 2 months back. I am also giving those entries below.

Now I am stuck, I am a little confused on the SCS instance and the DVEBMGS instance.

Request your help.

But what I really need some more clarity on is that:

I installed the central system installation with the following :

•Central Services Instance (SCS) - with usage types based on AS Java

•Database Instance

•Central Instance

Now the central services instance SCS02 has started and is green and the process list has the msg_server.exe and enserver.exe running. DVEBMGS03 instance is started with the process list msg_server.exe, disp+work.exe and igswd.exe. But the dispatcher is not able to connect to the J2EE engine. It exactly says “Dispatcher running, message server connection ok, J2EE status info unavailable” I did check if there is some problem in the profile parameters of the CI (<SID>_DVEBMGS03_<HOST>.PFL file)

-

---

trc file: "D:\usr\sap\NWS\DVEBMGS03\work\dev_jcontrol", trc level: 1, release: "700"

-

---

node name : jcontrol

pid : 304

system name : NWS

system nr. : 03

started at : Thu Dec 21 18:22:59 2006

arguments :

arg[00] : jcontrol

arg[01] : pf=d:\usr\sap\nws\sys\profile\NWS_DVEBMGS03_SAPNT35T

arg[02] : -c

[Thr 3764] Thu Dec 21 18:22:59 2006

[Thr 3764] *** WARNING => INFO: Unknown property [instance.box.number=NWSDVEBMGS03sapnt35t]

[jstartxx.c 841]

[Thr 3764] *** WARNING => INFO: Unknown property [instance.en.host=SAPNT35T] [jstartxx.c

841]

[Thr 3764] *** WARNING => INFO: Unknown property [instance.en.port=3202] [jstartxx.c 841]

[Thr 3764] *** WARNING => INFO: Unknown property [instance.system.id=3] [jstartxx.c

INSTANCE.PROPERTIES file below:

bootstrap.Type=bootstrap

bootstrap_ID39173100.ClassPath=./bootstrap/launcher.jar

bootstrap_ID39173100.JLaunchParameters=

bootstrap_ID39173100.JavaParameters=-Djco.jarm=1

bootstrap_ID39173100.JavaPath=C:/j2sdk1.4.2_12-x64

bootstrap_ID39173100.MainClass=com.sap.engine.offline.OfflineToolStart

bootstrap_ID39173100.MaxHeapSize=256

bootstrap_ID39173100.Name=dispatcher bootstrap

bootstrap_ID39173100.Parameters=com.sap.engine.bootstrap.Bootstrap ./bootstrap ID039173100

bootstrap_ID39173100.RootPath=D:/usr/sap/NWS/DVEBMGS03/j2ee/cluster

bootstrap_ID39173100.Type=bootstrap

bootstrap_ID39173150.ClassPath=./bootstrap/launcher.jar

bootstrap_ID39173150.JLaunchParameters=

bootstrap_ID39173150.JavaParameters=-Djco.jarm=1

bootstrap_ID39173150.JavaPath=C:/j2sdk1.4.2_12-x64

bootstrap_ID39173150.MainClass=com.sap.engine.offline.OfflineToolStart

bootstrap_ID39173150.MaxHeapSize=256

bootstrap_ID39173150.Name=server0 bootstrap

bootstrap_ID39173150.Parameters=com.sap.engine.bootstrap.Bootstrap ./bootstrap ID039173150

bootstrap_ID39173150.RootPath=D:/usr/sap/NWS/DVEBMGS03/j2ee/cluster

bootstrap_ID39173150.Type=bootstrap

instance.box.number=NWSDVEBMGS03sapnt35t

instance.en.host=SAPNT35T

instance.en.port=3202

instance.enabled=yes

instance.install.dir=D:/usr/sap/NWS/DVEBMGS03/j2ee

instance.ms.host=SAPNT35T

instance.ms.port=3902

instance.osLibsPath=D:/usr/sap/NWS/DVEBMGS03/j2ee/os_libs

instance.runAction=NONE

instance.runMode=NORMAL

instance.system.id=3

dev_bootstrap file:

-> arg[ 8]: -Dmemory.manager=256M

-> arg[ 9]: -Xmx256M

-> arg[ 10]: -DLoadBalanceRestricted=no

-> arg[ 11]: -Djstartup.mode=BOOTSTRAP

-> arg[ 12]: -Djstartup.ownProcessId=6088

-> arg[ 13]: -Djstartup.ownHardwareId=P0860745355

-> arg[ 14]: -Djstartup.whoami=bootstrap

-> arg[ 15]: -Djstartup.debuggable=yes

-> arg[ 16]: -Xss2m

-> arg[ 17]: -DSAPINFO=NWS_03_bootstrap

-> arg[ 18]: -DSAPSTART=1

-> arg[ 19]: -DCONNECT_PORT=3275

-> arg[ 20]: -DSAPSYSTEM=03

-> arg[ 21]: -DSAPSYSTEMNAME=NWS

-> arg[ 22]: -DSAPMYNAME=SAPNT35T_NWS_03

-> arg[ 23]: -DSAPPROFILE=D:\usr\sap\NWS\SYS\profile\NWS_DVEBMGS03_SAPNT35T

-> arg[ 24]: -DFRFC_FALLBACK=ON

-> arg[ 25]: -DFRFC_FALLBACK_HOST=localhost

-> arg[ 26]: -DSAPSTARTUP=1

-> arg[ 27]: -DSAPSYSTEM=03

-> arg[ 28]: -DSAPSYSTEMNAME=NWS

-> arg[ 29]: -DSAPMYNAME=SAPNT35T_NWS_03

-> arg[ 30]: -DSAPDBHOST=SAPNT35T

-> arg[ 31]: -Dj2ee.dbhost=SAPNT35T

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

CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources

CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain

CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub

CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS

CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices

CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile

CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup

[Thr 5456] Tue Oct 10 21:11:15 2006

[Thr 5456] JHVM_LoadJavaVM: Java VM created OK.

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

JHVM_BuildArgumentList: main method arguments of node [bootstrap]

-> arg[ 0]: com.sap.engine.bootstrap.Bootstrap

-> arg[ 1]: ./bootstrap

-> arg[ 2]: ID0391731

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

[Thr 5456] Tue Oct 10 21:11:17 2006

[Thr 5456] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes

[Thr 3492] Tue Oct 10 21:11:37 2006

[Thr 3492] JLaunchIExitJava: exit hook is called (rc = 0)

[Thr 3492] JLaunchCloseProgram: good bye (exitcode = 0)

Please let me know what could be the issue.

Thanks & Regards,

P. Kumaravel.

[Former Member]

Mathieu,

I'm facing the exact problem. Can you guide me in which start profile file you added the break line ?

The en.port for the Locking manager is set to 3200. I guess thats right.

Thanks,

D

[Former Member]

Hi Jaiswal,

The problem was solved by SAP Support :

"The first problem was that in the SCS instance there was no running

enqueue server as its starting line had no line break at the end in the

start profile. Without this NT cannot parse the line. After adding the

line break the enqueue server could start."

Regards,

Mathieu

[Former Member]

Mathieu,

I checked what u guyz advised. But its fine. Dispatcher and Server0 doesnt start up. Their status remains as Starting Framework.

In the default trace i find:

#1.5#02004C4F4F500001000000C100000590000421108DB5AB4A#1162254887531#com.sap.engine.core.locking.impl3.LockingManagerImpl##com.sap.engine.core.locking.impl3.LockingManagerImpl.jenqulib#######Thread[SAPEngine_EnquReader,5,main]##0#0#Error#1#/System/Server#Plain###Encomi: failed to connect to Deepankar/3200/Connection refused: connect)#

Please help me.

Thanks,

D.

[Former Member]

Hi Jaiswal,

Try to restore the profils files or activate the previous version of profiles with transaction code RZ10.

I had a lot of problem with dispatcher and server0, the problem was always with the profiles.

Regards,

Mathieu

[stefanh_lima]

Hello Mathieu,

have a look at the note 142100.

regars

stefan