disp+work.EXE dispatcher stopped and running but ...

Former Member · ‎10-25-2013

Hy Guys!

A installed a Netweaver Gateway 7.02. I used it 3 month. And suddenly my login has been broken. In my proccess list first disp+work.exe running but Dialog queue standstill and i tried to solve this problem ( I think i have to delete a log file , because it is full or not? ) I try install other database , and suddenly it stopped.

A tried use a Database Manager but i don't remember my username/ password. What is it?

Can you help me?

I attach my trace file.

Thanks your helps.

Best Regalds, Balazs

Trace:

*** WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 6 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 6423]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: write dp-profile-values into sys_adm_ext

DpIPCInit2: start server >MTC-SAP-PC_NSP_00 <

DpShMCreate: sizeof(wp_adm) 31696 (2264)

DpShMCreate: sizeof(tm_adm) 5517056 (27448)

DpShMCreate: sizeof(wp_ca_adm) 64000 (64)

DpShMCreate: sizeof(appc_ca_adm) 64000 (64)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/1384064/1384080

DpShMCreate: sizeof(comm_adm) 1384080 (2744)

DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0

DpShMCreate: sizeof(slock_adm) 0 (296)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (80)

DpShMCreate: sizeof(vmc_adm) 0 (2152)

DpShMCreate: sizeof(wall_adm) (41664/42896/64/192)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: sizeof(j2ee_adm) 3952

DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000DF20050, size: 7163600)

DpShMCreate: allocated sys_adm at 000000000DF20060

DpShMCreate: allocated wp_adm_list at 000000000DF23070

DpShMCreate: allocated wp_adm at 000000000DF23260

DpShMCreate: allocated tm_adm_list at 000000000DF2AE40

DpShMCreate: allocated tm_adm at 000000000DF2AE90

DpShMCreate: allocated wp_ca_adm at 000000000E46DDA0

DpShMCreate: allocated appc_ca_adm at 000000000E47D7B0

DpShMCreate: allocated comm_adm at 000000000E48D1C0

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 000000000E5DF060

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated gw_adm at 000000000E5DF110

DpShMCreate: allocated j2ee_adm at 000000000E5DF150

DpShMCreate: allocated ca_info at 000000000E5E00D0

DpShMCreate: allocated wall_adm at 000000000E5E0160

DpCommAttachTable: attached comm table (header=000000000E48D1C0/ft=000000000E48D1D0)

DpSysAdmIntInit: initialize sys_adm

rdisp/test_roll : roll strategy is DP_NORMAL_ROLL

dia token check not active (6 token)

MBUF state OFF

DpCommInitTable: init table for 500 entries

DpRqQInit: keep protect_queue / slots_per_queue 0 / 2001 in sys_adm

rdisp/queue_size_check_value : -> on,50,30,40,500,50,500,80

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> EsILock: use spinlock for locking

<ES> InitFreeList

<ES> block size is 4096 kByte.

<ES> Info: em/initial_size_MB( 6143MB) not multiple of em/blocksize_KB( 4096KB)

<ES> Info: em/initial_size_MB rounded up to 6144MB

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

<ES> 1535 blocks reserved for free list.

ES initialized.

mm.dump: set maximum dump mem to 96 MB

DpVmcSetActive: set vmc state DP_VMC_NOT_ACTIVE

MPI: dynamic quotas disabled.

MPI init: pipes=4000 buffers=1279 reserved=383 quota=10%

Thu Oct 24 23:27:35 2013

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.4 3.4 4.1) [dpxxdisp.c 1701]

***LOG Q0K=> DpMsAttach, mscon ( MTC-SAP-PC) [dpxxdisp.c 12514]

MBUF state LOADING

DpStartStopMsg: send start message (myname is >MTC-SAP-PC_NSP_00 <)

DpStartStopMsg: start msg sent

CCMS uses Shared Memory Key 73 for monitoring.

CCMS: Initalized shared memory of size 60000000 for monitoring segment.

CCMS: Checking Downtime Configuration of Monitoring Segment.

CCMS: AlMsUpload called by wp 1024.

CCMS: AlMsUpload successful for C:\usr\sap\NSP\DVEBMGS00\log\ALMTTREE.DAT (609 MTEs).

Thu Oct 24 23:27:36 2013

CCMS: start to initalize 3.X shared alert area (first segment).

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296]

MBUF state ACTIVE

DpWpBlksLow: max wp blocks in queue is 800 (80 %)

MBUF component UP

DpMsgProcess: 1 server in MBUF

DpAppcBlksLow: max appc blocks in queue is 500 (50 %)

Thu Oct 24 23:28:15 2013

*** ERROR => DpHdlDeadWp: W0 (pid 4048) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W1 (pid 4056) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W2 (pid 4064) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W3 (pid 4072) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W4 (pid 4080) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W5 (pid 4088) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W6 (pid 3100) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W7 (pid 3080) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W8 (pid 3088) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W9 (pid 1448) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W10 (pid 3128) died (severity=0, status=0) [dpxxwp.c 1531]

*** ERROR => DpHdlDeadWp: W11 (pid 3148) died (severity=0, status=0) [dpxxwp.c 1531]

*** DP_FATAL_ERROR => DpWPCheck: no more work processes

*** DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

NiWait: sleep (10000ms) ...

NiISelect: timeout 10000ms

NiISelect: maximum fd=1001

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Thu Oct 24 23:28:23 2013

NiISelect: TIMEOUT occured (10000ms)

dump system status

Workprocess Table (long) Thu Oct 24 21:28:23 2013

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

No Type Pid Status Cause Start Rstr Err Sem Time Program Cl User Action Table

-------------------------------------------------------------------------------------------------------------------------------

0 DIA -1 Ended no no 1 0 0 NO_ACTION

1 DIA -1 Ended no no 1 0 0 NO_ACTION

2 DIA -1 Ended no no 1 0 0 NO_ACTION

3 DIA -1 Ended no no 1 0 0 NO_ACTION

4 DIA -1 Ended no no 1 0 0 NO_ACTION

5 DIA -1 Ended no no 1 0 0 NO_ACTION

6 UPD -1 Ended no no 1 0 0 NO_ACTION

7 ENQ -1 Ended no no 1 0 0 NO_ACTION

8 BTC -1 Ended no no 1 0 0 NO_ACTION

9 BTC -1 Ended no no 1 0 0 NO_ACTION

10 SPO -1 Ended no no 1 0 0 NO_ACTION

11 UP2 -1 Ended no no 1 0 0 NO_ACTION

Dispatcher Queue Statistics Thu Oct 24 21:28:23 2013

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

+------+--------+--------+--------+------------+------------+

| Typ | now | high | max | writes | reads |

+------+--------+--------+--------+------------+------------+

| NOWP | 0 | 2 | 2000 | 6 | 6 |

+------+--------+--------+--------+------------+------------+

| DIA | 4 | 4 | 2000 | 4 | 0 |

+------+--------+--------+--------+------------+------------+

| UPD | 0 | 0 | 2000 | 0 | 0 |

+------+--------+--------+--------+------------+------------+

| ENQ | 0 | 0 | 2000 | 0 | 0 |

+------+--------+--------+--------+------------+------------+

| BTC | 0 | 0 | 2000 | 0 | 0 |

+------+--------+--------+--------+------------+------------+

| SPO | 0 | 0 | 2000 | 0 | 0 |

+------+--------+--------+--------+------------+------------+

| UP2 | 0 | 0 | 2000 | 0 | 0 |

+------+--------+--------+--------+------------+------------+

Former Member · ‎11-03-2013

Need to troubleshoot to narrow down the problem

1. check logs (look for any error messages)

2. check what other processes still running

3. kill all the SAP processes and do a clean restart to see if you still have the problem

4. check if SAP can connect to DB (R3trans -d)

former_member4224 · ‎10-31-2013

the work process died, hence the dispatcher triggered the emergency shutdown.

To understand the root cause you should check the dev_w* traces.

regards

Clebio

former_member45419 · ‎10-31-2013

Hi Balazs,

pls check this notes 72248

former_member183107 · ‎10-25-2013

Hi,

1. Please paste the dev_disp, dev_w0 logs.

2. Check whether DB is connected or not using R3trans -d.

3. Try to open JCMON and see whether the problem is with server0?

4. Check the default trace at location \usr\sap\<SID>\JC<InstNo>\j2ee\cluster\server<n>\log

Regards,

Himanshu

Reagan · ‎10-25-2013

Hello

Check the dev_w0 trace file.

If this is MaxDB then check whether the log area is full.

Regards

RB

former_member185239 · ‎10-25-2013

Hi Balazs,

As per the logs , SAP System is not able to connect to the database.

Run the R3trans -d command and paste the trans.log file.

With Regards

Ashutosh Chaturvedi

+919818619396

Sriram2009 · ‎10-25-2013

Hi

Kindly check the SAP Note 396309 - Dispatcher remains yellow, although the system is running

Note 1592236 - FAIL: process disp+work.EXE Dispatcher not running

Regards

Sriram

former_member188883 · ‎10-25-2013

Hi ,

Did you perform any memory parameter changes recently ?

If yes , try to revert those and reboot the server and check the results.

if no memory parameter changes performed, please shared dev_w0 log file

Regards,

Deepak Kori

disp+work.EXE dispatcher stopped and running but Dialog queue standstill

Accepted Solutions (0)

Answers (8)

Answers (8)

Re: Incorrect documentation regarding "Error Sanit...

Re: [BIG PROBLEM] SAP Host Agent cannot connect to...

Re: using Already availble XSUAA service to anothe...

Re: CDS Projection View parameters not allowed

using Already availble XSUAA service to another ap...