Hi Nandika,

Yes, if we add a send mediator with an endpoint to the out sequence, we
could see this behavior. But AFAIU, to allow adding send mediator with an
endpoint to the out sequence is wrong.
Because AFAIU we do not have any valid use case the send mediator might use
in the out sequence as we mentioned.

Thanks,
/Susankha.

On Fri, Aug 4, 2017 at 5:04 PM, Vinod Kavinda <vi...@wso2.com> wrote:

> Hi Senuwan,
> As a solution, Please use a Call mediator in place of the send mediator in
> the outSequece.
>
> Regards,
> Vinod
>
>
> On Fri, Aug 4, 2017 at 4:55 PM, Nandika Jayawardana <nand...@wso2.com>
> wrote:
>
>> This is the expected behavior. In in sequence, the request is sent to the
>> endpoint and response returns to the out sequence. When the message is sent
>> from out sequence, the response returns to the out sequence, resulting in
>> the loop.
>>
>> Regards
>> Nandika
>>
>> On Fri, Aug 4, 2017 at 12:20 PM, Senuwan Withana <senu...@wso2.com>
>> wrote:
>>
>>>
>>> *Scenario *
>>> I have created below proxy and added address endpoint URL.However by
>>> mistakenly I have added same endpoint URL to the 'Out Sequence'. After that
>>> I have send one SOAP request. in back-end recursively request going on.
>>>
>>>
>>> *Please refer XML file   [WSO2-ESB 4.9.0]*
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <proxy xmlns="http://ws.apache.org/ns/synapse";
>>>        name="tenone"
>>>        transports="http,https"
>>>        statistics="disable"
>>>        trace="disable"
>>>        startOnLoad="true">
>>>    <target>
>>>       <inSequence>
>>>          <log/>
>>>          <send>
>>>             <endpoint>
>>>                <address uri="http://www.mocky.io/v2/59
>>> 84075e110000b601416671"/>
>>>             </endpoint>
>>>          </send>
>>>       </inSequence>
>>>       <outSequence>
>>>          <send>
>>>             <endpoint>
>>>                <address uri="http://www.mocky.io/v2/59
>>> 84075e110000b601416671"/>
>>>             </endpoint>
>>>          </send>
>>>       </outSequence>
>>>    </target>
>>>    <description/>
>>> </proxy>
>>>
>>>
>>>
>>> *Carbon Log file is attached *
>>>
>>> As per my understand this might not be the expected behaviour and what
>>> we would able to do this.
>>>
>>>
>>> *Senuwan Withana*
>>> Software Engineer - Support Team | WSO2
>>>
>>> Email : senu...@wso2.com
>>> Mobile: 94773212853 <077%20321%202853>
>>> Web: http://www.wso2.com
>>>
>>>
>>>
>>
>>
>> --
>> Nandika Jayawardana
>> WSO2 Inc ; http://wso2.com
>> lean.enterprise.middleware
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vinod Kavinda
> Senior Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware <http://www.wso2.com>.*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
> [image: http://wso2.com/signature]
> <http://wso2.com/signature>
>
>
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Susankha Nirmala
Senior Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware

Mobile : +94 77 593 2146
blog : https://susankhanirmala.wordpress.com/
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to