-
1. Re: Error invoking a BPEL process which calls a web service
zhylninc Jun 27, 2013 5:43 AM (in response to zhylninc)logs
16:45:23,455 ERROR [org.switchyard.component.bpel.riftsaw.RiftsawServiceLocator] (ODEServer-1) No service references found for process '{http://www.jboss.org/bpel/examples}SayHello'
16:45:23,475 ERROR [org.apache.ode.bpel.engine.BpelRuntimeContextImpl] (ODEServer-1) Partner did not acknowledge message exchange: {PartnerRoleMex#hqejbhcnphr8e88nhfr1pf [PID {http://www.jboss.org/bpel/examples}SayHello-0] calling null.submitOrder(...) Status REQUEST}
16:45:23,499 ERROR [org.apache.ode.bpel.runtime.INVOKE] (ODEServer-1) Failure during invoke: Partner did not acknowledge.
16:45:23,523 INFO [org.apache.ode.bpel.engine.BpelRuntimeContextImpl] (ODEServer-1) ActivityRecovery: Registering activity 15, failure reason: Partner did not acknowledge. on channel 25
-
2. Re: Error invoking a BPEL process which calls a web service
objectiser Jun 27, 2013 6:09 AM (in response to zhylninc)Hi Mark
Can you provide the switchyard app archive that you are trying to run, and any test message you are sending.
The problem is that the BPEL process is attempting to locate a service with QName '{http://www.jboss.org/bpel/examples}SayHello', however according to your deploy.xml, the service it should be invoking is '{
urn:switchyard-quickstart:bean-service:1.0}
OrderService'.
Regards
Gary
-
4. Re: Error invoking a BPEL process which calls a web service
objectiser Jun 28, 2013 9:09 AM (in response to zhylninc)The problem where port type and service are defined in separate wsdls has not been resolved - a jira has just been created to track this: https://issues.jboss.org/browse/SWITCHYARD-1566