update java server from 7.00 SP17 to 7.05 SP05 with EHPI

[Former Member]

hi all

i' m upgrading a java server from version 7.00 SP17 to version 7.01 SP05 (ehp1) with the

EHPI installer

during the phase PREPARE_JSPM_QUEUE i get the error that the jspm has already been started

any ideas

regards tom

file: TroubleTicket_01.txt

SID................: JWC

Hostname...........: aapbwc

Install directory..: /usr/sap/JWC

Upgrade directory..: /usr/sap/JWC/EHPI/java

Database...........: Oracle

Operating System...: UNIX

JDK version........: 1.5.0_12 SAP AG

SAPJup version.....: 3.2.2

Source release.....: 700

Target release.....: 700

Start release SP...: $(/J2EE/StandardSystem/SPLevel)

Target release SP..: $(/J2EE/ShadowSystem/SPLevel)

Current usages.....:

ABAP stack present.: false

The execution of PREPARE/INIT/PREPARE_JSPM_QUEUE ended in error.

Could not connect JSPM tool.

JSPM has already been started.

file: PREPARE_JSPM_QUEUE_CSZ_01.LOG

Nov 9, 2009 11:11:51 AM [Warning]: com.

sap.sdt.j700.deploymentmgr.DeploymentManagerImpl [Thread[main,5,main]]: Deployment of a

rchive /usr/sap/trans/EPS/in/JSPM05_0-20002796.SCA has been rejected because it is alre

ady deployed.

Nov 9, 2009 11:11:51 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator

.createAndValidateQueue(JSPMSpStackQueuePreparator.java:184) [Thread[main,5,main]]: Cre

ating jspm queue sapjup-queue from sp stack file /usr/sap/trans/EPS/in/SPSTab.xml.

Nov 9, 2009 11:11:51 AM [Error]: com.sap.sdt.ucp.phases.AbstractP

haseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occ

urred during the execution of the phase.

Nov 9, 2009 11:11:51 AM [Error]: com.sap.sdt.sltool.rapi.connector.AbstractToolConn

ector.startTool(AbstractToolConnector.java:98) [Thread[main,5,main]]: JSPM has already

been started.

[Former Member]

Try switching it back to the original port 6250. That's what I did after switching it to 6240, grepping the process table for 'JSPM', finding an orphaned process, killing it, and trying again. It worked to get me past that error, but now I am getting a different one.

[Former Member]

hi sunny

definitivlely is not used neither from abab nor from java

regards tom

[Former Member]

hi

yes we have on the same system 2 instances

the abap instance BWC and the java instance JWC

totaly separated

regards tom

[sunny_pahuja2]

Hi,

Check 6240 port is not used by ICM of ABAP system ?

Thanks

Sunny

[Former Member]

hi ventsi

the port 6240 is not in use until the ehpi comes to the failing phase

PREPARE_JSPM_QUEUE phase

bash-3.00$ netstat -an | grep -i 6240

tcp4 0 0 *.6240 . LISTEN

tcp4 0 0 10.128.72.179.6240 10.128.72.179.49942 ESTABLISHED

tcp4 0 0 10.128.72.179.49942 10.128.72.179.6240 ESTABLISHED

and then it fails with the above error

regards tom

[sunny_pahuja2]

Hi,

Is on same host other systems are installed ?

@Ventsi: This is SAP AG Java not IBM and SUN. This is valid.

Thanks

Sunny

[Former Member]

hi sunny

i solved this problem before

i changed the value in the file /usr/sap/JWC/EHPI/java/config -> JspmProperties.xml port

from 6250 to 6240 (standard) i also solved the problem with the profile -> instanz ID

but now i got the problem described in this note

[Former Member]

Hello,

I noticed that you are using non supported JDK version - JDK version........: 1.5.0_12 SAP AG.

You should use 1.4.2 instead.

Try stopping JSPM GUI and the JSPM server and check if the port is still open.

If the port is not in use start JSPM again and you shouldn't experience the error.

If the port is in use it means that JSPM is not stopped or there is other program that is using it.

Regards,

Ventsi

[sunny_pahuja2]

Hi,

Check whether port number 6240 is free or used.

Check with nestat or lsof command. if port is not free, then make sure that this port should be free.

Thanks

Sunny