Re: Build failed in Jenkins: Stratos-41x-Commit-Build #8

I can see following log in Stratos-Common tests. Seems like a memory issue in the builder. Anuruddha : Could you please have a look? # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xada5852c, pid=2342, tid=4136737600 # # JRE version: 7.0_25-b15 # Jav

Re: New committer and PMC member: Dinithi De Silva

Congratulations Dinithi ! On Thu, Sep 10, 2015 at 10:47 AM, Lakmal Warusawithana wrote: > The Project Management Committee (PMC) for Apache Stratos > has asked Dinithi De Silva to become a committer and PMC member > and we are pleased to announce that he has accepted. > > Being a committer enabl

Build failed in Jenkins: Stratos-41x-Commit-Build #8

See Changes: [anuruddha789] Adding generic exception catch block to prevent application monitor failing silently [anuruddha789] Adding general exception catch block [anuruddha789] Fixing formatting issues [anuruddha789] Adding

Build failed in Jenkins: Stratos-41x-Commit-Build » Apache Stratos - Common #8

See -- [INFO] [INFO] --

[jira] [Resolved] (STRATOS-1537) Application Cluster Monitor Creation Fails Silently when uncaught exception is thrown

[ https://issues.apache.org/jira/browse/STRATOS-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anuruddha Lanka Liyanarachchi resolved STRATOS-1537. Resolution: Fixed Fix Version/s: 4.1.3 Fixed with c

[GitHub] stratos pull request: Catching generic exception in Application Cl...

Github user asfgit closed the pull request at: https://github.com/apache/stratos/pull/457 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[GitHub] stratos pull request: Catching generic exception in Application Cl...

Github user asfgit closed the pull request at: https://github.com/apache/stratos/pull/458 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

New committer and PMC member: Dinithi De Silva

The Project Management Committee (PMC) for Apache Stratos has asked Dinithi De Silva to become a committer and PMC member and we are pleased to announce that he has accepted. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process.

Re: [Dev] Publishing Complete Topology event on Demand

+1 for this approach. I hope PCA plugins will be able to use this. On Thu, Sep 10, 2015 at 10:17 AM, Udara Liyanage wrote: > +1 > > On Thu, Sep 10, 2015 at 10:16 AM, Reka Thirunavukkarasu > wrote: > >> +1. Great thought. It would increase the startup time of the components >> those who listens

Re: [Dev] Publishing Complete Topology event on Demand

+1 On Thu, Sep 10, 2015 at 10:16 AM, Reka Thirunavukkarasu wrote: > +1. Great thought. It would increase the startup time of the components > those who listens to CompleteTopology and PCA. > > Thanks, > Reka > > On Thu, Sep 10, 2015 at 1:09 AM, Imesh Gunaratne wrote: > >> Hi Devs, >> >> I would

Re: [Dev] Publishing Complete Topology event on Demand

+1. Great thought. It would increase the startup time of the components those who listens to CompleteTopology and PCA. Thanks, Reka On Thu, Sep 10, 2015 at 1:09 AM, Imesh Gunaratne wrote: > Hi Devs, > > I would like to propose $subject. > > Currently we do this with a one minute interval and it

Re: [Dev] Publishing Complete Topology event on Demand

On Thu, Sep 10, 2015 at 1:29 AM, Akila Ravihansa Perera wrote: > > Shall we call the topic as 'initializer' to be generic? We can further > extend this to Application hierarchy model initialization and tenant model > initialization using the same topic. These are also published periodically > by

Jenkins build is back to stable : Stratos-41x-Nightly-Build » Apache Stratos - Integration Tests #5

See

Jenkins build is back to stable : Stratos-41x-Nightly-Build #5

See

Jenkins build is back to stable : Stratos-41x-Nightly-Build » Apache Stratos - Messaging #5

See

Jenkins build became unstable: Stratos-Master-Nightly-Build » Apache Stratos - Integration Tests #620

See

Jenkins build became unstable: Stratos-Master-Nightly-Build #620

See

Re: [Dev] Publishing Complete Topology event on Demand

Hi Imesh, Great thought. This will considerably speed up instance activation process. Shall we call the topic as 'initializer' to be generic? We can further extend this to Application hierarchy model initialization and tenant model initialization using the same topic. These are also published per

[Dev] Publishing Complete Topology event on Demand

Hi Devs, I would like to propose $subject. Currently we do this with a one minute interval and its causing the cartridge agent and the servers to wait for around two minutes (in the worst case) to start. In Docker this is a considerable amount of delay. I think we can implement $subject by intro

[jira] [Resolved] (STRATOS-1557) Clear Metadata when Undeploying an Application

[ https://issues.apache.org/jira/browse/STRATOS-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne resolved STRATOS-1557. -- Resolution: Fixed > Clear Metadata when Undeploying an Application > -

[jira] [Commented] (STRATOS-1557) Clear Metadata when Undeploying an Application

[ https://issues.apache.org/jira/browse/STRATOS-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737451#comment-14737451 ] Imesh Gunaratne commented on STRATOS-1557: -- Fixed with commit revision: https:/

[Dev] Clear Metadata when Undeploying an Application

Hi Devs, I just implemented logic to do $subject. The fix was pushed to stratos-4.1.x branch with the following commit revision: https://github.com/apache/stratos/commit/597437184ab50b24eab7caf027db3147bf4cb617 JIRA: https://issues.apache.org/jira/browse/STRATOS-1557 Thanks -- Imesh Gunaratne

[jira] [Assigned] (STRATOS-1557) Clear Metadata when Undeploying an Application

[ https://issues.apache.org/jira/browse/STRATOS-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne reassigned STRATOS-1557: Assignee: Imesh Gunaratne > Clear Metadata when Undeploying an Application >

[jira] [Updated] (STRATOS-1557) Clear Metadata when Undeploying an Application

[ https://issues.apache.org/jira/browse/STRATOS-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-1557: - Issue Type: Improvement (was: Bug) > Clear Metadata when Undeploying an Application > -

[jira] [Updated] (STRATOS-1557) Clear Metadata when Undeploying an Application

[ https://issues.apache.org/jira/browse/STRATOS-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-1557: - Summary: Clear Metadata when Undeploying an Application (was: Clear Metadata API Space

[jira] [Updated] (STRATOS-1557) Clear Metadata when Undeploying an Application

[ https://issues.apache.org/jira/browse/STRATOS-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-1557: - Fix Version/s: 4.1.3 > Clear Metadata when Undeploying an Application >

Jenkins build is unstable: Stratos-Master-Commit-Build #812

See

Jenkins build is unstable: Stratos-Master-Commit-Build » Apache Stratos - Integration Tests #812

See

Jenkins build became unstable: Stratos-Master-Commit-Build » Apache Stratos - Messaging #812

See

Re: Strange Error in WSO2 Private Paas 4.1.2

We have move this discussion to WSO2 Dev since the problem is related to WSO2 Private PaaS. Thanks On Tue, Sep 8, 2015 at 7:06 PM, Monaco Marco wrote: > Hi, > > We have successfully installed WSO2 PPaaS 4.1.2 on our Openstack IaaS > Environment. > > After following this procedure ( > https://do

[GitHub] stratos pull request: Adding timestamp for cartridge_agent_helath_...

Github user Thanu commented on the pull request: https://github.com/apache/stratos/pull/456#issuecomment-138897909 Close this P/R as it's merged to master. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project d

[GitHub] stratos pull request: Adding timestamp for cartridge_agent_helath_...

Github user Thanu closed the pull request at: https://github.com/apache/stratos/pull/456 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enab

[GitHub] stratos pull request: Cleaning and Formatting

Github user imesh commented on the pull request: https://github.com/apache/stratos/pull/459#issuecomment-138889051 Thanks for the code clean up fix Thanuja! Now this is merged to master branch. --- If your project is set up for it, you can reply to this email and have your reply appe

[GitHub] stratos pull request: Cleaning and Formatting

Github user asfgit closed the pull request at: https://github.com/apache/stratos/pull/459 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is ena

[Dev] Kubernetes Memory Allocation Issue Fixed

Hi Devs, We recently found an issue in $subject. The problem was that Memory was defined in mega bytes in the cartridge definition and it was converted to bytes internally and sent to Kubernetes. This conversion was done using an Integer variable and it was reaching its maximum allowed value. Now

[jira] [Resolved] (STRATOS-1555) Maximum memory that can be allocated for a Pod is 2047 in Kubernetes

[ https://issues.apache.org/jira/browse/STRATOS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne resolved STRATOS-1555. -- Resolution: Fixed Fix Version/s: 4.1.3 > Maximum memory that can be allocated f

[jira] [Comment Edited] (STRATOS-1555) Maximum memory that can be allocated for a Pod is 2047 in Kubernetes

[ https://issues.apache.org/jira/browse/STRATOS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736689#comment-14736689 ] Imesh Gunaratne edited comment on STRATOS-1555 at 9/9/15 11:27 AM: ---

[jira] [Issue Comment Deleted] (STRATOS-1555) Maximum memory that can be allocated for a Pod is 2047 in Kubernetes

[ https://issues.apache.org/jira/browse/STRATOS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne updated STRATOS-1555: - Comment: was deleted (was: Fixed with commit revision: https://github.com/apache/strato

[jira] [Commented] (STRATOS-1555) Maximum memory that can be allocated for a Pod is 2047 in Kubernetes

[ https://issues.apache.org/jira/browse/STRATOS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736692#comment-14736692 ] Imesh Gunaratne commented on STRATOS-1555: -- Fixed with commit revision: https:

[jira] [Commented] (STRATOS-1555) Maximum memory that can be allocated for a Pod is 2047 in Kubernetes

[ https://issues.apache.org/jira/browse/STRATOS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736689#comment-14736689 ] Imesh Gunaratne commented on STRATOS-1555: -- Fixed with commit revision: https:

[jira] [Assigned] (STRATOS-1555) Maximum memory that can be allocated for a Pod is 2047 in Kubernetes

[ https://issues.apache.org/jira/browse/STRATOS-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne reassigned STRATOS-1555: Assignee: Imesh Gunaratne > Maximum memory that can be allocated for a Pod is 204

[jira] [Created] (STRATOS-1558) Upon receiving Member Fault event, CC should update the member to ERROR status in Topology

Akila created STRATOS-1558: -- Summary: Upon receiving Member Fault event, CC should update the member to ERROR status in Topology Key: STRATOS-1558 URL: https://issues.apache.org/jira/browse/STRATOS-1558 Proj

[jira] [Assigned] (STRATOS-1558) Upon receiving Member Fault event, CC should update the member to ERROR status in Topology

[ https://issues.apache.org/jira/browse/STRATOS-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila reassigned STRATOS-1558: -- Assignee: Akila > Upon receiving Member Fault event, CC should update the member to ERROR > status i

[jira] [Created] (STRATOS-1557) Clear Metadata API Space when Undeploying an Application

Imesh Gunaratne created STRATOS-1557: Summary: Clear Metadata API Space when Undeploying an Application Key: STRATOS-1557 URL: https://issues.apache.org/jira/browse/STRATOS-1557 Project: Stratos

[jira] [Created] (STRATOS-1556) Implement a data migration tool to convert 4.0.0 artifacts to 4.1.0

Akila created STRATOS-1556: -- Summary: Implement a data migration tool to convert 4.0.0 artifacts to 4.1.0 Key: STRATOS-1556 URL: https://issues.apache.org/jira/browse/STRATOS-1556 Project: Stratos

[jira] [Assigned] (STRATOS-1556) Implement a data migration tool to convert 4.0.0 artifacts to 4.1.0

[ https://issues.apache.org/jira/browse/STRATOS-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila reassigned STRATOS-1556: -- Assignee: Akila > Implement a data migration tool to convert 4.0.0 artifacts to 4.1.0 > -

[jira] [Created] (STRATOS-1555) Maximum memory that can be allocated for a Pod is 2047 in Kubernetes

Akila created STRATOS-1555: -- Summary: Maximum memory that can be allocated for a Pod is 2047 in Kubernetes Key: STRATOS-1555 URL: https://issues.apache.org/jira/browse/STRATOS-1555 Project: Stratos

[jira] [Assigned] (STRATOS-1554) Kubernetes services are not created in multiple Kubernetes clusters

[ https://issues.apache.org/jira/browse/STRATOS-1554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Imesh Gunaratne reassigned STRATOS-1554: Assignee: Imesh Gunaratne > Kubernetes services are not created in multiple Kuber

[jira] [Created] (STRATOS-1554) Kubernetes services are not created in multiple Kubernetes clusters

Akila created STRATOS-1554: -- Summary: Kubernetes services are not created in multiple Kubernetes clusters Key: STRATOS-1554 URL: https://issues.apache.org/jira/browse/STRATOS-1554 Project: Stratos

[jira] [Created] (STRATOS-1553) GetUsers REST API doesn't return all the feilds of the User

Reka Thirunavukkarasu created STRATOS-1553: -- Summary: GetUsers REST API doesn't return all the feilds of the User Key: STRATOS-1553 URL: https://issues.apache.org/jira/browse/STRATOS-1553 Pro

[jira] [Created] (STRATOS-1552) Debug logs are missing for Monitors

Reka Thirunavukkarasu created STRATOS-1552: -- Summary: Debug logs are missing for Monitors Key: STRATOS-1552 URL: https://issues.apache.org/jira/browse/STRATOS-1552 Project: Stratos I

[jira] [Updated] (STRATOS-1551) Application update not propagated to Applications Topology

[ https://issues.apache.org/jira/browse/STRATOS-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reka Thirunavukkarasu updated STRATOS-1551: --- Summary: Application update not propagated to Applications Topology (was: A

[jira] [Created] (STRATOS-1551) Application update not propergated to Applications Topology

Reka Thirunavukkarasu created STRATOS-1551: -- Summary: Application update not propergated to Applications Topology Key: STRATOS-1551 URL: https://issues.apache.org/jira/browse/STRATOS-1551 Pro

[jira] [Created] (STRATOS-1550) Hierarchical locking for ApplicationHolder

Akila created STRATOS-1550: -- Summary: Hierarchical locking for ApplicationHolder Key: STRATOS-1550 URL: https://issues.apache.org/jira/browse/STRATOS-1550 Project: Stratos Issue Type: Improvement

[jira] [Updated] (STRATOS-1472) Build the topology model in Python CA on the fly

[ https://issues.apache.org/jira/browse/STRATOS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila updated STRATOS-1472: --- Affects Version/s: 4.1.2 > Build the topology model in Python CA on the fly > --

[jira] [Created] (STRATOS-1549) Move PCA artifact distribution coordinator logic to a separate plugin

Akila created STRATOS-1549: -- Summary: Move PCA artifact distribution coordinator logic to a separate plugin Key: STRATOS-1549 URL: https://issues.apache.org/jira/browse/STRATOS-1549 Project: Stratos

[jira] [Commented] (STRATOS-1537) Application Cluster Monitor Creation Fails Silently when uncaught exception is thrown

[ https://issues.apache.org/jira/browse/STRATOS-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736317#comment-14736317 ] Anuruddha Lanka Liyanarachchi commented on STRATOS-1537: Followi