cancel
Showing results for 
Search instead for 
Did you mean: 

disp+work.exe (Dispatcher) fails to start

Former Member
0 Kudos

Hi,

When we restarted our server( SP11 on Windows), the dispatcher dosen't come up ( status:"Stopped"). We had been using the server for development purposes and after one of the BPM's ran into an infinite loop, we canceled the BPM process and restarted the Server.

Below is the developer trace when disp+work (dispatcher) starts up.

DpJ2eeStart: j2ee state = STARTED

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 2.6.1 2.6 4.0) [dpxxdisp.c 1466]

***LOG Q0K=> DpMsAttach, mscon ( cgnsap12) [dpxxdisp.c 9782]

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

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

Mon Jul 25 09:57:31 2005

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

DpMsgAdmin: Set release to 6400, patchlevel 0

DpJ2eeLogin: j2ee state = CONNECTED

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

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

DpMsgAdmin: Set patchno for this platform to 71

Release check o.K.

Mon Jul 25 09:57:35 2005

***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 785]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=4032)

      • ERROR => DpProcKill: kill failed [dpntdisp.c 433]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Mon Jul 25 09:58:10 2005

      • ERROR => W0 (pid 3016) died [dpxxdisp.c 12233]

      • ERROR => W1 (pid 2012) died [dpxxdisp.c 12233]

my types changed after wp death/restart 0xbf --> 0xbe

      • ERROR => W2 (pid 3832) died [dpxxdisp.c 12233]

my types changed after wp death/restart 0xbe --> 0xbc

      • ERROR => W3 (pid 2128) died [dpxxdisp.c 12233]

my types changed after wp death/restart 0xbc --> 0xb8

      • ERROR => W4 (pid 3348) died [dpxxdisp.c 12233]

      • ERROR => W5 (pid 3172) died [dpxxdisp.c 12233]

my types changed after wp death/restart 0xb8 --> 0xb0

      • ERROR => W6 (pid 924) died [dpxxdisp.c 12233]

my types changed after wp death/restart 0xb0 --> 0xa0

      • ERROR => W7 (pid 2016) died [dpxxdisp.c 12233]

my types changed after wp death/restart 0xa0 --> 0x80

      • DP_FATAL_ERROR => DpWPCheck: no more work processes

      • DISPATCHER EMERGENCY SHUTDOWN ***

increase tracelevel of WPs

killing W0-3016 (SIGUSR2)

      • ERROR => DpWpKill(3016, SIGUSR2) failed [dpxxtool.c 2477]

killing W1-2012 (SIGUSR2)

      • ERROR => DpWpKill(2012, SIGUSR2) failed [dpxxtool.c 2477]

killing W2-3832 (SIGUSR2)

      • ERROR => DpWpKill(3832, SIGUSR2) failed [dpxxtool.c 2477]

killing W3-2128 (SIGUSR2)

      • ERROR => DpWpKill(2128, SIGUSR2) failed [dpxxtool.c 2477]

killing W4-3348 (SIGUSR2)

      • ERROR => DpWpKill(3348, SIGUSR2) failed [dpxxtool.c 2477]

killing W5-3172 (SIGUSR2)

      • ERROR => DpWpKill(3172, SIGUSR2) failed [dpxxtool.c 2477]

killing W6-924 (SIGUSR2)

      • ERROR => DpWpKill(924, SIGUSR2) failed [dpxxtool.c 2477]

killing W7-2016 (SIGUSR2)

      • ERROR => DpWpKill(2016, SIGUSR2) failed [dpxxtool.c 2477]

NiWait: sleep (10000 msecs) ...

NiISelect: timeout 10000 ms

NiISelect: maximum fd=1581

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Mon Jul 25 09:58:20 2005

NiISelect: TIMEOUT occured (10000 ms)

dump system status

When we tried to login using the Config tool, i get the error message <b>" Error occured while working with Configuration (scanning). Msg: Eror while connecting to DB)</b>".

Any pointers.... what might have gone wrong..?

Cheers,

Siva Maranani.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Siva,

i have the same problem after install a SAP WAS 6.40 ABAP SR1. Could you solve the problem? If, yes please let it me know.

- Thanks in advance.

Regards, Ralf

Former Member
0 Kudos

Hi,

For me, the problem ws after a complte installation.

This might happen b'cos the DB would not have shutdown properly. Anyhow these were the steps i followed.

1) open ur command prompt by going to start>run>'cmd'

2) 'sqlplus'

3) username: scott , password: tiger

4) 'connect /as sysdba'

5) 'shutdown immediate'

6) restart the system

7) Go to SAP MMC and start the Server node. This will start the SAP-services and DB.

Hope this helps.

Cheers,

Siva Maranani.

stefan_grube
Active Contributor
0 Kudos

Is your database up and running? Check for errors there.

Regards

Stefan