While trying to resubmit a service from MWS which involves web service call to an external partner within it, it throws the below error to me:

[POP.012.9002.wm_mon_service_details] Remote Exception caught: electric.util.WrappedException: SOAPException( Client: [ISS.0088.9133] Error while encoding RPC output )

electric.util.WrappedException: SOAPException( Client: [ISS.0088.9133] Error while encoding RPC output )
at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.getCompatibleException(WSClientDynamicProxy.java:398)
at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invoke(WSClientDynamicProxy.java:214)
at $Proxy12.resubmit(Unknown Source)
at com.webMethods.bpo.portlet.wm_mon_service_details.Mon_service_details.resubmit_resubmit(Mon_service_details.java:532)
at com.webMethods.bpo.portlet.wm_mon_service_details.Mon_service_details.doResubmit(Mon_service_details.java:423)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.webMethods.portal.mech.portlet.impl.PortletMechanics.executePortletMethod(PortletMechanics.java:118)
at com.webMethods.portal.bizPolicy.command.portlet.ExecutePortletMethod.executePortletMethod(ExecutePortletMethod.java:53)
at com.webMethods.portal.framework.portlet.LegacyPortletContainer.process(LegacyPortletContainer.java:229)
at com.webMethods.portal.framework.portlet.LegacyPortletContainer.processPortletAction(LegacyPortletContainer.java:110)
at com.webMethods.portal.framework.portlet.beans.rest.RestfulPCAHandler.handle(RestfulPCAHandler.java:182)
at com.webMethods.portal.framework.dispatch.DispatchManager.handle(DispatchManager.java:438)
at com.webMethods.portal.framework.dispatch.DispatchManager.handleDispatch(DispatchManager.java:371)
at com.webMethods.portal.framework.impl.PortalServlet.service(PortalServlet.java:249)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830)
at com.webMethods.portal.framework.impl.NTLMFilter.doFilter(NTLMFilter.java:66)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at com.webMethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:32)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at com.webMethods.portal.framework.impl.RequestFilter.doFilter(RequestFilter.java:56)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at com.webMethods.caf.faces.servlet.XSSFilter.doFilter(XSSFilter.java:22)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at com.webMethods.portal.webApplication.WmWebAppContext.handle(WmWebAppContext.java:161)
at org.mortbay.http.HttpServer.service(HttpServer.java:909)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)

Can someone please suggest.

Thanks
Siva

Hi Shiva,

The above one which you shared is a more generic error in MWS. You will able to see what exact is the problem in IS logs. Can you kindly check with DBA’s to know any IS Core Audit database user was locked and the same in other DB’s. If yes, kindly unlock the user, and restart both IS and MWS. Please update the forum with your observations after checking the above list.

Thanks,

See the detail element in the SOAP fault to determine the exception that was thrown
and by which process it was thrown.

The same service when I resubmit from IS / Developer, works fine. So, it must be some configuration issue between MWS and IS. Opinion ?

Hi Siva,

please check if the Settings in the WmMonitor-Package are correct to connect to the MWS.

Additionally check for the SAML-Resolver setting in IS:
Single Sign-On with My webMethods Server
MWS SAML Resolver URL http://:/services/SAML

Regards,
Holger

Hi Siva,

Are you not able to submit any service from MWS or is the problem with only a single webService. Did you also check, any users locked in DB which i specified in my earlier reply ??

Thanks,