IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

error while enabling the process model having same name

  • 1.  error while enabling the process model having same name

    Posted Thu June 25, 2009 09:20 AM

    hi All,

    am getting below error while enabling and saving the process model having same process name and different version V002.

    2009-06-25 10:36:45 IST (portlet : WARN) [RID:10588] - [exception.wm_bam_process_config_details] Your last action caused an exception to occur while executing saveProcessModelToWS(). The details for that exception follow
    SOAPException( Client: [ISS.0088.9134] Exception occurred while processing the body of the message ). The stack follows:
    com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.java:397
    com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.java:216
    $Proxy2.java:-1
    com.webMethods.bpo.portlet.wm_bam_process_config_details.Bam_process_config_details.java:1387
    com.webMethods.bpo.portlet.wm_bam_process_config_details.Bam_process_config_details.java:1302
    sun.reflect.NativeMethodAccessorImpl.java:-2
    sun.reflect.NativeMethodAccessorImpl.java:39
    sun.reflect.DelegatingMethodAccessorImpl.java:25
    java.lang.reflect.Method.java:585
    com.webMethods.portal.mech.portlet.impl.PortletMechanics.java:114
    com.webMethods.portal.bizPolicy.command.portlet.ExecutePortletMethod.java:53
    com.webMethods.portal.framework.portlet.LegacyPortletContainer.java:229
    com.webMethods.portal.framework.portlet.LegacyPortletContainer.java:110
    com.webMethods.portal.framework.portlet.beans.rest.RestfulPCAHandler.java:182
    com.webMethods.portal.framework.dispatch.DispatchManager.java:438
    com.webMethods.portal.framework.dispatch.DispatchManager.java:371
    com.webMethods.portal.framework.impl.PortalServlet.java:242
    javax.servlet.http.HttpServlet.java:689
    org.mortbay.jetty.servlet.ServletHolder.java:428
    org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.java:830
    com.webMethods.portal.framework.impl.NTLMFilter.java:50
    org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.java:821
    com.webMethods.caf.faces.servlet.GZIPFilter.java:34
    org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.java:821
    org.mortbay.jetty.servlet.WebApplicationHandler.java:471
    org.mortbay.jetty.servlet.ServletHandler.java:568
    org.mortbay.http.HttpContext.java:1530
    org.mortbay.jetty.servlet.WebApplicationContext.java:633
    org.mortbay.http.HttpContext.java:1482
    com.webMethods.portal.webApplication.WmWebAppContext.java:159
    org.mortbay.http.HttpServer.java:909
    org.mortbay.http.HttpConnection.java:820
    org.mortbay.http.HttpConnection.java:986
    org.mortbay.http.HttpConnection.java:837
    org.mortbay.http.SocketListener.java:245
    org.mortbay.util.ThreadedServer.java:357
    org.mortbay.util.ThreadPool$PoolThread.java:534
    electric.util.WrappedException: SOAPException( Client: [ISS.0088.9134] Exception occurred while processing the body of the message )
    at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.getCompatibleException(WSClientDynamicProxy.java:397)
    at com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy.invoke(WSClientDynamicProxy.java:216)
    at $Proxy2.saveProcessModel(Unknown Source)
    at com.webMethods.bpo.portlet.wm_bam_process_config_details.Bam_process_config_details.saveProcessModelToWS(Bam_process_config_details.java:1387)
    at com.webMethods.bpo.portlet.wm_bam_process_config_details.Bam_process_config_details.submitMethod(Bam_process_config_details.java:1302)
    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:114)
    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:242)
    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:50)
    at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821)
    at com.webMethods.caf.faces.servlet.GZIPFilter.doFilter(GZIPFilter.java:34)
    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:159)
    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)
    2009-06-25 10:36:47 IST (Framework : INFO) [RID:10589] - Processing request [1wgu1d5dptfuh:Administrator] http://172.21.11.70:8090/meta/default/wm_xt_fabricfolder/0000006775 (GET)

    Regards,
    Anil Kumar Ellendula


    #webMethods-BPMS
    #BPM
    #webMethods


  • 2.  RE: error while enabling the process model having same name

    Posted Tue April 06, 2010 11:19 AM

    remove the duplicate process…ensure only 1version of any process model on the server at one time. The same name will cause duplication of metadata underlying the modeler.


    #BPM
    #webMethods-BPMS
    #webMethods


  • 3.  RE: error while enabling the process model having same name

    Posted Tue October 28, 2014 02:28 AM

    Hello Anil
    I’m stuck with same issue but didn’t create another version for process model,redeployed with same version .May i know how did you resolve it?


    #BPM
    #webMethods
    #webMethods-BPMS


  • 4.  RE: error while enabling the process model having same name

    Posted Tue October 28, 2014 04:20 AM

    Hi anil,

    You cant have only one process as active for given name, you can change versions but I doubt PE can manage two processes are in active…


    #webMethods-BPMS
    #BPM
    #webMethods