1 Reply Latest reply on Mar 2, 2007 7:43 PM by Meghana Joglekar

    transition to DOES_NOT_EXIST; my partnerLink name matches st

    Meghana Joglekar Novice

      My BPEL has partnerLink defined like this -

      <partnerLink name="NewHireClient" partnerLinkType="tns:AlfServiceFlow" myRole="AlfServiceFlowProvider" />

      and webservices.xml has
       name of the partner link served by this port

      Last time when I got this exception
      14:19:24,213 INFO [ServiceEndpointManager] WebService started: http://HQ02022:8
      14:21:04,100 WARN [HandlerWrapper] RuntimeException in handler method, transiti
      on to DOES_NOT_EXIST
      14:21:04,100 ERROR [HandlerChainBaseImpl] RuntimeException in request handler
       at org.jbpm.bpel.integration.server.SoapHandler.sendRequest(SoapHandler.
       at org.jbpm.bpel.integration.server.SoapHandler.handleRequest(SoapHandle
       at org.jboss.ws.core.jaxrpc.handler.HandlerWrapper.handleRequest(Handler
       at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleRequestIn
      14:21:04,210 WARN [HandlerWrapper] Handler is in state DOES_NOT_EXIST, skipping
       Handler.handleFault for: org.jbpm.bpel.integration.server.SoapHandler@d60cd6

      My partnerLink names were not matching. But now they do. so under what other circumstances the handler throws that exception? Because from the stack trace it is really hard to tell where else the BPEL process is misconfigured :(.

      BTW, in case this is related to http://jira.jboss.com/jira/browse/JBWS-1553

      I am following the workaround suggested by Alex in this thread.


      Thank you,