Uploaded image for project: 'RiftSaw'
  1. RiftSaw
  2. RIFTSAW-331

Cannot find port in wsdl exception

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.2.0.CR2
    • Fix Version/s: 2.1.4.Final, 2.2.0.Final
    • Component/s: Integration
    • Labels:
      None
    • Environment:

      JBoss-AS-5.1.0.GA-jdk6, jbossws-native-3.2.2.GA, Mac OSX, Mac's java version "1.6.0_22"

    • Steps to Reproduce:
      Hide

      By using dynpartner quickstart, deploy it into RiftSaw Server, it will have following exception:

      DEPLOYMENTS IN ERROR:
      Deployment "vfsfile:/Users/jeffyu/deploy/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-d7b62e76-d59a-44c0-a01e-e2ccc74a9e9b.war/" is in error due to the following reason(s): org.jboss.ws.WSException: Cannot find port in wsdl:

      {http://ode/bpel/responder.wsdl}

      DynResponderPort

      at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
      at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
      at org.jboss.deployers.plugins.main.MainDeployerImpl.deploy(MainDeployerImpl.java:565)
      at org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint(EndpointManager.java:187)
      ... 12 more
      12:01:10,901 ERROR [RiftSawProcessStore] Unknown error
      org.apache.ode.bpel.iapi.ContextException: Failed to activate endpoint
      at org.jboss.soa.bpel.runtime.engine.ode.JAXWSBindingContext.activateMyRoleEndpoint(JAXWSBindingContext.java:97)
      at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:619)
      at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:348)
      at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:321)
      at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.handleEvent(BPELEngineImpl.java:622)
      at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.access$100(BPELEngineImpl.java:61)
      at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl$ProcessStoreListenerImpl.onProcessStoreEvent(BPELEngineImpl.java:684)
      at org.apache.ode.store.ProcessStoreImpl.fireEvent(ProcessStoreImpl.java:665)
      at org.apache.ode.store.ProcessStoreImpl.fireStateChange(ProcessStoreImpl.java:671)
      at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:318)
      at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.doDeploy(RiftSawProcessStore.java:178)
      at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.run(RiftSawProcessStore.java:105)
      Caused by: org.jboss.soa.bpel.runtime.ws.EndpointManagementException: Failed to create endpoint
      at org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint(EndpointManager.java:207)
      at org.jboss.soa.bpel.runtime.engine.ode.JAXWSBindingContext.activateMyRoleEndpoint(JAXWSBindingContext.java:92)
      ... 11 more
      Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

      Show
      By using dynpartner quickstart, deploy it into RiftSaw Server, it will have following exception: DEPLOYMENTS IN ERROR: Deployment "vfsfile:/Users/jeffyu/deploy/jboss-5.1.0.GA/server/default/tmp/riftsaw/riftsaw-d7b62e76-d59a-44c0-a01e-e2ccc74a9e9b.war/" is in error due to the following reason(s): org.jboss.ws.WSException: Cannot find port in wsdl: {http://ode/bpel/responder.wsdl} DynResponderPort at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939) at org.jboss.deployers.plugins.main.MainDeployerImpl.deploy(MainDeployerImpl.java:565) at org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint(EndpointManager.java:187) ... 12 more 12:01:10,901 ERROR [RiftSawProcessStore] Unknown error org.apache.ode.bpel.iapi.ContextException: Failed to activate endpoint at org.jboss.soa.bpel.runtime.engine.ode.JAXWSBindingContext.activateMyRoleEndpoint(JAXWSBindingContext.java:97) at org.apache.ode.bpel.engine.BpelProcess.activate(BpelProcess.java:619) at org.apache.ode.bpel.engine.BpelEngineImpl.registerProcess(BpelEngineImpl.java:348) at org.apache.ode.bpel.engine.BpelServerImpl.register(BpelServerImpl.java:321) at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.handleEvent(BPELEngineImpl.java:622) at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl.access$100(BPELEngineImpl.java:61) at org.jboss.soa.bpel.runtime.engine.ode.BPELEngineImpl$ProcessStoreListenerImpl.onProcessStoreEvent(BPELEngineImpl.java:684) at org.apache.ode.store.ProcessStoreImpl.fireEvent(ProcessStoreImpl.java:665) at org.apache.ode.store.ProcessStoreImpl.fireStateChange(ProcessStoreImpl.java:671) at org.apache.ode.store.ProcessStoreImpl.deploy(ProcessStoreImpl.java:318) at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.doDeploy(RiftSawProcessStore.java:178) at org.apache.ode.store.RiftSawProcessStore$DeployScheduler.run(RiftSawProcessStore.java:105) Caused by: org.jboss.soa.bpel.runtime.ws.EndpointManagementException: Failed to create endpoint at org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint(EndpointManager.java:207) at org.jboss.soa.bpel.runtime.engine.ode.JAXWSBindingContext.activateMyRoleEndpoint(JAXWSBindingContext.java:92) ... 11 more Caused by: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

      Gliffy Diagrams

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jeff.yuchang Jeff Yu
                Reporter:
                jeff.yuchang Jeff Yu
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: