cancel
Showing results for 
Search instead for 
Did you mean: 

custom FTP Adapter module - P4 RuntimeException

peter_wallner2
Active Contributor
0 Kudos

Dear experts,

We are upgrading our PI system from 7.0 to 7.3 and I have two adapter modules that I need to migrate to 7.3.

I downloaded the latest version of NWDS which is 7.1 SP13 and I have followed the following blogs for PI 7.1:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e674...

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0ac06cf-6ee2-2c10-df98-e17430ca5...

I also referred to:

http://wiki.sdn.sap.com/wiki/display/XI/XIlibrariesfor+development

Are there any differences in developing an adapter module for PI 7.3?

When deploying the EAR file with NWDS I received the following errors in the logfile:


Deploy Exception.Unexpected exception. [ERROR: 04.11.2011 13:03:20 /userOut/daView_category (eclipse.UserOutLocation) [Thread[Deploy Thread,5,main]] ]

Thank you for any ideas on this.

Best regards,

Peter

The complete logfile is this:


--- Deploying file(s):
	C:workspace-nwds-7.1SetNameInZipArchiveEARSetNameInZipArchiveEAR.ear

--- Status:
	Deploy Exception.

--- Description:
	
		  S U M M A R Y
~~~~~~~~~~~~~~~~~~~

Successfully deployed:	      0

Deployed with warnings:	      0

Failed deployments:		      1

~~~~~~~~~~~~~~~~~~~

Unexpected exception.

1. File:C:workspace-nwds-7.1SetNameInZipArchiveEARSetNameInZipArchiveEAR.ear
	NULL
	Deploy status:Initial
	Version:null


--- Exception:
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] P4RuntimeException.
Reason: Unexpected exception.
	at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:882)
	at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
	at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
	at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:122)
Caused by: com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
	at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:648)
	at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:617)
	at com.sap.engine.services.dc.cm.deploy.Deployer_Stub.deploy(Deployer_Stub.java:279)
	at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:688)
	... 3 more
Caused by: java.rmi.RemoteException: ERROR: ; nested exception is: 
	java.lang.NoSuchMethodError: com.sap.jvm.monitor.os.OsInfo.getUsableSpaceWithError(Ljava/lang/String;)J
	at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:482)
	at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
	at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
	at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
	at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:983)
	at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
	at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
	at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
	at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
	at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: java.lang.NoSuchMethodError: com.sap.jvm.monitor.os.OsInfo.getUsableSpaceWithError(Ljava/lang/String;)J
	at com.sap.engine.services.dc.util.FileUtils.getUsableSpaceWithError(FileUtils.java:257)
	at com.sap.engine.services.dc.cm.deploy.impl.SduLoader.doCheckForSufficientDiskSpace(SduLoader.java:168)
	at com.sap.engine.services.dc.cm.deploy.impl.SduLoader.load(SduLoader.java:65)
	at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.loadArchives(DeployerImpl.java:1171)
	at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deployInternal(DeployerImpl.java:326)
	at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:224)
	at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:910)
	at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:459)
	... 9 more

Edited by: Peter Wallner on Nov 4, 2011 1:01 PM - added complete logfile

Edited by: Peter Wallner on Nov 4, 2011 1:03 PM - edited logfile content

Accepted Solutions (0)

Answers (1)

Answers (1)

markus_schalk
Participant
0 Kudos

Hello Peter,

please have a look at sap Note 1004000 - SAP NetWeaver PI Adapter/Module Development: API Changes

MIGRATION NOTES

API: SAP NetWeaver04 XI 3.0/7.0 any SP; Documentation: XI 3.0/7.0 any SP

XI 3.0/7.0 adapter and module implementations cannot be deployed as of SAP NetWeaver PI 7.1. The source code must be adjusted first. Please use the API cross reference attached here. Further information can be found in the PI documentation on SAP Help Portal.

This should help you out!

Kind regards,

Markus Schalk

peter_wallner2
Active Contributor
0 Kudos

Hello Markus,

I did adjust the source code I had for PI 7.0 to PI 7.1 before I created the EAR file with NWDS 7.1

(also the libraries are different from PI 7.0 to PI 7.1).

I was just wondering if there are also adjustments from PI 7.1 to PI 7.3 but I could not find any information on that. I assume

it stays the same.

But in the meantime I found:

http://wiki.sdn.sap.com/wiki/display/TechTSG/%28JSTTSG%29%28Deploy%29Problems-P20

which might be the solution.

The line: "java.lang.NoSuchMethodError: com.sap.jvm.monitor.os.OsInfo.getUsableSpaceWithError" I also

have in my error logfile. I have to check with my colleagues on that.

Best regards,

Peter

markus_schalk
Participant
0 Kudos

Hello Peter,

i am sorry i didn't get your question right, as you where talking about update form 7.0 to 7.3 i thought your asking how to adapt your modules from 7.0 to 7.x...

I don't know any changes made in module development from 7.1 to 7.3 so you should be fine with your coding right now!

As you already found out, your problem could have something to do with your jvm.

I wish you good luck fixing it soon!

Kind regards,

Markus

peter_wallner2
Active Contributor
0 Kudos

Hello Markus, Hello experts,

I downloaded NWDS 7.3 and set up the adapter module coding again. When I try to deploy it, it brings the same error.

With NWDS 7.1 and NWDS 7.3 I am using "jdk1.6.0_07".

Is there a guide line somewhere on how to develop an adapter module with NWDS 7.3 for PI 7.3?

- The EJB Project I created is "SAP EJB J2EE 1.4 Project" - does that work for PI 7.3?

(the other option would be "SAP EJB Java EE 5 Project")

- What libraries (JARS) do I have to include for 7.3? (I included the JARS I used to develop for 7.1)

I could not find any documentation on this. Thank you for your help again!

Best regards,

Peter

Edited by: Peter Wallner on Nov 8, 2011 1:46 PM - added JDK version

peter_wallner2
Active Contributor
0 Kudos

Ok, my "solution" was that the deployment does not work in our development system.

I tried deploying on our test system and it worked!

Thank you for you help though.

Conclusion:

To develop an adapter module for PI 7.3 one can use the same libraries and guide lines as for PI 7.1

Best regards,

Peter

Former Member
0 Kudos

Hi Peter,

I am facing the same error. Can you please confirm following things to me ?

1) What was jdk version you used ?

2) What was NWDS version you used 7.3 or 7.1? Is it SP level need to be same as of PI ?

3) what java facet setting you selected in NWDS Java 6 or Java 5 ?

Regards

Inder

peter_wallner2
Active Contributor
0 Kudos

Hello Inder,

1) jdk1.5.0_22

2) NWDS 7.30 I do not think that the SP level matters.

3) I am not sure where you choose the facet setting - please let me know and I check.

Regards,

Peter

Former Member
0 Kudos

Thanks Peter. I was facing the above error. This error occurs if your jvm is older than 1.6.025. I updated jvm and it fised the issue..