Page tree
Skip to end of metadata
Go to start of metadata

Problem

Deployment  fails with Exception: com/sap/engine/services/rmi_p4/exception/NoSuchOperationException

In general this exception means that on skeleton(server) side the called operation (from stub(client) side) is not available. In the skeleton there is no such method.
There could be three reasons causing this issue:

1. In the stub a new method has been written and thus the stub side is newer than skeleton side.
2. A method has been deleted from the stub side.
3. The method signature has been changed and thus it is different on stub and skeleton side. 

Keywords

  • NoSuchOperationException
  • p4

Symptoms

1.

The deployment fails with the following exception:

CausedBy:com.sap.engine.services.rmi_p4.exception.NoSuchOperationException:
Incorrect Operation: 4_p4_generateSessionId() with skel com.sap.engine.services.dc.cm.impl.CMImplp4_Skel@5080cbb1
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:493)
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)
 

2. 

The deployment fails with the following exception:

com.sap.engine.services.rmi_p4.exception.NoSuchOperationException:
Incorrect Operation: 1_p4_generateSessionId() with skel com.sap.engine.services.dc.cm.impl.CMImplp4_Skel@5080cbb1
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:493)
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)

Solution

1. If you have the exception present in symptom 1 your client stub has a newer version than the server skeleton. Use client stub with older version of sap.com~tc~je~clientlib~impl.jar. The version should be the same as the one on server side. 

2. If you have the exception present in symptom 2 your client stub has a older version than the server skeleton. Use client stub with newer version of sap.com~tc~je~clientlib~impl.jar. The version should be the same as the one on server side. 

Sample logs

Related SAP Notes

N/A

  • No labels