Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 974

Re: [Nwv 7.31] Many problems when upgrading to the SP

$
0
0

Hi Ashutosh

 

Thank you for your help. This is the stack trace.

 

possible inconsistency between kernel and deploy controller detected while using Sap Control webservice;

Kernel update to at least patch level 90 is recommended.

[EXCEPTION]

javax.xml.ws.WebServiceException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.

    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:174)

    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:121)

    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84)

    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65)

    at $Proxy464.j2EEControlCluster(Unknown Source)

    at com.sap.engine.services.dc.jstartup.impl.JStartupClusterManagerImpl.restartCluster(JStartupClusterManagerImpl.java:188)

    at com.sap.engine.services.dc.cm.server.impl.AbstractRestartServerService.restart(AbstractRestartServerService.java:202)

    at com.sap.engine.services.dc.cm.server.impl.AbstractRestartServerService.restartInSafeMode(AbstractRestartServerService.java:112)

    at com.sap.engine.services.dc.cm.deploy.impl.OfflineDeployPostProcessor.postProcess(OfflineDeployPostProcessor.java:105)

    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:1138)

    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:1027)

    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:815)

    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deployInternal(DeployerImpl.java:450)

    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:462)

    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: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Client protocol has thrown an exception. Protocol name is [Unknown]. See nested exception for details.

    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1489)

    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)

    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)

    at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:168)

    ... 24 more

Caused by: java.lang.IllegalArgumentException: Implementation for Consumer Protocol with name [SecurityProtocol] is not registered in the client web services runtime. This protocol is required for normal web services client execution.

    at com.sap.engine.services.webservices.espbase.client.bindings.ConsumerProtocolFactory.getProtocols(ConsumerProtocolFactory.java:145)

    at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1312)

    ... 27 more

 

Reagrds,

Mehdi.


Viewing all articles
Browse latest Browse all 974

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>