cancel
Showing results for 
Search instead for 
Did you mean: 

webservices_3606 error message

Former Member
0 Kudos

Hi,

from the java stack I´m calling a webservice at abap side and receive the error message webservices_3606. Does anyone know what this means? Below I added the full callstack.

I can call other webservices from other application at the same server.

Thanks in advance

Helmut

webservices_3606 
[EXCEPTION]
 com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: Cannot get logical port implementation. See nested exception.
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ServiceBaseServer.getPort(ServiceBaseServer.java:368)
 at com.eonis.ewa.ibsatweb.wsproxy.storagedetails_2.Z_EGVIBS_GET_STORAGE_DETAILS_2ServiceImpl.getLogicalPort(Z_EGVIBS_GET_STORAGE_DETAILS_2ServiceImpl.java:11)
 at com.eonis.ewa.ibsatweb.dao.CFoldersDAO_WS.getStorageDetails(CFoldersDAO_WS.java:159)
 at com.eonis.ewa.ibsatweb.businessprocess.GetStorageDetailsBP$InnerGetStorageDetails.performImpl(GetStorageDetailsBP.java:94)
 at com.eonis.intlib.tc.java.tif.core.businessprocess.AbstractCommand.perform(AbstractCommand.java:69)
 at com.eonis.ewa.ibsatweb.businessprocess.SaveInitialCommissiongBP$InnerSaveInitialCommissioning.getStorageDetails(SaveInitialCommissiongBP.java:770)
 at com.eonis.ewa.ibsatweb.businessprocess.SaveInitialCommissiongBP$InnerSaveInitialCommissioning.performImpl(SaveInitialCommissiongBP.java:303)
 at com.eonis.intlib.tc.java.tif.core.businessprocess.AbstractCommand.perform(AbstractCommand.java:69)
 at com.eonis.ewa.ibsatweb.ejb.InbetriebSetzungAtWebEJBBean.saveInitialCommissioning(InbetriebSetzungAtWebEJBBean.java:83)
 at com.eonis.ewa.ibsatweb.ejb.InbetriebSetzungAtWebEJBLocalLocalObjectImpl0_0.saveInitialCommissioning(InbetriebSetzungAtWebEJBLocalLocalObjectImpl0_0.java:103)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
 at java.lang.reflect.Method.invoke(Method.java:391)
 at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
 at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
 at SoapServlet.doPost(SoapServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(AccessController.java:219)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.engine.services.webservices.jaxrpc.wsdl2java.lpapi.StubConfigurationException:  Unable to get instance of feature provider with name <WSDMClientProtocol> used in logical port <Z_EGVIBS_GET_STORAGE_DETAILS_2PortType>.
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.lpapi.LogicalPortFactory.getConfiguredStub(LogicalPortFactory.java:684)
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ServiceBaseServer.getPort(ServiceBaseServer.java:366)
 ... 35 more
Caused by: com.sap.engine.services.webservices.exceptions.BaseComponentInstantiationException: Plug-in component instanciation error! The problem is: there is no client protocol factory registered. The error refers to component: WSDMClientProtocol, type: client protocol. Additional info: {3}.
 at com.sap.engine.services.webservices.runtime.component.ComponentFactoryImpl.getClientProtocolInstance(ComponentFactoryImpl.java:86)
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.lpapi.LogicalPortFactory.getConfiguredStub(LogicalPortFactory.java:682)
 ... 36 more
Caused by: com.sap.engine.services.webservices.exceptions.RegistryException: Element WSDMClientProtocol not found in com.sap.engine.services.webservices.runtime.component.ClientProtocolFactoryRegistry! Additional information: {2}.
 at com.sap.engine.services.webservices.runtime.component.ComponentRegistry.getComponent(ComponentRegistry.java:35)
 at com.sap.engine.services.webservices.runtime.component.ClientProtocolFactoryRegistry.getClientProtocolFactory(ClientProtocolFactoryRegistry.java:23)
 at com.sap.engine.services.webservices.runtime.component.ComponentFactoryImpl.getClientProtocolInstance(ComponentFactoryImpl.java:80)
 ... 37 more

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello,

Here is the important part of the above error message:

Caused by: com.sap.engine.services.webservices.jaxrpc.wsdl2java.lpapi.StubConfigurationException: Unable to get instance of feature provider with name used in logical port .

...

Caused by: com.sap.engine.services.webservices.exceptions.BaseComponentInstantiationException: Plug-in component instanciation error! The problem is: there is no client protocol factory registered. The error refers to component: WSDMClientProtocol, type: client protocol.

u2026

Caused by: com.sap.engine.services.webservices.exceptions.RegistryException: Element WSDMClientProtocol not found in com.sap.engine.services.webservices.runtime.component.ClientProtocolFactoryRegistry! Additional information: .

You should try to find other errors related to WSDMClientProtocol in the defaultTrace.

You could also increase the log severity to DEBUG on location: com.sap.engine.services.webservices

To do this, open Visual Admin, go to Services->Log Configuration, go to "Locations", find the location, given above and change the severity. Save change and reproduce the fault.

Restart the server node and reproduce the issue to generate the logs. Review the defaultTrace for other errors or warnings related to WSDMClientProtocol.

Regards,

Ventsi Tsachev

htammen
Active Contributor
0 Kudos

Thanks for your answer but I´ve already done all the things you´ve suggested without any further results except restarting the server. I`m not allowed to do that and the admins are currently not available.

Very curious is that the same application runs at another identical configured server without problems and that other applications that use similar technologies are also running at this server.

Regards

Helmut