Re: [Dev] [ESB] Issue in Load Balanced Endpoint when one end point is unavailable

2014-10-29 Thread Dilini Muthumala
Hi,
This is to inform that I've created a Jira -
https://wso2.org/jira/browse/ESBJAVA-3407

Thanks,
Dilini

On Tue, Oct 28, 2014 at 9:17 PM, Dilini Muthumala  wrote:

> Correction:
>
> On Tue, Oct 28, 2014 at 8:12 PM, Dilini Muthumala  wrote:
>>
>> When (at least) one endpoint is unavailable I noticed that the log
>> mediator in the api doesn't get executed (generally, what ever given after
>> the send mediator doesn't get executed).
>>
>
> This happens only when it's "the unavailable endpoint" 's turn to serve
> the request.
> For example, let's say endpoint_0_1 is unavailable. log mediator doesn't
> get executed when  it's endpoint_0_1's turn (according to LB algorithm) to
> serve the request.
>
>
>>
>> I used ESB 4.8.1.
>> Just want to know if this is a known issue or I have missed something
>> when configuring; I will create a Jira if not.
>>
>> Thanks,
>> Dilini
>>
>> --
>> *Dilini Muthumala*
>> Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail :* dil...@wso2.com
>> *Mobile: *+94713 400 029
>>
>
>
>
> --
> *Dilini Muthumala*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail :* dil...@wso2.com
> *Mobile: *+94713 400 029
>



-- 
*Dilini Muthumala*
Software Engineer,
WSO2 Inc.

*E-mail :* dil...@wso2.com
*Mobile: *+94713 400 029
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [ESB] Issue in Load Balanced Endpoint when one end point is unavailable

2014-10-28 Thread Dilini Muthumala
Correction:

On Tue, Oct 28, 2014 at 8:12 PM, Dilini Muthumala  wrote:
>
> When (at least) one endpoint is unavailable I noticed that the log
> mediator in the api doesn't get executed (generally, what ever given after
> the send mediator doesn't get executed).
>

This happens only when it's "the unavailable endpoint" 's turn to serve the
request.
For example, let's say endpoint_0_1 is unavailable. log mediator doesn't
get executed when  it's endpoint_0_1's turn (according to LB algorithm) to
serve the request.


>
> I used ESB 4.8.1.
> Just want to know if this is a known issue or I have missed something when
> configuring; I will create a Jira if not.
>
> Thanks,
> Dilini
>
> --
> *Dilini Muthumala*
> Software Engineer,
> WSO2 Inc.
>
> *E-mail :* dil...@wso2.com
> *Mobile: *+94713 400 029
>



-- 
*Dilini Muthumala*
Software Engineer,
WSO2 Inc.

*E-mail :* dil...@wso2.com
*Mobile: *+94713 400 029
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [ESB] Issue in Load Balanced Endpoint when one end point is unavailable

2014-10-28 Thread Dilini Muthumala
Hi,

I created an API with a load-balanced endpoint (*endpoint_0*). Configuration
attached as LBApi.xml.

http://ws.apache.org/ns/synapse"; name="LBApi" context="/LBApi">
   
  
 

 
 http://ws.apache.org/ns/synapse"/>
  
  
 
  
   


Let's say *endpoint_0* consist of three endpoints and the load is balanced
among those three endpoints. Configuration of endpoint_0 is attached as
endpoint_0.xml.

When (at least) one endpoint is unavailable I noticed that the log mediator
in the api doesn't get executed (generally, what ever given after the send
mediator doesn't get executed).

I used ESB 4.8.1.
Just want to know if this is a known issue or I have missed something when
configuring; I will create a Jira if not.

Thanks,
Dilini

-- 
*Dilini Muthumala*
Software Engineer,
WSO2 Inc.

*E-mail :* dil...@wso2.com
*Mobile: *+94713 400 029

http://ws.apache.org/ns/synapse"; name="LBApi" context="/LBApi">
   
  
 

 
 http://ws.apache.org/ns/synapse"/>
  
  
 
  
   


http://ws.apache.org/ns/synapse"; name="endpoint_0">
   
  
 http://10.100.5.59:9773/services/HelloService/"/>
 http://10.100.5.59:9773/services/HelloService/"/>
  
  
 http://10.100.5.59:9774/services/HelloService/"/>
 http://10.100.5.59:9774/services/HelloService/"/>
  
  
 http://10.100.5.59:9775/services/HelloService/"/>
 http://10.100.5.59:9775/services/HelloService/"/>
  
   

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev