Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

JSPM - J2EE update went wrong?!

Hello,

i wanted to update my Java stack from patch lvl 12 to 15. It was my first time to do a update with JSPM (Im new in SAP administration).

So i first patched the JSPM from 12 to 15. Then I restarted it and patched the:

Basetables from 12 to 15.0

Core-Tools from 12 to 15.0

JLogView from 12 to 15.0

SAP-JEE from 12.4 to 15.4

SAP-JEECOR from 12.0 to 15.0

SAP-JTECHF from 12.0 to 15.0

After this i restarted the server and now my J2EE Engine will not start again (J2EE: Some processes running).

.........................

I already restartet the whole server but the same issue. Any idea what went wrong?!

Here is my dev_trace of the dispatcher:

-


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

-


sysno 00

sid C60

systemid 562 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 146

intno 20050900

make: multithreaded, Unicode, 64 bit, optimized

pid 5044

Wed Oct 08 15:08:27 2008

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

length of sys_adm_ext is 576 bytes

      • SWITCH TRC-HIDE on ***

***LOG Q00=> DpSapEnvInit, DPStart (00 5044) [dpxxdisp.c 1243]

shared lib "dw_xml.dll" version 146 successfully loaded

shared lib "dw_xtc.dll" version 146 successfully loaded

shared lib "dw_stl.dll" version 146 successfully loaded

shared lib "dw_gui.dll" version 146 successfully loaded

shared lib "dw_mdm.dll" version 146 successfully loaded

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

use internal message server connection to port 3900

Wed Oct 08 15:08:32 2008

      • 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 5371]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

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

DpIPCInit2: start server >dmsapcrm07_C60_00 <

DpShMCreate: sizeof(wp_adm) 29600 (1480)

DpShMCreate: sizeof(tm_adm) 5652128 (28120)

DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

DpCommTableSize: max/headSize/ftSize/tableSize=500/16/552064/552080

DpShMCreate: sizeof(comm_adm) 552080 (1088)

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

DpShMCreate: sizeof(slock_adm) 0 (104)

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

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1864)

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

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000EE80050, size: 6353024)

DpShMCreate: allocated sys_adm at 000000000EE80050

DpShMCreate: allocated wp_adm at 000000000EE82150

DpShMCreate: allocated tm_adm_list at 000000000EE894F0

DpShMCreate: allocated tm_adm at 000000000EE89550

DpShMCreate: allocated wp_ca_adm at 000000000F3ED3F0

DpShMCreate: allocated appc_ca_adm at 000000000F3F31B0

DpShMCreate: allocated comm_adm at 000000000F3F50F0

DpShMCreate: system runs without slock table

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 000000000F47BD80

DpShMCreate: allocated gw_adm at 000000000F47BE00

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 000000000F47BE30

DpShMCreate: allocated wall_adm at 000000000F47BE40

MBUF state OFF

DpCommInitTable: init table for 500 entries

ThTaskStatus: rdisp/reset_online_during_debug 0

EmInit: MmSetImplementation( 2 ).

MM global diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 4096 kByte.

Using implementation view

<EsNT> Using memory model view.

<EsNT> Memory Reset disabled as NT default

<ES> 127 blocks reserved for free list.

ES initialized.

J2EE server info

start = TRUE

state = STARTED

pid = 2588

argv[0] = C:\usr\sap\C60\DVEBMGS00\exe\jcontrol.EXE

argv[1] = C:\usr\sap\C60\DVEBMGS00\exe\jcontrol.EXE

argv[2] = pf=C:\usr\sap\C60\SYS\profile\C60_DVEBMGS00_dmsapcrm07

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=65000

argv[5] = -DSAPSYSTEM=00

argv[6] = -DSAPSYSTEMNAME=C60

argv[7] = -DSAPMYNAME=dmsapcrm07_C60_00

argv[8] = -DSAPPROFILE=C:\usr\sap\C60\SYS\profile\C60_DVEBMGS00_dmsapcrm07

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

***LOG Q0K=> DpMsAttach, mscon ( dmsapcrm07) [dpxxdisp.c 11822]

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

DpStartStopMsg: start msg sent

Wed Oct 08 15:08:33 2008

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 146

Release check o.K.

DpJ2eeLogin: j2ee state = CONNECTED

Wed Oct 08 15:08:41 2008

MBUF state ACTIVE

DpModState: change server state from STARTING to ACTIVE

Wed Oct 08 15:29:36 2008

J2EE server info

start = TRUE

state = ACTIVE

pid = 2588

http = 50000

https = 50001

load balance = 1

start_lazy = 0

start_control = SAP J2EE startup framework

Not what you were looking for? View more on this topic or Ask a question