Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC1

[Afkham Azeez]

Merged

On Tue, Jan 5, 2016 at 7:44 AM, Sameera Jayasoma  wrote:

> Hi Azeez,
>
> https://github.com/wso2/product-mss/pull/107
>
> Thanks,
> Sameera.
>
> On Mon, Jan 4, 2016 at 4:47 PM, Afkham Azeez  wrote:
>
>> We are also missing the sample & documentation for the security stuff
>> that Sameera implemented so until that is added, we can't ship, and that is
>> the only blocker for this release.
>>
>> On Mon, Jan 4, 2016 at 2:56 PM, Afkham Azeez  wrote:
>>
>>> -1.
>>>
>>> The petstore sample requires copying IS but IS is not used in the
>>> sample. Lakmal removed the scripts which were used for copying & starting
>>> up IS. We will have to repack.
>>>
>>> On Wed, Dec 23, 2015 at 12:19 PM, Samiyuru Senarathne >> > wrote:
>>>
 Hi Devs,

 This is the 1st Release Candidate of WSO2 Microservices Server 1.0.0.

 Please download, test the product and vote.

 *​Source and binary distribution files:*

 https://github.com/wso2/product-mss/releases/download/v1.0.0-RC1/wso2mss-1.0.0.zip

 *Maven staging repository:*
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-245/
 http://maven.wso2.org/nexus/content/repositories/orgwso2-246/

 *The tag to be voted upon:*
 https://github.com/wso2/product-mss/tree/v1.0.0-RC1


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

 Thank you,
 Carbon Team
 --
 Samiyuru Senarathne
 *Software Engineer*
 Mobile : +94 (0) 71 134 6087
 samiy...@wso2.com

>>>
>>>
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * *
>>> *email: **az...@wso2.com* 
>>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>>> *http://blog.afkham.org* 
>>> *twitter: **http://twitter.com/afkham_azeez*
>>> 
>>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>>> *
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>


-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

Re: [Dev] Synapse failure while moving App Manager data publisher to new version

[Dinusha Senanayaka]

On Tue, Jan 5, 2016 at 10:40 AM, Nuwan Dias  wrote:

> I guess Visitha is referring to carbon-mediation. There was an effort to
> upgrade the data-publisher dependency version recently on carbon-mediation
> but it had to be stopped due to some issues faced in the process. Jagath
> knowns the context.
>
Yes, this should be carbon-mediation.
@Jagath: What is the status of updating carbon-mediation. Is that blocked
with some issue ?

Regards,
Dinusha.

>
> On Tue, Jan 5, 2016 at 10:37 AM, Isuru Udana  wrote:
>
>> Hi Visitha,
>>
>> Synapse does not depend on data publishers.
>>
>> Thanks.
>>
>> On Tue, Jan 5, 2016 at 10:32 AM, Visitha Wijesinghe 
>> wrote:
>>
>>>
>>> Hi
>>>
>>> When App Manager moving to the new data publisher which is provided by
>>> DAS, we are getting a synapse failure.
>>>
>>>-
>>>
>>>org.wso2.carbon.databridge.commons_4.4.4
>>>-
>>>
>>>org.wso2.carbon.databridge.commons.thrift_4.4.4
>>>-
>>>
>>>org.wso2.carbon.databridge.agent.thrift_4.4.4
>>>
>>> Reason for this failure is above mentioned old version of jar's contains
>>> synapse dependencies which are not supported by the new versions mentioned
>>> bellow.
>>>
>>>-
>>>
>>>org.wso2.carbon.databridge.agent-5.0.6
>>>-
>>>
>>>org.wso2.carbon.databridge.commons.thrift_5.0.6
>>>-
>>>
>>>org.wso2.carbon.databridge.commons_5.0.6
>>>
>>> App Manager – DAS migration blocks due to this. Is there any plans of
>>> migrating synapse to the latest data publisher ? If so can we get time line
>>> for it ? Else do we have any alternative solution?
>>>
>>> --
>>>
>>> *Visitha Wijesinghe*
>>> Software Engineer Trainee.
>>> WSO2 Lanka (pvt) Ltd.
>>>
>>> Mobile - +94772617187
>>>
>>
>>
>>
>> --
>> *Isuru Udana*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nuwan Dias
>
> Technical Lead - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.0.0 RC3

[Kamidu Punchihewa]

Hi all,

I have tested the following scenarios in EMM web app in a standalone setup
using the default user store and a secondary user store.

   - Created a role
  - Update a role
  - Rove existing roles
  - Manage permissions to a role
  - Created an user
  - Edited the user's details and saved
  - Invited the user via email
  - Read the enrollment URL via QR code
  - Removed the user
  - Changed the password
  - Manage Platform Configuration
  - Create a Policy
  - Edited the Policy
  - Modified Policy priority
  - Users and roles search

No issues found.
*My vote : [x] - Stable - Go ahead and release*

Thanks & Regards

Kamidu Sachith Punchihewa
*Software Engineer*
WSO2, Inc.
lean . enterprise . middleware
Mobile : +94 (0) 770566749 <%2B94%20%280%29%20773%20451194>


Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
retransmit, disseminate, or otherwise use the information contained in this
communication. Internet communications cannot be guaranteed to be timely,
secure, error or virus-free. The sender does not accept liability for any
errors or omissions.

On Mon, Jan 4, 2016 at 4:50 PM, Prabath Abeysekera 
wrote:

> Hi Devs,
>
> This is the third release candidate of WSO2 Enterprise Mobility Manager
> 2.0.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12592
>
> Please download, test and vote.
>
> Source & binary distribution files:
> https://github.com/wso2/product-mdm/releases/tag/v2.0.0-RC3
>
> The tag to be voted upon:
> https://github.com/wso2/product-mdm/tree/v2.0.0-RC3
>
> Known issues
> https://wso2.org/jira/issues/?filter=12593
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
>
> Thanks and Regards,
> EMM/IoTS Team
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Synapse failure while moving App Manager data publisher to new version

[Nuwan Dias]

I guess Visitha is referring to carbon-mediation. There was an effort to
upgrade the data-publisher dependency version recently on carbon-mediation
but it had to be stopped due to some issues faced in the process. Jagath
knowns the context.

On Tue, Jan 5, 2016 at 10:37 AM, Isuru Udana  wrote:

> Hi Visitha,
>
> Synapse does not depend on data publishers.
>
> Thanks.
>
> On Tue, Jan 5, 2016 at 10:32 AM, Visitha Wijesinghe 
> wrote:
>
>>
>> Hi
>>
>> When App Manager moving to the new data publisher which is provided by
>> DAS, we are getting a synapse failure.
>>
>>-
>>
>>org.wso2.carbon.databridge.commons_4.4.4
>>-
>>
>>org.wso2.carbon.databridge.commons.thrift_4.4.4
>>-
>>
>>org.wso2.carbon.databridge.agent.thrift_4.4.4
>>
>> Reason for this failure is above mentioned old version of jar's contains
>> synapse dependencies which are not supported by the new versions mentioned
>> bellow.
>>
>>-
>>
>>org.wso2.carbon.databridge.agent-5.0.6
>>-
>>
>>org.wso2.carbon.databridge.commons.thrift_5.0.6
>>-
>>
>>org.wso2.carbon.databridge.commons_5.0.6
>>
>> App Manager – DAS migration blocks due to this. Is there any plans of
>> migrating synapse to the latest data publisher ? If so can we get time line
>> for it ? Else do we have any alternative solution?
>>
>> --
>>
>> *Visitha Wijesinghe*
>> Software Engineer Trainee.
>> WSO2 Lanka (pvt) Ltd.
>>
>> Mobile - +94772617187
>>
>
>
>
> --
> *Isuru Udana*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Dias

Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Synapse failure while moving App Manager data publisher to new version

[Isuru Udana]

Hi Visitha,

Synapse does not depend on data publishers.

Thanks.

On Tue, Jan 5, 2016 at 10:32 AM, Visitha Wijesinghe 
wrote:

>
> Hi
>
> When App Manager moving to the new data publisher which is provided by
> DAS, we are getting a synapse failure.
>
>-
>
>org.wso2.carbon.databridge.commons_4.4.4
>-
>
>org.wso2.carbon.databridge.commons.thrift_4.4.4
>-
>
>org.wso2.carbon.databridge.agent.thrift_4.4.4
>
> Reason for this failure is above mentioned old version of jar's contains
> synapse dependencies which are not supported by the new versions mentioned
> bellow.
>
>-
>
>org.wso2.carbon.databridge.agent-5.0.6
>-
>
>org.wso2.carbon.databridge.commons.thrift_5.0.6
>-
>
>org.wso2.carbon.databridge.commons_5.0.6
>
> App Manager – DAS migration blocks due to this. Is there any plans of
> migrating synapse to the latest data publisher ? If so can we get time line
> for it ? Else do we have any alternative solution?
>
> --
>
> *Visitha Wijesinghe*
> Software Engineer Trainee.
> WSO2 Lanka (pvt) Ltd.
>
> Mobile - +94772617187
>



-- 
*Isuru Udana*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Synapse failure while moving App Manager data publisher to new version

[Visitha Wijesinghe]

Hi

When App Manager moving to the new data publisher which is provided by DAS,
we are getting a synapse failure.

   -

   org.wso2.carbon.databridge.commons_4.4.4
   -

   org.wso2.carbon.databridge.commons.thrift_4.4.4
   -

   org.wso2.carbon.databridge.agent.thrift_4.4.4

Reason for this failure is above mentioned old version of jar's contains
synapse dependencies which are not supported by the new versions mentioned
bellow.

   -

   org.wso2.carbon.databridge.agent-5.0.6
   -

   org.wso2.carbon.databridge.commons.thrift_5.0.6
   -

   org.wso2.carbon.databridge.commons_5.0.6

App Manager – DAS migration blocks due to this. Is there any plans of
migrating synapse to the latest data publisher ? If so can we get time line
for it ? Else do we have any alternative solution?

-- 

*Visitha Wijesinghe*
Software Engineer Trainee.
WSO2 Lanka (pvt) Ltd.

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

Re: [Dev] Cleaning up ML REST API

[Nirmal Fernando]

Hi Frank,

Are you ok to have it at 3.30pm on 6th ? If not we can have it at 4pm too.

On Mon, Jan 4, 2016 at 9:43 PM, Frank Leymann  wrote:

> ​Hi Nirmal,
>
> during our last call on the ML REST API we said that we want to continue
> our walkthru of the commented API document.  By mail we tentatively agreed
> on Wednesday, January 6th, 4pm Colombo time we another Skype Call or
> Hangout.  Should we take that time slot?  I would be available for an hour
> that time...​
>
>
> Best regards,
> Frank
>
> 2015-12-13 12:22 GMT+01:00 Frank Leymann :
>
>> Dear Thamali,
>>
>> I added a bunch of comments.  For each of the methods (get, post,) I
>> suggested modifications to your API that you may want to use as template
>> for the other APIs; of course, I argued why I suggested individual pieces.
>> I also started to make use of Swagger Paramters: and Definitions: sections
>> to better ensure reuse of the different declarations of the API.
>>
>> Finally: I need to much better understand the ML data model. See my
>> comments for clarification need I have :-)  This understanding is key to be
>> able to recommend the use of "processing function resources" or not.
>>
>> I am looking forward to our discussion on Wednesday...
>>
>>
>> Best regards,
>> Frank
>>
>> 2015-12-01 12:55 GMT+01:00 Thamali Wijewardhana :
>>
>>> Link for the swagger definition:
>>>
>>>
>>> https://docs.google.com/a/wso2.com/document/d/1KYmXyuEFJMhFMy6p-SjRztVrgW8mr83LZR2U4BK4d-M/edit?usp=sharing
>>>
>>>
>>> On Tue, Dec 1, 2015 at 4:32 PM, Thamali Wijewardhana 
>>> wrote:
>>>


 On Thu, Nov 26, 2015 at 7:40 PM, Frank Leymann  wrote:

> Dear all, sorry for the delay  :-(
>
> What about one of the following time slots:
>
> Tuesday, Dec 1, 4pm Colombo Time
> Wednesday, Dec 2, 4pm Colombo Time
> Friday, Dec 4, 4pm Colombo Time
>
> I will be available later than 4pm but this won't be convenient for
> you in Colombo.
>
>
>
> Best regards,
> Frank
>
> 2015-11-25 8:43 GMT+01:00 Nirmal Fernando :
>
>> Hi Frank,
>>
>> Could you please let us know few time slots?
>>
>> On Mon, Nov 23, 2015 at 9:29 AM, Nirmal Fernando 
>> wrote:
>>
>>> Absolutely. We'll wait till Frank confirms a time. Thanks.
>>>
>>> On Sun, Nov 22, 2015 at 10:18 PM, Sanjeewa Malalgoda <
>>> sanje...@wso2.com> wrote:
>>>
 Hi nirmal,
 please invite apim rest api team as well. we would like to join
 this discussion.

 Thanks
 sanjeewa.

 sent from my phone
 On Nov 22, 2015 7:00 PM, "Nirmal Fernando"  wrote:

> Thanks Frank for the response. +1 for having a call. Could you
> please propose few time slots?
>
> On Sun, Nov 22, 2015 at 6:55 PM, Frank Leymann 
> wrote:
>
>> Dear Thamali,
>>
>> we (APIM, ES Publisher,... teams) developed some guidelines on
>> making all of our APIs more consistent. For example, versioning 
>> (major,
>> minor, patch) as part of the URL context etc.  Also, you are not 
>> using PUT
>> but always POST - this has some implications a bunch of REST-folks 
>> are
>> serious about. Similarly, the use of proper HTTP headers is a REST 
>> issue to
>> reduce the amount of data transferred, to avoid potential concurrency
>> problems etc.
>>
>> Should we have a call to discuss the API and check where we can
>> help?
>>
>>
>>
>> Best regards,
>> Frank
>>
>> 2015-11-18 12:10 GMT+01:00 Nirmal Fernando :
>>
>>> Thanks Thamali! Please try to generate the Swagger definition
>>> for ML API as the next step.
>>>
>>> On Wed, Nov 18, 2015 at 12:21 PM, Thamali Wijewardhana <
>>> tham...@wso2.com> wrote:
>>>
 REST API standards define the way to produce a RESTful API. For
 an API to become a RESTful API, it should confirm to those REST
 standards.This document includes a set of  improvements to make 
 the WSO2
 API, a RESTful API.



 https://docs.google.com/spreadsheets/d/1HYiS-TpqYaZTtBLLSIeYZ_nvZkbt7zAFwetnHLe4vg8/edit#gid=0



>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Le

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC3

[Nuwan Dias]

These scripts are no longer maintained within the release pack. The
migration scripts, clients, etc are hosted on the documentation page which
explains the steps for migration as well.

Thanks,
NuwanD.

On Tue, Jan 5, 2016 at 3:51 AM, Vanjikumaran Sivajothy 
wrote:

> I do not see the migration scripts for 1.9.X -> 1.10;
> Does it mean that there is no schema change?
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Dias

Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC1

[Sameera Jayasoma]

Hi Azeez,

https://github.com/wso2/product-mss/pull/107

Thanks,
Sameera.

On Mon, Jan 4, 2016 at 4:47 PM, Afkham Azeez  wrote:

> We are also missing the sample & documentation for the security stuff that
> Sameera implemented so until that is added, we can't ship, and that is the
> only blocker for this release.
>
> On Mon, Jan 4, 2016 at 2:56 PM, Afkham Azeez  wrote:
>
>> -1.
>>
>> The petstore sample requires copying IS but IS is not used in the sample.
>> Lakmal removed the scripts which were used for copying & starting up IS. We
>> will have to repack.
>>
>> On Wed, Dec 23, 2015 at 12:19 PM, Samiyuru Senarathne 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 1st Release Candidate of WSO2 Microservices Server 1.0.0.
>>>
>>> Please download, test the product and vote.
>>>
>>> *​Source and binary distribution files:*
>>>
>>> https://github.com/wso2/product-mss/releases/download/v1.0.0-RC1/wso2mss-1.0.0.zip
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-245/
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2-246/
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/product-mss/tree/v1.0.0-RC1
>>>
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Thank you,
>>> Carbon Team
>>> --
>>> Samiyuru Senarathne
>>> *Software Engineer*
>>> Mobile : +94 (0) 71 134 6087
>>> samiy...@wso2.com
>>>
>>
>>
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * *
>> *email: **az...@wso2.com* 
>> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
>> *http://blog.afkham.org* 
>> *twitter: **http://twitter.com/afkham_azeez*
>> 
>> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
Sameera Jayasoma,
Software Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://blog.sameera.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

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

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC3

[Abimaran Kugathasan]

Couldn't find directory for migration-1.8.0_to_1.9.0 also which is there in
1.9.1

On Mon, Jan 4, 2016 at 2:21 PM, Vanjikumaran Sivajothy 
wrote:

> I do not see the migration scripts for 1.9.X -> 1.10;
> Does it mean that there is no schema change?
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks
Abimaran Kugathasan

Software Engineer | WSO2 Inc
Data & APIs Technologies Team
Mobile : +94 773922820


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

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC3

[Vanjikumaran Sivajothy]

I do not see the migration scripts for 1.9.X -> 1.10;
Does it mean that there is no schema change?
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC3

[Chamila Adhikarinayake]

Hi Devs,

This is the third release candidate of WSO2 API Manager 1.10.0.

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

Please download, test and vote.

Binary distribution files:
http://svn.wso2.org/repos/wso2/people/chamilaa/apim-1.10.0-rc3/

The tag to be voted upon:
https://github.com/wso2/product-apim/tree/v1.10.0-rc3


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

Thanks and Regards,
WSO2 API Manager Team

-- 
Regards,
Chamila Adhikarinayake
Software Engineer
WSO2, Inc.
Mobile - +94712346437
Email  - chami...@wso2.com
Blog  -  http://helpfromadhi.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][PPaaS] Puppet modules for WSO2 Products

[Imesh Gunaratne]

Thanks Thanuja! Will review and merge.

On Mon, Jan 4, 2016 at 6:50 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi All,
>
> Completed the AS puppet module according to the refactored hiera yaml
> files and templates. Updated the same p/r [1] with latest changes. Please
> review and merge.
>
> [1]. https://github.com/wso2/puppet-modules/pull/5
>
> Thanks.
>
> On Wed, Dec 30, 2015 at 1:03 PM, Rajkumar Rajaratnam 
> wrote:
>
>>
>>
>> On Wed, Dec 23, 2015 at 1:11 PM, Rajkumar Rajaratnam 
>> wrote:
>>
>>> I have completed ESB 4.9.0 and G-Reg 4.6.0/5.1.0 puppet modules with
>>> hiera. I have tested clustering, registry mounting, depsync, etc with
>>> vagrant.
>>>
>>
>> ​Completed PPaaS 4.1.0/4.1.1 puppet modules with hiera.
>>
>> Thanks,
>> Raj.​
>>
>>
>>>
>>> PS - still we are doing some improvements in hiera data structure at the
>>> moment.
>>>
>>> Thanks,
>>> Raj.
>>>
>>> On Wed, Dec 23, 2015 at 12:54 PM, Chamila De Alwis 
>>> wrote:
>>>
 Hi Thanuja,

 Sure. I'll start working on WSO2 Message Broker module.


 Regards,
 Chamila de Alwis
 Committer and PMC Member - Apache Stratos
 Software Engineer | WSO2 | +94772207163
 Blog: code.chamiladealwis.com



 On Wed, Dec 23, 2015 at 12:53 PM, Thanuja Uruththirakodeeswaran <
 thanu...@wso2.com> wrote:

> Hi Chamila,
>
> I've started to work on AS puppet module. Could you please take
> another product.
>
> Thanks.
>
> On Wed, Dec 23, 2015 at 12:42 PM, Chamila De Alwis 
> wrote:
>
>> Hi,
>>
>> I've started working on the the Puppet module for WSO2 Application
>> Server on [1]. This is based on the generic WSO2 Base Puppet module and
>> will follow the same pattern as the other modules.
>>
>> If you have started working on a module, please update with the
>> latest status.
>>
>> [1] - https://github.com/wso2/puppet-modules
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>


>>>
>>>
>>> --
>>> Rajkumar Rajaratnam
>>> Committer & PMC Member, Apache Stratos
>>> Software Engineer, WSO2
>>>
>>> Mobile : +94777568639
>>> Blog : rajkumarr.com
>>>
>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>



-- 
*Imesh Gunaratne*
Senior Technical Lead
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: http://imesh.gunaratne.org
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][PPaaS] Puppet modules for WSO2 Products

[Thanuja Uruththirakodeeswaran]

Hi All,

Completed the AS puppet module according to the refactored hiera yaml files
and templates. Updated the same p/r [1] with latest changes. Please review
and merge.

[1]. https://github.com/wso2/puppet-modules/pull/5

Thanks.

On Wed, Dec 30, 2015 at 1:03 PM, Rajkumar Rajaratnam 
wrote:

>
>
> On Wed, Dec 23, 2015 at 1:11 PM, Rajkumar Rajaratnam 
> wrote:
>
>> I have completed ESB 4.9.0 and G-Reg 4.6.0/5.1.0 puppet modules with
>> hiera. I have tested clustering, registry mounting, depsync, etc with
>> vagrant.
>>
>
> ​Completed PPaaS 4.1.0/4.1.1 puppet modules with hiera.
>
> Thanks,
> Raj.​
>
>
>>
>> PS - still we are doing some improvements in hiera data structure at the
>> moment.
>>
>> Thanks,
>> Raj.
>>
>> On Wed, Dec 23, 2015 at 12:54 PM, Chamila De Alwis 
>> wrote:
>>
>>> Hi Thanuja,
>>>
>>> Sure. I'll start working on WSO2 Message Broker module.
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer | WSO2 | +94772207163
>>> Blog: code.chamiladealwis.com
>>>
>>>
>>>
>>> On Wed, Dec 23, 2015 at 12:53 PM, Thanuja Uruththirakodeeswaran <
>>> thanu...@wso2.com> wrote:
>>>
 Hi Chamila,

 I've started to work on AS puppet module. Could you please take another
 product.

 Thanks.

 On Wed, Dec 23, 2015 at 12:42 PM, Chamila De Alwis 
 wrote:

> Hi,
>
> I've started working on the the Puppet module for WSO2 Application
> Server on [1]. This is based on the generic WSO2 Base Puppet module and
> will follow the same pattern as the other modules.
>
> If you have started working on a module, please update with the latest
> status.
>
> [1] - https://github.com/wso2/puppet-modules
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Software Engineer | WSO2 | +94772207163
> Blog: code.chamiladealwis.com
>
>
>


 --
 Thanuja Uruththirakodeeswaran
 Software Engineer
 WSO2 Inc.;http://wso2.com
 lean.enterprise.middleware

 mobile: +94 774363167

>>>
>>>
>>
>>
>> --
>> Rajkumar Rajaratnam
>> Committer & PMC Member, Apache Stratos
>> Software Engineer, WSO2
>>
>> Mobile : +94777568639
>> Blog : rajkumarr.com
>>
>
>
>
> --
> Rajkumar Rajaratnam
> Committer & PMC Member, Apache Stratos
> Software Engineer, WSO2
>
> Mobile : +94777568639
> Blog : rajkumarr.com
>



-- 
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC2

[Chamila Adhikarinayake]

Hi all,
We are canceling the vote due to the issue raised in [1] and will start a
new vote for WSO2 API Manager 1.10.0 RC3 shortly.

[1] https://wso2.org/jira/browse/APIMANAGER-4447

Chamila

On Mon, Jan 4, 2016 at 2:54 PM, Chamila Adhikarinayake 
wrote:

> Hi Devs,
>
> This is the second release candidate of WSO2 API Manager 1.10.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=12597
>
> Please download, test and vote.
>
> Source & binary distribution files:
> https://github.com/wso2/product-apim/releases/tag/v1.10.0-rc2
>
> The tag to be voted upon:
> https://github.com/wso2/product-apim/tree/v1.10.0-rc2
>
>
> [ ]  Stable - go ahead and release
> [ ]  Broken - do not release (explain why)
>
> Thanks and Regards,
> WSO2 API Manager Team
>
> --
> Regards,
> Chamila Adhikarinayake
> Software Engineer
> WSO2, Inc.
> Mobile - +94712346437
> Email  - chami...@wso2.com
> Blog  -  http://helpfromadhi.blogspot.com/
>



-- 
Regards,
Chamila Adhikarinayake
Software Engineer
WSO2, Inc.
Mobile - +94712346437
Email  - chami...@wso2.com
Blog  -  http://helpfromadhi.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Release carbon archetypes to maven central

[Kishanthan Thangarajah]

Great. Thanks Manuri.

On Fri, Jan 1, 2016 at 12:45 PM, Manuri Amaya Perera 
wrote:

> Hi,
>
> Proceeded as mentioned above and released to maven central[1].
>
> [1] https://repo1.maven.org/maven2/org/wso2/carbon
>
> Thank you.
>
> On Sun, Dec 27, 2015 at 3:35 PM, Manuri Amaya Perera 
> wrote:
>
>> Hi,
>>
>> There is a requirement to upload javadoc jars when uploading a jar to
>> maven central. But for archetypes we do not have java files therefore there
>> are no javadocs. They suggest to upload fake "-javadoc.jar" with a README
>> inside, if we do not have real javadoc jars[1]. I suppose this would not be
>> a problem.
>>
>> WDYT?
>>
>> [1]
>> http://central.sonatype.org/pages/requirements.html#supply-javadoc-and-sources
>>
>> Thank you.
>>
>> Thank you.
>>
>> On Tue, Dec 22, 2015 at 3:03 PM, Manuri Amaya Perera 
>> wrote:
>>
>>> Hi,
>>>
>>> Ticket created[1].
>>>
>>> [1] https://issues.sonatype.org/browse/OSSRH-19570
>>>
>>> Thank you.
>>>
>>> On Tue, Dec 22, 2015 at 2:47 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 +1

 Thanks,

 On Tue, Dec 22, 2015 at 2:34 PM, Manuri Amaya Perera 
 wrote:

> Hi,
>
> According to [1] I have created a jira account in [2]. Now we need to
> create a ticket for a new project there like[3].
>
> Shall I proceed with creating the ticket with following information.
>
> Priority: Major
> Group Id: org.wso2.carbon
> Project URL:https://github.com/wso2/carbon-kernel
> SCM url: https://github.com/wso2/carbon-kernel.git
> Already Synced to Central: No
>
> According to sonatype docs the process takes less than 2 business
> days[4]
>
> [1]
> https://docs.google.com/a/wso2.com/document/d/1wiJUcia398iStT-nUrVnIil_eJEsEofqurY-gBG6gZk/edit?usp=sharing
> [2] https://issues.sonatype.org
> [3] https://issues.sonatype.org/browse/OSSRH-12494
> [4] http://central.sonatype.org/pages/ossrh-guide.html
>
> Thank you.
>
> On Tue, Dec 22, 2015 at 2:05 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Hi Manuri,
>>
>> Now that carbon kernel 5.0.0 is released, we can now proceed with
>> releasing both carbon archetypes to maven central. Can we start on this
>> task?
>>
>> Thanks,
>> Kishanthan.
>>
>> --
>> *Kishanthan Thangarajah*
>> Associate Technical Lead,
>> Platform Technologies Team,
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - +94773426635
>> Blog - *http://kishanthan.wordpress.com
>> *
>> Twitter - *http://twitter.com/kishanthan
>> *
>>
>
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>



 --
 *Kishanthan Thangarajah*
 Associate Technical Lead,
 Platform Technologies Team,
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - +94773426635
 Blog - *http://kishanthan.wordpress.com
 *
 Twitter - *http://twitter.com/kishanthan
 *

>>>
>>>
>>>
>>> --
>>>
>>> *Manuri Amaya Perera*
>>>
>>> *Software Engineer*
>>>
>>> *WSO2 Inc.*
>>>
>>> *Blog: http://manuriamayaperera.blogspot.com
>>> *
>>>
>>
>>
>>
>> --
>>
>> *Manuri Amaya Perera*
>>
>> *Software Engineer*
>>
>> *WSO2 Inc.*
>>
>> *Blog: http://manuriamayaperera.blogspot.com
>> *
>>
>
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.blogspot.com
> *
>



-- 
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [VOTE] Release WSO2 Enterprise Mobility Manager 2.0.0 RC3

[Prabath Abeysekera]

Hi Devs,

This is the third release candidate of WSO2 Enterprise Mobility Manager
2.0.0.

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

Please download, test and vote.

Source & binary distribution files:
https://github.com/wso2/product-mdm/releases/tag/v2.0.0-RC3

The tag to be voted upon:
https://github.com/wso2/product-mdm/tree/v2.0.0-RC3

Known issues
https://wso2.org/jira/issues/?filter=12593


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


Thanks and Regards,
EMM/IoTS Team

-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC1

[Afkham Azeez]

We are also missing the sample & documentation for the security stuff that
Sameera implemented so until that is added, we can't ship, and that is the
only blocker for this release.

On Mon, Jan 4, 2016 at 2:56 PM, Afkham Azeez  wrote:

> -1.
>
> The petstore sample requires copying IS but IS is not used in the sample.
> Lakmal removed the scripts which were used for copying & starting up IS. We
> will have to repack.
>
> On Wed, Dec 23, 2015 at 12:19 PM, Samiyuru Senarathne 
> wrote:
>
>> Hi Devs,
>>
>> This is the 1st Release Candidate of WSO2 Microservices Server 1.0.0.
>>
>> Please download, test the product and vote.
>>
>> *​Source and binary distribution files:*
>>
>> https://github.com/wso2/product-mss/releases/download/v1.0.0-RC1/wso2mss-1.0.0.zip
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-245/
>> http://maven.wso2.org/nexus/content/repositories/orgwso2-246/
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/product-mss/tree/v1.0.0-RC1
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you,
>> Carbon Team
>> --
>> Samiyuru Senarathne
>> *Software Engineer*
>> Mobile : +94 (0) 71 134 6087
>> samiy...@wso2.com
>>
>
>
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * *
> *email: **az...@wso2.com* 
> * cell: +94 77 3320919 <%2B94%2077%203320919>blog: *
> *http://blog.afkham.org* 
> *twitter: **http://twitter.com/afkham_azeez*
> 
> *linked-in: **http://lk.linkedin.com/in/afkhamazeez
> *
>
> *Lean . Enterprise . Middleware*
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

Re: [Dev] Usage of Siddhi-Scheduler-pool Thread Pools and how to Configure them

[Lasantha Fernando]

Hi Isuru,

These jars are from CEP 3.0.0. Siddhi-2.0.0.wso2v5 was a release done with
some bug fixes for the PPaaS release.

That version of Siddhi also should have the same behaviour with regard to
thread creation.

Thanks,
Lasantha

On 4 January 2016 at 15:54, Isuru Haththotuwa  wrote:

> Hi Lasantha,
>
> Thanks for the reply.
>
> These are the siddhi versions found in Stratos latest packs, AFAIK from
> CEP 3.1.0 [1].
>
> Not seeing any issues, but thought of finding if there is a way to fine
> tune the thread/thread pool usage since its starting quite a number of
> thread pools at startup. So if this is not configurable, suppose there is
> no way to control the thread usage.
>
> [1].
> siddhi-api_2.0.0.wso2v5.jar
> siddhi-core_2.0.0.wso2v5.jar
> siddhi-query_2.0.0.wso2v5.jar
>
> On Mon, Jan 4, 2016 at 2:33 PM, Lasantha Fernando 
> wrote:
>
>> Hi Isuru,
>>
>> Is PPaaS using the old CEP 3.1.0 features? What is the Siddhi version
>> that is being used?
>>
>> In Siddhi-2.x, usually a thread pool was created per Siddhi Manager, and
>> each Execution plan had its own Siddhi manager. So the number of pools
>> would correlate to the number of execution plans.
>>
>> Unfortunately, for CEP 3.1.0, these thread pool sizes were not
>> configurable using CEP features. But the default values worked in most use
>> cases. Are you seeing any issues due to the large number of Siddhi threads
>> that are created?
>>
>> Thanks,
>> Lasantha
>>
>> On 4 January 2016 at 13:49, Isuru Haththotuwa  wrote:
>>
>>> Hi CEP team,
>>>
>>> When the PPaaS single JVM pack (with CEP features) is started, there are
>>> quite a number of Siddhi-Scheduler-pool-xx [1] thread pools visible.
>>> Threads are mostly in WAITING state [1]. What is the usage of these thread
>>> pools? Can we configure the number of pools/threads?
>>>
>>> [1].
>>> "Siddhi-Scheduler-pool-12-thread-20" prio=10 tid=0x7f96d44f7000
>>> nid=0x3636 waiting on condition [0x7f96b7fbe000]
>>>java.lang.Thread.State: WAITING (parking)
>>> at sun.misc.Unsafe.park(Native Method)
>>> - parking to wait for  <0x000781e97af8> (a
>>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
>>> at
>>> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>>> at
>>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1085)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> at java.lang.Thread.run(Thread.java:745)
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* *
>>>
>>>
>>>
>>
>>
>> --
>> *Lasantha Fernando*
>> Senior Software Engineer - Data Technologies Team
>> WSO2 Inc. http://wso2.com
>>
>> email: lasan...@wso2.com
>> mobile: (+94) 71 5247551
>>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
*Lasantha Fernando*
Senior Software Engineer - Data Technologies Team
WSO2 Inc. http://wso2.com

email: lasan...@wso2.com
mobile: (+94) 71 5247551
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Usage of Siddhi-Scheduler-pool Thread Pools and how to Configure them

[Isuru Haththotuwa]

Hi Lasantha,

Thanks for the reply.

These are the siddhi versions found in Stratos latest packs, AFAIK from CEP
3.1.0 [1].

Not seeing any issues, but thought of finding if there is a way to fine
tune the thread/thread pool usage since its starting quite a number of
thread pools at startup. So if this is not configurable, suppose there is
no way to control the thread usage.

[1].
siddhi-api_2.0.0.wso2v5.jar
siddhi-core_2.0.0.wso2v5.jar
siddhi-query_2.0.0.wso2v5.jar

On Mon, Jan 4, 2016 at 2:33 PM, Lasantha Fernando  wrote:

> Hi Isuru,
>
> Is PPaaS using the old CEP 3.1.0 features? What is the Siddhi version that
> is being used?
>
> In Siddhi-2.x, usually a thread pool was created per Siddhi Manager, and
> each Execution plan had its own Siddhi manager. So the number of pools
> would correlate to the number of execution plans.
>
> Unfortunately, for CEP 3.1.0, these thread pool sizes were not
> configurable using CEP features. But the default values worked in most use
> cases. Are you seeing any issues due to the large number of Siddhi threads
> that are created?
>
> Thanks,
> Lasantha
>
> On 4 January 2016 at 13:49, Isuru Haththotuwa  wrote:
>
>> Hi CEP team,
>>
>> When the PPaaS single JVM pack (with CEP features) is started, there are
>> quite a number of Siddhi-Scheduler-pool-xx [1] thread pools visible.
>> Threads are mostly in WAITING state [1]. What is the usage of these thread
>> pools? Can we configure the number of pools/threads?
>>
>> [1].
>> "Siddhi-Scheduler-pool-12-thread-20" prio=10 tid=0x7f96d44f7000
>> nid=0x3636 waiting on condition [0x7f96b7fbe000]
>>java.lang.Thread.State: WAITING (parking)
>> at sun.misc.Unsafe.park(Native Method)
>> - parking to wait for  <0x000781e97af8> (a
>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
>> at
>> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>> at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1085)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
>> at
>> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>
>
> --
> *Lasantha Fernando*
> Senior Software Engineer - Data Technologies Team
> WSO2 Inc. http://wso2.com
>
> email: lasan...@wso2.com
> mobile: (+94) 71 5247551
>



-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Microservices Server 1.0.0 RC1

[Afkham Azeez]

-1.

The petstore sample requires copying IS but IS is not used in the sample.
Lakmal removed the scripts which were used for copying & starting up IS. We
will have to repack.

On Wed, Dec 23, 2015 at 12:19 PM, Samiyuru Senarathne 
wrote:

> Hi Devs,
>
> This is the 1st Release Candidate of WSO2 Microservices Server 1.0.0.
>
> Please download, test the product and vote.
>
> *​Source and binary distribution files:*
>
> https://github.com/wso2/product-mss/releases/download/v1.0.0-RC1/wso2mss-1.0.0.zip
>
> *Maven staging repository:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbonmss-245/
> http://maven.wso2.org/nexus/content/repositories/orgwso2-246/
>
> *The tag to be voted upon:*
> https://github.com/wso2/product-mss/tree/v1.0.0-RC1
>
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you,
> Carbon Team
> --
> Samiyuru Senarathne
> *Software Engineer*
> Mobile : +94 (0) 71 134 6087
> samiy...@wso2.com
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

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

[Dev] [VOTE] Release WSO2 API Manager 1.10.0 RC2

[Chamila Adhikarinayake]

Hi Devs,

This is the second release candidate of WSO2 API Manager 1.10.0.

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

Please download, test and vote.

Source & binary distribution files:
https://github.com/wso2/product-apim/releases/tag/v1.10.0-rc2

The tag to be voted upon:
https://github.com/wso2/product-apim/tree/v1.10.0-rc2


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

Thanks and Regards,
WSO2 API Manager Team

-- 
Regards,
Chamila Adhikarinayake
Software Engineer
WSO2, Inc.
Mobile - +94712346437
Email  - chami...@wso2.com
Blog  -  http://helpfromadhi.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Usage of Siddhi-Scheduler-pool Thread Pools and how to Configure them

[Lasantha Fernando]

Hi Isuru,

Is PPaaS using the old CEP 3.1.0 features? What is the Siddhi version that
is being used?

In Siddhi-2.x, usually a thread pool was created per Siddhi Manager, and
each Execution plan had its own Siddhi manager. So the number of pools
would correlate to the number of execution plans.

Unfortunately, for CEP 3.1.0, these thread pool sizes were not configurable
using CEP features. But the default values worked in most use cases. Are
you seeing any issues due to the large number of Siddhi threads that are
created?

Thanks,
Lasantha

On 4 January 2016 at 13:49, Isuru Haththotuwa  wrote:

> Hi CEP team,
>
> When the PPaaS single JVM pack (with CEP features) is started, there are
> quite a number of Siddhi-Scheduler-pool-xx [1] thread pools visible.
> Threads are mostly in WAITING state [1]. What is the usage of these thread
> pools? Can we configure the number of pools/threads?
>
> [1].
> "Siddhi-Scheduler-pool-12-thread-20" prio=10 tid=0x7f96d44f7000
> nid=0x3636 waiting on condition [0x7f96b7fbe000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x000781e97af8> (a
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
> at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1085)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
> at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
*Lasantha Fernando*
Senior Software Engineer - Data Technologies Team
WSO2 Inc. http://wso2.com

email: lasan...@wso2.com
mobile: (+94) 71 5247551
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Usage of Siddhi-Scheduler-pool Thread Pools and how to Configure them

[Isuru Haththotuwa]

Hi CEP team,

When the PPaaS single JVM pack (with CEP features) is started, there are
quite a number of Siddhi-Scheduler-pool-xx [1] thread pools visible.
Threads are mostly in WAITING state [1]. What is the usage of these thread
pools? Can we configure the number of pools/threads?

[1].
"Siddhi-Scheduler-pool-12-thread-20" prio=10 tid=0x7f96d44f7000
nid=0x3636 waiting on condition [0x7f96b7fbe000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x000781e97af8> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1085)
at
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807)
at
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev