cancel
Showing results for 
Search instead for 
Did you mean: 

j2ee status info unavailable

Former Member
0 Kudos

Hi all

I have installed SAP ECC 6 in my system. After installation I started SAPMMC then it gave me j2ee status info unavailable. BElow i have given developer trace file. Please help me put from it.

DpJ2eeStart: j2ee state = STARTED

rdisp/http_min_wait_dia_wp : 1 -> 1

***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c 1611]

***LOG Q0K=> DpMsAttach, mscon ( sapdemo) [dpxxdisp.c 11163]

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

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

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

DpMsgAdmin: Set release to 7000, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

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

DpMsgAdmin: Set patchno for this platform to 33

Release check o.K.

Sat Apr 11 13:01:48 2009

DpJ2eeLogin: j2ee state = CONNECTED

Sat Apr 11 13:01:51 2009

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4211]

      • ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1460

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:2495) [nixxi.cpp 4211]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

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

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

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Sat Apr 11 13:02:27 2009

      • ERROR => W0 (pid 4092) died [dpxxdisp.c 13748]

      • ERROR => W1 (pid 1776) died [dpxxdisp.c 13748]

      • ERROR => W2 (pid 2140) died [dpxxdisp.c 13748]

      • ERROR => W3 (pid 3124) died [dpxxdisp.c 13748]

      • ERROR => W4 (pid 2908) died [dpxxdisp.c 13748]

      • ERROR => W5 (pid 2820) died [dpxxdisp.c 13748]

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

      • ERROR => W6 (pid 208) died [dpxxdisp.c 13748]

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

      • ERROR => W7 (pid 976) died [dpxxdisp.c 13748]

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

      • ERROR => W8 (pid 3008) died [dpxxdisp.c 13748]

      • ERROR => W9 (pid 1556) died [dpxxdisp.c 13748]

      • ERROR => W10 (pid 688) died [dpxxdisp.c 13748]

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

      • ERROR => W11 (pid 4048) died [dpxxdisp.c 13748]

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

      • ERROR => W12 (pid 1224) died [dpxxdisp.c 13748]

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-4092 (SIGUSR2)

      • ERROR => DpWpKill(4092, SIGUSR2) failed [dpxxtool.c 2586]

killing W1-1776 (SIGUSR2)

      • ERROR => DpWpKill(1776, SIGUSR2) failed [dpxxtool.c 2586]

killing W2-2140 (SIGUSR2)

      • ERROR => DpWpKill(2140, SIGUSR2) failed [dpxxtool.c 2586]

killing W3-3124 (SIGUSR2)

      • ERROR => DpWpKill(3124, SIGUSR2) failed [dpxxtool.c 2586]

killing W4-2908 (SIGUSR2)

      • ERROR => DpWpKill(2908, SIGUSR2) failed [dpxxtool.c 2586]

killing W5-2820 (SIGUSR2)

      • ERROR => DpWpKill(2820, SIGUSR2) failed [dpxxtool.c 2586]

killing W6-208 (SIGUSR2)

      • ERROR => DpWpKill(208, SIGUSR2) failed [dpxxtool.c 2586]

killing W7-976 (SIGUSR2)

      • ERROR => DpWpKill(976, SIGUSR2) failed [dpxxtool.c 2586]

killing W8-3008 (SIGUSR2)

      • ERROR => DpWpKill(3008, SIGUSR2) failed [dpxxtool.c 2586]

killing W9-1556 (SIGUSR2)

      • ERROR => DpWpKill(1556, SIGUSR2) failed [dpxxtool.c 2586]

killing W10-688 (SIGUSR2)

      • ERROR => DpWpKill(688, SIGUSR2) failed [dpxxtool.c 2586]

killing W11-4048 (SIGUSR2)

      • ERROR => DpWpKill(4048, SIGUSR2) failed [dpxxtool.c 2586]

killing W12-1224 (SIGUSR2)

      • ERROR => DpWpKill(1224, SIGUSR2) failed [dpxxtool.c 2586]

NiWait: sleep (10000ms) ...

NiISelect: timeout 10000ms

NiISelect: maximum fd=1589

NiISelect: read-mask is NULL

NiISelect: write-mask is NULL

Sat Apr 11 13:02:37 2009

NiISelect: TIMEOUT occured (10000ms)

dump system status

Workprocess Table (long) Sat Apr 11 07:32:37 2009

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

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

Check the oracle services and listner is running

If possble restart the sytem once

Regards

Uday

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Check your network connection and also check dev_bootstrap and dev_jcontrol.

Please find document below on J2EE startup issues.

[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e09e4a5e-8280-2a10-ca98-a59dd47d396d ]

Hope this helps.

Manoj

Former Member
0 Kudos

thnks all of you.... i have sloved the problem......

listener was working fine.....

the problem was in database part...

database not mounted was the error...

System was not able to find the control files....

so i checked the alert.log file in which i got the path of control path then i altered the system with the following systax

alter system set control_files='path' scope=spfile.

then the database was mounted and all things worked fine.

Thanks

Former Member
0 Kudos

Hi Pradeep

is disp+work running ?once check R3trans -d with sidadm, if it is finished with rc=0, once restart sap including db, if finished with rc other than 0, then check trans.log

Bhudev

Former Member
0 Kudos

no disp+work not working its in yellow color