Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-4259

ServiceTaskHandler logs error messages for web service namespace/servicename attempts

    Details

      Description

      If you use ServiceTask for web services with multiple WSDL imports and those imports have different namespaces, ServiceTaskHandler attempts to create a WS client with combinations of namespaces and a servicename until it gets the correct combination.

      https://github.com/droolsjbpm/jbpm/blob/master/jbpm-workitems/src/main/java/org/jbpm/process/workitem/bpmn2/ServiceTaskHandler.java#L193-L212

      The logic is okay as the ServiceTask doesn't know the expected namespace as per BPMN2 spec. But during the attempts, you may see ERROR logs like this:

      26/08/2016 21:34:33,661 ERROR [org.jbpm.process.workitem.bpmn2.ServiceTaskHandler] (http-10.170.49.231:8443-1) Error when creating WS Client: org.apache.cxf.service.factory.ServiceConstructionException: Could not find definition for service {urn:com.example.service:1.0}MyService.
              at org.apache.cxf.wsdl11.WSDLServiceFactory.create(WSDLServiceFactory.java:171) [cxf-rt-core-2.7.18.redhat-1.jar:2.7.18.redhat-1]
              at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:298) [cxf-rt-databinding-jaxb-2.7.18.redhat-1.jar:2.7.18.redhat-1]
              at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:240) [cxf-rt-databinding-jaxb-2.7.18.redhat-1.jar:2.7.18.redhat-1]
              at org.jbpm.process.workitem.bpmn2.ServiceTaskHandler.getWSClient(ServiceTaskHandler.java:200) [jbpm-workitems-6.4.0.Final-redhat-3.jar:6.4.0.Final-redhat-3]
              at org.jbpm.process.workitem.bpmn2.ServiceTaskHandler.executeWorkItem(ServiceTaskHandler.java:99) [jbpm-workitems-6.4.0.Final-redhat-3.jar:6.4.0.Final-redhat-3]
              at org.drools.persistence.jpa.processinstance.JPAWorkItemManager.internalExecuteWorkItem(JPAWorkItemManager.java:69) [drools-persistence-jpa-6.4.0.Final-redhat-3.jar:6.4.0.Final-redhat-3]
              at org.jbpm.workflow.instance.node.WorkItemNodeInstance.internalTrigger(WorkItemNodeInstance.java:138) [jbpm-flow-6.4.0.Final-redhat-3.jar:6.4.0.Final-redhat-3]
              at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:173) [jbpm-flow-6.4.0.Final-redhat-3.jar:6.4.0.Final-redhat-3]
              at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:366) [jbpm-flow-6.4.0.Final-redhat-3.jar:6.4.0.Final-redhat-3]
      ...
      

      As long as a client is eventually created, you can ignore the ERROR. So better to lower the log level.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                swiderski.maciej Maciej Swiderski
                Reporter:
                tkobayashi Toshiya Kobayashi
                Tester:
                Tomáš Livora
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: