Is your second service being called?
Did you check the HTTP transport logs?


On Fri, Aug 1, 2008 at 8:17 AM, NGUYEN Cong Kinh <
[EMAIL PROTECTED]> wrote:

> Hi,
>
> Thank for your attention. But, in my service, I use as following:
>
> public String sayBPEL(String input){
>    return "BPEL: " + input;
> }
>
> public String alarm(String input){
>   return "Coucou " + input;
> }
>
> Which means that the service is really simple. The problem here is my BPEL
> (two these services) runs well with an same input. But, when using two
> inputs, there is an error. Could you test my example to give me some exact
> advices ?
>
> Really, there are some changes in two programs BPEL.
>
> 1. HelloWorld1
>
> in the file BPEL:
>
>            <bpws:copy>
>                <bpws:from part="payload" variable="input"
> query="/payload/input"/>
>                <bpws:to part="parameters" variable="coucouLinkRequest"/>
>            </bpws:copy>
>
> in the file wsdl:
>
>            <element name="HelloWorldRequest">
>                <complexType>
>                    <sequence>
>                        <element name="input" type="string"/>
>                    </sequence>
>                </complexType>
>            </element>
>
>
> 2. HelloWorld2:
>
> in the file BPEL:
>
>            <bpws:copy>
>                <bpws:from part="payload" variable="input"
> query="/payload/input2"/>
>                <bpws:to part="parameters" variable="coucouLinkRequest"/>
>            </bpws:copy>
>
> in the file wsdl:
>
>            <element name="HelloWorldRequest">
>                <complexType>
>                    <sequence>
>                        <element name="input" type="string"/>
>                        <element name="input2" type="string"/>
>                    </sequence>
>                </complexType>
>            </element>
>
> The other is same in two programs BPEL.
>
> Regards,
> Kinh
>
> > Hi,
> >
> > Looks like your 2nd service call times out;  is your 2nd service sending
> a
> > response?
> >
> > Try setting the "httpclient" log category to DEBUG and analyze the
> > XML/HTTP
> > messages exchanges between Ode and your services.
> >
> > alex
> >
> >
> > On Fri, Aug 1, 2008 at 3:27 AM, NGUYEN Cong Kinh <
> > [EMAIL PROTECTED]> wrote:
> >
> >> Hello everybody,
> >>
> >> I using apache-ode 1.2. Could you help me to solve my problem ?
> >>
> >> The archive of web service is given at
> >> http://www.tsi.enst.fr/~nguyen/TestWsBpel.war<http://www.tsi.enst.fr/%7Enguyen/TestWsBpel.war>
> <http://www.tsi.enst.fr/%7Enguyen/TestWsBpel.war>
> >>
> >> In my BPEL program, there are two called services (each service with an
> >> input). When I use a same input (same input value) to two services (the
> >> BPEL at
> >> http://www.tsi.enst.fr/~nguyen/HelloWorld1.zip<http://www.tsi.enst.fr/%7Enguyen/HelloWorld1.zip>
> <http://www.tsi.enst.fr/%7Enguyen/HelloWorld1.zip>),
> >> it runs well.
> >> But, when using two different inputs (the BPEL at
> >> http://www.tsi.enst.fr/~nguyen/HelloWorld2.zip<http://www.tsi.enst.fr/%7Enguyen/HelloWorld2.zip>
> <http://www.tsi.enst.fr/%7Enguyen/HelloWorld2.zip>),
> >> there is an error :
> >>
> >> DEBUG - GeronimoLog.debug(66) | Triggering response
> >> ERROR - GeronimoLog.error(104) | Failure during invoke:
> >> INFO - GeronimoLog.info(79) | ActivityRecovery: Registering activity 11,
> >> failure
> >>  reason:  on channel 21
> >> DEBUG - GeronimoLog.debug(66) | Setting execution state on instance
> >> 43051
> >> DEBUG - GeronimoLog.debug(66) | Thread[ODEServer-2,5,main]:
> >> unlock(iid=43051)
> >> ERROR - GeronimoLog.error(104) | Timeout or execution error when waiting
> >> for res
> >> ponse to MEX {MyRoleMex#hqejbhcnphr3h7ke4elnv4 [Client
> >> hqejbhcnphr3h7ke4elnv3] c
> >> alling
> >> {http://eclipse.org/bpel/sample}HelloWorldService.process(...)<http://eclipse.org/bpel/sample%7DHelloWorldService.process%28...%29>
> <http://eclipse.org/bpel/sample%7DHelloWorldService.process%28...%29>
> >> }
> >> java.util
> >> .concurrent.TimeoutException: Message exchange
> >> org.apache.ode.bpel.engine.MyRole
> >> [EMAIL PROTECTED] timed out when waiting for a
> >> response!
> >>
> >> Regards,
> >>
> >> --
> >> NGUYEN Cong Kinh
> >>
> >>
> >
>
>
> --
> NGUYEN Cong Kinh
>
>

Reply via email to