problem in logon to j2ee instance

[Former Member]

Hi Friends,

i have installed XI 3.0. i am able to logon to ABAP instance but unable to logon to j2ee instance( But in the management console its status is green). i the browser @port 50000 its shows dispatcher running but no server connected. In J2ee visual administrator its shows error in connection. i gave user name as J2EE_admin, host name <myhost name>, Port as 50004. i have copied the error log below.

Please help me to solve the problem.

VISUAL Administrator Log

#1.5#C000A8A8010100000000000100DC1F04000569DDB10549E0#1523775762156#/System/Server/VisualAdministrationTool##com.sap.engine.services.adminadapter.gui.tasks.LoginTask#######Thread[Thread-2,5,main]##0#0#Error#1#com.sap.engine.services.adminadapter.gui.tasks.LoginTask#Plain###Error while trying to login to SIVA: Connection lost.#

ENSERVER DEVELOPER TRACE (J2EE INSTANCE ITS STATUS IS GREEN)

enserver developer trace(Started).

trc file: "dev_enqsrv", trc level: 1, release: "640"

-

---

systemid 560 (PC with Windows NT)

relno 6400

patchlevel 0

patchno 0

intno 20020600

make: multithreaded, Unicode

pid 3000

[Thr 2464] Sun Apr 15 12:28:49 2018

[Thr 2464] *** ERROR => ShmDelete: Invalid shared memory Key=34. [shmnt.c 682]

[Thr 2464] *** ERROR => ShmCleanup: ShmDelete failed for Key:34. [shmnt.c 756]

[Thr 2464] initialize_global: enqueue server without replication

[Thr 2464] Enqueue: EnqMemStartupAction Utc=1523775529

[Thr 2464] Enqueue Info: replication enabled

[Thr 2464] Enqueue Info: enque/replication_dll not set

[Thr 2464] Sun Apr 15 12:28:50 2018

[Thr 2464] ***LOG GEZ=> Server start [encllog.cpp 526]

DEVELOPER TRACE OF DISPATCHER ( IN ABAP INSTANCE ITS STATUS ALSO GREEN)

Sun Apr 15 12:28:54 2018

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

length of sys_adm_ext is 524 bytes

systemid 560 (PC with Windows NT)

relno 6400

patchlevel 0

patchno 43

intno 20020600

make: multithreaded, Unicode

pid 3016

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

shared lib "dw_xml.dll" version 43 successfully loaded

shared lib "dw_xtc.dll" version 43 successfully loaded

shared lib "dw_stl.dll" version 43 successfully loaded

shared lib "dw_gui.dll" version 43 successfully loaded

Sun Apr 15 12:28:59 2018

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

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

MtxInit: -2 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: JAVA is not active

DpShMCreate: sizeof(wp_adm) 10528 (1316)

DpShMCreate: sizeof(tm_adm) 2780232 (13832)

DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

DpShMCreate: sizeof(comm_adm) 290000 (580)

DpShMCreate: sizeof(vmc_adm) 0 (372)

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

DpShMCreate: SHM_DP_ADM_KEY (addr: 06A70040, size: 3192688)

DpShMCreate: allocated sys_adm at 06A70040

DpShMCreate: allocated wp_adm at 06A71B58

DpShMCreate: allocated tm_adm_list at 06A74478

DpShMCreate: allocated tm_adm at 06A744A0

DpShMCreate: allocated wp_ca_adm at 06D1B0E8

DpShMCreate: allocated appc_ca_adm at 06D20EA8

DpShMCreate: allocated comm_adm_list at 06D22DE8

DpShMCreate: allocated comm_adm at 06D22E00

DpShMCreate: allocated vmc_adm_list at 06D69AD0

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 06D69AF8

DpShMCreate: allocated wall_adm at 06D69B00

MBUF state OFF

EmInit: MmSetImplementation( 2 ).

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation flat

<EsNT> Memory Reset disabled as NT default

<ES> 1981 blocks reserved for free list.

ES initialized.

J2EE server info

start = TRUE

state = STARTED

pid = 3676

argv[0] = D:\usr\sap\SXI\DVEBMGS00\j2ee\os_libs\jcontrol.EXE

argv[1] = D:\usr\sap\SXI\DVEBMGS00\j2ee\os_libs\jcontrol.EXE

argv[2] = pf=D:\usr\sap\SXI\SYS\profile\SXI_DVEBMGS00_SIVA

argv[3] = -DSAPSTART=1

argv[4] = -DCONNECT_PORT=3317

argv[5] = -DLISTEN_PORT=3318

argv[6] = -DSAPSYSTEM=00

argv[7] = -DSAPSYSTEMNAME=SXI

argv[8] = -DSAPMYNAME=SIVA_SXI_00

argv[9] = -DSAPPROFILE=D:\usr\sap\SXI\SYS\profile\SXI_DVEBMGS00_SIVA

argv[10] = -DFRFC_FALLBACK=ON

argv[11] = -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 ( 2.6.1 2.6 4.0) [dpxxdisp.c 1462]

***LOG Q0K=> DpMsAttach, mscon ( SIVA) [dpxxdisp.c 9736]

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

Sun Apr 15 12:29:00 2018

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

Sun Apr 15 12:29:01 2018

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 43

Release check o.K.

Sun Apr 15 12:29:29 2018

MBUF state ACTIVE

DpModState: change server state from STARTING to ACTIVE

Thanks & Reards

SHIVA.

[phanikumar_akella]

Please check if Listner for Oracle running or not.

[paul_digance]

Try logging on to port 50100 in your browser, i.e.

Server homepage:

http://<server>:50100

Server XI homepage:

http://<server>:50100/rep/start/index.jsp

If this works, log on to the J2EE Administrator on port 50104 instead of 50004.

(Please assign forum points if this solves the problem)

Thanks,

Paul D.

[agasthuri_doss]

Hi,

check if the SAPService<SID> has "full access" control over the ..\usr\sap\<SID> directory in the directory security properties.

Regards

Agasthuri Doss

[Former Member]

Hi All,

If the J2EE used to run before it can not be a cse of wrong parameters in SMICM,

Are you aware if during satrt up there were some bulky data getting processed??

Some time this happens.., probably cheking the start up log can be a good idea.

Another restart will do the trick it the Log does not give any thing specific.

You can open a Customer message as well for SAP

Regards

Piyush

[Former Member]

Hi Siva,

just ask your basis guys to see the startup-log of your XI J2EE engine....if it has errors in it, then ask your basis guys to restart your XI server completely......then after complete XI server restart, check again with your basis guys to see if your J2EE engine startup log doesnt have any error in it......then if there is no error and your XI J2EE engine is up and running, then you can log into your XI J2EE engine..

Thanks,

Rajeev Gupta

[Former Member]

Hi,

Did you check SMICM?

Looks like a case of incorrect profile parameters. Ask SAP for list of correct profile parameters.

Check with this link also:

http://help.sap.com/saphelp_nw2004s/helpdata/en/c4/3a615d505211d189550000e829fbbd/frameset.htm

Regards,

Puloma.