Hi Ajith,
The scenario which you have tested is not correct. If you put
mediator in the outSequence, since you are cloning the request and send to
2 back ends, ESB will get 2 responses and tries to send back 2 responses to
client and that is causing this exception. What happens is that ESB will
Hi Ajith,
I have already added a fix to the NPE and currently testing that. Just
wanted to let you know that this is happening due to a configuration issue.
The code was written assuming that this NPE cannot occur in proper
configurations. But there can be some edge cases where this can become
On Tue, Oct 6, 2015 at 9:31 AM, Chanaka Fernando wrote:
> Hi Ajith,
>
> I have already added a fix to the NPE and currently testing that. Just
> wanted to let you know that this is happening due to a configuration issue.
> The code was written assuming that this NPE cannot
On Tue, Oct 6, 2015 at 5:06 AM, Chanaka Fernando wrote:
> Hi Ajith,
>
> The scenario which you have tested is not correct. If you put
> mediator in the outSequence, since you are cloning the request and send to
> 2 back ends, ESB will get 2 responses and tries to send back 2
Hi Ajith,
We have already identified this issue and currently working on a fix.
Thanks for reporting this issue.
On Mon, Oct 5, 2015 at 12:56 AM, Ajith Vitharana wrote:
> Hi All
>
> I did a slight change to sample [1] (used instead of at
> the outSequence) , now I'm getting
On Mon, Oct 5, 2015 at 5:59 AM, Chanaka Fernando wrote:
> Hi Ajith,
>
> We have already identified this issue and currently working on a fix.
> Thanks for reporting this issue.
>
Thanks for looking to this.
-Ajith
>
> On Mon, Oct 5, 2015 at 12:56 AM, Ajith Vitharana
Hi All
I did a slight change to sample [1] (used instead of at the
outSequence) , now I'm getting following exception.
[1] https://docs.wso2.com/display/IntegrationPatterns/Durable+Subscriber
[2015-10-04 15:19:30,891] DEBUG - wire << "[\r][\n]"
[2015-10-04 15:19:30,892] ERROR -