[jira] [Resolved] (STRATOS-1565) Fix registry transactions exception handling

[ https://issues.apache.org/jira/browse/STRATOS-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1565. Resolution: Fixed > Fix registry transactions exception handling > ---

[jira] [Commented] (STRATOS-1565) Fix registry transactions exception handling

[ https://issues.apache.org/jira/browse/STRATOS-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746976#comment-14746976 ] Akila commented on STRATOS-1565: Fixed in 0b913ebdcb40d173d2fa4548c7e8e4217dfa4e6a and

[jira] [Created] (STRATOS-1565) Fix registry transactions exception handling

Akila created STRATOS-1565: -- Summary: Fix registry transactions exception handling Key: STRATOS-1565 URL: https://issues.apache.org/jira/browse/STRATOS-1565 Project: Stratos Issue Type: Bug Affe

[jira] [Commented] (STRATOS-1564) Update the topology context in PCA upon receiving CompleteTopologyEvent

[ https://issues.apache.org/jira/browse/STRATOS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746955#comment-14746955 ] Akila commented on STRATOS-1564: Committed in 477686c6ae5f5648357135bebac8e1aeb0067ee8

[jira] [Resolved] (STRATOS-1564) Update the topology context in PCA upon receiving CompleteTopologyEvent

[ https://issues.apache.org/jira/browse/STRATOS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akila resolved STRATOS-1564. Resolution: Implemented > Update the topology context in PCA upon receiving CompleteTopologyEvent > --

[jira] [Commented] (STRATOS-1564) Update the topology context in PCA upon receiving CompleteTopologyEvent

[ https://issues.apache.org/jira/browse/STRATOS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746953#comment-14746953 ] Akila commented on STRATOS-1564: Once STRATOS-1472 is resolved, this temporary fix shoul

Jenkins build is back to normal : Stratos-41x-Commit-Build #30

See

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

See

Jenkins build is back to normal : Stratos-41x-Commit-Build » Apache Stratos - RESTful admin service module #30

See

[jira] [Created] (STRATOS-1564) Update the topology context in PCA upon receiving CompleteTopologyEvent

Akila created STRATOS-1564: -- Summary: Update the topology context in PCA upon receiving CompleteTopologyEvent Key: STRATOS-1564 URL: https://issues.apache.org/jira/browse/STRATOS-1564 Project: Stratos

[jira] [Created] (STRATOS-1563) Undeploy button should be invisible for the tenants for multitenant application

Dinithi De SIlva created STRATOS-1563: - Summary: Undeploy button should be invisible for the tenants for multitenant application Key: STRATOS-1563 URL: https://issues.apache.org/jira/browse/STRATOS-1563

Re: [Dev] Integration Tests Failing in 4.1.x Branch

Great. That registry locks without releasing may cause this intermittent issue. Will see with the new build. As there are no such a big functional changes from 4.1.2 to 4.1.3, we can check this integration test against 4.1.2 release as we don't experience this issue with 4.1.2 Thanks, Gayan On We

Re: New committer and PMC member: Anuruddha Liyanarachchi

Congratulations Anuruddha !!! On Wed, Sep 16, 2015 at 10:09 AM, Pubudu Gunatilaka wrote: > Congratulations !!! > > On Wed, Sep 16, 2015 at 9:58 AM, Dinithi De Silva > wrote: > >> Congratulations Anuruddha...!!! >> >> On Wed, Sep 16, 2015 at 9:56 AM, Imesh Gunaratne >> wrote: >> >>> Congratulat

Re: [Dev] Integration Tests Failing in 4.1.x Branch

Hi Gayan, Yes, this was my mistake. Sorry for the inconvenience. I've fixed it now. While going through Carbon registry transactions one by one, I noticed that some transactions are not handled properly. There were cases in which registry exception could permanently leave a lock without releasing

Re: [Dev] Integration Tests Failing in 4.1.x Branch

yeah.Seems we are catching the wrong exception. StratosApiV41Utils.java try { autoscalerServiceClient.undeployApplication(applicationId, force); try { clearMetadata(applicationId); } catch (RegistryException e) {

Re: New committer and PMC member: Anuruddha Liyanarachchi

Congratulations !!! On Wed, Sep 16, 2015 at 9:58 AM, Dinithi De Silva wrote: > Congratulations Anuruddha...!!! > > On Wed, Sep 16, 2015 at 9:56 AM, Imesh Gunaratne wrote: > >> Congratulations Anuruddha! >> >> On Wed, Sep 16, 2015 at 9:53 AM, Lakmal Warusawithana >> wrote: >> >>> The Project Ma

Re: New committer and PMC member: Anuruddha Liyanarachchi

Congratulations Anuruddha...!!! On Wed, Sep 16, 2015 at 9:56 AM, Imesh Gunaratne wrote: > Congratulations Anuruddha! > > On Wed, Sep 16, 2015 at 9:53 AM, Lakmal Warusawithana > wrote: > >> The Project Management Committee (PMC) for Apache Stratos >> has asked Anuruddha Liyanarachchi to become a

Re: New committer and PMC member: Anuruddha Liyanarachchi

Congratulations Anuruddha! On Wed, Sep 16, 2015 at 9:53 AM, Lakmal Warusawithana wrote: > The Project Management Committee (PMC) for Apache Stratos > has asked Anuruddha Liyanarachchi to become a committer and PMC member > and we are pleased to announce that he has accepted. > > Being a committe

New committer and PMC member: Anuruddha Liyanarachchi

The Project Management Committee (PMC) for Apache Stratos has asked Anuruddha Liyanarachchi 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 p

Re: Repository path is empty. Cannot perform Git operations

Currently payload parameters get generated at the time application is created. Until the existing application is deleted and created again they do not get updated. We need to improve this logic. On Wed, Sep 16, 2015 at 8:52 AM, Udara Liyanage wrote: > Hi, > > Earlier I did not have APPLICATION_P

Re: [Dev] Integration Tests Failing in 4.1.x Branch

I'm now seeing below error in 4.1.x branch: [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:48.133s [INFO] Finished at: Wed Sep 16 09:42:32 IST

Re: Repository path is empty. Cannot perform Git operations

Hi, Earlier I did not have APPLICATION_PATH parameter in my cartridge. Then I updated the cartridge(PUT /applications) adding this parameter. Still it did not work. I got this resolved only after deleting my tomcat application and tomcat cartridge and re deploying both. Until that APPLICATION_PAT

Repository path is empty. Cannot perform Git operations

Hi, I get the following error when deployed a tomcat cartridge. Though I added *APPLICATION_PATH *as a payload parameter, agent.conf still set APPLICATION_PATH to null {"clusterId":"tomcatr1.my-tomcat.tomcat.domain","repoUserName":"","repoPassword":"","repoURL":" https://github.com/lakwarus/sing

Jenkins build is back to normal : Stratos-41x-Nightly-Build » Apache Stratos - Common #10

See

Build failed in Jenkins: Stratos-41x-Nightly-Build #10

See Changes: [ravihansa3000] Fixing PCA live tests and PCA conflicts [ravihansa3000] Fixing log class names [ravihansa3000] Adding exclude directives to Stratos distribution descriptor to replace customized artifacts [raviha

Build failed in Jenkins: Stratos-41x-Nightly-Build » Apache Stratos - RESTful admin service module #10

See Changes: [ravihansa3000] Fix registry transactions exception handling -- [INFO]

Build failed in Jenkins: Stratos-41x-Commit-Build » Apache Stratos - RESTful admin service module #29

See Changes: [ravihansa3000] Fix registry transactions exception handling -- [INFO]

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

See Changes: [ravihansa3000] Fix registry transactions exception handling -- [...truncated 5326 lines...] Sending artifact delta relative to Stratos-41x-Commit-Build ? Apache Stratos - Ku

Jenkins build is still unstable: Stratos-41x-Commit-Build #28

See

Jenkins build is still unstable: Stratos-41x-Commit-Build » Apache Stratos - Integration Tests #28

See

Jenkins build became unstable: Stratos-41x-Commit-Build #27

See

Jenkins build became unstable: Stratos-41x-Commit-Build » Apache Stratos - Integration Tests #27

See

Jenkins build is back to normal : Stratos-41x-Commit-Build » WSO2 Carbon - UI #26

See

Jenkins build is back to normal : Stratos-41x-Commit-Build #26

See

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

See

Re: [Dev] Integration Tests Failing in 4.1.x Branch

Hi, I'm still not able to reproduce this issue locally. I've run integration tests multiple times and they are successful at every time. I compared the p2-profile and and configuration files between Stratos 4.1.2 and Stratos 4.1.3-SNAPSHOT, and there are no differences in p2-profile. Same dependen

Build failed in Jenkins: Stratos-41x-Commit-Build » WSO2 Carbon - UI #25

See -- [INFO] [INFO]

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

See Changes: [ravihansa3000] Fixing log class names [ravihansa3000] Adding exclude directives to Stratos distribution descriptor to replace customized artifacts -- [...truncated 4664 lin

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

See Changes: [ravihansa3000] Fix smoke test script to use test goal, adding class comments [ravihansa3000] Adding validation to addApplicationSignup [ravihansa3000] Making signup button available only when application is active

Build failed in Jenkins: Stratos-41x-Commit-Build » WSO2 Carbon - UI #24

See -- [...truncated 75 lines...] Downloaded: http://maven.wso2.org/nexus/content/groups/wso2-public/org/wso2/carbon/carbon-kernel-dependents/4.1.0/carbon-ke

Build failed in Jenkins: Stratos-41x-Nightly-Build #9

See Changes: [ravihansa3000] Package specific logging for integration tests [imesh] Select next available sequence numbers for pods, services and append application id [ravihansa3000] Fix smoke test script to use test goal, ad

Build failed in Jenkins: Stratos-41x-Nightly-Build » Apache Stratos - Common #9

See -- [INFO] [INFO] -

[jira] [Commented] (STRATOS-1464) Untagged or Wrongly spawned instances are not terminated by Stratos

[ https://issues.apache.org/jira/browse/STRATOS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745224#comment-14745224 ] Gayan Gunarathne commented on STRATOS-1464: --- Further there can be Instance is

[jira] [Resolved] (STRATOS-1562) Application Sign Up is Enabled before Activating the Application

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

[jira] [Created] (STRATOS-1562) Application Sign Up is Enabled before Activating the Application

Anuruddha Lanka Liyanarachchi created STRATOS-1562: -- Summary: Application Sign Up is Enabled before Activating the Application Key: STRATOS-1562 URL: https://issues.apache.org/jira/browse/STRATOS-

[jira] [Resolved] (STRATOS-1559) Cannot Unsign up from Management Console UI

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

Re: Stratos 4.1: "Too many open files" issue

Hi Martin, CA is publishing events in every 15s by default. If you want to change it, please add -Dstats.notifier.interval=xx to stratos.sh of the CA. In order to add thrift-agent-config.xml to CA: - Please create /conf/data-bridge folder - Place the attached thrift-agent-config.xml with cu