J2EE connection failed during EHPi configuration phase

[Former Member]

Dear All,

I'm updating solution manager using EHPi tool. During J2EE configuration phase it throws error:

Could not execute dialog UserPasswords. See previous messages. Error while trying to validate Administrator password. Possible reason: the J2EE engine is not started. Error while trying to get initial context. com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances Nested exceptions are: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: xxx.xxx.xxx.xxx and port: 50004 ] com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances Nested exceptions are: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection on host: xxx.xxx.xxx.xxx and port: 50004

(code)

Instance number is 00 ABAP and 01 Java, so I wonder if port 50004 is correct. Anyway - http://localhost:50004 or with 50000 and 50001 are 'not found' by browser. Both stacks are green in MMC. java_start is set to 1. What could be wrong?

thanks in advance

[sunny_pahuja2]

Hi,

Is it Solman 7.1 upgrade ? If not then you cannot use EHPi tool to upgrade solman, you have to use normal SAINT/JSPM for upgrade.

Thanks

Sunny

[Former Member]

Yes this is Solman 7 with EHP1. Phase 'checks' passed correctly. Also SAINT/SPAM update without problems. Stack.xml imported correctly too. What about this J2EE problem? Any ideas?

[Former Member]

Refer Note 1169247 - Additional info for Solution Manager 7.0 EHP1 update

and update guide SAP soution manager.

[Former Member]

thanks.

I hadn't profile parameters:

icm/server_port_0 = PROT=HTTP,PORT=5$$00,TIMEOUT=60,PROCTIMEOUT=600 
icm/server_port_1 = PROT=P4,PORT=5$$04 

so I set them. After reboot disp+work.exe status is:

Running, Message Server connection ok, Dialog Queue time: 0.00 sec, AS Java: Starting the processes

and AS Java status doesn't want to change. Still starting. In Access points I can see:

xxx.xxx.xxx.xxx 50000 HTTP icm active
127.0.0.1 50000 HTTP icm active

and others, but there is no service at port 50004... which I need.

When I open http://localhost:50000 I see:

SAP NetWeaver Application Server	

500 Internal Server Error

Error:	-1
Version:	7200
Component:	HTTP_PLG
Date/Time:	Thu Jun 09 17:14:24 2011
Module:	http_plg.c
Line:	4696
Server:	SAPSVR_SM1_00
Error Tag:	{0003001c}
Detail:	No handler defined for this URL

© 2001-2009, SAP AG

when I try to connect to message server using Visual J2EE administrator using port 8101 I see:

http://hostname:8101/msgserver/text/logon returned empty list of connection parameters

in browser the same link gives:

version 1.0

and just http://hostname:8101/

Not found

The following error occured:

MsSGetNextLogon: no server found which provides service HTTP (msxxserv.c [21523])

SAP message server ,release 720 (SM1) 

so.... conclusion: there is nothing that works

[Former Member]

Check the trace in dev_server0, std_server0.out and dev_jcontrol.

Regards,

Pinkle

[Former Member]

dev_jcontrol:

-
trc file: "dev_jcontrol", trc level: 1, release: "720"
-
node name   : jcontrol
pid         : 11336
system name : SM1
system nr.  : 00
started at  : Thu Jun 09 17:04:13 2011
arguments	  :
	  arg[00] : C:\usr\sap\SM1\DVEBMGS00\exe\jcontrol.EXE
	  arg[01] : pf=C:\usr\sap\SM1\SYS\profile\SM1_DVEBMGS00_SAPSVR
	  arg[02] : -DSAPSTART=1
	  arg[03] : -DCONNECT_PORT=64994
	  arg[04] : -DSAPSYSTEM=00
	  arg[05] : -DSAPSYSTEMNAME=SM1
	  arg[06] : -DSAPMYNAME=SAPSVR_SM1_00
	  arg[07] : -DSAPPROFILE=C:\usr\sap\SM1\SYS\profile\SM1_DVEBMGS00_SAPSVR
	  arg[08] : -DFRFC_FALLBACK=ON
	  arg[09] : -DFRFC_FALLBACK_HOST=localhost
[Thr 12872] Thu Jun 09 17:04:13 2011
[Thr 12872] *** WARNING => Can't open property file [C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\instance.properties] [jstartxx.c   2066]
**********************************************************************
Used property files
-> files [00] : C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\instance.properties
-> files [01] : C:\usr\sap\SM1\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
**********************************************************************
**********************************************************************
Bootstrap nodes
**********************************************************************
**********************************************************************
Worker nodes
-> [00] sdm                  : C:\usr\sap\SM1\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
**********************************************************************
**********************************************************************
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\SM1\DVEBMGS00\j2ee\cluster\instance.properties;C:\usr\sap\SM1\DVEBMGS00\SDM\program\config\sdm_jstartup.properties]
-> ms host    : SAPSVR
-> ms port    : 3901
-> OS libs    : C:\usr\sap\SM1\DVEBMGS00\exe
-> Admin URL  : 
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
**********************************************************************
[Thr 12872] Thu Jun 09 17:04:14 2011
[Thr 12872] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 12872] INFO: Invalid property value [Debbugable=yes]
[Thr 12872] [Node: SDM] java home is set by profile parameter
[Thr 12872] 	Java Home: C:/Program Files/j2sdk1_4_2_30-x64
[Thr 11992] JControlSocketServerFunc: Thread 11992 started as handler thread for control socket.
[Thr 11680] JControlRequestFunc: Thread 11680 started as listener thread for np messages.
[Thr 13648] JControlDPMessageProxy: Thread 13648 started as handler thread for R/3 dispatcher messages.
**********************************************************************
JStartupIReadSection: read node properties [sdm]
-> node name          : SDM
-> node type          : sdm
-> node execute       : yes
-> java path          : C:/Program Files/j2sdk1_4_2_30-x64
-> java parameters    : 
-> java vm version    : 1.4.2_30-b04
-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 256M
-> root path          : C:\usr\sap\SM1\DVEBMGS00\SDM\program
-> class path         : C:\usr\sap\SM1\DVEBMGS00\SDM\program\bin\SDM.jar
-> OS libs path       : C:\usr\sap\SM1\DVEBMGS00\exe
-> main class         : SDMInternal
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : C:\usr\sap\SM1\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\SM1\DVEBMGS00\exe\jvmx.jar
-> shutdown class     : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters         : server sdmhome=C:\usr\sap\SM1\DVEBMGS00\SDM\program
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120 sec.
**********************************************************************
[Thr 12872] Thu Jun 09 17:04:16 2011
[Thr 12872] JControlMSConnect: attached to message server (SAPSVR/3901)
**********************************************************************
JControlStartJLaunch: program = C:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe
-> arg[00] = C:\usr\sap\SM1\DVEBMGS00\exe\jlaunch.exe
-> arg[01] = pf=C:\usr\sap\SM1\SYS\profile\SM1_DVEBMGS00_SAPSVR
-> arg[02] = -DSAPINFO=SM1_00_sdm
-> arg[03] = -nodeId=0
-> arg[04] = -file=C:\usr\sap\SM1\DVEBMGS00\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_11336
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=C:\usr\sap\SM1\DVEBMGS00\work\jvm_sdm.out
-> arg[08] = -stdOutFile=C:\usr\sap\SM1\DVEBMGS00\work\std_sdm.out
-> arg[09] = -locOutFile=C:\usr\sap\SM1\DVEBMGS00\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=C:\usr\sap\SM1\SYS\profile\SM1_DVEBMGS00_SAPSVR
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=54999
-> arg[14] = -DSAPSYSTEM=00
-> arg[15] = -DSAPSYSTEMNAME=SM1
-> arg[16] = -DSAPMYNAME=SAPSVR_SM1_00
-> arg[17] = -DSAPPROFILE=C:\usr\sap\SM1\SYS\profile\SM1_DVEBMGS00_SAPSVR
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\Program Files\j2sdk1_4_2_30-x64\jre\bin\server;C:\Program Files\j2sdk1_4_2_30-x64\jre\bin;C:\oracle\S11\102\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\usr\sap\SM1\SYS\exe\uc\NTAMD64
-> exe path = PATH=C:\Program Files\j2sdk1_4_2_30-x64\bin;C:\usr\sap\SM1\DVEBMGS00\exe;C:\oracle\S11\102\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;c:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;C:\usr\sap\SM1\SYS\exe\uc\NTAMD64
**********************************************************************
[Thr 12076] JControlMSMessageFunc: Thread 12076 started as listener thread for ms messages.
[Thr 12872] JControlICheckProcessList: process SDM started (PID:10592)
[Thr 12872] JControlMSSendLogon: delete SDM logon information (rc=0)
[Thr 12076] Thu Jun 09 17:04:20 2011
[Thr 12076] JControlMSMessageFunc: received command:12, argument:4 from Message Server
[Thr 12076] JControlProcessMessage: received <disable processes 4> command
[Thr 12076] JControlIEnableProcesses: disable processes of type (Exclude:0) [SDM Server]
[Thr 12076] JControlIDisableProcess: disable process SDM
[Thr 12076] JControlIProcessSoftKill: soft kill of process SDM (pid:10592)
[Thr 12872] Thu Jun 09 17:04:25 2011
[Thr 12872] JControlICheckProcessList: process SDM (pid:10592) died (STOPPING)
[Thr 12872] JControlIResetProcess: reset process SDM

two other files does not exists...

Edited by: pw.skiba on Jun 10, 2011 9:25 AM

Edited by: pw.skiba on Jun 10, 2011 9:26 AM

[Former Member]

please provide more logs as requested by Pinkle, as the log you pasted is not having error information.

[Former Member]

there was broken system import and some parts of Java stack were not available. I installed Solman again and it's ok.