2 Replies Latest reply on Sep 20, 2017 2:04 AM by Aryan Anantwar

    "Process could not be found" error in catalina log

      Share This:

      This error appears in catalina log file sometimes and then stops.

       

      Set 19, 2017 11:37:02 AM com.sun.xml.ws.server.sei.TieHandler createResponse

      SEVERE: Process ":NextelBAO_Horizon:NextelBAO_Horizon_GetMsisdnInformation" of grid "ProdGrid" could not be found, or is not a fully-automated process and cannot be execute through this web service.

      java.lang.IllegalArgumentException: Process ":NextelBAO_Horizon:NextelBAO_Horizon_GetMsisdnInformation" of grid "ProdGrid" could not be found, or is not a fully-automated process and cannot be execute through this web service.

      at com.bmc.ao.soa.OrchestratorServiceImpl.executeProcess(OrchestratorServiceImpl.java:614)

      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

      at java.lang.reflect.Method.invoke(Unknown Source)

      at com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:250)

      at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:149)

      at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:94)

      at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:961)

      at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:910)

      at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:873)

      at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:775)

      at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:386)

      at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:640)

      at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:263)

      at com.sun.xml.ws.transport.http.servlet.ServletAdapter.invokeAsync(ServletAdapter.java:218)

      at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:159)

      at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:194)

      at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:80)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:641)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

      at com.bmc.atrium.sso.agents.web.jee.JEEFilter.doFilter(Unknown Source)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

      at org.springframework.security.ui.logout.LogoutFilter.doFilterHttp(LogoutFilter.java:89)

      at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53)

      at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:236)

      at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)

      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)

      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)

      at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)

      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)

      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)

      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)

      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)

      at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)

      at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)

      at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)

      at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

      at java.lang.Thread.run(Unknown Source)

       

      Does anyone know the reason?

       

      Thanks,

        • 1. Re: "Process could not be found" error in catalina log
          Matthew Highcove

          This most often occurs when a user tries to use one of BAO's web services to run a workflow that is not available for web service calls. Here, a user sent a web service request telling BAO to run the workflow "NextelBAO_Horizon_GetMsisdnInformation" in the module "NextelBAO_Horizon", but that workflow either does not exist, is not active on the grid, or is not exposed as SOAP. If you do not intend for this workflow to be run via web service, you must determine what service or user is calling BAO trying to run it.

           

          If you do intend for this process to be run via SOAP, verify the following:

          • The module and workflow name are correct.
          • The module NextelBAO_Horizon is active on your grid. Uploading the module to the Repository is not sufficient; the module must be activated for BAO to use it.
          • The module is the correct version. If you created or updated the workflow NextelBAO_Horizon_GetMsisdnInformation in Development Studio but have not exported it to the Repository or activated it, the grid does not have access to your changes.
          • The workflow is exposed as SOAP. In Development Studio, open the workflow, right-click on the background canvas, and select "Properties". The checkbox next to "Expose Process: As SOAP" must be enabled.
          • The workflow has no Operator Dialog activities. These are part of semi-automated workflows, and a workflow started via SOAP call cannot use them.
          • 2. Re: "Process could not be found" error in catalina log
            Aryan Anantwar

            Hi,

             

            also check that the AO user account is used for calling that workflow via webservice has permissions to execute that workflow.

            • Login to CDP console
            • Navigate to Administration Tab
            • Navigate to Grid Permissions and check.

             

            Regards,

            Aryan Anantwar