Re: [Dev] Custom UserStore works on 5.1.0, 5.2.0 not working in 5.3.0 and 5.4.0-M1

[Johann Nallathamby]

On Tue, Jul 4, 2017 at 9:59 AM, Hasintha Indrajee  wrote:

> We will be maintaining user store property to indicate whether the user
> store supports claim operations (There may be multiple operation types, but
> in this case claim operations). Before setting claims in pre and post
> authentication listeners we will check whether the underlying user store is
> supported for claim operations and will only continue if it's supported.
> Unless returns and continues the flow.
>

+1. I think this may be the best way as of now.


>
> There were few options discussed
>
> 1) We can just turn off these event handlers which get fired on
> authentication events. But we may only need to skip a specific user store
> and we may still need to use identity management functionality with rest of
> the user stores. In this case we have to introduce a user tore level
> property/configuration.
>
> 2) One of the other options is to expect a predefined run time exception
> from the methods which are not implemented in User Store Manager  level and
> handle them at our event handlers so that it will not have an effect on the
> rest of the flow since we handle the run time exception. We thought of not
> going with this since altering logic and taking decisions based on the type
> of exception and error messages is not a good practice.
>
>
> 3) Another possibility was to introduce above check (checking newly
> introduced user store property and skipping) at the
> IdentityMgtEventListener level so that none of the handlers will be fired
> if the user store is not supported for that particular operation. This is
> not a proper fix since we may still need to get events to event handler
> level even if the user store is not supported certain operations. eg - Even
> though the user store is not supported for claim operations the deployment
> may be using JDBC based Identity Store. In that we don't need handlers to
> be skipped.
>
> Hence the best option seems to be handling the behaviour based on newly
> introduced property at specific concrete handler level. Depending on the
> logic of specific handler it will decide whether to handle this event or
> skip and continue.
>
> On Tue, Jul 4, 2017 at 9:35 AM, Sagara Gunathunga  wrote:
>
>>
>> Hasintha, could you please update the thread with the solution we agreed
>> ?
>>
>>
>> Thanks !
>>
>> On Wed, Jun 21, 2017 at 1:01 PM, Isura Karunaratne 
>> wrote:
>>
>>> Hi
>>>
>>> On Wed, Jun 21, 2017 at 11:06 AM, Farasath Ahamed 
>>> wrote:
>>>




 On Wed, Jun 21, 2017 at 11:03 AM, Isura Karunaratne 
 wrote:

>
>
> On Tue, Jun 20, 2017 at 11:29 PM, Johann Nallathamby 
> wrote:
>
>> If these two handlers are disabled by default there shouldn't be any
>> problem. According to default identity-event.properties file they are
>> disabled. How come they get triggered then?
>>
>
> Yes. By default the account lock/disabled features are disabled. If it
> is required to use account lock/disable features, there should be a way to
> store user properties.
>

 Looks like we haven't used the property to check whether the listener
 is enabled or disabled although we have defined in
 identity-event.properties. Therefore the handlers get fired on
 pre-authentications

>>>
>>> Yes. This issue is fixed with https://wso2.org/jira/browse/IDENTITY-6091
>>>
>>> Thanks
>>> Isura.
>>>


>
> Also, if the um_user_attribute table is not there, most of the use
> cases will be broken. (Add User/ Update User/ Get  Users ...). So, I think
> that user store is incomplete.
>
> Thanks
> Isura.
>
>
>>
>> On Tue, Jun 20, 2017 at 7:25 PM, Farasath Ahamed 
>> wrote:
>>
>>> Hi,
>>>
>>> The minimum requirement to write a custom JDBC user store manager so
>>> far (before IS 5.3.0) was to simply override the doAuthenticate() 
>>> method.
>>> So a custom user store that was written for 5.0.0 worked without any
>>> modifications (may be dependency changes).
>>>
>>> But when we use the same code on IS 5.3.0, the custom user store
>>> implementations that only override the doAuthenticate() are broken 
>>> because
>>> account disabled[1] and account locked[2] handlers introduced in IS 
>>> 5.3.0.
>>>
>>> These two handlers call the getUserClaimValues() method of the
>>> userstore to retrieve some claims. Since we haven't overridden the 
>>> method
>>> in custom userstore implementation it calls the super class. This leads 
>>> to
>>> trying to find the claims from a non-existing table[3].
>>>
>>> One way to solve is to override the getUserClaimValues() method. But
>>> in the PoV of the extension developer, this would be an unnecessary 
>>> step if
>>> the 

Re: [Dev] Custom UserStore works on 5.1.0, 5.2.0 not working in 5.3.0 and 5.4.0-M1

[Hasintha Indrajee]

We will be maintaining user store property to indicate whether the user
store supports claim operations (There may be multiple operation types, but
in this case claim operations). Before setting claims in pre and post
authentication listeners we will check whether the underlying user store is
supported for claim operations and will only continue if it's supported.
Unless returns and continues the flow.

There were few options discussed

1) We can just turn off these event handlers which get fired on
authentication events. But we may only need to skip a specific user store
and we may still need to use identity management functionality with rest of
the user stores. In this case we have to introduce a user tore level
property/configuration.

2) One of the other options is to expect a predefined run time exception
from the methods which are not implemented in User Store Manager  level and
handle them at our event handlers so that it will not have an effect on the
rest of the flow since we handle the run time exception. We thought of not
going with this since altering logic and taking decisions based on the type
of exception and error messages is not a good practice.


3) Another possibility was to introduce above check (checking newly
introduced user store property and skipping) at the
IdentityMgtEventListener level so that none of the handlers will be fired
if the user store is not supported for that particular operation. This is
not a proper fix since we may still need to get events to event handler
level even if the user store is not supported certain operations. eg - Even
though the user store is not supported for claim operations the deployment
may be using JDBC based Identity Store. In that we don't need handlers to
be skipped.

Hence the best option seems to be handling the behaviour based on newly
introduced property at specific concrete handler level. Depending on the
logic of specific handler it will decide whether to handle this event or
skip and continue.

On Tue, Jul 4, 2017 at 9:35 AM, Sagara Gunathunga  wrote:

>
> Hasintha, could you please update the thread with the solution we agreed ?
>
>
>
> Thanks !
>
> On Wed, Jun 21, 2017 at 1:01 PM, Isura Karunaratne  wrote:
>
>> Hi
>>
>> On Wed, Jun 21, 2017 at 11:06 AM, Farasath Ahamed 
>> wrote:
>>
>>>
>>>
>>>
>>>
>>> On Wed, Jun 21, 2017 at 11:03 AM, Isura Karunaratne 
>>> wrote:
>>>


 On Tue, Jun 20, 2017 at 11:29 PM, Johann Nallathamby 
 wrote:

> If these two handlers are disabled by default there shouldn't be any
> problem. According to default identity-event.properties file they are
> disabled. How come they get triggered then?
>

 Yes. By default the account lock/disabled features are disabled. If it
 is required to use account lock/disable features, there should be a way to
 store user properties.

>>>
>>> Looks like we haven't used the property to check whether the listener is
>>> enabled or disabled although we have defined in
>>> identity-event.properties. Therefore the handlers get fired on
>>> pre-authentications
>>>
>>
>> Yes. This issue is fixed with https://wso2.org/jira/browse/IDENTITY-6091
>>
>> Thanks
>> Isura.
>>
>>>
>>>

 Also, if the um_user_attribute table is not there, most of the use
 cases will be broken. (Add User/ Update User/ Get  Users ...). So, I think
 that user store is incomplete.

 Thanks
 Isura.


>
> On Tue, Jun 20, 2017 at 7:25 PM, Farasath Ahamed 
> wrote:
>
>> Hi,
>>
>> The minimum requirement to write a custom JDBC user store manager so
>> far (before IS 5.3.0) was to simply override the doAuthenticate() method.
>> So a custom user store that was written for 5.0.0 worked without any
>> modifications (may be dependency changes).
>>
>> But when we use the same code on IS 5.3.0, the custom user store
>> implementations that only override the doAuthenticate() are broken 
>> because
>> account disabled[1] and account locked[2] handlers introduced in IS 
>> 5.3.0.
>>
>> These two handlers call the getUserClaimValues() method of the
>> userstore to retrieve some claims. Since we haven't overridden the method
>> in custom userstore implementation it calls the super class. This leads 
>> to
>> trying to find the claims from a non-existing table[3].
>>
>> One way to solve is to override the getUserClaimValues() method. But
>> in the PoV of the extension developer, this would be an unnecessary step 
>> if
>> the custom user store is just used for authentication only as explained 
>> in
>> [4].
>>
>> Even in the official docs[5], we do not have any mention of having to
>> implement the getUserClaimValues() method.
>>
>> What would be the correct and the most efficient way to resolve this?

Re: [Dev] Custom UserStore works on 5.1.0, 5.2.0 not working in 5.3.0 and 5.4.0-M1

[Sagara Gunathunga]

Hasintha, could you please update the thread with the solution we agreed ?


Thanks !

On Wed, Jun 21, 2017 at 1:01 PM, Isura Karunaratne  wrote:

> Hi
>
> On Wed, Jun 21, 2017 at 11:06 AM, Farasath Ahamed 
> wrote:
>
>>
>>
>>
>>
>> On Wed, Jun 21, 2017 at 11:03 AM, Isura Karunaratne 
>> wrote:
>>
>>>
>>>
>>> On Tue, Jun 20, 2017 at 11:29 PM, Johann Nallathamby 
>>> wrote:
>>>
 If these two handlers are disabled by default there shouldn't be any
 problem. According to default identity-event.properties file they are
 disabled. How come they get triggered then?

>>>
>>> Yes. By default the account lock/disabled features are disabled. If it
>>> is required to use account lock/disable features, there should be a way to
>>> store user properties.
>>>
>>
>> Looks like we haven't used the property to check whether the listener is
>> enabled or disabled although we have defined in identity-event.properties.
>> Therefore the handlers get fired on pre-authentications
>>
>
> Yes. This issue is fixed with https://wso2.org/jira/browse/IDENTITY-6091
>
> Thanks
> Isura.
>
>>
>>
>>>
>>> Also, if the um_user_attribute table is not there, most of the use cases
>>> will be broken. (Add User/ Update User/ Get  Users ...). So, I think that
>>> user store is incomplete.
>>>
>>> Thanks
>>> Isura.
>>>
>>>

 On Tue, Jun 20, 2017 at 7:25 PM, Farasath Ahamed 
 wrote:

> Hi,
>
> The minimum requirement to write a custom JDBC user store manager so
> far (before IS 5.3.0) was to simply override the doAuthenticate() method.
> So a custom user store that was written for 5.0.0 worked without any
> modifications (may be dependency changes).
>
> But when we use the same code on IS 5.3.0, the custom user store
> implementations that only override the doAuthenticate() are broken because
> account disabled[1] and account locked[2] handlers introduced in IS 5.3.0.
>
> These two handlers call the getUserClaimValues() method of the
> userstore to retrieve some claims. Since we haven't overridden the method
> in custom userstore implementation it calls the super class. This leads to
> trying to find the claims from a non-existing table[3].
>
> One way to solve is to override the getUserClaimValues() method. But
> in the PoV of the extension developer, this would be an unnecessary step 
> if
> the custom user store is just used for authentication only as explained in
> [4].
>
> Even in the official docs[5], we do not have any mention of having to
> implement the getUserClaimValues() method.
>
> What would be the correct and the most efficient way to resolve this?
> Appreciate your thoughts.
>
>
>
> [1] https://github.com/wso2-extensions/identity-event-handle
> r-account-lock/blob/master/components/org.wso2.carbon.identi
> ty.handler.event.account.lock/src/main/java/org/wso2/carbon/
> identity/handler/event/account/lock/AccountDisableHandler.java#L89
>
> [2] https://github.com/wso2-extensions/identity-event-handle
> r-account-lock/blob/master/components/org.wso2.carbon.identi
> ty.handler.event.account.lock/src/main/java/org/wso2/carbon/
> identity/handler/event/account/lock/AccountLockHandler.java#L186
>
> [3] https://wso2.org/jira/browse/IDENTITY-6074?focusedCommen
> tId=134555=com.atlassian.jira.plugin.system.issuetabpan
> els:comment-tabpanel#comment-134555
>
> [4] https://wso2.org/jira/browse/IDENTITY-6074
>
>
>
>
> Thanks,
> Farasath Ahamed
> Software Engineer, WSO2 Inc.; http://wso2.com
> Mobile: +94777603866
> Blog: blog.farazath.com
> Twitter: @farazath619 
> 
>
>
>


 --
 Thanks & Regards,

 *Johann Dilantha Nallathamby*
 Senior Technical Lead - WSO2 Identity Server
 Governance Technologies Team
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - *+9476950*
 Blog - *http://nallaa.wordpress.com *

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


>>>
>>>
>>> --
>>>
>>> *Isura Dilhara Karunaratne*
>>> Senior Software Engineer | WSO2
>>> Email: is...@wso2.com
>>> Mob : +94 772 254 810 <+94%2077%20225%204810>
>>> Blog : http://isurad.blogspot.com/
>>>
>>>
>>>
>>>
>>
>
>
> --
>
> *Isura Dilhara Karunaratne*
> Senior Software Engineer | WSO2
> Email: is...@wso2.com
> Mob : +94 772 254 810 <+94%2077%20225%204810>
> Blog : http://isurad.blogspot.com/
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sagara Gunathunga

Associate Director / Architect; 

Re: [Dev] [GSoC][Siddhi][CEP]: Siddhi Pattern for Absence of Events

[Gobinath]

Hi,
Sure. I will add test cases for each of these cases.


Thanks & Regards,
Gobinath

On Mon, Jul 3, 2017 at 2:23 PM, Sriskandarajah Suhothayan 
wrote:

>
>
> On Mon, Jul 3, 2017 at 5:18 PM, Gobinath  wrote:
>
>> Hi,
>>
>> The following absent event cases are implemented and tested so far and
>> now I am focusing on testing these patterns in the form of *Sequence*.
>> If you find any cases that I missed or any improvements, please share them.
>>
>>
>>
>> A not B for 1sec
>>
>> After the arrival of A, wait for 1 sec & B not arrived
>>
>> A → not B and C
>>
>> When C arrive if B is not available
>>
>> A → (not B and C) within 1sec
>>
>> If B not arrived but C arrived within 1 sec from A
>>
>> A → (not B for 1sec  and C) within 2sec
>>
>> Wait for 1 sec from the arrival of A; if B not arrived and C arrived and
>> both happened within 2 sec from A
>>
>> not A for 1sec → B
>>
>> Wait for 1 sec; if A not arrived but B arrived after 1sec
>>
>> not A and B → C
>>
>> When B arrive if A is not available followed by C
>>
>> every ( not B and  A)  → C
>>
>> Every combination of the previous case
>>
>> every ( not B for 1sec) → C
>>
>> Check and emit C every second, if B not arrive
>>
>> A → not B  for 1 sec and not C for 1 sec
>>
>> After A, both B and C are not received within 1 sec
>>
>> not A  for 1 sec and not B for 1 sec → C
>>
>> A and B are not received for 1 sec and then C
>>
>> A → not B   for 1 sec or not C for 1 sec
>>
>> After A, wait for 1 sec B or C not received
>>
>> not A  for 1 sec or not B for 1 sec → C
>>
>> Wait for 1 sec; A or B not received followed by C
>>
>> A → not B for 1 sec or C
>>
>> After A, if C arrives, emit it otherwise emit after 1 sec if B not arrived
>>
>> not A for 1 sec or B → C
>>
>> Same as previous but the other way around
>>
>> I think these will also work but better if you can check them too via
> testcase.
>
> A → C or not B for 1 sec
>
> B or not A for 1 sec → C
>
> every (not B  for 1 sec and not C for 1 sec ) -> A
>
> every (not B  for 1 sec or not C for 1 sec ) -> A
>
> every (B *and* not C for 1 sec ) -> A
>
> every (not C for 1 sec *and* B ) -> A
>
> every (B *or* not C for 1 sec ) -> A
>
> every (not C for 1 sec *or* B ) -> A
>
> every (B *and* (not C and D) ) -> A
>
> every ( (not C and D) *and* B ) -> A
>
> every (B *or* (not C and D) ) -> A
>
> every ((not C and D) *or* B ) -> A
>
>
>>
>> Thanks & Regards,
>> Gobinath
>>
>> On Sun, Jul 2, 2017 at 6:34 AM, Gobinath  wrote:
>>
>>> Thanks, Suho.
>>>
>>> Sure I will.
>>>
>>>
>>> Thanks & Regards,
>>> Gobinath
>>>
>>> On Sun, Jul 2, 2017 at 6:32 AM, Sriskandarajah Suhothayan >> > wrote:
>>>
 Thanks merged the PR.

 Can you inform in SOF that you have fixed this issue, and this is the
 PR.

 Thanks
 Suho

 On Sun, Jul 2, 2017 at 6:21 AM, Gobinath  wrote:

> Hi,
>
> Please find the PR [1] fixing the following issues in Siddhi.
>
> 1. Logical pattern not obeying the '*within*' keyword
>
> 2. Sequence not obeying the '*every*' keyword
>
> 3. Logical pattern '*from* *A or B select...*' not producing the
> output
>
> With this fix, the problems asked in Stack Overflow [2] are resolved.
>
>
> [1] https://github.com/wso2/siddhi/pull/436
>
> [2] https://stackoverflow.com/questions/41557227/siddhi-logi
> cal-and-with-within-executes-callback-unexpectedly
>
>
> Thanks & Regards,
> Gobinath
>
>
> On Sat, May 13, 2017 at 8:02 AM, Gobinath 
> wrote:
>
>> Hi,
>>
>> I've fixed the duplicate output with 'OR' in the PR #354 [1].
>> According to this fix, the *addState* method of
>> *LogicalPreStateProcessor* treats both PATTERN and SEQUENCE in the
>> same way [2]. It does not break any existing tests but please check 
>> whether
>> it makes sense or not.
>>
>>
>> [1] https://github.com/wso2/siddhi/pull/354
>>
>> [2] https://github.com/wso2/siddhi/pull/354/commits/803e4d0f
>> 486d7268af117bcfe42f4c704f98b3b5#diff-32293ae88907e099f28593
>> e5496e1e67R62
>>
>>
>> Thanks & Regards,
>> Gobinath
>>
>> On Mon, May 8, 2017 at 1:24 AM, Sriskandarajah Suhothayan <
>> s...@wso2.com> wrote:
>>
>>> I have merged that. +1 this also should give 1 output.
>>>
>>> Thanks for the fixes.
>>>
>>> Regards
>>> Suho
>>>
>>> On Mon, May 8, 2017 at 10:18 AM, Nirmal Fernando 
>>> wrote:
>>>
 Again, I'd only expect one o/p;
 Event{timestamp=1494203709496, data=[WSO2, null, 4.7],
 isExpired=false}

 On Mon, May 8, 2017 at 6:25 AM, Gobinath 
 wrote:

> Hi,
>
> I've found a minor bug and sent the PR [1] with the fix. Similar
> behavior is noticed 

Re: [Dev] [GSoC][Siddhi][CEP]: Siddhi Pattern for Absence of Events

[Sriskandarajah Suhothayan]

On Mon, Jul 3, 2017 at 5:18 PM, Gobinath  wrote:

> Hi,
>
> The following absent event cases are implemented and tested so far and now
> I am focusing on testing these patterns in the form of *Sequence*. If you
> find any cases that I missed or any improvements, please share them.
>
>
>
> A not B for 1sec
>
> After the arrival of A, wait for 1 sec & B not arrived
>
> A → not B and C
>
> When C arrive if B is not available
>
> A → (not B and C) within 1sec
>
> If B not arrived but C arrived within 1 sec from A
>
> A → (not B for 1sec  and C) within 2sec
>
> Wait for 1 sec from the arrival of A; if B not arrived and C arrived and
> both happened within 2 sec from A
>
> not A for 1sec → B
>
> Wait for 1 sec; if A not arrived but B arrived after 1sec
>
> not A and B → C
>
> When B arrive if A is not available followed by C
>
> every ( not B and  A)  → C
>
> Every combination of the previous case
>
> every ( not B for 1sec) → C
>
> Check and emit C every second, if B not arrive
>
> A → not B  for 1 sec and not C for 1 sec
>
> After A, both B and C are not received within 1 sec
>
> not A  for 1 sec and not B for 1 sec → C
>
> A and B are not received for 1 sec and then C
>
> A → not B   for 1 sec or not C for 1 sec
>
> After A, wait for 1 sec B or C not received
>
> not A  for 1 sec or not B for 1 sec → C
>
> Wait for 1 sec; A or B not received followed by C
>
> A → not B for 1 sec or C
>
> After A, if C arrives, emit it otherwise emit after 1 sec if B not arrived
>
> not A for 1 sec or B → C
>
> Same as previous but the other way around
>
> I think these will also work but better if you can check them too via
testcase.

A → C or not B for 1 sec

B or not A for 1 sec → C

every (not B  for 1 sec and not C for 1 sec ) -> A

every (not B  for 1 sec or not C for 1 sec ) -> A

every (B *and* not C for 1 sec ) -> A

every (not C for 1 sec *and* B ) -> A

every (B *or* not C for 1 sec ) -> A

every (not C for 1 sec *or* B ) -> A

every (B *and* (not C and D) ) -> A

every ( (not C and D) *and* B ) -> A

every (B *or* (not C and D) ) -> A

every ((not C and D) *or* B ) -> A


>
> Thanks & Regards,
> Gobinath
>
> On Sun, Jul 2, 2017 at 6:34 AM, Gobinath  wrote:
>
>> Thanks, Suho.
>>
>> Sure I will.
>>
>>
>> Thanks & Regards,
>> Gobinath
>>
>> On Sun, Jul 2, 2017 at 6:32 AM, Sriskandarajah Suhothayan 
>> wrote:
>>
>>> Thanks merged the PR.
>>>
>>> Can you inform in SOF that you have fixed this issue, and this is the
>>> PR.
>>>
>>> Thanks
>>> Suho
>>>
>>> On Sun, Jul 2, 2017 at 6:21 AM, Gobinath  wrote:
>>>
 Hi,

 Please find the PR [1] fixing the following issues in Siddhi.

 1. Logical pattern not obeying the '*within*' keyword

 2. Sequence not obeying the '*every*' keyword

 3. Logical pattern '*from* *A or B select...*' not producing the output

 With this fix, the problems asked in Stack Overflow [2] are resolved.


 [1] https://github.com/wso2/siddhi/pull/436

 [2] https://stackoverflow.com/questions/41557227/siddhi-logi
 cal-and-with-within-executes-callback-unexpectedly


 Thanks & Regards,
 Gobinath


 On Sat, May 13, 2017 at 8:02 AM, Gobinath  wrote:

> Hi,
>
> I've fixed the duplicate output with 'OR' in the PR #354 [1].
> According to this fix, the *addState* method of
> *LogicalPreStateProcessor* treats both PATTERN and SEQUENCE in the
> same way [2]. It does not break any existing tests but please check 
> whether
> it makes sense or not.
>
>
> [1] https://github.com/wso2/siddhi/pull/354
>
> [2] https://github.com/wso2/siddhi/pull/354/commits/803e4d0f
> 486d7268af117bcfe42f4c704f98b3b5#diff-32293ae88907e099f28593
> e5496e1e67R62
>
>
> Thanks & Regards,
> Gobinath
>
> On Mon, May 8, 2017 at 1:24 AM, Sriskandarajah Suhothayan <
> s...@wso2.com> wrote:
>
>> I have merged that. +1 this also should give 1 output.
>>
>> Thanks for the fixes.
>>
>> Regards
>> Suho
>>
>> On Mon, May 8, 2017 at 10:18 AM, Nirmal Fernando 
>> wrote:
>>
>>> Again, I'd only expect one o/p;
>>> Event{timestamp=1494203709496, data=[WSO2, null, 4.7],
>>> isExpired=false}
>>>
>>> On Mon, May 8, 2017 at 6:25 AM, Gobinath 
>>> wrote:
>>>
 Hi,

 I've found a minor bug and sent the PR [1] with the fix. Similar
 behavior is noticed with *or* operator as well (Even after the
 fix). I have given the code and the output below for your concern.

 // Query: e1 or e2 -> e3

 define stream Stream1 (symbol string, price float, volume int);
 define stream Stream2 (symbol string, price float, volume int);

 @info(name = 'query1')
 from e1=Stream1[price > 

[Dev] Problems on MB Cluster Enterprise Integrator 6.1.0

[Júnior]

Hello,

I am trying to setup a cluster for the Broker Profile on AWS.

I am able to start the first node without problem, but when we start the
second node, it doesn't start because it says it is not able to get the
node id of the other member:

TID: [-1234] [] [2017-07-03 12:55:10,193] ERROR
{org.wso2.andes.server.registry.ApplicationRegistry} -
 org.wso2.andes.kernel.AndesException: Failed to read Node id of hazelcast
member Member [X.X.X.X]:5711

On the nodes I have leave the nodeId on broker.xml as default, so it will
generate a random one.

Do you have any clue on where should I set this node id?

Thanks,



-- 
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC][Siddhi][CEP]: Siddhi Pattern for Absence of Events

[Gobinath]

Hi,

The following absent event cases are implemented and tested so far and now
I am focusing on testing these patterns in the form of *Sequence*. If you
find any cases that I missed or any improvements, please share them.



A not B for 1sec

After the arrival of A, wait for 1 sec & B not arrived

A → not B and C

When C arrive if B is not available

A → (not B and C) within 1sec

If B not arrived but C arrived within 1 sec from A

A → (not B for 1sec  and C) within 2sec

Wait for 1 sec from the arrival of A; if B not arrived and C arrived and
both happened within 2 sec from A

not A for 1sec → B

Wait for 1 sec; if A not arrived but B arrived after 1sec

not A and B → C

When B arrive if A is not available followed by C

every ( not B and  A)  → C

Every combination of the previous case

every ( not B for 1sec) → C

Check and emit C every second, if B not arrive

A → not B  for 1 sec and not C for 1 sec

After A, both B and C are not received within 1 sec

not A  for 1 sec and not B for 1 sec → C

A and B are not received for 1 sec and then C

A → not B   for 1 sec or not C for 1 sec

After A, wait for 1 sec B or C not received

not A  for 1 sec or not B for 1 sec → C

Wait for 1 sec; A or B not received followed by C

A → not B for 1 sec or C

After A, if C arrives, emit it otherwise emit after 1 sec if B not arrived

not A for 1 sec or B → C

Same as previous but the other way around



Thanks & Regards,
Gobinath

On Sun, Jul 2, 2017 at 6:34 AM, Gobinath  wrote:

> Thanks, Suho.
>
> Sure I will.
>
>
> Thanks & Regards,
> Gobinath
>
> On Sun, Jul 2, 2017 at 6:32 AM, Sriskandarajah Suhothayan 
> wrote:
>
>> Thanks merged the PR.
>>
>> Can you inform in SOF that you have fixed this issue, and this is the PR.
>>
>> Thanks
>> Suho
>>
>> On Sun, Jul 2, 2017 at 6:21 AM, Gobinath  wrote:
>>
>>> Hi,
>>>
>>> Please find the PR [1] fixing the following issues in Siddhi.
>>>
>>> 1. Logical pattern not obeying the '*within*' keyword
>>>
>>> 2. Sequence not obeying the '*every*' keyword
>>>
>>> 3. Logical pattern '*from* *A or B select...*' not producing the output
>>>
>>> With this fix, the problems asked in Stack Overflow [2] are resolved.
>>>
>>>
>>> [1] https://github.com/wso2/siddhi/pull/436
>>>
>>> [2] https://stackoverflow.com/questions/41557227/siddhi-logi
>>> cal-and-with-within-executes-callback-unexpectedly
>>>
>>>
>>> Thanks & Regards,
>>> Gobinath
>>>
>>>
>>> On Sat, May 13, 2017 at 8:02 AM, Gobinath  wrote:
>>>
 Hi,

 I've fixed the duplicate output with 'OR' in the PR #354 [1]. According
 to this fix, the *addState* method of *LogicalPreStateProcessor*
 treats both PATTERN and SEQUENCE in the same way [2]. It does not break any
 existing tests but please check whether it makes sense or not.


 [1] https://github.com/wso2/siddhi/pull/354

 [2] https://github.com/wso2/siddhi/pull/354/commits/803e4d0f
 486d7268af117bcfe42f4c704f98b3b5#diff-32293ae88907e099f28593
 e5496e1e67R62


 Thanks & Regards,
 Gobinath

 On Mon, May 8, 2017 at 1:24 AM, Sriskandarajah Suhothayan <
 s...@wso2.com> wrote:

> I have merged that. +1 this also should give 1 output.
>
> Thanks for the fixes.
>
> Regards
> Suho
>
> On Mon, May 8, 2017 at 10:18 AM, Nirmal Fernando 
> wrote:
>
>> Again, I'd only expect one o/p;
>> Event{timestamp=1494203709496, data=[WSO2, null, 4.7],
>> isExpired=false}
>>
>> On Mon, May 8, 2017 at 6:25 AM, Gobinath 
>> wrote:
>>
>>> Hi,
>>>
>>> I've found a minor bug and sent the PR [1] with the fix. Similar
>>> behavior is noticed with *or* operator as well (Even after the
>>> fix). I have given the code and the output below for your concern.
>>>
>>> // Query: e1 or e2 -> e3
>>>
>>> define stream Stream1 (symbol string, price float, volume int);
>>> define stream Stream2 (symbol string, price float, volume int);
>>>
>>> @info(name = 'query1')
>>> from e1=Stream1[price > 20] or e2=Stream2[price >30] ->
>>> e3=Stream2['IBM' == symbol]
>>> select e1.symbol as symbol1, e2.price as price2, e3.price as price3
>>> insert into OutputStream;
>>>
>>> // Input
>>> Stream1.send(new Object[]{"WSO2", 55.6f, 100});
>>> Stream2.send(new Object[]{"GOOG", 72.7f, 100});
>>> Stream2.send(new Object[]{"IBM", 4.7f, 100});
>>>
>>> // Output
>>> Event{timestamp=1494203709496, data=[WSO2, null, 4.7],
>>> isExpired=false}
>>> Event{timestamp=1494203709496, data=[WSO2, null, 4.7],
>>> isExpired=false}
>>>
>>> If it is also a bug, please do let me know without merging the PR. I
>>> will fix it under the same PR.
>>>
>>> [1] https://github.com/wso2/siddhi/pull/345
>>>
>>>
>>> Thanks & Regards,
>>> Gobinath
>>>
>>> On 

Re: [Dev] WSO2 Committers += Yasassri Ratnayake

[Hasitha Amal De Silva]

Congrats Yasassri !! :)

On Mon, Jul 3, 2017 at 2:35 PM, Chankami Maddumage 
wrote:

> Congratulations Yasassri ..! !
>
> On Mon, Jul 3, 2017 at 1:06 PM, Chalitha Waldeniyage 
> wrote:
>
>> Congratulations Yasassri!!
>>
>> On Mon, Jul 3, 2017 at 1:04 PM, Dumidu Handakumbura 
>> wrote:
>>
>>> Congrats Yasassri. 
>>>
>>> On Mon, Jul 3, 2017 at 10:09 AM, Maneesha Wijesekara 
>>> wrote:
>>>
 Congratulations Yasassri :)

 On Mon, Jul 3, 2017 at 10:07 AM, Ushani Balasooriya 
 wrote:

> Hi All,
>
> It's my pleasure to announce Yasassri Ratnayake as a WSO2 Committer.
> He has given a great contribution to ESB, MB, App Manager and EI
> product releases.
> In recognition of his contribution, dedication, and commitment he has
> been voted as a WSO2 committer.
>
> Congratulations Yasassri and keep up the good work...!
>
> Thanks,
> --
> *Ushani Balasooriya*
> Associate Technical Lead - EE;
> WSO2 Inc; http://www.wso2.com/.
> Mobile; +94772636796
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Maneesha Wijesekara
 Software Engineer
 WSO2 Inc.

 Email: manee...@wso2.com
 Linkedin: http://linkedin.com/in/maneeshawijesekara
 Mobile: +94712443119

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


>>>
>>>
>>> --
>>> *Dumidu Handakumbura*
>>> Software Engineer
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile;
>>> *+9406740 <+94%2077%20770%206740> *
>>> Blogs; fossmerchant.blogspot.com *; *ballerinagist.blogspot.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Chalitha Maheshwari*
>> Software Engineer-QA,
>> WSO2 Inc.
>>
>> *E-mail:* chali...@wso2.com
>> *Mobile: *+94710 411 112 <+94%2071%20041%201112>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Best Regards ,
>
>
> *Chankami Maddumage*
> Software Engineer - QA Team
> WSO2 Inc; http://www.wso2.com/.
> Mobile: +94 (0) 73096 <%2B94%20%280%29%20773%20381%20250>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : +94772037426
Blog: http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Yasassri Ratnayake

[Chankami Maddumage]

Congratulations Yasassri ..! !

On Mon, Jul 3, 2017 at 1:06 PM, Chalitha Waldeniyage 
wrote:

> Congratulations Yasassri!!
>
> On Mon, Jul 3, 2017 at 1:04 PM, Dumidu Handakumbura 
> wrote:
>
>> Congrats Yasassri. 
>>
>> On Mon, Jul 3, 2017 at 10:09 AM, Maneesha Wijesekara 
>> wrote:
>>
>>> Congratulations Yasassri :)
>>>
>>> On Mon, Jul 3, 2017 at 10:07 AM, Ushani Balasooriya 
>>> wrote:
>>>
 Hi All,

 It's my pleasure to announce Yasassri Ratnayake as a WSO2 Committer. He has
 given a great contribution to ESB, MB, App Manager and EI product releases.
 In recognition of his contribution, dedication, and commitment he has
 been voted as a WSO2 committer.

 Congratulations Yasassri and keep up the good work...!

 Thanks,
 --
 *Ushani Balasooriya*
 Associate Technical Lead - EE;
 WSO2 Inc; http://www.wso2.com/.
 Mobile; +94772636796


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


>>>
>>>
>>> --
>>> Maneesha Wijesekara
>>> Software Engineer
>>> WSO2 Inc.
>>>
>>> Email: manee...@wso2.com
>>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>>> Mobile: +94712443119
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Dumidu Handakumbura*
>> Software Engineer
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile;
>> *+9406740 <+94%2077%20770%206740> *
>> Blogs; fossmerchant.blogspot.com *; *ballerinagist.blogspot.com
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Chalitha Maheshwari*
> Software Engineer-QA,
> WSO2 Inc.
>
> *E-mail:* chali...@wso2.com
> *Mobile: *+94710 411 112 <+94%2071%20041%201112>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards ,


*Chankami Maddumage*
Software Engineer - QA Team
WSO2 Inc; http://www.wso2.com/.
Mobile: +94 (0) 73096 <%2B94%20%280%29%20773%20381%20250>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

[Pubudu Gunatilaka]

Hi Dileepa,

You need to add the K8 membership scheme jar to dropins folder [1] and for
the latest membership schema you don't need to include the dependency jars.
Please go through [1]. Mysql jar should be copied to lib directory.

Do you see any errors in the docker image build log? Based on what you
shared, it looks like puppet has not ran correctly. Could you please share
the docker image build log?

[1] -
https://github.com/wso2/kubernetes-common/tree/master/kubernetes-membership-scheme

Thank you!

On Mon, Jul 3, 2017 at 1:23 PM, Dileepa Jayakody 
wrote:

> Hi Anuruddha et al,
>
> Thanks. Renaming the mysql file worked, and I was able to build the docker
> image.
> However I'm getting a JAVA_HOME error when I run the image locally.
>
> docker run wso2am-kubernetes-pattern-1:2.1.0
>
> Initializing wso2am-2.1.0 in default profile on kubernetes platform...
> Successfully updated localMemberHost with 172.17.0.2
> Creating directory /mnt/172.17.0.2
> Creating symlink [Target] /mnt/wso2am-2.1.0, [Link] /mnt/
> 172.17.0.2/wso2am-2.1.0
> /usr/local/bin/init.sh: line 94: /etc/profile.d/set_java_home.sh: No such
> file or directory
> Starting wso2am-2.1.0 with [Startup Args] , [CARBON_HOME] /mnt/
> 172.17.0.2/wso2am-2.1.0
> Error: JAVA_HOME is not defined correctly.
>  CARBON cannot execute /opt/java/bin/java
>
>
> I have copied the jdk-8u131-linux-x64.tar.gz to
> PUPPET_HOME/modules/wso2base/files and also to 
> PUPPET_HOME/modules/wso2am_runtime/files
>
>
> The wso2am-2.1.0.zip is copied to PUPPET_HOME/modules/wso2am_runtime/files
>
> The dependency jars, kubernetes membership scheme jar and mysql jar are
> copied to : PUPPET_HOME/modules/wso2am_runtime/files/configs/
> repository/components/lib
>
> Can you please verify my dependency file-paths above are correct? The
> paths are not defined in the github guide [1] step 7.
>
> Please let me know if I have done any configuration mistake.
>
> Thanks,
> Dileepa
>
>
>
> On Fri, Jun 30, 2017 at 4:38 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi Dileepa,
>>
>> Your mysql connector jar is different than what puppet is trying to copy.
>> Rename your mysql jar to mysql-connector-java-5.1.36-bin.jar.
>>
>> mysql-connector-java-5.1.36.jar != mysql-connector-java-5.1.36-bin.jar
>>
>>
>> On Fri, Jun 30, 2017 at 12:57 PM, Dileepa Jayakody <
>> dileepajayak...@gmail.com> wrote:
>>
>>> Hi Pubudu,
>>>
>>> Thanks. Checking out v1.0.0 from puppet-base resolved above error.
>>> However, I'm getting a new error, related to the mysql jar file.
>>>
>>> Notice: /Stage[main]/Wso2base::Configure/Wso2base::Push_templates[re
>>> pository/conf/carbon.xml]/File[/mnt/wso2am-2.1.0/repository/conf/carbon.xml]/content:
>>> content changed '{md5}5c92af40d406b3368ceafd3b582017bd' to
>>> '{md5}326757437935bb13c3d71d8ae692d04b'
>>> Error: /Stage[main]/Wso2base::Configure/Wso2base::Push_files[reposi
>>> tory/components/lib/mysql-connector-java-5.1.36-bin.jar]
>>> /File[/mnt/wso2am-2.1.0/repository/components/lib/mysq
>>> l-connector-java-5.1.36-bin.jar]: Could not evaluate: Could not
>>> retrieve information from environment production source(s)
>>> puppet:///modules/wso2am_runtime/configs/repository/componen
>>> ts/lib/mysql-connector-java-5.1.36-bin.jar,
>>> puppet:///modules/wso2base/configs/repository/components/lib
>>> /mysql-connector-java-5.1.36-bin.jar, puppet:///files/configs/reposi
>>> tory/components/lib/mysql-connector-java-5.1.36-bin.jar
>>>
>>> ERROR: Docker image wso2am-traffic-manager-kubernetes-pattern-3:2.1.0
>>> creation failed
>>>
>>>
>>> As in the guide step 7, I have copied the following jars to
>>> *PUPPET_HOME/modules*
>>> jackson-annotations-2.5.4.jar
>>> jackson-databind-2.5.4.jar
>>> jackson-core-2.5.4.jar
>>> kubernetes-membership-scheme-1.0.0.jar
>>> mysql-connector-java-5.1.36.jar
>>>
>>> jdk-8u131-linux-x64.tar.gz
>>> wso2am-2.1.0.zip
>>>
>>> I also tried executing the build as per the older guide by copying the
>>> jdk to PUPPET_HOME/modules/wso2base/files and the dependencies,
>>> kubernetes-membership-schemes to PUPPET_HOME/modules/wso2am/wso
>>> 2am_runtime/files/configs/repository/components/lib
>>>
>>> Still I'm getting the same error. :(
>>>
>>> Any idea what I might be doing wrong here?
>>>
>>> Thanks,
>>> Dileepa
>>>
>>>
>>> On Fri, Jun 30, 2017 at 3:10 PM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Dileepa,

 Could you please check the tag of the wso2base module? By default, it
 refers the master branch and this has to point to v1.0.0 [1]. In your setup
 check the git branch in /modules/wso2base. You need to
 check out this to [1].

 We are having discussions to remove puppet scripts when creating Docker
 images. Hopefully, with K8 release we will remove puppet and allow users to
 provide configuration files. All you need is to have a docker image for the
 product with relevant configurations to run on K8s.

 [1] - 

Re: [Dev] Issues with deploying WSO2 APIM 2.1.0 in Google Cloud

[Dileepa Jayakody]

Hi Anuruddha et al,

Thanks. Renaming the mysql file worked, and I was able to build the docker
image.
However I'm getting a JAVA_HOME error when I run the image locally.

docker run wso2am-kubernetes-pattern-1:2.1.0

Initializing wso2am-2.1.0 in default profile on kubernetes platform...
Successfully updated localMemberHost with 172.17.0.2
Creating directory /mnt/172.17.0.2
Creating symlink [Target] /mnt/wso2am-2.1.0, [Link] /mnt/
172.17.0.2/wso2am-2.1.0
/usr/local/bin/init.sh: line 94: /etc/profile.d/set_java_home.sh: No such
file or directory
Starting wso2am-2.1.0 with [Startup Args] , [CARBON_HOME] /mnt/
172.17.0.2/wso2am-2.1.0
Error: JAVA_HOME is not defined correctly.
 CARBON cannot execute /opt/java/bin/java


I have copied the jdk-8u131-linux-x64.tar.gz to
PUPPET_HOME/modules/wso2base/files and also to
PUPPET_HOME/modules/wso2am_runtime/files

The wso2am-2.1.0.zip is copied to PUPPET_HOME/modules/wso2am_runtime/files

The dependency jars, kubernetes membership scheme jar and mysql jar are
copied to :
PUPPET_HOME/modules/wso2am_runtime/files/configs/repository/components/lib

Can you please verify my dependency file-paths above are correct? The paths
are not defined in the github guide [1] step 7.

Please let me know if I have done any configuration mistake.

Thanks,
Dileepa



On Fri, Jun 30, 2017 at 4:38 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi Dileepa,
>
> Your mysql connector jar is different than what puppet is trying to copy.
> Rename your mysql jar to mysql-connector-java-5.1.36-bin.jar.
>
> mysql-connector-java-5.1.36.jar != mysql-connector-java-5.1.36-bin.jar
>
>
> On Fri, Jun 30, 2017 at 12:57 PM, Dileepa Jayakody <
> dileepajayak...@gmail.com> wrote:
>
>> Hi Pubudu,
>>
>> Thanks. Checking out v1.0.0 from puppet-base resolved above error.
>> However, I'm getting a new error, related to the mysql jar file.
>>
>> Notice: /Stage[main]/Wso2base::Configure/Wso2base::Push_templates[
>> repository/conf/carbon.xml]/File[/mnt/wso2am-2.1.0/
>> repository/conf/carbon.xml]/content: content changed
>> '{md5}5c92af40d406b3368ceafd3b582017bd' to '{md5}326757437935bb13c3d71d8a
>> e692d04b'
>> Error: /Stage[main]/Wso2base::Configure/Wso2base::Push_files[
>> repository/components/lib/mysql-connector-java-5.1.36-
>> bin.jar]/File[/mnt/wso2am-2.1.0/repository/components/lib/
>> mysql-connector-java-5.1.36-bin.jar]: Could not evaluate: Could not
>> retrieve information from environment production source(s)
>> puppet:///modules/wso2am_runtime/configs/repository/componen
>> ts/lib/mysql-connector-java-5.1.36-bin.jar,
>> puppet:///modules/wso2base/configs/repository/components/lib
>> /mysql-connector-java-5.1.36-bin.jar, puppet:///files/configs/reposi
>> tory/components/lib/mysql-connector-java-5.1.36-bin.jar
>>
>> ERROR: Docker image wso2am-traffic-manager-kubernetes-pattern-3:2.1.0
>> creation failed
>>
>>
>> As in the guide step 7, I have copied the following jars to
>> *PUPPET_HOME/modules*
>> jackson-annotations-2.5.4.jar
>> jackson-databind-2.5.4.jar
>> jackson-core-2.5.4.jar
>> kubernetes-membership-scheme-1.0.0.jar
>> mysql-connector-java-5.1.36.jar
>>
>> jdk-8u131-linux-x64.tar.gz
>> wso2am-2.1.0.zip
>>
>> I also tried executing the build as per the older guide by copying the
>> jdk to PUPPET_HOME/modules/wso2base/files and the dependencies,
>> kubernetes-membership-schemes to PUPPET_HOME/modules/wso2am/wso
>> 2am_runtime/files/configs/repository/components/lib
>>
>> Still I'm getting the same error. :(
>>
>> Any idea what I might be doing wrong here?
>>
>> Thanks,
>> Dileepa
>>
>>
>> On Fri, Jun 30, 2017 at 3:10 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Dileepa,
>>>
>>> Could you please check the tag of the wso2base module? By default, it
>>> refers the master branch and this has to point to v1.0.0 [1]. In your setup
>>> check the git branch in /modules/wso2base. You need to
>>> check out this to [1].
>>>
>>> We are having discussions to remove puppet scripts when creating Docker
>>> images. Hopefully, with K8 release we will remove puppet and allow users to
>>> provide configuration files. All you need is to have a docker image for the
>>> product with relevant configurations to run on K8s.
>>>
>>> [1] - https://github.com/wso2/puppet-base/tree/v1.0.0
>>>
>>> Thank you!
>>>
>>> On Fri, Jun 30, 2017 at 2:39 PM, Dileepa Jayakody <
>>> dileepajayak...@gmail.com> wrote:
>>>
 Hi Pubudu, Isuru,

 Thanks, yes manifests have been deleted by mistake. Now the
 PUPPET_HOME/manifests directory has site.pp.
 But now when I build again I'm getting another error by the puppet
 agent.

 log;

 172.17.0.2 - - [30/Jun/2017 14:34:07] "GET
 /modules/wso2am_runtime/templates/repository/deployment/serv
 er/synapse-configs/default/api/_UserInfoAPI_.xml.erb HTTP/1.1" 200 -
 Running Puppet agent...
 Error: Must pass install_java to Class[Wso2base] at
 /etc/puppet/modules/wso2am_runtime/manifests/init.pp:165 on node
 

Re: [Dev] WSO2 Committers += Yasassri Ratnayake

[Chalitha Waldeniyage]

Congratulations Yasassri!!

On Mon, Jul 3, 2017 at 1:04 PM, Dumidu Handakumbura  wrote:

> Congrats Yasassri. 
>
> On Mon, Jul 3, 2017 at 10:09 AM, Maneesha Wijesekara 
> wrote:
>
>> Congratulations Yasassri :)
>>
>> On Mon, Jul 3, 2017 at 10:07 AM, Ushani Balasooriya 
>> wrote:
>>
>>> Hi All,
>>>
>>> It's my pleasure to announce Yasassri Ratnayake as a WSO2 Committer. He has
>>> given a great contribution to ESB, MB, App Manager and EI product releases.
>>> In recognition of his contribution, dedication, and commitment he has
>>> been voted as a WSO2 committer.
>>>
>>> Congratulations Yasassri and keep up the good work...!
>>>
>>> Thanks,
>>> --
>>> *Ushani Balasooriya*
>>> Associate Technical Lead - EE;
>>> WSO2 Inc; http://www.wso2.com/.
>>> Mobile; +94772636796
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Maneesha Wijesekara
>> Software Engineer
>> WSO2 Inc.
>>
>> Email: manee...@wso2.com
>> Linkedin: http://linkedin.com/in/maneeshawijesekara
>> Mobile: +94712443119
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Dumidu Handakumbura*
> Software Engineer
> WSO2 Inc; http://www.wso2.com/.
> Mobile;
> *+9406740 <+94%2077%20770%206740> *
> Blogs; fossmerchant.blogspot.com *; *ballerinagist.blogspot.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Chalitha Maheshwari*
Software Engineer-QA,
WSO2 Inc.

*E-mail:* chali...@wso2.com
*Mobile: *+94710 411 112
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Yasassri Ratnayake

[Dumidu Handakumbura]

Congrats Yasassri. 

On Mon, Jul 3, 2017 at 10:09 AM, Maneesha Wijesekara 
wrote:

> Congratulations Yasassri :)
>
> On Mon, Jul 3, 2017 at 10:07 AM, Ushani Balasooriya 
> wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce Yasassri Ratnayake as a WSO2 Committer. He has
>> given a great contribution to ESB, MB, App Manager and EI product releases.
>> In recognition of his contribution, dedication, and commitment he has
>> been voted as a WSO2 committer.
>>
>> Congratulations Yasassri and keep up the good work...!
>>
>> Thanks,
>> --
>> *Ushani Balasooriya*
>> Associate Technical Lead - EE;
>> WSO2 Inc; http://www.wso2.com/.
>> Mobile; +94772636796
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Maneesha Wijesekara
> Software Engineer
> WSO2 Inc.
>
> Email: manee...@wso2.com
> Linkedin: http://linkedin.com/in/maneeshawijesekara
> Mobile: +94712443119
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Dumidu Handakumbura*
Software Engineer
WSO2 Inc; http://www.wso2.com/.
Mobile;
*+9406740 *
Blogs; fossmerchant.blogspot.com *; *ballerinagist.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev