try assigning the service-ref containing the soap address element directly to the partnerlink and no via the string variable partnerEPR
On Wed, Sep 14, 2016 at 4:38 PM, Jit K <jkf...@gmail.com> wrote: > Hi Sathwik, > > The results of using flag usePeer2Peer are as follows. > > *usePeer2Peer="false" on invoke in deploy.xml* > invoke locally deployed child process - fails (expected) > invoke remotely deployed child process - *fails *(should work as you > said) > > *usePeer2Peer="false" not specified on invoke in deploy.xml* > invoke locally deployed child process - works (expected) > invoke remotely deployed child process - fails (expected) > > I have used the second approach (Simple URL, wrapped in an soap:address > element from http://ode.apache.org/endpoint-references.html) to pass in > the EPR to the partnerlink. > > The error in all the failure cases is same as follows > > 15:12:07,706 WARN [EndpointFactory] Couldnt create any endpoint for > element <?xml version="1.0" encoding="UTF-8"?> > <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref"> > <temporary-simple-type-wrapper xmlns="" xmlns:sref="http://docs.oasis- > open.org/wsbpel/2.0/serviceref"> > <soap:address location="http://server2:8110/ode.1.3.6/processes/ > GetHostNameAddrProcess" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/ > "/> > </temporary-simple-type-wrapper> > </service-ref> > 15:12:07,706 ERROR [BpelRuntimeContextImpl] Couldn't find endpoint for > partner EPR <?xml version="1.0" encoding="UTF-8"?> > <service-ref xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref"> > <temporary-simple-type-wrapper xmlns="" xmlns:sref="http://docs.oasis- > open.org/wsbpel/2.0/serviceref"> > <soap:address location="http://server2:8110/ode.1.3.6/processes/ > GetHostNameAddrProcess" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/ > "/> > </temporary-simple-type-wrapper> > </service-ref> > 15:12:07,706 ERROR [INVOKE] Failure during invoke: UnknownEndpoint > 15:12:07,706 INFO [BpelRuntimeContextImpl] ActivityRecovery: Registering > activity 13, failure reason: UnknownEndpoint on channel 22 > > Attaching the updated Main and Child Process packages. > > Regards, > JK > > >