Skip to Content
avatar image
Former Member

Java problem - J2EE status info unavailable

Hi

( Environment: ECC6 patched to NW SP16 / Unicode / 700 Kernel patch 173 / Dbserver=DB2/400 )

When I start the Application server instance (Windows) with J2EE after applying SP16 of JSPM support package patches, the disp+work.exe on the System Management console has a yellow light and status of :

Running, message server connection ok; dialog queue time 0.00sec; J2EE status info unavailable.

The dev_jcontrol trace file has the error messages:

trc file: "U:\usr\sap\WFD\D00\work\dev_jcontrol", trc level: 1, release: "700"

-


node name : jcontrol

pid : 2308

system name : WFD

system nr. : 00

started at : Thu Sep 25 15:46:00 2008

arguments :

arg[00] : U:\usr\sap\WFD\D00\exe\jcontrol.EXE

arg[01] : pf=
sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6

arg[02] : -DSAPSTART=1

arg[03] : -DCONNECT_PORT=64990

arg[04] : -DSAPSYSTEM=00

arg[05] : -DSAPSYSTEMNAME=WFD

arg[06] : -DSAPMYNAME=dfbhl6_WFD_00

arg[07] : -DSAPPROFILE=
sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6

arg[08] : -DFRFC_FALLBACK=ON

arg[09] : -DFRFC_FALLBACK_HOST=localhost

[Thr 2040] Thu Sep 25 15:46:00 2008

[Thr 2040] *** WARNING => INFO: Unknown property [instance.box.number=WFDD00dfbhl6] [jstartxx.c 841]

[Thr 2040] *** WARNING => INFO: Unknown property [instance.en.host=sapdev] [jstartxx.c 841]

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

[Thr 2040] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c 841]

[Thr 2040] JControlExecuteBootstrap: execute bootstrap process [bootstrap]

[Thr 3504] JControlDPMessageProxy: Thread 3504 started as handler thread for R/3 dispatcher messages.

[Thr 2040] [Node: bootstrap] java home is set by profile parameter

Java Home: C:\j2sdk1.4.2_13

[Thr 2040] JStartupICheckFrameworkPackage: can't find framework package U:\usr\sap\WFD\D00\exe\jvmx.jar

[Thr 2040] JControlCheckRunMode: run mode of the instance = safe

[Thr 2040] Instance is disabled -> terminate.

[Thr 2040] JControlCloseProgram: started (exitcode = -11113)

[Thr 2040] JControlCloseProgram: good bye... (exitcode = -11113)

Any ideas what is wrong? Have tried restarting the Application server.

regards

Michael.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

10 Answers

  • avatar image
    Former Member
    Sep 25, 2008 at 09:13 AM

    Hi Michael,

    Is it creating std_server0.out & std_dispatcher.out files in work directory?

    If yes, then please check which service is failing to start. Based on that we can fix the problem.

    As per SAP Notes, exitcode = -11113 is due to failure of some essential service.

    Regards,

    -Pankaj Kapote

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 25, 2008 at 12:35 PM

    Hi Michael,

    Thr 2040 JStartupICheckFrameworkPackage: can't find framework package U:\usr\sap\WFD\D00\exe\jvmx.jar

    check for this package

    Regards

    Ashok

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 26, 2008 at 12:10 AM

    Thanks for the replies. To answer your questions:

    Ashok,

    Thr 2040 JStartupICheckFrameworkPackage: can't find framework package U:\usr\sap\WFD\D00\exe\jvmx.jar

    check for this package :

    A: I checked, and the file is not there. It isn't on the WFQ system I just installed either which is based on the latest SR3 ECC6 Kit.

    Pankaj,

    Is it creating std_server0.out & std_dispatcher.out files in work directory?

    A: Good question. The files are there but dated 23/9/08 (when last shutdown) , whereas all other trace files including the dev_jcontrol and dev_bootstrap were created when the instance started up yesterday are dated 25/9/08 3:45pm.

    One thing I noticed in the Std_server0.out is that the WFQ (new) system has in this file:

    SAP J2EE Engine Version 7.00 PatchLevel 109886.44 is starting...

    For the WFD instance, the last entries when J2EE was shutdown has different patch level-

    Sep 23, 2008 7:20:43 PM

    SAP J2EE Engine Version 7.00 PatchLevel 109044.44 is shutting down! PatchLevel 109044.44 August 11, 2007 13:13 GMT

    There are other errors in this file (see below)

    regards

    Michael

    std_server0.out

    Sep 22, 2008 7:20:20 PM ...ebbase.framework.FrontController.init

    [SAPEngine_Application_Thread[impl:3]_21] Fatal: Error when loading the XCM configuration.

    Create a configuration in XCM with the name fscm/bd. Start XCM: (context-root)/admin/xcm/init.do.

    Configure SAP Biller Direct with XCM, and start SAP Biller Direct again.

    739.587: [ParNew 207277K->126808K(745472K), 0.3747820 secs]

    Sep 22, 2008 7:20:26 PM ...t.ECFactory.getSystemExecutionContext

    [Timeout Service Synchronous Internal Thread]

    Fatal: Error when loading the XCM configuration. Create a configuration in XCM with the name fscm/bd.

    Start XCM: (context-root)/admin/xcm/init.do.Configure SAP Biller Direct with XCM, and start SAP Biller Direct again.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Michael,

      You can ignore the error "can't find framework package U:\usr\sap\WFD\D00\exe\jvmx.jar". This is not the cause of your problem.

      If you are sure that std_server0.out & std_dispatcher.out files are not getting created means J2EE Engine startup process is not even reaching to that point.

      I would suggest you to give startsap comand & then monitor the "work" directory for the logs. Sort the files with date & time. Look at the files one by one which are created newly.

      Hope, this helps you in finding out the cause of the problem.

      Good Luck!

      -Pankaj Kapote

  • avatar image
    Former Member
    Sep 26, 2008 at 06:51 AM

    Hi,

    I just noticed that this is your Dialog Instance.

    Is your CI instance running & the profiles (
    sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6) are accessible to dialog instance?

    Regards,

    -Pankaj Kapote

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 26, 2008 at 07:16 AM

    Pankaj,

    I ended the db CI also and restarted everything including reboot of the Windows app server.

    In the work directory on the Dialog Windows instance the last files created are:

    available.log

    dev_disp

    dev_jcontrol

    std_bootstrap.out

    log_bootstrap_ID

    jvm_bootstrap.out

    dev_bootstrap

    dev_w4

    dev_disp :

    Fri Sep 26 16:42:53 2008

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

    MBUF state PREPARED

    MBUF component UP

    DpMBufHwIdSet: set Hardware-ID

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

    DpMsgAdmin: Set patchno for this platform to 173

    Release check o.K.

    Fri Sep 26 16:43:00 2008

    DpJ2eeLogin: j2ee state = CONNECTED

    Fri Sep 26 16:43:27 2008

    MBUF state ACTIVE

    DpModState: change server state from STARTING to ACTIVE

    Fri Sep 26 16:43:50 2008

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

    • ERROR => NiIRead: SiRecv failed for hdl 5 / sock 192

    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:1358) [nixxi.cpp 4424]

    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

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

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

    DpIJ2eeShutdown: j2ee state = SHUTDOWN

    Fri Sep 26 16:43:51 2008

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 2640

    argv[0] = U:\usr\sap\WFD\D00\exe\jcontrol.EXE

    argv[1] = U:\usr\sap\WFD\D00\exe\jcontrol.EXE

    argv[2] = pf=
    sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=64999

    argv[5] = -DSAPSYSTEM=00

    argv[6] = -DSAPSYSTEMNAME=WFD

    argv[7] = -DSAPMYNAME=dfbhl6_WFD_00

    argv[8] = -DSAPPROFILE=
    sapdev\sapmnt\WFD\SYS\profile\WFD_D00_dfbhl6

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Sep 26 16:43:52 2008

    DpJ2eeLogin: j2ee state = CONNECTED

    Fri Sep 26 16:44:24 2008

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

    • ERROR => NiIRead: SiRecv failed for hdl 6 / sock 176

    (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:1470) [nixxi.cpp 4424]

    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

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

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

    DpIJ2eeShutdown: j2ee state = SHUTDOWN

    ---this is repeated many times

    regards

    Michael

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 26, 2008 at 09:52 AM

    had u made any changes in UME via config tool.

    This generally happens when J2ee does not get correct data from security store.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello!

      I have exactly the same problem in the target system of a system copy.

      Before the copy we implemented in the source system SPS16.

      At the end of dev_jcontrol log you can see the info:

      [Thr xxxx] Instance is disabled -> terminate

      In the ..\J2EE\cluster\instance.properties file there is an entry:

      instance.enabled=no

      In the source system the entry is

      instance.enabled=yes

      I could not find the parameter in the offline editor to change it.

      I guess this is the reason why J2EE engine aborts.

  • avatar image
    Former Member
    Oct 02, 2008 at 09:42 AM

    Hi,

    I believe some of your profile parameters got jeopardized, can you please have a look at SAP Note 741289 and implement it if needed.

    Thanks, Dibya

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello!

      Thanks for the tip but I have already solved the probelm.

      The parameter instance.enabled become the value 'no' because of instance.runMode=safe that was derived from the source system during system copy. However in the source system instance.enabled=yes.

      In the Configuration Tool (\j2ee\configtool\configtool.cmd) --> Edit mode --> node Cluster_data I changed the parameter runMode from "safe" to "normal" and restarted the system.

      I could not find the parameter instance.enabled in the Editor but it has been automatically changed to 'yes' during restart and J2EE started properly.

      I still have to check why the parameter instance.runMode had the value 'safe' in the source system.

      Regards

      Pawel

  • avatar image
    Former Member
    Oct 05, 2008 at 08:20 PM

    Hi,

    If safe mode is ON, then you can also turn it off by going into the configtool. then choose File > Safe mode > No.

    Then restart the j2ee cluster.

    Debasis.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 20, 2009 at 11:15 AM

    Hi,

    *I am too getting the following error "Running, message server connection ok; dialog queue time 0.00sec; J2EE status info unavailable."*

    the trace is as follows. Kindly help

    thanks

    Denis.

    -


    trc file: "dev_disp", trc level: 1, release: "700"

    -


    sysno 01

    sid DM0

    systemid 560 (PC with Windows NT)

    relno 7000

    patchlevel 0

    patchno 52

    intno 20050900

    make: multithreaded, Unicode, optimized

    pid 2228

    Fri Nov 20 15:43:45 2009

    kernel runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)

    length of sys_adm_ext is 572 bytes

    • SWITCH TRC-HIDE on ***

    ***LOG Q00=> DpSapEnvInit, DPStart (01 2228) [dpxxdisp.c 1231]

    shared lib "dw_xml.dll" version 52 successfully loaded

    shared lib "dw_xtc.dll" version 52 successfully loaded

    shared lib "dw_stl.dll" version 52 successfully loaded

    shared lib "dw_gui.dll" version 52 successfully loaded

    rdisp/softcancel_sequence : -> 0,5,-1

    use internal message server connection to port 3901

    Fri Nov 20 15:43:50 2009

    • WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds

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

    MtxInit: 30000 0 0

    DpSysAdmExtInit: ABAP is active

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

    DpIPCInit2: start server >sapserver_DM0_01 <

    DpShMCreate: sizeof(wp_adm) 14080 (1408)

    DpShMCreate: sizeof(tm_adm) 3954072 (19672)

    DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

    DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

    DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064

    DpShMCreate: sizeof(comm_adm) 528064 (1048)

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

    DpShMCreate: sizeof(file_adm) 0 (72)

    DpShMCreate: sizeof(vmc_adm) 0 (1452)

    DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)

    DpShMCreate: sizeof(gw_adm) 48

    DpShMCreate: SHM_DP_ADM_KEY (addr: 05DC0040, size: 4608920)

    DpShMCreate: allocated sys_adm at 05DC0040

    DpShMCreate: allocated wp_adm at 05DC1E28

    DpShMCreate: allocated tm_adm_list at 05DC5528

    DpShMCreate: allocated tm_adm at 05DC5558

    DpShMCreate: allocated wp_ca_adm at 0618AAF0

    DpShMCreate: allocated appc_ca_adm at 061908B0

    DpShMCreate: allocated comm_adm at 061927F0

    DpShMCreate: system runs without file table

    DpShMCreate: allocated vmc_adm_list at 062136B0

    DpShMCreate: allocated gw_adm at 062136F0

    DpShMCreate: system runs without vmc_adm

    DpShMCreate: allocated ca_info at 06213720

    DpShMCreate: allocated wall_adm at 06213728

    Fri Nov 20 15:43:51 2009

    MBUF state OFF

    Fri Nov 20 15:43:53 2009

    EmInit: MmSetImplementation( 2 ).

    MM diagnostic options set: 0

    <ES> client 0 initializing ....

    <ES> InitFreeList

    <ES> block size is 4096 kByte.

    Using implementation flat

    <EsNT> Memory Reset disabled as NT default

    <ES> 1022 blocks reserved for free list.

    ES initialized.

    Fri Nov 20 15:43:54 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 2724

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1044

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    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 1617]

    Fri Nov 20 15:43:55 2009

    ***LOG Q0K=> DpMsAttach, mscon ( sapserver) [dpxxdisp.c 11414]

    Fri Nov 20 15:43:56 2009

    DpStartStopMsg: send start message (myname is >sapserver_DM0_01 <)

    DpStartStopMsg: start msg sent

    Fri Nov 20 15:43:57 2009

    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

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

    Fri Nov 20 15:44:00 2009

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

    DpMsgAdmin: Set release to 7000, patchlevel 0

    Fri Nov 20 15:44:01 2009

    MBUF state PREPARED

    MBUF component UP

    DpMBufHwIdSet: set Hardware-ID

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

    DpMsgAdmin: Set patchno for this platform to 52

    Release check o.K.

    Fri Nov 20 15:44:37 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:44:57 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 1064

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1081

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:45:17 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:45:37 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 2656

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1107

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:45:57 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:46:19 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 1428

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1113

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:46:37 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:46:46 2009

    MBUF state ACTIVE

    Fri Nov 20 15:46:53 2009

    DpModState: change server state from STARTING to ACTIVE

    Fri Nov 20 15:46:57 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 3192

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1131

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:47:17 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:47:37 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 3180

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1141

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:47:57 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:48:08 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 15:48:17 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 952

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1147

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:48:37 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:48:58 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 3192

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1156

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:49:17 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:49:37 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 3660

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1164

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:50:01 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:50:21 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 2208

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1171

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:50:41 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:51:01 2009

    DpEnvCheckJ2ee: switch off j2ee start flag

    Fri Nov 20 15:59:24 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 15:59:25 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 15:59:45 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 15:59:46 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    SoftCancel request for T16 U19 M0 received from IC_MAN

    Fri Nov 20 15:59:51 2009

    SoftCancel request for T15 U18 M0 received from IC_MAN

    Fri Nov 20 15:59:52 2009

    • ERROR => DpRqCheck: mode 0 in status CANCEL [dpxxdisp.c 6815]

    Fri Nov 20 15:59:56 2009

    SoftCancel request for T14 U17 M0 received from IC_MAN

    Fri Nov 20 16:01:09 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 16:01:10 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 16:01:15 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 16:01:16 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 16:01:17 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 16:01:18 2009

    SoftCancel request for T16 U22 M0 received from IC_MAN

    Fri Nov 20 16:01:23 2009

    SoftCancel request for T15 U21 M0 received from IC_MAN

    Fri Nov 20 16:01:28 2009

    SoftCancel request for T14 U20 M0 received from IC_MAN

    Fri Nov 20 16:01:29 2009

    • ERROR => DpRqCheck: T14 in state TM_SLOT_FREE [dpxxdisp.c 6753]

    ***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 5104]

    Fri Nov 20 16:01:30 2009

    • ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5901): [dpxxdisp.c 5106]

    -IN-- sender_id DISPATCHER tid 14 wp_ca_blk 50 wp_id 1

    -IN-- action SEND_TO_WP uid 20 appc_ca_blk -1 type DIA

    -IN-- new_stat WP_WAIT mode 0 len 672 rq_id 527

    -IN-- req_info MSG_WITH_REQ_BUF MSG_WITH_OH

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 20, 2009 at 11:16 AM

    Hi,

    *I am too getting the following error "Running, message server connection ok; dialog queue time 0.00sec; J2EE status info unavailable."*

    the trace is as follows. Kindly help

    thanks

    Denis.

    -


    trc file: "dev_disp", trc level: 1, release: "700"

    -


    sysno 01

    sid DM0

    systemid 560 (PC with Windows NT)

    relno 7000

    patchlevel 0

    patchno 52

    intno 20050900

    make: multithreaded, Unicode, optimized

    pid 2228

    Fri Nov 20 15:43:45 2009

    kernel runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)

    length of sys_adm_ext is 572 bytes

    • SWITCH TRC-HIDE on ***

    ***LOG Q00=> DpSapEnvInit, DPStart (01 2228) [dpxxdisp.c 1231]

    shared lib "dw_xml.dll" version 52 successfully loaded

    shared lib "dw_xtc.dll" version 52 successfully loaded

    shared lib "dw_stl.dll" version 52 successfully loaded

    shared lib "dw_gui.dll" version 52 successfully loaded

    rdisp/softcancel_sequence : -> 0,5,-1

    use internal message server connection to port 3901

    Fri Nov 20 15:43:50 2009

    • WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds

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

    MtxInit: 30000 0 0

    DpSysAdmExtInit: ABAP is active

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

    DpIPCInit2: start server >sapserver_DM0_01 <

    DpShMCreate: sizeof(wp_adm) 14080 (1408)

    DpShMCreate: sizeof(tm_adm) 3954072 (19672)

    DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

    DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

    DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064

    DpShMCreate: sizeof(comm_adm) 528064 (1048)

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

    DpShMCreate: sizeof(file_adm) 0 (72)

    DpShMCreate: sizeof(vmc_adm) 0 (1452)

    DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)

    DpShMCreate: sizeof(gw_adm) 48

    DpShMCreate: SHM_DP_ADM_KEY (addr: 05DC0040, size: 4608920)

    DpShMCreate: allocated sys_adm at 05DC0040

    DpShMCreate: allocated wp_adm at 05DC1E28

    DpShMCreate: allocated tm_adm_list at 05DC5528

    DpShMCreate: allocated tm_adm at 05DC5558

    DpShMCreate: allocated wp_ca_adm at 0618AAF0

    DpShMCreate: allocated appc_ca_adm at 061908B0

    DpShMCreate: allocated comm_adm at 061927F0

    DpShMCreate: system runs without file table

    DpShMCreate: allocated vmc_adm_list at 062136B0

    DpShMCreate: allocated gw_adm at 062136F0

    DpShMCreate: system runs without vmc_adm

    DpShMCreate: allocated ca_info at 06213720

    DpShMCreate: allocated wall_adm at 06213728

    Fri Nov 20 15:43:51 2009

    MBUF state OFF

    Fri Nov 20 15:43:53 2009

    EmInit: MmSetImplementation( 2 ).

    MM diagnostic options set: 0

    <ES> client 0 initializing ....

    <ES> InitFreeList

    <ES> block size is 4096 kByte.

    Using implementation flat

    <EsNT> Memory Reset disabled as NT default

    <ES> 1022 blocks reserved for free list.

    ES initialized.

    Fri Nov 20 15:43:54 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 2724

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1044

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    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 1617]

    Fri Nov 20 15:43:55 2009

    ***LOG Q0K=> DpMsAttach, mscon ( sapserver) [dpxxdisp.c 11414]

    Fri Nov 20 15:43:56 2009

    DpStartStopMsg: send start message (myname is >sapserver_DM0_01 <)

    DpStartStopMsg: start msg sent

    Fri Nov 20 15:43:57 2009

    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

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

    Fri Nov 20 15:44:00 2009

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

    DpMsgAdmin: Set release to 7000, patchlevel 0

    Fri Nov 20 15:44:01 2009

    MBUF state PREPARED

    MBUF component UP

    DpMBufHwIdSet: set Hardware-ID

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

    DpMsgAdmin: Set patchno for this platform to 52

    Release check o.K.

    Fri Nov 20 15:44:37 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:44:57 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 1064

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1081

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:45:17 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:45:37 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 2656

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1107

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:45:57 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:46:19 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 1428

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1113

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:46:37 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:46:46 2009

    MBUF state ACTIVE

    Fri Nov 20 15:46:53 2009

    DpModState: change server state from STARTING to ACTIVE

    Fri Nov 20 15:46:57 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 3192

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1131

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:47:17 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:47:37 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 3180

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1141

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:47:57 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:48:08 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 15:48:17 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 952

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1147

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:48:37 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:48:58 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 3192

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1156

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:49:17 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:49:37 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 3660

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1164

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:50:01 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:50:21 2009

    J2EE server info

    start = TRUE

    state = STARTED

    pid = 2208

    argv[0] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[1] = D:\usr\sap\DM0\DVEBMGS01\exe\jcontrol.EXE

    argv[2] = pf=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[3] = -DSAPSTART=1

    argv[4] = -DCONNECT_PORT=1171

    argv[5] = -DSAPSYSTEM=01

    argv[6] = -DSAPSYSTEMNAME=DM0

    argv[7] = -DSAPMYNAME=sapserver_DM0_01

    argv[8] = -DSAPPROFILE=D:\usr\sap\DM0\SYS\profile\DM0_DVEBMGS01_sapserver

    argv[9] = -DFRFC_FALLBACK=ON

    argv[10] = -DFRFC_FALLBACK_HOST=localhost

    start_lazy = 0

    start_control = SAP J2EE startup framework

    DpJ2eeStart: j2ee state = STARTED

    Fri Nov 20 15:50:41 2009

    DpJ2eeEmergencyShutdown: j2ee state = SHUTDOWN

    Fri Nov 20 15:51:01 2009

    DpEnvCheckJ2ee: switch off j2ee start flag

    Fri Nov 20 15:59:24 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 15:59:25 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 15:59:45 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 15:59:46 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    SoftCancel request for T16 U19 M0 received from IC_MAN

    Fri Nov 20 15:59:51 2009

    SoftCancel request for T15 U18 M0 received from IC_MAN

    Fri Nov 20 15:59:52 2009

    • ERROR => DpRqCheck: mode 0 in status CANCEL [dpxxdisp.c 6815]

    Fri Nov 20 15:59:56 2009

    SoftCancel request for T14 U17 M0 received from IC_MAN

    Fri Nov 20 16:01:09 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 16:01:10 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 16:01:15 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 16:01:16 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 16:01:17 2009

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    • WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

    Fri Nov 20 16:01:18 2009

    SoftCancel request for T16 U22 M0 received from IC_MAN

    Fri Nov 20 16:01:23 2009

    SoftCancel request for T15 U21 M0 received from IC_MAN

    Fri Nov 20 16:01:28 2009

    SoftCancel request for T14 U20 M0 received from IC_MAN

    Fri Nov 20 16:01:29 2009

    • ERROR => DpRqCheck: T14 in state TM_SLOT_FREE [dpxxdisp.c 6753]

    ***LOG Q0G=> DpRqBadHandle, bad_req ( DIA) [dpxxdisp.c 5104]

    Fri Nov 20 16:01:30 2009

    • ERROR => BAD REQUEST - Reason: DpRqCheck failed (line 5901): [dpxxdisp.c 5106]

    -IN-- sender_id DISPATCHER tid 14 wp_ca_blk 50 wp_id 1

    -IN-- action SEND_TO_WP uid 20 appc_ca_blk -1 type DIA

    -IN-- new_stat WP_WAIT mode 0 len 672 rq_id 527

    -IN-- req_info MSG_WITH_REQ_BUF MSG_WITH_OH

    Add comment
    10|10000 characters needed characters exceeded