Hi,

yes, if your process is long running consider using a receive-invoke pair
instead of a receive-reply pair. The partner role of the partnerlink can be
statically initialized, when the callback service has a static URL. You may
also use parts of ODEs dynamic partnerlink feature, which requires a
callback EPR sent with the initial request. However, if I'm not mistaken,
this feature was slightly broken recently but Sathwik provided a fix.
Please get back to us if this is a feature you need.

HTH,
  Tammo

On Mon, Jul 20, 2015 at 5:05 PM, MyGmail <sudarshand...@gmail.com> wrote:

> Hi,
>
> Thanks for your quick response, I got the link yesterday while reading
> through ode docs and it property settings.
>
> Webservice response times are good, it's in ms. But we do have wait
> (20-30s) with max 3-5 retrys at extreme case. Do you suggest different
> approach in such cases??
>
> Sent from my iPhone
>
> > On Jul 20, 2015, at 4:41 AM, Tammo van Lessen <tvanles...@gmail.com>
> wrote:
> >
> > To emphasize Sathwiks question: Having long-running request-response
> > operations is a common anti-pattern. It is not only error-prone, it also
> > consumes a lot of resources and kills scalability. This is also why BPEL
> > has concepts for asynchronous messaging with correlation, this is the way
> > to go for operations that last longer than a (small) couple of seconds...
> >
> > Best,
> >  Tammo
> >
> >> On Mon, Jul 20, 2015 at 9:47 AM, Sathwik B P <sathwik...@gmail.com>
> wrote:
> >>
> >> Have a look at
> >> http://ode.apache.org/endpoint-configuration.html
> >> mex.timeout is the parameter.
> >>
> >> I don't understand your business case. Why would you want to have a
> wait of
> >> more than 120Seconds for a Request-Reponse MEP  process?
> >>
> >> On Mon, Jul 20, 2015 at 3:18 AM, Bhanu Sudarshan <
> sudarshand...@gmail.com>
> >> wrote:
> >>
> >>> Hi All,
> >>>
> >>> I need a new help with Apache ODE,
> >>>
> >>> I created a simple bpel flow with string input and string output with
> >>> assign value of fixed string to an output. Before the reply message i
> >> added
> >>> a wait of 120 sec. which throws up an mex timeout exception.
> >>>
> >>> The following is soapui error:
> >>>
> >>> ode:Fault
> >>> Timeout or execution error when waiting for response to MEX
> >> (MyRoleMesx……)
> >>> …….. java.util.concurrent,TimeoutException: Message exchange
> >>> org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture
> >>> timeout (120000 ms) when waiting for a response.
> >>>
> >>> Can you please help me out in increasing the timeout or resolve the
> >> issue.
> >>>
> >>>
> >>>
> >>>> On May 25, 2015, at 1:29 AM, Sathwik B P <sathwik...@gmail.com>
> wrote:
> >>>>
> >>>> I suppose you are invoking an external web service developed through
> >> CXF
> >>>> from ODE.
> >>>>
> >>>> There is no restrictions from ODE for invoking external web services
> >>>> developed under any web service frameworks.
> >>>>
> >>>> Check you request generation.
> >>>>
> >>>> regards,
> >>>> sathwik
> >>>>
> >>>> On Sat, May 23, 2015 at 10:14 PM, Bhanu Sudarshan <
> >>> sudarshand...@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> I am getting weird exception on soap request, not valid while
> invoking
> >>> my
> >>>>> service through ODE.
> >>>>>
> >>>>> <?xml version=“1.0” encoding=‘utf-8’?> <soap:Envelope xmlns:soap=“
> >>>>> http://schemas.xmlsoap.org/soap/envelope/“>
> >>>>> <soap:Body><soap:Fault><faultcode>
> >> Error:cvc-complex-type.2.4.a:Invalid
> >>>>> content was found starting with element ‘’Netbackuprequest”. One of
> >>>>> ‘{Netbackuprequest}’ is expected.
> >>>>> </faultstring></soap:Fault></soap:Body></soap:Envelope>
> >>>>>
> >>>>> Can you please guide me, Is APACHE ODE compatible to invoke cxc web
> >>>>> service, or its limited to axis2? or the default initialization code
> >> for
> >>>>> soap request generated through eclipse bpel web designed is wrong.
> >> Then
> >>>>> what’s the right way.
> >>>>>
> >>>>> Your help is greatly appreciated. I need a response asap for my
> >> project
> >>>>> work.
> >>>>>
> >>>>> Regards,
> >>>>> BHANU
> >
> >
> >
> > --
> > Tammo van Lessen - http://www.taval.de
>



-- 
Tammo van Lessen - http://www.taval.de

Reply via email to