CE71: error during applying SP with CEUPDATE tool

[Former Member]

Hi Experts ,

Iam getting following error while updating SP through CEUPDATE tool .

The execution of a command has failed

Error message: Unable to start JSPM. $(0) Remote connection was closed.

The request could not be processed.

SOLUTION: Check the file UpdateSystem.log for more information on how to solve the problem.

-

---

-

---

Progress of TASK_DEPLOY

-

---

Status : ERROR

Total Units : 100

Current Units : 5

Progress : 5

Status Details :

com.sap.sdt.jspm.c42.exceptions.StartException: Unable to start JSPM. $(0)

Remote connection was closed. The request could not be processed.

Exception : com.sap.sdt.jspm.c42.exceptions.StartException: Unable to start JSPM. $(0)

Remote connection was closed. The request could not be processed.

TaskResult : null

Exception in thread "C42JSPMAdapter_Deploy" java.lang.NullPointerException:

at com.sap.sdt.jspm.c42.workers.DeployWorker.run(DeployWorker.java:192)

at java.lang.Thread.run(Thread.java:725)

com.sap.lm.jspmadapter.standalone.adapter.CallJSPMAdapter-INFO: JSPM finished with an error rc: 3

com.sap.sdt.jspm.c42.exceptions.StartException: Unable to start JSPM. $(0)

Remote connection was closed. The request could not be processed.

at com.sap.sdt.jspm.c42.workers.JspmConnectWorker.startJSPM(JspmConnectWorker.java:153)

at com.sap.sdt.jspm.c42.workers.DeployWorker.deploy(DeployWorker.java:115)

at com.sap.sdt.jspm.c42.workers.DeployWorker.run(DeployWorker.java:176)

at java.lang.Thread.run(Thread.java:725)

Caused by: com.sap.sdt.jspm.rapi.connector.JSPMConnectorException: Remote connection was closed. The request could not be processed.

at com.sap.sdt.jspm.rapi.connector.JSPMConnector.waitForToolReady(JSPMConnector.java:177)

at com.sap.sdt.jspm.rapi.connector.JSPMConnector.startJSPM(JSPMConnector.java:128)

at com.sap.sdt.jspm.c42.workers.JspmConnectWorker.startJSPM(JspmConnectWorker.java:149)

... 3 more

com.sap.sdt.jspm.rapi.connector.JSPMConnectorException: Remote connection was closed. The request could not be processed.

at com.sap.sdt.jspm.rapi.connector.JSPMConnector.waitForToolReady(JSPMConnector.java:177)

at com.sap.sdt.jspm.rapi.connector.JSPMConnector.startJSPM(JSPMConnector.java:128)

at com.sap.sdt.jspm.c42.workers.JspmConnectWorker.startJSPM(JspmConnectWorker.java:149)

at com.sap.sdt.jspm.c42.workers.DeployWorker.deploy(DeployWorker.java:115)

at com.sap.sdt.jspm.c42.workers.DeployWorker.run(DeployWorker.java:176)

at java.lang.Thread.run(Thread.java:725)

UPDATEXE ends with 1

java.io.FileNotFoundException: class_prefetch.lst (Permission denied)

at java.io.FileOutputStream.open(Native Method)

at java.io.FileOutputStream.<init>(FileOutputStream.java:179)

at java.io.FileOutputStream.<init>(FileOutputStream.java:70)

at com.sap.engine.offline.FileClassLoader.close(FileClassLoader.java:1553)

at com.sap.engine.offline.FileClassLoader$1InternalHook.run(FileClassLoader.java:375)

Please advise

Thanks & regards ,

Jayakrishna

[Former Member]

Hi,

I am also getting the same error.

I am updating CE 711 SP1 to SP4.

com.sap.sdt.jspm.c42.exceptions.StartException: Unable to start JSPM

Remote connection was closed. The request could not be processed.

I am using Virtual Server.

I have manually updated JSPM and JVM to 5.1.051, but still running into same issue.

Any help is highly appreciated.

Regards,

Rao

[Former Member]

We are receiving the same error message updating from NW CE 7.0 SPS 6 to 7.11 SPS3 using the ceupdatemanager tool. It appears to be related to the fact that our environment is setup with a virtual hostname, the connection to the SDTServer fails with connection refused. We have opened a customer msg and are waiting on a response from SAP Support.

I have tried a number of configuration changes regarding hostnames but without success.

The tool worked without issue in our development environment which is not clustered and does not use a virtual hostname.

Edited by: Jeremy Blawn on Dec 8, 2009 9:58 PM

[Former Member]

Try upgrading the JSPM component manually to 7.11.x. Then upgrade SAPJVM as a single component to the latest version (as of this writing - 5.1.046). This resolved our connection issue when JSPM is spawned through ceupdatemanager.

Let me know if this works for you.

Thanks,

Jeremy

[former_member184154]

Jeremy,

I am really interested in your valuable pint of view. As you may guess I am running into the same problem.

My CE is running inside a VM.

I noticed that the "normal" update process has successfully updated the JSPM, and that's fine.

How do you "update JVM as a single component"? Using JSPM? I have tried all the 4 initial JSPM options, but it looks like it's not recongizing any SCA/SAR inside my inbox. (it sees the installed version of each component but not the target one...)

Any clue?

Thanks in advance.

Alex

[former_member184154]

Never mind: found the answer myself!

Note 1133020 to do it via JSPM or (I like this, oh yes) note 1025085 to do it manually.

Cheers,

Alex

[former_member184154]

And, after all, I happily confirm that the workaround works...!

JSPM in my case was the only thing that was successfully updated by the CEUPDATEMANAGER.

But then, the infamous error.

After upgrading the JVM, ALL RIGHT. The update process smoothly continues.

Cheers,

Alex