[Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Manuri Amaya Perera]

Hi Devs,

WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.

This release fixes the following issues:
https://wso2.org/jira/issues/?filter=12396

Please download and test your products with kernel 4.4.2 RC1 and vote. Vote
will be open for 72 hours or as longer as needed.

*​Source and binary distribution files:*
http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2

*Maven staging repository:*
http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/


*The tag to be voted upon:*
https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1


[ ] Broken - do not release (explain why)
[ ] Stable - go ahead and release


Thank you
Carbon Team

​

-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Kasun Indrasiri]

We found that following fixes were missing in latest kernel release while
doing ESB 4.9.
Any plans to include them in this release.

https://wso2.org/jira/browse/CARBON-14807
https://wso2.org/jira/browse/CARBON-14959
https://wso2.org/jira/browse/CARBON-14764
https://wso2.org/jira/browse/CARBON-15248
https://wso2.org/jira/browse/CARBON-15141
https://wso2.org/jira/browse/CARBON-15223
https://wso2.org/jira/browse/CARBON-15184
https://wso2.org/jira/browse/CARBON-14730
https://wso2.org/jira/browse/CARBON-15248

On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera 
wrote:

> Hi Devs,
>
> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12396
>
> Please download and test your products with kernel 4.4.2 RC1 and vote.
> Vote will be open for 72 hours or as longer as needed.
>
> *​Source and binary distribution files:*
> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
> 
>
> *The tag to be voted upon:*
> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thank you
> Carbon Team
>
> ​
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Manuri Amaya Perera]

Hi Kasun,

[1] is already fixed. Regarding [2], according to the comment in the jira,
the fix is available in [3].

I suppose [4] also is fixed. @Ishara Could you please confirm ?

Rest of the issues will be fixed in the next release.


[1] https://wso2.org/jira/browse/CARBON-15184
[2] https://wso2.org/jira/browse/CARBON-14730
[3] https://github.com/wso2/cipher-tool
[4] https://wso2.org/jira/browse/CARBON-14959

Thank you.

On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri  wrote:

> We found that following fixes were missing in latest kernel release while
> doing ESB 4.9.
> Any plans to include them in this release.
>
> https://wso2.org/jira/browse/CARBON-14807
> https://wso2.org/jira/browse/CARBON-14959
> https://wso2.org/jira/browse/CARBON-14764
> https://wso2.org/jira/browse/CARBON-15248
> https://wso2.org/jira/browse/CARBON-15141
> https://wso2.org/jira/browse/CARBON-15223
> https://wso2.org/jira/browse/CARBON-15184
> https://wso2.org/jira/browse/CARBON-14730
> https://wso2.org/jira/browse/CARBON-15248
>
> On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera 
> wrote:
>
>> Hi Devs,
>>
>> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12396
>>
>> Please download and test your products with kernel 4.4.2 RC1 and vote.
>> Vote will be open for 72 hours or as longer as needed.
>>
>> *​Source and binary distribution files:*
>> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
>> 
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thank you
>> Carbon Team
>>
>> ​
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Kasun Indrasiri]

Hi Manuri,

We don't have an immediate requirement to have these fixes for ESB as 4.9
is already released. But these are missing patches and we need to at least
make them blockers for the next release.

On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera 
wrote:

> Hi Kasun,
>
> [1] is already fixed. Regarding [2], according to the comment in the jira,
> the fix is available in [3].
>
> I suppose [4] also is fixed. @Ishara Could you please confirm ?
>
> Rest of the issues will be fixed in the next release.
>
>
> [1] https://wso2.org/jira/browse/CARBON-15184
> [2] https://wso2.org/jira/browse/CARBON-14730
> [3] https://github.com/wso2/cipher-tool
> [4] https://wso2.org/jira/browse/CARBON-14959
>
> Thank you.
>
> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri  wrote:
>
>> We found that following fixes were missing in latest kernel release while
>> doing ESB 4.9.
>> Any plans to include them in this release.
>>
>> https://wso2.org/jira/browse/CARBON-14807
>> https://wso2.org/jira/browse/CARBON-14959
>> https://wso2.org/jira/browse/CARBON-14764
>> https://wso2.org/jira/browse/CARBON-15248
>> https://wso2.org/jira/browse/CARBON-15141
>> https://wso2.org/jira/browse/CARBON-15223
>> https://wso2.org/jira/browse/CARBON-15184
>> https://wso2.org/jira/browse/CARBON-14730
>> https://wso2.org/jira/browse/CARBON-15248
>>
>> On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12396
>>>
>>> Please download and test your products with kernel 4.4.2 RC1 and vote.
>>> Vote will be open for 72 hours or as longer as needed.
>>>
>>> *​Source and binary distribution files:*
>>> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
>>> 
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>>
>>> Thank you
>>> Carbon Team
>>>
>>> ​
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> *
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>



-- 
Kasun Indrasiri
Software Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Manuri Amaya Perera]

Hi Kasun,

Noted.

Thank you.

On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri  wrote:

> Hi Manuri,
>
> We don't have an immediate requirement to have these fixes for ESB as 4.9
> is already released. But these are missing patches and we need to at least
> make them blockers for the next release.
>
> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera 
> wrote:
>
>> Hi Kasun,
>>
>> [1] is already fixed. Regarding [2], according to the comment in the
>> jira, the fix is available in [3].
>>
>> I suppose [4] also is fixed. @Ishara Could you please confirm ?
>>
>> Rest of the issues will be fixed in the next release.
>>
>>
>> [1] https://wso2.org/jira/browse/CARBON-15184
>> [2] https://wso2.org/jira/browse/CARBON-14730
>> [3] https://github.com/wso2/cipher-tool
>> [4] https://wso2.org/jira/browse/CARBON-14959
>>
>> Thank you.
>>
>> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri  wrote:
>>
>>> We found that following fixes were missing in latest kernel release
>>> while doing ESB 4.9.
>>> Any plans to include them in this release.
>>>
>>> https://wso2.org/jira/browse/CARBON-14807
>>> https://wso2.org/jira/browse/CARBON-14959
>>> https://wso2.org/jira/browse/CARBON-14764
>>> https://wso2.org/jira/browse/CARBON-15248
>>> https://wso2.org/jira/browse/CARBON-15141
>>> https://wso2.org/jira/browse/CARBON-15223
>>> https://wso2.org/jira/browse/CARBON-15184
>>> https://wso2.org/jira/browse/CARBON-14730
>>> https://wso2.org/jira/browse/CARBON-15248
>>>
>>> On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera 
>>> wrote:
>>>
 Hi Devs,

 WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.

 This release fixes the following issues:
 https://wso2.org/jira/issues/?filter=12396

 Please download and test your products with kernel 4.4.2 RC1 and vote.
 Vote will be open for 72 hours or as longer as needed.

 *​Source and binary distribution files:*
 http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2

 *Maven staging repository:*
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
 

 *The tag to be voted upon:*
 https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1


 [ ] Broken - do not release (explain why)
 [ ] Stable - go ahead and release


 Thank you
 Carbon Team

 ​

 --

 *Manuri Amaya Perera*

 *Software Engineer*

 *WSO2 Inc.*

 *Blog: http://manuriamayaperera.blogspot.com
 *

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


>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Ramith Jayasinghe]

do we have a fix for https://wso2.org/jira/browse/MB-1326 ?

On Fri, Sep 18, 2015 at 4:51 PM, Manuri Amaya Perera  wrote:
> Hi Kasun,
>
> Noted.
>
> Thank you.
>
> On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri  wrote:
>>
>> Hi Manuri,
>>
>> We don't have an immediate requirement to have these fixes for ESB as 4.9
>> is already released. But these are missing patches and we need to at least
>> make them blockers for the next release.
>>
>> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera 
>> wrote:
>>>
>>> Hi Kasun,
>>>
>>> [1] is already fixed. Regarding [2], according to the comment in the
>>> jira, the fix is available in [3].
>>>
>>> I suppose [4] also is fixed. @Ishara Could you please confirm ?
>>>
>>> Rest of the issues will be fixed in the next release.
>>>
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-15184
>>> [2] https://wso2.org/jira/browse/CARBON-14730
>>> [3] https://github.com/wso2/cipher-tool
>>> [4] https://wso2.org/jira/browse/CARBON-14959
>>>
>>> Thank you.
>>>
>>> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri  wrote:

 We found that following fixes were missing in latest kernel release
 while doing ESB 4.9.
 Any plans to include them in this release.

 https://wso2.org/jira/browse/CARBON-14807
 https://wso2.org/jira/browse/CARBON-14959
 https://wso2.org/jira/browse/CARBON-14764
 https://wso2.org/jira/browse/CARBON-15248
 https://wso2.org/jira/browse/CARBON-15141
 https://wso2.org/jira/browse/CARBON-15223
 https://wso2.org/jira/browse/CARBON-15184
 https://wso2.org/jira/browse/CARBON-14730
 https://wso2.org/jira/browse/CARBON-15248

 On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera 
 wrote:
>
> Hi Devs,
>
> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12396
>
> Please download and test your products with kernel 4.4.2 RC1 and vote.
> Vote will be open for 72 hours or as longer as needed.
>
> Source and binary distribution files:
> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>
> Maven staging repository:
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
>
> The tag to be voted upon:
> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thank you
> Carbon Team
>
>
> --
> Manuri Amaya Perera
> Software Engineer
> WSO2 Inc.
>
> Blog: http://manuriamayaperera.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/
>>>
>>>
>>>
>>>
>>> --
>>> Manuri Amaya Perera
>>> Software Engineer
>>> WSO2 Inc.
>>>
>>> Blog: http://manuriamayaperera.blogspot.com
>>
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>
>
>
>
> --
> Manuri Amaya Perera
> Software Engineer
> WSO2 Inc.
>
> Blog: http://manuriamayaperera.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>



-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Niranjan Karunanandham]

Hi Kasun,

I went through the JIRAs that was mentioned in the previous mail. Please
see the comments below:

   -
   - https://wso2.org/jira/browse/CARBON-14807 - Patch is merged to 4.4.0
   branch, but as per the comment from Sandapa, the patch does not solve the
   issue completely.
   - https://wso2.org/jira/browse/CARBON-14959 - Available in 4.4.2
   - https://wso2.org/jira/browse/CARBON-14764 - Jira is directed to APIM.
   Therefore cloned the JIRA to Carbon to track it [1].
   - https://wso2.org/jira/browse/CARBON-15141 - Fix is to axiom and is
   available in v1.2.11-wso2v9
   - https://wso2.org/jira/browse/CARBON-15223 - Seems the PR is merged to
   4.4.2 but the JIRA is not updated. @Kalpa can you please update this.
   - https://wso2.org/jira/browse/CARBON-15184 - Available in 4.4.2
   - https://wso2.org/jira/browse/CARBON-14730 - Available in 4.4.2
   - https://wso2.org/jira/browse/CARBON-15248 - available in 4.5.0. This
   contains API addition so it will be there in the 4.5.0 release[1].

[1] - https://wso2.org/jira/browse/CARBON-15439
[2] - Mail Subject : [Carbon-Kernel-4.4.2 Release] Patches from ESB 4.9.0
release which are not in carbon-kernel-4.4.1

Regards,
Nira

On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri  wrote:

> Hi Manuri,
>
> We don't have an immediate requirement to have these fixes for ESB as 4.9
> is already released. But these are missing patches and we need to at least
> make them blockers for the next release.
>
> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera 
> wrote:
>
>> Hi Kasun,
>>
>> [1] is already fixed. Regarding [2], according to the comment in the
>> jira, the fix is available in [3].
>>
>> I suppose [4] also is fixed. @Ishara Could you please confirm ?
>>
>> Rest of the issues will be fixed in the next release.
>>
>>
>> [1] https://wso2.org/jira/browse/CARBON-15184
>> [2] https://wso2.org/jira/browse/CARBON-14730
>> [3] https://github.com/wso2/cipher-tool
>> [4] https://wso2.org/jira/browse/CARBON-14959
>>
>> Thank you.
>>
>> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri  wrote:
>>
>>> We found that following fixes were missing in latest kernel release
>>> while doing ESB 4.9.
>>> Any plans to include them in this release.
>>>
>>> https://wso2.org/jira/browse/CARBON-14807
>>> https://wso2.org/jira/browse/CARBON-14959
>>> https://wso2.org/jira/browse/CARBON-14764
>>> https://wso2.org/jira/browse/CARBON-15248
>>> https://wso2.org/jira/browse/CARBON-15141
>>> https://wso2.org/jira/browse/CARBON-15223
>>> https://wso2.org/jira/browse/CARBON-15184
>>> https://wso2.org/jira/browse/CARBON-14730
>>> https://wso2.org/jira/browse/CARBON-15248
>>>
>>> On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera 
>>> wrote:
>>>
 Hi Devs,

 WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.

 This release fixes the following issues:
 https://wso2.org/jira/issues/?filter=12396

 Please download and test your products with kernel 4.4.2 RC1 and vote.
 Vote will be open for 72 hours or as longer as needed.

 *​Source and binary distribution files:*
 http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2

 *Maven staging repository:*
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
 

 *The tag to be voted upon:*
 https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1


 [ ] Broken - do not release (explain why)
 [ ] Stable - go ahead and release


 Thank you
 Carbon Team

 ​

 --

 *Manuri Amaya Perera*

 *Software Engineer*

 *WSO2 Inc.*

 *Blog: http://manuriamayaperera.blogspot.com
 *

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


>>>
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Niranjan Karunanandham]

Hi Ishara,

On Tue, Sep 22, 2015 at 11:16 AM, Niranjan Karunanandham 
wrote:

> Hi Kasun,
>
> I went through the JIRAs that was mentioned in the previous mail. Please
> see the comments below:
>
>-
>- https://wso2.org/jira/browse/CARBON-14807 - Patch is merged to 4.4.0
>branch, but as per the comment from Sandapa, the patch does not solve the
>issue completely.
>- https://wso2.org/jira/browse/CARBON-14959 - Available in 4.4.2
>
> As per the comment in the JIRA [1], this is moved to the userstore
manager. Will you be able to update the JIRA where the fix is please.


>
>- https://wso2.org/jira/browse/CARBON-14764 - Jira is directed to
>APIM. Therefore cloned the JIRA to Carbon to track it [1].
>- https://wso2.org/jira/browse/CARBON-15141 - Fix is to axiom and is
>available in v1.2.11-wso2v9
>- https://wso2.org/jira/browse/CARBON-15223 - Seems the PR is merged
>to 4.4.2 but the JIRA is not updated. @Kalpa can you please update this.
>- https://wso2.org/jira/browse/CARBON-15184 - Available in 4.4.2
>- https://wso2.org/jira/browse/CARBON-14730 - Available in 4.4.2
>- https://wso2.org/jira/browse/CARBON-15248 - available in 4.5.0. This
>contains API addition so it will be there in the 4.5.0 release[1].
>
> [1] - https://wso2.org/jira/browse/CARBON-15439
> [2] - Mail Subject : [Carbon-Kernel-4.4.2 Release] Patches from ESB 4.9.0
> release which are not in carbon-kernel-4.4.1
>
> Regards,
> Nira
>
> On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri  wrote:
>
>> Hi Manuri,
>>
>> We don't have an immediate requirement to have these fixes for ESB as 4.9
>> is already released. But these are missing patches and we need to at least
>> make them blockers for the next release.
>>
>> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera 
>> wrote:
>>
>>> Hi Kasun,
>>>
>>> [1] is already fixed. Regarding [2], according to the comment in the
>>> jira, the fix is available in [3].
>>>
>>> I suppose [4] also is fixed. @Ishara Could you please confirm ?
>>>
>>> Rest of the issues will be fixed in the next release.
>>>
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-15184
>>> [2] https://wso2.org/jira/browse/CARBON-14730
>>> [3] https://github.com/wso2/cipher-tool
>>> [4] https://wso2.org/jira/browse/CARBON-14959
>>>
>>> Thank you.
>>>
>>> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri  wrote:
>>>
 We found that following fixes were missing in latest kernel release
 while doing ESB 4.9.
 Any plans to include them in this release.

 https://wso2.org/jira/browse/CARBON-14807
 https://wso2.org/jira/browse/CARBON-14959
 https://wso2.org/jira/browse/CARBON-14764
 https://wso2.org/jira/browse/CARBON-15248
 https://wso2.org/jira/browse/CARBON-15141
 https://wso2.org/jira/browse/CARBON-15223
 https://wso2.org/jira/browse/CARBON-15184
 https://wso2.org/jira/browse/CARBON-14730
 https://wso2.org/jira/browse/CARBON-15248

 On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera 
 wrote:

> Hi Devs,
>
> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12396
>
> Please download and test your products with kernel 4.4.2 RC1 and vote.
> Vote will be open for 72 hours or as longer as needed.
>
> *​Source and binary distribution files:*
> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
> 
>
> *The tag to be voted upon:*
> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thank you
> Carbon Team
>
> ​
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/

>>>
>>>
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>>

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Kalpa Welivitigoda]

Hi Niranjan/Kasun,

On Tue, Sep 22, 2015 at 11:22 AM, Niranjan Karunanandham 
wrote:

> Hi Ishara,
>
> On Tue, Sep 22, 2015 at 11:16 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Kasun,
>>
>> I went through the JIRAs that was mentioned in the previous mail. Please
>> see the comments below:
>>
>>-
>>- https://wso2.org/jira/browse/CARBON-14807 - Patch is merged to
>>4.4.0 branch, but as per the comment from Sandapa, the patch does not 
>> solve
>>the issue completely.
>>- https://wso2.org/jira/browse/CARBON-14959 - Available in 4.4.2
>>
>> As per the comment in the JIRA [1], this is moved to the userstore
> manager. Will you be able to update the JIRA where the fix is please.
>
>
>>
>>- https://wso2.org/jira/browse/CARBON-14764 - Jira is directed to
>>APIM. Therefore cloned the JIRA to Carbon to track it [1].
>>- https://wso2.org/jira/browse/CARBON-15141 - Fix is to axiom and is
>>available in v1.2.11-wso2v9
>>- https://wso2.org/jira/browse/CARBON-15223 - Seems the PR is merged
>>to 4.4.2 but the JIRA is not updated. @Kalpa can you please update this.
>>
>> The fix has gone to carbon-commons [3] and and is available since 4.2.4.
Updated the JIRA.

>
>>- https://wso2.org/jira/browse/CARBON-15184 - Available in 4.4.2
>>- https://wso2.org/jira/browse/CARBON-14730 - Available in 4.4.2
>>- https://wso2.org/jira/browse/CARBON-15248 - available in 4.5.0.
>>This contains API addition so it will be there in the 4.5.0 release[1].
>>
>> [1] - https://wso2.org/jira/browse/CARBON-15439
>> [2] - Mail Subject : [Carbon-Kernel-4.4.2 Release] Patches from ESB 4.9.0
>> release which are not in carbon-kernel-4.4.1
>>
>> Regards,
>> Nira
>>
>> On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri  wrote:
>>
>>> Hi Manuri,
>>>
>>> We don't have an immediate requirement to have these fixes for ESB as
>>> 4.9 is already released. But these are missing patches and we need to at
>>> least make them blockers for the next release.
>>>
>>> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera 
>>> wrote:
>>>
 Hi Kasun,

 [1] is already fixed. Regarding [2], according to the comment in the
 jira, the fix is available in [3].

 I suppose [4] also is fixed. @Ishara Could you please confirm ?

 Rest of the issues will be fixed in the next release.


 [1] https://wso2.org/jira/browse/CARBON-15184
 [2] https://wso2.org/jira/browse/CARBON-14730
 [3] https://github.com/wso2/cipher-tool
 [4] https://wso2.org/jira/browse/CARBON-14959

 Thank you.

 On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri 
 wrote:

> We found that following fixes were missing in latest kernel release
> while doing ESB 4.9.
> Any plans to include them in this release.
>
> https://wso2.org/jira/browse/CARBON-14807
> https://wso2.org/jira/browse/CARBON-14959
> https://wso2.org/jira/browse/CARBON-14764
> https://wso2.org/jira/browse/CARBON-15248
> https://wso2.org/jira/browse/CARBON-15141
> https://wso2.org/jira/browse/CARBON-15223
> https://wso2.org/jira/browse/CARBON-15184
> https://wso2.org/jira/browse/CARBON-14730
> https://wso2.org/jira/browse/CARBON-15248
>
> On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera  > wrote:
>
>> Hi Devs,
>>
>> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12396
>>
>> Please download and test your products with kernel 4.4.2 RC1 and
>> vote. Vote will be open for 72 hours or as longer as needed.
>>
>> *​Source and binary distribution files:*
>> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
>> 
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thank you
>> Carbon Team
>>
>> ​
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



 --

>>>

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Kasun Indrasiri]

Hi Nira,

On Tue, Sep 22, 2015 at 11:16 AM, Niranjan Karunanandham 
wrote:

> Hi Kasun,
>
> I went through the JIRAs that was mentioned in the previous mail. Please
> see the comments below:
>
>-
>- https://wso2.org/jira/browse/CARBON-14807 - Patch is merged to 4.4.0
>branch, but as per the comment from Sandapa, the patch does not solve the
>issue completely.
>
> So, then is that an ESB specific issue?

>
>- https://wso2.org/jira/browse/CARBON-14959 - Available in 4.4.2
>- https://wso2.org/jira/browse/CARBON-14764 - Jira is directed to
>APIM. Therefore cloned the JIRA to Carbon to track it [1].
>- https://wso2.org/jira/browse/CARBON-15141 - Fix is to axiom and is
>available in v1.2.11-wso2v9
>- https://wso2.org/jira/browse/CARBON-15223 - Seems the PR is merged
>to 4.4.2 but the JIRA is not updated. @Kalpa can you please update this.
>- https://wso2.org/jira/browse/CARBON-15184 - Available in 4.4.2
>- https://wso2.org/jira/browse/CARBON-14730 - Available in 4.4.2
>- https://wso2.org/jira/browse/CARBON-15248 - available in 4.5.0. This
>contains API addition so it will be there in the 4.5.0 release[1].
>
> [1] - https://wso2.org/jira/browse/CARBON-15439
> [2] - Mail Subject : [Carbon-Kernel-4.4.2 Release] Patches from ESB 4.9.0
> release which are not in carbon-kernel-4.4.1
>
>
Thanks a lot for looking into these issues.  I guess, we are good to
proceed with this release.

> Regards,
> Nira
>
> On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri  wrote:
>
>> Hi Manuri,
>>
>> We don't have an immediate requirement to have these fixes for ESB as 4.9
>> is already released. But these are missing patches and we need to at least
>> make them blockers for the next release.
>>
>> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera 
>> wrote:
>>
>>> Hi Kasun,
>>>
>>> [1] is already fixed. Regarding [2], according to the comment in the
>>> jira, the fix is available in [3].
>>>
>>> I suppose [4] also is fixed. @Ishara Could you please confirm ?
>>>
>>> Rest of the issues will be fixed in the next release.
>>>
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-15184
>>> [2] https://wso2.org/jira/browse/CARBON-14730
>>> [3] https://github.com/wso2/cipher-tool
>>> [4] https://wso2.org/jira/browse/CARBON-14959
>>>
>>> Thank you.
>>>
>>> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri  wrote:
>>>
 We found that following fixes were missing in latest kernel release
 while doing ESB 4.9.
 Any plans to include them in this release.

 https://wso2.org/jira/browse/CARBON-14807
 https://wso2.org/jira/browse/CARBON-14959
 https://wso2.org/jira/browse/CARBON-14764
 https://wso2.org/jira/browse/CARBON-15248
 https://wso2.org/jira/browse/CARBON-15141
 https://wso2.org/jira/browse/CARBON-15223
 https://wso2.org/jira/browse/CARBON-15184
 https://wso2.org/jira/browse/CARBON-14730
 https://wso2.org/jira/browse/CARBON-15248

 On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera 
 wrote:

> Hi Devs,
>
> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12396
>
> Please download and test your products with kernel 4.4.2 RC1 and vote.
> Vote will be open for 72 hours or as longer as needed.
>
> *​Source and binary distribution files:*
> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
> 
>
> *The tag to be voted upon:*
> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thank you
> Carbon Team
>
> ​
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/

>>>
>>>
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>> 

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Niranjan Karunanandham]

Hi Kasun,

On Tue, Sep 22, 2015 at 11:27 AM, Kasun Indrasiri  wrote:

>
> Hi Nira,
>
> On Tue, Sep 22, 2015 at 11:16 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Kasun,
>>
>> I went through the JIRAs that was mentioned in the previous mail. Please
>> see the comments below:
>>
>>-
>>- https://wso2.org/jira/browse/CARBON-14807 - Patch is merged to
>>4.4.0 branch, but as per the comment from Sandapa, the patch does not 
>> solve
>>the issue completely.
>>
>> So, then is that an ESB specific issue?
>
We need to look into this to know where the issue is being created. I have
re-opened the JIRA with the target version as 4.4.3 so that it is looked
into before the next release.


>>- https://wso2.org/jira/browse/CARBON-14959 - Available in 4.4.2
>>- https://wso2.org/jira/browse/CARBON-14764 - Jira is directed to
>>APIM. Therefore cloned the JIRA to Carbon to track it [1].
>>- https://wso2.org/jira/browse/CARBON-15141 - Fix is to axiom and is
>>available in v1.2.11-wso2v9
>>- https://wso2.org/jira/browse/CARBON-15223 - Seems the PR is merged
>>to 4.4.2 but the JIRA is not updated. @Kalpa can you please update this.
>>- https://wso2.org/jira/browse/CARBON-15184 - Available in 4.4.2
>>- https://wso2.org/jira/browse/CARBON-14730 - Available in 4.4.2
>>- https://wso2.org/jira/browse/CARBON-15248 - available in 4.5.0.
>>This contains API addition so it will be there in the 4.5.0 release[1].
>>
>> [1] - https://wso2.org/jira/browse/CARBON-15439
>> [2] - Mail Subject : [Carbon-Kernel-4.4.2 Release] Patches from ESB 4.9.0
>> release which are not in carbon-kernel-4.4.1
>>
>>
> Thanks a lot for looking into these issues.  I guess, we are good to
> proceed with this release.
>
>> Regards,
>> Nira
>>
>> On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri  wrote:
>>
>>> Hi Manuri,
>>>
>>> We don't have an immediate requirement to have these fixes for ESB as
>>> 4.9 is already released. But these are missing patches and we need to at
>>> least make them blockers for the next release.
>>>
>>> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera 
>>> wrote:
>>>
 Hi Kasun,

 [1] is already fixed. Regarding [2], according to the comment in the
 jira, the fix is available in [3].

 I suppose [4] also is fixed. @Ishara Could you please confirm ?

 Rest of the issues will be fixed in the next release.


 [1] https://wso2.org/jira/browse/CARBON-15184
 [2] https://wso2.org/jira/browse/CARBON-14730
 [3] https://github.com/wso2/cipher-tool
 [4] https://wso2.org/jira/browse/CARBON-14959

 Thank you.

 On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri 
 wrote:

> We found that following fixes were missing in latest kernel release
> while doing ESB 4.9.
> Any plans to include them in this release.
>
> https://wso2.org/jira/browse/CARBON-14807
> https://wso2.org/jira/browse/CARBON-14959
> https://wso2.org/jira/browse/CARBON-14764
> https://wso2.org/jira/browse/CARBON-15248
> https://wso2.org/jira/browse/CARBON-15141
> https://wso2.org/jira/browse/CARBON-15223
> https://wso2.org/jira/browse/CARBON-15184
> https://wso2.org/jira/browse/CARBON-14730
> https://wso2.org/jira/browse/CARBON-15248
>
> On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera  > wrote:
>
>> Hi Devs,
>>
>> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12396
>>
>> Please download and test your products with kernel 4.4.2 RC1 and
>> vote. Vote will be open for 72 hours or as longer as needed.
>>
>> *​Source and binary distribution files:*
>> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
>> 
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thank you
>> Carbon Team
>>
>> ​
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[KasunG Gajasinghe]

Hi Ramith,

Is this a blocker for the release? [1]

@All, please send your votes across asap to get this release done.

[1] https://wso2.org/jira/browse/MB-1326

Thanks.

On Tue, Sep 22, 2015 at 11:33 AM, Niranjan Karunanandham 
wrote:

> Hi Kasun,
>
> On Tue, Sep 22, 2015 at 11:27 AM, Kasun Indrasiri  wrote:
>
>>
>> Hi Nira,
>>
>> On Tue, Sep 22, 2015 at 11:16 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Kasun,
>>>
>>> I went through the JIRAs that was mentioned in the previous mail. Please
>>> see the comments below:
>>>
>>>-
>>>- https://wso2.org/jira/browse/CARBON-14807 - Patch is merged to
>>>4.4.0 branch, but as per the comment from Sandapa, the patch does not 
>>> solve
>>>the issue completely.
>>>
>>> So, then is that an ESB specific issue?
>>
> We need to look into this to know where the issue is being created. I have
> re-opened the JIRA with the target version as 4.4.3 so that it is looked
> into before the next release.
>
>
>>>- https://wso2.org/jira/browse/CARBON-14959 - Available in 4.4.2
>>>- https://wso2.org/jira/browse/CARBON-14764 - Jira is directed to
>>>APIM. Therefore cloned the JIRA to Carbon to track it [1].
>>>- https://wso2.org/jira/browse/CARBON-15141 - Fix is to axiom and is
>>>available in v1.2.11-wso2v9
>>>- https://wso2.org/jira/browse/CARBON-15223 - Seems the PR is merged
>>>to 4.4.2 but the JIRA is not updated. @Kalpa can you please update this.
>>>- https://wso2.org/jira/browse/CARBON-15184 - Available in 4.4.2
>>>- https://wso2.org/jira/browse/CARBON-14730 - Available in 4.4.2
>>>- https://wso2.org/jira/browse/CARBON-15248 - available in 4.5.0.
>>>This contains API addition so it will be there in the 4.5.0 release[1].
>>>
>>> [1] - https://wso2.org/jira/browse/CARBON-15439
>>> [2] - Mail Subject : [Carbon-Kernel-4.4.2 Release] Patches from ESB
>>> 4.9.0 release which are not in carbon-kernel-4.4.1
>>>
>>>
>> Thanks a lot for looking into these issues.  I guess, we are good to
>> proceed with this release.
>>
>>> Regards,
>>> Nira
>>>
>>> On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri  wrote:
>>>
 Hi Manuri,

 We don't have an immediate requirement to have these fixes for ESB as
 4.9 is already released. But these are missing patches and we need to at
 least make them blockers for the next release.

 On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera 
 wrote:

> Hi Kasun,
>
> [1] is already fixed. Regarding [2], according to the comment in the
> jira, the fix is available in [3].
>
> I suppose [4] also is fixed. @Ishara Could you please confirm ?
>
> Rest of the issues will be fixed in the next release.
>
>
> [1] https://wso2.org/jira/browse/CARBON-15184
> [2] https://wso2.org/jira/browse/CARBON-14730
> [3] https://github.com/wso2/cipher-tool
> [4] https://wso2.org/jira/browse/CARBON-14959
>
> Thank you.
>
> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri 
> wrote:
>
>> We found that following fixes were missing in latest kernel release
>> while doing ESB 4.9.
>> Any plans to include them in this release.
>>
>> https://wso2.org/jira/browse/CARBON-14807
>> https://wso2.org/jira/browse/CARBON-14959
>> https://wso2.org/jira/browse/CARBON-14764
>> https://wso2.org/jira/browse/CARBON-15248
>> https://wso2.org/jira/browse/CARBON-15141
>> https://wso2.org/jira/browse/CARBON-15223
>> https://wso2.org/jira/browse/CARBON-15184
>> https://wso2.org/jira/browse/CARBON-14730
>> https://wso2.org/jira/browse/CARBON-15248
>>
>> On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera <
>> manu...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12396
>>>
>>> Please download and test your products with kernel 4.4.2 RC1 and
>>> vote. Vote will be open for 72 hours or as longer as needed.
>>>
>>> *​Source and binary distribution files:*
>>> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
>>> 
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>>
>>> Thank you
>>> Carbon Team
>>>
>>> ​
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> 

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Yasassri Ratnayake]

Hi All,

After testing MB with Carbon 4.4.2 RC1 we still observed [1].

[1] - https://wso2.org/jira/browse/MB-1326

With Regards,

On Tue, Sep 22, 2015 at 4:52 PM, KasunG Gajasinghe  wrote:

> Hi Ramith,
>
> Is this a blocker for the release? [1]
>
> @All, please send your votes across asap to get this release done.
>
> [1] https://wso2.org/jira/browse/MB-1326
>
> Thanks.
>
> On Tue, Sep 22, 2015 at 11:33 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Kasun,
>>
>> On Tue, Sep 22, 2015 at 11:27 AM, Kasun Indrasiri  wrote:
>>
>>>
>>> Hi Nira,
>>>
>>> On Tue, Sep 22, 2015 at 11:16 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Kasun,

 I went through the JIRAs that was mentioned in the previous mail.
 Please see the comments below:

-
- https://wso2.org/jira/browse/CARBON-14807 - Patch is merged to
4.4.0 branch, but as per the comment from Sandapa, the patch does not 
 solve
the issue completely.

 So, then is that an ESB specific issue?
>>>
>> We need to look into this to know where the issue is being created. I
>> have re-opened the JIRA with the target version as 4.4.3 so that it is
>> looked into before the next release.
>>
>>
- https://wso2.org/jira/browse/CARBON-14959 - Available in 4.4.2
- https://wso2.org/jira/browse/CARBON-14764 - Jira is directed to
APIM. Therefore cloned the JIRA to Carbon to track it [1].
- https://wso2.org/jira/browse/CARBON-15141 - Fix is to axiom and
is available in v1.2.11-wso2v9
- https://wso2.org/jira/browse/CARBON-15223 - Seems the PR is
merged to 4.4.2 but the JIRA is not updated. @Kalpa can you please 
 update
this.
- https://wso2.org/jira/browse/CARBON-15184 - Available in 4.4.2
- https://wso2.org/jira/browse/CARBON-14730 - Available in 4.4.2
- https://wso2.org/jira/browse/CARBON-15248 - available in 4.5.0.
This contains API addition so it will be there in the 4.5.0 release[1].

 [1] - https://wso2.org/jira/browse/CARBON-15439
 [2] - Mail Subject : [Carbon-Kernel-4.4.2 Release] Patches from ESB
 4.9.0 release which are not in carbon-kernel-4.4.1


>>> Thanks a lot for looking into these issues.  I guess, we are good to
>>> proceed with this release.
>>>
 Regards,
 Nira

 On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri 
 wrote:

> Hi Manuri,
>
> We don't have an immediate requirement to have these fixes for ESB as
> 4.9 is already released. But these are missing patches and we need to at
> least make them blockers for the next release.
>
> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera  > wrote:
>
>> Hi Kasun,
>>
>> [1] is already fixed. Regarding [2], according to the comment in the
>> jira, the fix is available in [3].
>>
>> I suppose [4] also is fixed. @Ishara Could you please confirm ?
>>
>> Rest of the issues will be fixed in the next release.
>>
>>
>> [1] https://wso2.org/jira/browse/CARBON-15184
>> [2] https://wso2.org/jira/browse/CARBON-14730
>> [3] https://github.com/wso2/cipher-tool
>> [4] https://wso2.org/jira/browse/CARBON-14959
>>
>> Thank you.
>>
>> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri 
>> wrote:
>>
>>> We found that following fixes were missing in latest kernel release
>>> while doing ESB 4.9.
>>> Any plans to include them in this release.
>>>
>>> https://wso2.org/jira/browse/CARBON-14807
>>> https://wso2.org/jira/browse/CARBON-14959
>>> https://wso2.org/jira/browse/CARBON-14764
>>> https://wso2.org/jira/browse/CARBON-15248
>>> https://wso2.org/jira/browse/CARBON-15141
>>> https://wso2.org/jira/browse/CARBON-15223
>>> https://wso2.org/jira/browse/CARBON-15184
>>> https://wso2.org/jira/browse/CARBON-14730
>>> https://wso2.org/jira/browse/CARBON-15248
>>>
>>> On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera <
>>> manu...@wso2.com> wrote:
>>>
 Hi Devs,

 WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.

 This release fixes the following issues:
 https://wso2.org/jira/issues/?filter=12396

 Please download and test your products with kernel 4.4.2 RC1 and
 vote. Vote will be open for 72 hours or as longer as needed.

 *​Source and binary distribution files:*
 http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2

 *Maven staging repository:*
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
 

 *The tag to be voted upon:*
 https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[KasunG Gajasinghe]

On Tue, Sep 22, 2015 at 5:57 PM, Yasassri Ratnayake 
wrote:

> Hi All,
>
> After testing MB with Carbon 4.4.2 RC1 we still observed [1].
>
>
Ok. Is it a blocker? If so, can you explain why that's the case?


> [1] - https://wso2.org/jira/browse/MB-1326
>
> With Regards,
>
> On Tue, Sep 22, 2015 at 4:52 PM, KasunG Gajasinghe 
> wrote:
>
>> Hi Ramith,
>>
>> Is this a blocker for the release? [1]
>>
>> @All, please send your votes across asap to get this release done.
>>
>> [1] https://wso2.org/jira/browse/MB-1326
>>
>> Thanks.
>>
>> On Tue, Sep 22, 2015 at 11:33 AM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Kasun,
>>>
>>> On Tue, Sep 22, 2015 at 11:27 AM, Kasun Indrasiri 
>>> wrote:
>>>

 Hi Nira,

 On Tue, Sep 22, 2015 at 11:16 AM, Niranjan Karunanandham <
 niran...@wso2.com> wrote:

> Hi Kasun,
>
> I went through the JIRAs that was mentioned in the previous mail.
> Please see the comments below:
>
>-
>- https://wso2.org/jira/browse/CARBON-14807 - Patch is merged to
>4.4.0 branch, but as per the comment from Sandapa, the patch does not 
> solve
>the issue completely.
>
> So, then is that an ESB specific issue?

>>> We need to look into this to know where the issue is being created. I
>>> have re-opened the JIRA with the target version as 4.4.3 so that it is
>>> looked into before the next release.
>>>
>>>
>- https://wso2.org/jira/browse/CARBON-14959 - Available in 4.4.2
>- https://wso2.org/jira/browse/CARBON-14764 - Jira is directed to
>APIM. Therefore cloned the JIRA to Carbon to track it [1].
>- https://wso2.org/jira/browse/CARBON-15141 - Fix is to axiom and
>is available in v1.2.11-wso2v9
>- https://wso2.org/jira/browse/CARBON-15223 - Seems the PR is
>merged to 4.4.2 but the JIRA is not updated. @Kalpa can you please 
> update
>this.
>- https://wso2.org/jira/browse/CARBON-15184 - Available in 4.4.2
>- https://wso2.org/jira/browse/CARBON-14730 - Available in 4.4.2
>- https://wso2.org/jira/browse/CARBON-15248 - available in 4.5.0.
>This contains API addition so it will be there in the 4.5.0 release[1].
>
> [1] - https://wso2.org/jira/browse/CARBON-15439
> [2] - Mail Subject : [Carbon-Kernel-4.4.2 Release] Patches from ESB
> 4.9.0 release which are not in carbon-kernel-4.4.1
>
>
 Thanks a lot for looking into these issues.  I guess, we are good to
 proceed with this release.

> Regards,
> Nira
>
> On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri 
> wrote:
>
>> Hi Manuri,
>>
>> We don't have an immediate requirement to have these fixes for ESB as
>> 4.9 is already released. But these are missing patches and we need to at
>> least make them blockers for the next release.
>>
>> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera <
>> manu...@wso2.com> wrote:
>>
>>> Hi Kasun,
>>>
>>> [1] is already fixed. Regarding [2], according to the comment in the
>>> jira, the fix is available in [3].
>>>
>>> I suppose [4] also is fixed. @Ishara Could you please confirm ?
>>>
>>> Rest of the issues will be fixed in the next release.
>>>
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-15184
>>> [2] https://wso2.org/jira/browse/CARBON-14730
>>> [3] https://github.com/wso2/cipher-tool
>>> [4] https://wso2.org/jira/browse/CARBON-14959
>>>
>>> Thank you.
>>>
>>> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri 
>>> wrote:
>>>
 We found that following fixes were missing in latest kernel release
 while doing ESB 4.9.
 Any plans to include them in this release.

 https://wso2.org/jira/browse/CARBON-14807
 https://wso2.org/jira/browse/CARBON-14959
 https://wso2.org/jira/browse/CARBON-14764
 https://wso2.org/jira/browse/CARBON-15248
 https://wso2.org/jira/browse/CARBON-15141
 https://wso2.org/jira/browse/CARBON-15223
 https://wso2.org/jira/browse/CARBON-15184
 https://wso2.org/jira/browse/CARBON-14730
 https://wso2.org/jira/browse/CARBON-15248

 On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera <
 manu...@wso2.com> wrote:

> Hi Devs,
>
> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12396
>
> Please download and test your products with kernel 4.4.2 RC1 and
> vote. Vote will be open for 72 hours or as longer as needed.
>
> *​Source and binary distribution files:*
> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Indika Sampath]

Hi Kausn,

We had same issue [1] reported above by Yassasri [2] in carbon-kernel 4.4.0
with MySQL database. But it has fixed by Indunil [3] in carbon 4.4.x
branch. I was tested it in MySQL and didn't encounter issue. We build a
pack with carbon-kernel 4.4.2 RC1 tested with Oracle database. Now we are
observing same issue and we need to fixed it. Because this is a blocker for
MB. We couldn't add like more than 20 subscriptions at a same time to MB
due to this.

[1] https://wso2.org/jira/browse/MB-1128
[2] https://wso2.org/jira/browse/MB-1326
[3] https://wso2.org/jira/browse/IDENTITY-3423

Cheers!

On Tue, Sep 22, 2015 at 5:59 PM, KasunG Gajasinghe  wrote:

>
>
> On Tue, Sep 22, 2015 at 5:57 PM, Yasassri Ratnayake 
> wrote:
>
>> Hi All,
>>
>> After testing MB with Carbon 4.4.2 RC1 we still observed [1].
>>
>>
> Ok. Is it a blocker? If so, can you explain why that's the case?
>
>
>> [1] - https://wso2.org/jira/browse/MB-1326
>>
>> With Regards,
>>
>> On Tue, Sep 22, 2015 at 4:52 PM, KasunG Gajasinghe 
>> wrote:
>>
>>> Hi Ramith,
>>>
>>> Is this a blocker for the release? [1]
>>>
>>> @All, please send your votes across asap to get this release done.
>>>
>>> [1] https://wso2.org/jira/browse/MB-1326
>>>
>>> Thanks.
>>>
>>> On Tue, Sep 22, 2015 at 11:33 AM, Niranjan Karunanandham <
>>> niran...@wso2.com> wrote:
>>>
 Hi Kasun,

 On Tue, Sep 22, 2015 at 11:27 AM, Kasun Indrasiri 
 wrote:

>
> Hi Nira,
>
> On Tue, Sep 22, 2015 at 11:16 AM, Niranjan Karunanandham <
> niran...@wso2.com> wrote:
>
>> Hi Kasun,
>>
>> I went through the JIRAs that was mentioned in the previous mail.
>> Please see the comments below:
>>
>>-
>>- https://wso2.org/jira/browse/CARBON-14807 - Patch is merged to
>>4.4.0 branch, but as per the comment from Sandapa, the patch does not 
>> solve
>>the issue completely.
>>
>> So, then is that an ESB specific issue?
>
 We need to look into this to know where the issue is being created. I
 have re-opened the JIRA with the target version as 4.4.3 so that it is
 looked into before the next release.


>>- https://wso2.org/jira/browse/CARBON-14959 - Available in 4.4.2
>>- https://wso2.org/jira/browse/CARBON-14764 - Jira is directed to
>>APIM. Therefore cloned the JIRA to Carbon to track it [1].
>>- https://wso2.org/jira/browse/CARBON-15141 - Fix is to axiom and
>>is available in v1.2.11-wso2v9
>>- https://wso2.org/jira/browse/CARBON-15223 - Seems the PR is
>>merged to 4.4.2 but the JIRA is not updated. @Kalpa can you please 
>> update
>>this.
>>- https://wso2.org/jira/browse/CARBON-15184 - Available in 4.4.2
>>- https://wso2.org/jira/browse/CARBON-14730 - Available in 4.4.2
>>- https://wso2.org/jira/browse/CARBON-15248 - available in 4.5.0.
>>This contains API addition so it will be there in the 4.5.0 
>> release[1].
>>
>> [1] - https://wso2.org/jira/browse/CARBON-15439
>> [2] - Mail Subject : [Carbon-Kernel-4.4.2 Release] Patches from ESB
>> 4.9.0 release which are not in carbon-kernel-4.4.1
>>
>>
> Thanks a lot for looking into these issues.  I guess, we are good to
> proceed with this release.
>
>> Regards,
>> Nira
>>
>> On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri 
>> wrote:
>>
>>> Hi Manuri,
>>>
>>> We don't have an immediate requirement to have these fixes for ESB
>>> as 4.9 is already released. But these are missing patches and we need 
>>> to at
>>> least make them blockers for the next release.
>>>
>>> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera <
>>> manu...@wso2.com> wrote:
>>>
 Hi Kasun,

 [1] is already fixed. Regarding [2], according to the comment in
 the jira, the fix is available in [3].

 I suppose [4] also is fixed. @Ishara Could you please confirm ?

 Rest of the issues will be fixed in the next release.


 [1] https://wso2.org/jira/browse/CARBON-15184
 [2] https://wso2.org/jira/browse/CARBON-14730
 [3] https://github.com/wso2/cipher-tool
 [4] https://wso2.org/jira/browse/CARBON-14959

 Thank you.

 On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri 
 wrote:

> We found that following fixes were missing in latest kernel
> release while doing ESB 4.9.
> Any plans to include them in this release.
>
> https://wso2.org/jira/browse/CARBON-14807
> https://wso2.org/jira/browse/CARBON-14959
> https://wso2.org/jira/browse/CARBON-14764
> https://wso2.org/jira/browse/CARBON-15248
> https://wso2.org/jira/browse/CARBON-15141
> https://wso2.org/jira/browse/CARBON-15223
> https://wso2.org/jira/browse/CARBON-15184
>>>

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Kasun Gajasinghe]

> On Sep 22, 2015, at 6:19 PM, Indika Sampath  wrote:
> 
> Hi Kausn,
> 
> We had same issue [1] reported above by Yassasri [2] in carbon-kernel 4.4.0 
> with MySQL database. But it has fixed by Indunil [3] in carbon 4.4.x branch. 
> I was tested it in MySQL and didn't encounter issue. We build a pack with 
> carbon-kernel 4.4.2 RC1 tested with Oracle database. Now we are observing 
> same issue and we need to fixed it. Because this is a blocker for MB. We 
> couldn't add like more than 20 subscriptions at a same time to MB due to 
> this.  

Ok Indika. Who is working on this? Can you provide an ETA for the fix? This 
should be fixed in user core as I see. 

Thanks.  

> 
> [1] https://wso2.org/jira/browse/MB-1128
> [2] https://wso2.org/jira/browse/MB-1326
> [3] https://wso2.org/jira/browse/IDENTITY-3423
> 
> Cheers!
> 
>> On Tue, Sep 22, 2015 at 5:59 PM, KasunG Gajasinghe  wrote:
>> 
>> 
>>> On Tue, Sep 22, 2015 at 5:57 PM, Yasassri Ratnayake  
>>> wrote:
>>> Hi All,
>>> 
>>> After testing MB with Carbon 4.4.2 RC1 we still observed [1].
>>> 
>> 
>> Ok. Is it a blocker? If so, can you explain why that's the case?
>>  
>>> [1] - https://wso2.org/jira/browse/MB-1326
>>> 
>>> With Regards,
>>> 
 On Tue, Sep 22, 2015 at 4:52 PM, KasunG Gajasinghe  wrote:
 Hi Ramith,
 
 Is this a blocker for the release? [1]
 
 @All, please send your votes across asap to get this release done.
 
 [1] https://wso2.org/jira/browse/MB-1326
 
 Thanks.
 
> On Tue, Sep 22, 2015 at 11:33 AM, Niranjan Karunanandham 
>  wrote:
> Hi Kasun,
> 
>> On Tue, Sep 22, 2015 at 11:27 AM, Kasun Indrasiri  wrote:
>> 
>> Hi Nira, 
>> 
>>> On Tue, Sep 22, 2015 at 11:16 AM, Niranjan Karunanandham 
>>>  wrote:
>>> Hi Kasun,
>>> 
>>> I went through the JIRAs that was mentioned in the previous mail. 
>>> Please see the comments below:
>>> https://wso2.org/jira/browse/CARBON-14807 - Patch is merged to 4.4.0 
>>> branch, but as per the comment from Sandapa, the patch does not solve 
>>> the issue completely.
>> 
>> So, then is that an ESB specific issue?  
> 
> We need to look into this to know where the issue is being created. I 
> have re-opened the JIRA with the target version as 4.4.3 so that it is 
> looked into before the next release.
> 
>>> https://wso2.org/jira/browse/CARBON-14959 - Available in 4.4.2
>>> https://wso2.org/jira/browse/CARBON-14764 - Jira is directed to APIM. 
>>> Therefore cloned the JIRA to Carbon to track it [1].
>>> https://wso2.org/jira/browse/CARBON-15141 - Fix is to axiom and is 
>>> available in v1.2.11-wso2v9
>>> https://wso2.org/jira/browse/CARBON-15223 - Seems the PR is merged to 
>>> 4.4.2 but the JIRA is not updated. @Kalpa can you please update this.
>>> https://wso2.org/jira/browse/CARBON-15184 - Available in 4.4.2
>>> https://wso2.org/jira/browse/CARBON-14730 - Available in 4.4.2
>>> https://wso2.org/jira/browse/CARBON-15248 - available in 4.5.0. This 
>>> contains API addition so it will be there in the 4.5.0 release[1]. 
>>> [1] - https://wso2.org/jira/browse/CARBON-15439
>>> [2] - Mail Subject : [Carbon-Kernel-4.4.2 Release] Patches from ESB 
>>> 4.9.0 release which are not in carbon-kernel-4.4.1
>>> 
>> 
>> Thanks a lot for looking into these issues.  I guess, we are good to 
>> proceed with this release. 
>>> Regards,
>>> Nira
>>> 
 On Fri, Sep 18, 2015 at 2:47 PM, Kasun Indrasiri  
 wrote:
>>> 
 Hi Manuri, 
 
 We don't have an immediate requirement to have these fixes for ESB as 
 4.9 is already released. But these are missing patches and we need to 
 at least make them blockers for the next release. 
 
> On Fri, Sep 18, 2015 at 2:32 PM, Manuri Amaya Perera 
>  wrote:
> Hi Kasun,
> 
> [1] is already fixed. Regarding [2], according to the comment in the 
> jira, the fix is available in [3].
> 
> I suppose [4] also is fixed. @Ishara Could you please confirm ?
> 
> Rest of the issues will be fixed in the next release.
> 
> 
> [1] https://wso2.org/jira/browse/CARBON-15184
> [2] https://wso2.org/jira/browse/CARBON-14730
> [3] https://github.com/wso2/cipher-tool
> [4] https://wso2.org/jira/browse/CARBON-14959
> 
> Thank you.
> 
>> On Fri, Sep 18, 2015 at 7:39 AM, Kasun Indrasiri  
>> wrote:
>> We found that following fixes were missing in latest kernel release 
>> while doing ESB 4.9. 
>> Any plans to include them in this release. 
>> 
>> https://wso2.org/jira/browse/CARBON-14807
>> https://wso2.org/jira/browse/CARBON-14959
>> https://wso2.org/jira/browse/CARBON-14764
>> https://wso2.org/jira/browse/CA

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Indunil Upeksha Rathnayake]

Hi Kasun,

I'll work on the issue and provide a fix ASAP. The ETA for the fix is as
follows.
Best Case Estimate: 24/09/2015
Most Likely Estimate: 25/09/2015
Worst Case Estimate: 26/09/2015

Thanks and Regards
 --
Indunil Upeksha Rathnayake
Software Engineer | WSO2 Inc
Emailindu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Indika Sampath]

Hi All,

[X] - Broken since user core is not working for message broker multiple
subscription use-cases.

Cheers!

On Wed, Sep 23, 2015 at 10:16 AM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

> Hi Kasun,
>
> I'll work on the issue and provide a fix ASAP. The ETA for the fix is as
> follows.
> Best Case Estimate: 24/09/2015
> Most Likely Estimate: 25/09/2015
> Worst Case Estimate: 26/09/2015
>
> Thanks and Regards
>  --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
>



-- 
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Manuri Amaya Perera]

Hi all,

We are calling this vote off due to the above discussed issue in MB and
 will start a new vote for Kernel 4.4.2 RC2 release.

Thank you.

On Thu, Sep 17, 2015 at 6:55 PM, Manuri Amaya Perera 
wrote:

> Hi Devs,
>
> WSO2 Carbon Kernel 4.4.2 RC1 Release Vote.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12396
>
> Please download and test your products with kernel 4.4.2 RC1 and vote.
> Vote will be open for 72 hours or as longer as needed.
>
> *​Source and binary distribution files:*
> http://svn.wso2.org/repos/wso2/people/sameera/work/carbon-4.4.2
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-109/
> 
>
> *The tag to be voted upon:*
> https://github.com/wso2/carbon4-kernel/tree/v4.4.2-rc1
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
>
> Thank you
> Carbon Team
>
> ​
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>



-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Niranjan Karunanandham]

Hi Indunil / Indika,

Can you clone the MB JIRA for this to Carbon JIRA with the target version
as 4.4.2 with the priority as L1? Also does this issue happen with other
DBs such as mssql, psotgre, etc... ? If so, should it be also addressed?

Regards,
Nira

On Wed, Sep 23, 2015 at 10:57 AM, Indika Sampath  wrote:

> Hi All,
>
> [X] - Broken since user core is not working for message broker multiple
> subscription use-cases.
>
> Cheers!
>
> On Wed, Sep 23, 2015 at 10:16 AM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi Kasun,
>>
>> I'll work on the issue and provide a fix ASAP. The ETA for the fix is as
>> follows.
>> Best Case Estimate: 24/09/2015
>> Most Likely Estimate: 25/09/2015
>> Worst Case Estimate: 26/09/2015
>>
>> Thanks and Regards
>>  --
>> Indunil Upeksha Rathnayake
>> Software Engineer | WSO2 Inc
>> Emailindu...@wso2.com
>>
>
>
>
> --
> Indika Sampath
> Senior Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 716 424 744
> Blog: http://indikasampath.blogspot.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Jason De Silva]

Hi Niranjan,

We were able to continuously reproduce this issue in MSSQL and Oracle.

With Regards,

On Wed, Sep 23, 2015 at 5:08 PM, Niranjan Karunanandham 
wrote:

> Hi Indunil / Indika,
>
> Can you clone the MB JIRA for this to Carbon JIRA with the target version
> as 4.4.2 with the priority as L1? Also does this issue happen with other
> DBs such as mssql, psotgre, etc... ? If so, should it be also addressed?
>
> Regards,
> Nira
>
> On Wed, Sep 23, 2015 at 10:57 AM, Indika Sampath  wrote:
>
>> Hi All,
>>
>> [X] - Broken since user core is not working for message broker multiple
>> subscription use-cases.
>>
>> Cheers!
>>
>> On Wed, Sep 23, 2015 at 10:16 AM, Indunil Upeksha Rathnayake <
>> indu...@wso2.com> wrote:
>>
>>> Hi Kasun,
>>>
>>> I'll work on the issue and provide a fix ASAP. The ETA for the fix is as
>>> follows.
>>> Best Case Estimate: 24/09/2015
>>> Most Likely Estimate: 25/09/2015
>>> Worst Case Estimate: 26/09/2015
>>>
>>> Thanks and Regards
>>>  --
>>> Indunil Upeksha Rathnayake
>>> Software Engineer | WSO2 Inc
>>> Emailindu...@wso2.com
>>>
>>
>>
>>
>> --
>> Indika Sampath
>> Senior Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Phone: +94 716 424 744
>> Blog: http://indikasampath.blogspot.com/
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Jason De Silva
*Software Engineer - QA*
Mobile: +94 (0) 772 097 678
Email: jas...@wso2.com
WSO2 Inc. www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Johann Nallathamby]

Created Carbon JIRA: https://wso2.org/jira/browse/CARBON-15446

On Wed, Sep 23, 2015 at 5:08 PM, Niranjan Karunanandham 
wrote:

> Hi Indunil / Indika,
>
> Can you clone the MB JIRA for this to Carbon JIRA with the target version
> as 4.4.2 with the priority as L1? Also does this issue happen with other
> DBs such as mssql, psotgre, etc... ? If so, should it be also addressed?
>
> Regards,
> Nira
>
> On Wed, Sep 23, 2015 at 10:57 AM, Indika Sampath  wrote:
>
>> Hi All,
>>
>> [X] - Broken since user core is not working for message broker multiple
>> subscription use-cases.
>>
>> Cheers!
>>
>> On Wed, Sep 23, 2015 at 10:16 AM, Indunil Upeksha Rathnayake <
>> indu...@wso2.com> wrote:
>>
>>> Hi Kasun,
>>>
>>> I'll work on the issue and provide a fix ASAP. The ETA for the fix is as
>>> follows.
>>> Best Case Estimate: 24/09/2015
>>> Most Likely Estimate: 25/09/2015
>>> Worst Case Estimate: 26/09/2015
>>>
>>> Thanks and Regards
>>>  --
>>> Indunil Upeksha Rathnayake
>>> Software Engineer | WSO2 Inc
>>> Emailindu...@wso2.com
>>>
>>
>>
>>
>> --
>> Indika Sampath
>> Senior Software Engineer
>> WSO2 Inc.
>> http://wso2.com
>>
>> Phone: +94 716 424 744
>> Blog: http://indikasampath.blogspot.com/
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of 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

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Niranjan Karunanandham]

Thanks Johann.

On Wed, Sep 23, 2015 at 11:37 PM, Johann Nallathamby 
wrote:

> Created Carbon JIRA: https://wso2.org/jira/browse/CARBON-15446
>
> On Wed, Sep 23, 2015 at 5:08 PM, Niranjan Karunanandham  > wrote:
>
>> Hi Indunil / Indika,
>>
>> Can you clone the MB JIRA for this to Carbon JIRA with the target version
>> as 4.4.2 with the priority as L1? Also does this issue happen with other
>> DBs such as mssql, psotgre, etc... ? If so, should it be also addressed?
>>
>> Regards,
>> Nira
>>
>> On Wed, Sep 23, 2015 at 10:57 AM, Indika Sampath 
>> wrote:
>>
>>> Hi All,
>>>
>>> [X] - Broken since user core is not working for message broker multiple
>>> subscription use-cases.
>>>
>>> Cheers!
>>>
>>> On Wed, Sep 23, 2015 at 10:16 AM, Indunil Upeksha Rathnayake <
>>> indu...@wso2.com> wrote:
>>>
 Hi Kasun,

 I'll work on the issue and provide a fix ASAP. The ETA for the fix is
 as follows.
 Best Case Estimate: 24/09/2015
 Most Likely Estimate: 25/09/2015
 Worst Case Estimate: 26/09/2015

 Thanks and Regards
  --
 Indunil Upeksha Rathnayake
 Software Engineer | WSO2 Inc
 Emailindu...@wso2.com

>>>
>>>
>>>
>>> --
>>> Indika Sampath
>>> Senior Software Engineer
>>> WSO2 Inc.
>>> http://wso2.com
>>>
>>> Phone: +94 716 424 744
>>> Blog: http://indikasampath.blogspot.com/
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>



-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Indunil Upeksha Rathnayake]

Hi,

The deadlock issue(https://wso2.org/jira/browse/MB-1326) come up in oracle
and mssql when clearResourceAuthorizations where permissions are deleted in
UM_ROLE_PERMISSIONS, UM_USER_PERMISSIONS and UM_PERMISSION tables through
one transaction. The fix would be using cascade delete for above tables.

But I think another issue(foreign key constraint violation) may come up
when addAuthorizationForRole, as following example scenario. Ex: Node1 may
be retrieve the permission entry in UM_PERMISSION table (in
addAuthorizationForRole()) and just after that node2 may delete the entry
(in clearResourceAuthorizations()) and after that when node1 trying to
delete & add permissions in UM_ROLE_PERMISSIONS (in
addAuthorizationForRole()) will return the above exception since the entry
in UM_PERMISSION is already deleted.
I think the fix need to be, if UM_ROLE_PERMISSIONS and UM_PERMISSION tables
are going to update, first have to lock both tables, until all the required
operations are finished. Then meanwhile another node can't delete any
entries.

Please provide your opinions regarding this.

Thanks and Regards
-- 
Indunil Upeksha Rathnayake
Software Engineer | WSO2 Inc
Emailindu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Darshana Gunawardana]

Hi Indunil,

On Fri, Sep 25, 2015 at 10:15 AM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

> Hi,
>
> The deadlock issue(https://wso2.org/jira/browse/MB-1326) come up in
> oracle and mssql when clearResourceAuthorizations where permissions are
> deleted in UM_ROLE_PERMISSIONS, UM_USER_PERMISSIONS and UM_PERMISSION
> tables through one transaction. The fix would be using cascade delete for
> above tables.
>

+1


> But I think another issue(foreign key constraint violation) may come up
> when addAuthorizationForRole, as following example scenario. Ex: Node1 may
> be retrieve the permission entry in UM_PERMISSION table (in
> addAuthorizationForRole()) and just after that node2 may delete the entry
> (in clearResourceAuthorizations()) and after that when node1 trying to
> delete & add permissions in UM_ROLE_PERMISSIONS (in
> addAuthorizationForRole()) will return the above exception since the entry
> in UM_PERMISSION is already deleted.
>
I think the fix need to be, if UM_ROLE_PERMISSIONS and UM_PERMISSION tables
> are going to update, first have to lock both tables, until all the required
> operations are finished. Then meanwhile another node can't delete any
> entries.
>

Have you able to reproduce this behavior? I guess we cannot lock those
tables from the java code in db in dependent manner. Please check with our
db experts.

In worst case we could handle IntegrityConstraintViolationException since
its ok to avoiding addAuthorization for a permission which got deleted
later.

Thanks,


> Please provide your opinions regarding this.
>
> Thanks and Regards
> --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
>



-- 
Regards,


*Darshana Gunawardana*Senior Software Engineer
WSO2 Inc.; http://wso2.com

*E-mail: darsh...@wso2.com *
*Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Johann Nallathamby]

On Fri, Sep 25, 2015 at 11:16 AM, Darshana Gunawardana 
wrote:

> Hi Indunil,
>
> On Fri, Sep 25, 2015 at 10:15 AM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>>
>> The deadlock issue(https://wso2.org/jira/browse/MB-1326) come up in
>> oracle and mssql when clearResourceAuthorizations where permissions are
>> deleted in UM_ROLE_PERMISSIONS, UM_USER_PERMISSIONS and UM_PERMISSION
>> tables through one transaction. The fix would be using cascade delete for
>> above tables.
>>
>
> +1
>
>
>> But I think another issue(foreign key constraint violation) may come up
>> when addAuthorizationForRole, as following example scenario. Ex: Node1 may
>> be retrieve the permission entry in UM_PERMISSION table (in
>> addAuthorizationForRole()) and just after that node2 may delete the entry
>> (in clearResourceAuthorizations()) and after that when node1 trying to
>> delete & add permissions in UM_ROLE_PERMISSIONS (in
>> addAuthorizationForRole()) will return the above exception since the entry
>> in UM_PERMISSION is already deleted.
>>
> I think the fix need to be, if UM_ROLE_PERMISSIONS and UM_PERMISSION
>> tables are going to update, first have to lock both tables, until all the
>> required operations are finished. Then meanwhile another node can't delete
>> any entries.
>>
>
> Have you able to reproduce this behavior? I guess we cannot lock those
> tables from the java code in db in dependent manner. Please check with our
> db experts.
>
> In worst case we could handle IntegrityConstraintViolationException since
> its ok to avoiding addAuthorization for a permission which got deleted
> later.
>

Yes, lets not go into locking tables. As much as possible try to avoid it
or recover gracefully.

>
> Thanks,
>
>
>> Please provide your opinions regarding this.
>>
>> Thanks and Regards
>> --
>> Indunil Upeksha Rathnayake
>> Software Engineer | WSO2 Inc
>> Emailindu...@wso2.com
>>
>
>
>
> --
> Regards,
>
>
> *Darshana Gunawardana*Senior Software Engineer
> WSO2 Inc.; http://wso2.com
>
> *E-mail: darsh...@wso2.com *
> *Mobile: +94718566859 <%2B94718566859>*Lean . Enterprise . Middleware
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of 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

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Ramith Jayasinghe]

Hi,
If you are hoping to handle/catch
'IntegrityConstraintViolationException' consider following:

'IntegrityConstraintViolationException' is only thrown in Oracle and
mysql database drivers ( check their driver source code and you will
see). from what I know MSSQL drivers doesn't throw these. I have seen
similar approach has been adapted in Hibernate (ORM) framework code as
well.

therefore, if you go down this path you need to check SQLState [1].
You might find[2] useful as reference.

[1] 
http://docs.oracle.com/javase/7/docs/api/java/sql/SQLException.html#getSQLState()
[2] 
https://github.com/wso2/andes/blob/master/modules/andes-core/broker/src/main/java/org/wso2/andes/store/rdbms/RDBMSStoreUtils.java#115

On Fri, Sep 25, 2015 at 11:16 AM, Darshana Gunawardana
 wrote:
> Hi Indunil,
>
> On Fri, Sep 25, 2015 at 10:15 AM, Indunil Upeksha Rathnayake
>  wrote:
>>
>> Hi,
>>
>> The deadlock issue(https://wso2.org/jira/browse/MB-1326) come up in oracle
>> and mssql when clearResourceAuthorizations where permissions are deleted in
>> UM_ROLE_PERMISSIONS, UM_USER_PERMISSIONS and UM_PERMISSION tables through
>> one transaction. The fix would be using cascade delete for above tables.
>
>
> +1
>
>>
>> But I think another issue(foreign key constraint violation) may come up
>> when addAuthorizationForRole, as following example scenario. Ex: Node1 may
>> be retrieve the permission entry in UM_PERMISSION table (in
>> addAuthorizationForRole()) and just after that node2 may delete the entry
>> (in clearResourceAuthorizations()) and after that when node1 trying to
>> delete & add permissions in UM_ROLE_PERMISSIONS (in
>> addAuthorizationForRole()) will return the above exception since the entry
>> in UM_PERMISSION is already deleted.
>>
>> I think the fix need to be, if UM_ROLE_PERMISSIONS and UM_PERMISSION
>> tables are going to update, first have to lock both tables, until all the
>> required operations are finished. Then meanwhile another node can't delete
>> any entries.
>
>
> Have you able to reproduce this behavior? I guess we cannot lock those
> tables from the java code in db in dependent manner. Please check with our
> db experts.
>
> In worst case we could handle IntegrityConstraintViolationException since
> its ok to avoiding addAuthorization for a permission which got deleted
> later.
>
> Thanks,
>
>>
>> Please provide your opinions regarding this.
>>
>> Thanks and Regards
>> --
>> Indunil Upeksha Rathnayake
>> Software Engineer | WSO2 Inc
>> Emailindu...@wso2.com
>
>
>
>
> --
> Regards,
>
> Darshana Gunawardana
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> E-mail: darsh...@wso2.com
> Mobile: +94718566859
> Lean . Enterprise . Middleware



-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Sasikala Kottegoda]

Hi all,

We applied the patch given by Indunil which had cascade delete on the
tables. However, it gave a dead lock in 'DELETE FROM UM_PERMISSION WHERE
UM_RESOURCE_ID = ? AND UM_TENANT_ID=?' and 'DELETE FROM UM_HYBRID_ROLE
WHERE UM_ROLE_NAME = ? AND UM_TENANT_ID=?'(The stack trace is attached).
Following are the code lines which give the error:

dbConnection = DatabaseUtil.getDBConnection(this.dataSource);

DatabaseUtil.updateDatabase(dbConnection, "DELETE FROM UM_HYBRID_ROLE
WHERE UM_ROLE_NAME = ? AND UM_TENANT_ID=?", new Object[]{roleName,
Integer.valueOf(this.tenantId)});
dbConnection.commit();

and

dbConnection1 = this.getDBConnection();

DatabaseUtil.updateDatabase(dbConnection1, "DELETE FROM UM_PERMISSION
WHERE UM_RESOURCE_ID = ? AND UM_TENANT_ID=?", new Object[]{resourceId,
Integer.valueOf(this.tenantId)});

this.permissionTree.clearResourceAuthorizations(resourceId);
dbConnection1.commit();


Also when I looked at the script, I found out the following
information regarding foreign key relationships:


   1. UM_ROLE_PERMISSION has 2 parent tables, UM_PERMISSION and UM_DOMAIN
   2. UM_HYBRID_USER_ROLE has 2 parent tables, UM HYBRID_ROLE and UM_DOMAIN


One possible reason for the deadlock is if oracle locks the parent
table when deleting from a child table. A similar issue is reported
at[1]

[1] 
http://stackoverflow.com/questions/9373843/meet-deadlock-when-deleting-different-records-from-same-table-in-different-trans


On Fri, Sep 25, 2015 at 1:06 PM, Ramith Jayasinghe  wrote:

> Hi,
> If you are hoping to handle/catch
> 'IntegrityConstraintViolationException' consider following:
>
> 'IntegrityConstraintViolationException' is only thrown in Oracle and
> mysql database drivers ( check their driver source code and you will
> see). from what I know MSSQL drivers doesn't throw these. I have seen
> similar approach has been adapted in Hibernate (ORM) framework code as
> well.
>
> therefore, if you go down this path you need to check SQLState [1].
> You might find[2] useful as reference.
>
> [1]
> http://docs.oracle.com/javase/7/docs/api/java/sql/SQLException.html#getSQLState()
> [2]
> https://github.com/wso2/andes/blob/master/modules/andes-core/broker/src/main/java/org/wso2/andes/store/rdbms/RDBMSStoreUtils.java#115
>
> On Fri, Sep 25, 2015 at 11:16 AM, Darshana Gunawardana
>  wrote:
> > Hi Indunil,
> >
> > On Fri, Sep 25, 2015 at 10:15 AM, Indunil Upeksha Rathnayake
> >  wrote:
> >>
> >> Hi,
> >>
> >> The deadlock issue(https://wso2.org/jira/browse/MB-1326) come up in
> oracle
> >> and mssql when clearResourceAuthorizations where permissions are
> deleted in
> >> UM_ROLE_PERMISSIONS, UM_USER_PERMISSIONS and UM_PERMISSION tables
> through
> >> one transaction. The fix would be using cascade delete for above tables.
> >
> >
> > +1
> >
> >>
> >> But I think another issue(foreign key constraint violation) may come up
> >> when addAuthorizationForRole, as following example scenario. Ex: Node1
> may
> >> be retrieve the permission entry in UM_PERMISSION table (in
> >> addAuthorizationForRole()) and just after that node2 may delete the
> entry
> >> (in clearResourceAuthorizations()) and after that when node1 trying to
> >> delete & add permissions in UM_ROLE_PERMISSIONS (in
> >> addAuthorizationForRole()) will return the above exception since the
> entry
> >> in UM_PERMISSION is already deleted.
> >>
> >> I think the fix need to be, if UM_ROLE_PERMISSIONS and UM_PERMISSION
> >> tables are going to update, first have to lock both tables, until all
> the
> >> required operations are finished. Then meanwhile another node can't
> delete
> >> any entries.
> >
> >
> > Have you able to reproduce this behavior? I guess we cannot lock those
> > tables from the java code in db in dependent manner. Please check with
> our
> > db experts.
> >
> > In worst case we could handle IntegrityConstraintViolationException since
> > its ok to avoiding addAuthorization for a permission which got deleted
> > later.
> >
> > Thanks,
> >
> >>
> >> Please provide your opinions regarding this.
> >>
> >> Thanks and Regards
> >> --
> >> Indunil Upeksha Rathnayake
> >> Software Engineer | WSO2 Inc
> >> Emailindu...@wso2.com
> >
> >
> >
> >
> > --
> > Regards,
> >
> > Darshana Gunawardana
> > Senior Software Engineer
> > WSO2 Inc.; http://wso2.com
> > E-mail: darsh...@wso2.com
> > Mobile: +94718566859
> > Lean . Enterprise . Middleware
>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851
>



-- 
Sasikala Kottegoda
*Software Engineer*
WSO2 Inc., http://wso2.com/
lean. enterprise. middleware
Mobile: +94 774835928/712792401


ORA-00060_
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Manuri Amaya Perera]

Hi Indunil,

Could you please give an update on the status of the issue.

Thank you.

On Wed, Sep 23, 2015 at 10:16 AM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

> Hi Kasun,
>
> I'll work on the issue and provide a fix ASAP. The ETA for the fix is as
> follows.
> Best Case Estimate: 24/09/2015
> Most Likely Estimate: 25/09/2015
> Worst Case Estimate: 26/09/2015
>
> Thanks and Regards
>  --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Indunil Upeksha Rathnayake]

Hi Manuri,

The fix is done, it works for oracle and currently testing for mssql. Soon
after testing for mssql finishes, will commit the changes to master and
4.4.x branches.

Thanks and Regards
-- 
Indunil Upeksha Rathnayake
Software Engineer | WSO2 Inc
Emailindu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Manuri Amaya Perera]

Okay. Thank you Indunil.

On Mon, Sep 28, 2015 at 12:12 PM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:

> Hi Manuri,
>
> The fix is done, it works for oracle and currently testing for mssql. Soon
> after testing for mssql finishes, will commit the changes to master and
> 4.4.x branches.
>
> Thanks and Regards
> --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
>



-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Manuri Amaya Perera]

Hi Indunil,

As I understand, "FOREIGN KEY constraint violation" issue is a regression
issue therefore the deadlock issue cannot be resolved until foreign key
constraint violation issue is fixed, right?

Thank you.

On Thu, Oct 1, 2015 at 2:01 PM, Indunil Upeksha Rathnayake  wrote:

> Hi,
> The deadlock issue in https://wso2.org/jira/browse/MB-1326 is resolved in
> both oracle 12c and 11g r2. (Please refer previous mails in this mail
> thread to get the idea of the issue). Then after a "FOREIGN KEY constraint
> violation" issue occurred in both mssql and oracle, intermittently (Refer
> the attached file "errorLog_foriegnKeyViolation" for the error log). For
> that, issued the fix in https://github.com/wso2/carbon-kernel/pull/512,
> and it worked for oracle, but not for mssql. This is tested in following
> scenarios in MB cluster.
>
> 1. 5 queues - 5 subscribers and 5 consumers ( 1 publisher and 1 consumer
> each )
> 2. 5 Topics - 5 subscribers and 5 consumers ( in mssql, it breaks for this
> scenario)
> 3. 100 topics - 100 publishers and 100 consumers ( 1 publisher and 1
> consumer each )
> 4. 1 topic - 100 subscribers / 100 consumers
> 5. Mixed scenario where multiple queues, topics and durable topics are used
>
> I have attached all the debug logs here. Please consider this matter and
> provide your feedbacks on resolving this.
>
> Thanks and Regards
> --
> Indunil Upeksha Rathnayake
> Software Engineer | WSO2 Inc
> Emailindu...@wso2.com
>
>


-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Johann Nallathamby]

Hi All,

We had a discussion involving MB team members and IS team members.

Summary of the discussion:

Possibility of deadlocks occurring have drastically reduced in MySQL and
Oracle with the patches given so far and tested with high levels of
concurrency. Only MSSQL gives deadlocks and that too for very small
concurrency levels. In our experience we have in fact encountered several
deadlocking issues with MSSQL setups previously also in certain other
scenarios, and had to move to a non DB solution.

At this moment we have fixed the code level issues which we have found so
far. Beyond this it may be hard to find issues at code level. The fixes
done so far also, doesn't completely eliminate the possibility of a
deadlock; they only reduce it to a large extent, but that level doesn't
seem to be enough for MSSQL. From our side we will look into profiling this
use case on MSSQL server.

If we are to completely eliminate deadlocking we will have to lock the
tables which we haven't done as a practice because it will drastically
reduce performance. Other option available is for the MB code to recover
from the specific exception by retrying.

However during the discussion there were several problems raised regarding
implementation of topics.

MB uses internal roles and permissions in user kernel to authorize access
to Topics and Queues.

First we figured out that permission (resource + action) are being created
for each subscription (queues or topics). And for each subscription an
internal role is also being created. The creation of permission seems
redundant, because the resource name actually has a one-to-one
correspondence with the role name (resource name can be derived from role
name), and action can contain only 3 values, publish, subscribe and
changePermission. Every time a new subscription is added a new role and 3
new permissions are added for that subscription which is unwanted overhead.
Every time a subscription is deleted the corresponding role and 3
permissions are deleted. In a high load scenario there are many DB calls
going on which effects performance drastically.

In this case what we discussed with Indika is that, the permissions can be
fixed to publish, subscribe and changePermission; they can be added
through component.xml and will appear in the permission tree as well. Only
the internal role can be created and those 3 permissions assigned. This way
we are adding and deleting the internal role only and not doing any
operations to the UM_PERMISSION  table which will reduce a lot of DB calls.

The problem happens only for topics and not for queues, because in queues
you don't seem to be creating roles or permissions per subscription. But
for topics you do that and that seems to be executing huge amount of DB
calls on the user-mgt tables to add and remove roles and permissions.

Further when we discussed we also pointed out that creating an internal
role per topic subscription is an unwanted overhead. Normally we create
roles if we are going to assign a set of users to it. Using internal roles
for queues seems correct. The use case requires users other than the
subscriber to be added to the role for that topic. In case of topics, as
per the implementation, you create a role per subscription (internally
create a temp queue) and and assign the subscriber to it. As per Indika and
Hasitha there is no use case to assign other users to it. The only
requirement is to keep track of the user who subscribed to that temp queue.
In this case creating a role as well as 3 permissions for it is
unnecessary. You can just keep the name of the user along with the
subscription/temp queue name in the metadata table that MB has.

Please look into these options. As per IS team's understanding improvements
along these lines will give a substantial improvement. We can help you in
implementing these changes.

Regards,
Johann.



On Thu, Oct 1, 2015 at 2:36 PM, Manuri Amaya Perera 
wrote:

> Hi Indunil,
>
> As I understand, "FOREIGN KEY constraint violation" issue is a regression
> issue therefore the deadlock issue cannot be resolved until foreign key
> constraint violation issue is fixed, right?
>
> Thank you.
>
> On Thu, Oct 1, 2015 at 2:01 PM, Indunil Upeksha Rathnayake <
> indu...@wso2.com> wrote:
>
>> Hi,
>> The deadlock issue in https://wso2.org/jira/browse/MB-1326 is resolved
>> in both oracle 12c and 11g r2. (Please refer previous mails in this mail
>> thread to get the idea of the issue). Then after a "FOREIGN KEY constraint
>> violation" issue occurred in both mssql and oracle, intermittently (Refer
>> the attached file "errorLog_foriegnKeyViolation" for the error log). For
>> that, issued the fix in https://github.com/wso2/carbon-kernel/pull/512,
>> and it worked for oracle, but not for mssql. This is tested in following
>> scenarios in MB cluster.
>>
>> 1. 5 queues - 5 subscribers and 5 consumers ( 1 publisher and 1 consumer
>> each )
>> 2. 5 Topics - 5 subscribers and 5 consumers ( in mssql, it breaks for
>

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Indika Sampath]

Hi Johann,

I have avoid creating role for each tmp queue when subscription adding to
non durable topic. Now we only create one internal role by topic name and
assign subscribe, publish and changePermission. Please find the PR [1]. We
have build a MB 3.0.0-SNAPSHOT pack with all latest changes including PR
[1] and check again with MSSQL. But we still encounter same dead-lock
issue. We are only adding 5 subscription at once. We have 2 node cluster
setup. Just add 2 subscription to node1 and 3 subscription to node2. It
seems root cause is not because of creating tmp role for each subscription.
Now we are adding patch given by Indunil, and check whether it resolve the
issue and update mail.

[1] https://github.com/wso2/carbon-business-messaging/pull/170

Cheers!

On Fri, Oct 2, 2015 at 5:08 PM, Johann Nallathamby  wrote:

> Hi All,
>
> We had a discussion involving MB team members and IS team members.
>
> Summary of the discussion:
>
> Possibility of deadlocks occurring have drastically reduced in MySQL and
> Oracle with the patches given so far and tested with high levels of
> concurrency. Only MSSQL gives deadlocks and that too for very small
> concurrency levels. In our experience we have in fact encountered several
> deadlocking issues with MSSQL setups previously also in certain other
> scenarios, and had to move to a non DB solution.
>
> At this moment we have fixed the code level issues which we have found so
> far. Beyond this it may be hard to find issues at code level. The fixes
> done so far also, doesn't completely eliminate the possibility of a
> deadlock; they only reduce it to a large extent, but that level doesn't
> seem to be enough for MSSQL. From our side we will look into profiling this
> use case on MSSQL server.
>
> If we are to completely eliminate deadlocking we will have to lock the
> tables which we haven't done as a practice because it will drastically
> reduce performance. Other option available is for the MB code to recover
> from the specific exception by retrying.
>
> However during the discussion there were several problems raised regarding
> implementation of topics.
>
> MB uses internal roles and permissions in user kernel to authorize access
> to Topics and Queues.
>
> First we figured out that permission (resource + action) are being created
> for each subscription (queues or topics). And for each subscription an
> internal role is also being created. The creation of permission seems
> redundant, because the resource name actually has a one-to-one
> correspondence with the role name (resource name can be derived from role
> name), and action can contain only 3 values, publish, subscribe and
> changePermission. Every time a new subscription is added a new role and 3
> new permissions are added for that subscription which is unwanted overhead.
> Every time a subscription is deleted the corresponding role and 3
> permissions are deleted. In a high load scenario there are many DB calls
> going on which effects performance drastically.
>
> In this case what we discussed with Indika is that, the permissions can be
> fixed to publish, subscribe and changePermission; they can be added
> through component.xml and will appear in the permission tree as well. Only
> the internal role can be created and those 3 permissions assigned. This way
> we are adding and deleting the internal role only and not doing any
> operations to the UM_PERMISSION  table which will reduce a lot of DB calls.
>
> The problem happens only for topics and not for queues, because in queues
> you don't seem to be creating roles or permissions per subscription. But
> for topics you do that and that seems to be executing huge amount of DB
> calls on the user-mgt tables to add and remove roles and permissions.
>
> Further when we discussed we also pointed out that creating an internal
> role per topic subscription is an unwanted overhead. Normally we create
> roles if we are going to assign a set of users to it. Using internal roles
> for queues seems correct. The use case requires users other than the
> subscriber to be added to the role for that topic. In case of topics, as
> per the implementation, you create a role per subscription (internally
> create a temp queue) and and assign the subscriber to it. As per Indika and
> Hasitha there is no use case to assign other users to it. The only
> requirement is to keep track of the user who subscribed to that temp queue.
> In this case creating a role as well as 3 permissions for it is
> unnecessary. You can just keep the name of the user along with the
> subscription/temp queue name in the metadata table that MB has.
>
> Please look into these options. As per IS team's understanding
> improvements along these lines will give a substantial improvement. We can
> help you in implementing these changes.
>
> Regards,
> Johann.
>
>
>
> On Thu, Oct 1, 2015 at 2:36 PM, Manuri Amaya Perera 
> wrote:
>
>> Hi Indunil,
>>
>> As I understand, "FOREIGN KEY constraint violation" issu

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Rajith Vitharana]

Hi,

This issue is blocking DSS 3.5.0 release as well, We need kernel 4.4.2 for
the DSS 3.5.0 as we can't use kernel 4.4.1(which has a bug in axis2json)
for now we are using kernel 4.4.0 but we can't use that for the final
release due to version incompatibilities, for example we can't install DSS
features in ESB 4.9.0 if we use kernel 4.4.0. Appreciate if we can solve
this issue ASAP

Thanks,

On Fri, Oct 2, 2015 at 5:36 PM, Indika Sampath  wrote:

> Hi Johann,
>
> I have avoid creating role for each tmp queue when subscription adding to
> non durable topic. Now we only create one internal role by topic name and
> assign subscribe, publish and changePermission. Please find the PR [1]. We
> have build a MB 3.0.0-SNAPSHOT pack with all latest changes including PR
> [1] and check again with MSSQL. But we still encounter same dead-lock
> issue. We are only adding 5 subscription at once. We have 2 node cluster
> setup. Just add 2 subscription to node1 and 3 subscription to node2. It
> seems root cause is not because of creating tmp role for each subscription.
> Now we are adding patch given by Indunil, and check whether it resolve the
> issue and update mail.
>
> [1] https://github.com/wso2/carbon-business-messaging/pull/170
>
> Cheers!
>
> On Fri, Oct 2, 2015 at 5:08 PM, Johann Nallathamby 
> wrote:
>
>> Hi All,
>>
>> We had a discussion involving MB team members and IS team members.
>>
>> Summary of the discussion:
>>
>> Possibility of deadlocks occurring have drastically reduced in MySQL and
>> Oracle with the patches given so far and tested with high levels of
>> concurrency. Only MSSQL gives deadlocks and that too for very small
>> concurrency levels. In our experience we have in fact encountered several
>> deadlocking issues with MSSQL setups previously also in certain other
>> scenarios, and had to move to a non DB solution.
>>
>> At this moment we have fixed the code level issues which we have found so
>> far. Beyond this it may be hard to find issues at code level. The fixes
>> done so far also, doesn't completely eliminate the possibility of a
>> deadlock; they only reduce it to a large extent, but that level doesn't
>> seem to be enough for MSSQL. From our side we will look into profiling this
>> use case on MSSQL server.
>>
>> If we are to completely eliminate deadlocking we will have to lock the
>> tables which we haven't done as a practice because it will drastically
>> reduce performance. Other option available is for the MB code to recover
>> from the specific exception by retrying.
>>
>> However during the discussion there were several problems raised
>> regarding implementation of topics.
>>
>> MB uses internal roles and permissions in user kernel to authorize access
>> to Topics and Queues.
>>
>> First we figured out that permission (resource + action) are being
>> created for each subscription (queues or topics). And for each subscription
>> an internal role is also being created. The creation of permission seems
>> redundant, because the resource name actually has a one-to-one
>> correspondence with the role name (resource name can be derived from role
>> name), and action can contain only 3 values, publish, subscribe and
>> changePermission. Every time a new subscription is added a new role and 3
>> new permissions are added for that subscription which is unwanted overhead.
>> Every time a subscription is deleted the corresponding role and 3
>> permissions are deleted. In a high load scenario there are many DB calls
>> going on which effects performance drastically.
>>
>> In this case what we discussed with Indika is that, the permissions can
>> be fixed to publish, subscribe and changePermission; they can be added
>> through component.xml and will appear in the permission tree as well. Only
>> the internal role can be created and those 3 permissions assigned. This way
>> we are adding and deleting the internal role only and not doing any
>> operations to the UM_PERMISSION  table which will reduce a lot of DB calls.
>>
>> The problem happens only for topics and not for queues, because in queues
>> you don't seem to be creating roles or permissions per subscription. But
>> for topics you do that and that seems to be executing huge amount of DB
>> calls on the user-mgt tables to add and remove roles and permissions.
>>
>> Further when we discussed we also pointed out that creating an internal
>> role per topic subscription is an unwanted overhead. Normally we create
>> roles if we are going to assign a set of users to it. Using internal roles
>> for queues seems correct. The use case requires users other than the
>> subscriber to be added to the role for that topic. In case of topics, as
>> per the implementation, you create a role per subscription (internally
>> create a temp queue) and and assign the subscriber to it. As per Indika and
>> Hasitha there is no use case to assign other users to it. The only
>> requirement is to keep track of the user who subscribed to that temp queue.
>> In t

Re: [Dev] [Vote] Release WSO2 Carbon Kernel 4.4.2 RC1

[Indunil Upeksha Rathnayake]

Hi,

As per my understanding on the non durable subscription flow in MB, when
adding a subscription for a topic (ex:topic1), it will create an internal
role if topic1 is not exists. After adding an internal role, it'll add
permissions to the role such as publish, subscribe etc. This will update
the UM_PERMISSION and UM_ROLE_PERMISSION tables. In UM_PERMISSION table it
will add a resourceId per a topic. And the role created for a topic will be
deleted with the permissions available to that, when all the subscriptions
for the same topic are disconnected. So that the row level changes in
UM_PERMISSION will occur when adding and deleting a topic.

When adding a topic, an INSERT statement in UM_PERMISSION table, will place
an exclusive lock on rows until that has been committed (or rolled back).
In there, a SELECT might be blocked, since in the mean time this
subscription in another node, will be accessing permissions for the same
topic in UM_PERMISSION table, by considering that the permissions are
available since the role is created for the topic. But the deadlock occurs
in "addAuthorizationForRole" method in JDBCAuthorizationManager class,
where it adds permissions for the role. Two nodes can't be adding and
giving permissions to the same topic, so that this can't be a row level
locking and has to be a table level locking.  When deleting a topic,
another subscription for same topic can't be exists, so in that scenario
also a row level locking can't be occur due to SELECT, but a table level
locking can be exists.

This may be the reason that this works for oracle but not for mssql and can
be because of the Lock Escalation available in SQL Server or as in the [1]
some versions of SQL Server doesn't support row level locking. Please refer
[1] for the difference in locking mechanism in Oracle and SQL Server .

If the reason behind this is lock escalation, that can be avoided by
introducing proper indexing mechanism. And "WITH (NOLOCK)" or "WITH
(READPAST)" also can be useful in mssql to avoid deadlocks, but it'll lead
to invalid results or dirty reads. So as tharindu mentioned, the best way
to avoid this can be removing changes done in UM_PERMISSION table.

[1]
https://docs.oracle.com/cd/E10405_01/appdev.120/e10379/ss_oracle_compared.htm#i1038519

Thanks and Regards
-- 
Indunil Upeksha Rathnayake
Software Engineer | WSO2 Inc
Emailindu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev