Re: Jenkins build became unstable: Stratos-41x-Nightly-Build #64

Though the following ConcurrentModificationException is not related to the above test failure, instance startup is failing due to this. Will have a look at it later. [2015-12-02 00:52:51,718] ERROR {org.apache.stratos.cloud.controller.services.impl.InstanceCreator} - Could not start instance: [ca

Re: Jenkins build became unstable: Stratos-41x-Nightly-Build #64

Application didn't become active in Metadata service test case. Gayan triggered another build and it succeeded. However, I am will check on this intermittent failure. Tests run: 32, Failures: 1, Errors: 0, Skipped: 6, Time elapsed: 1,017.86 sec <<< FAILURE! - in TestSuite deployApplications(org.a

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

See

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

See

Jenkins build became unstable: Stratos-41x-Nightly-Build #64

See

Jenkins build became unstable: Stratos-41x-Nightly-Build » Apache Stratos - Integration Tests #64

See

Re: [Discuss] Release Apache Stratos 4.1.5

As we have fixed the issues that we identified, I think we are good go with rc2 release.Please reply to this if you encounter any blocker for this rc2 release. Thanks, Gayan On Sun, Nov 29, 2015 at 11:44 PM, Gayan Gunarathne wrote: > > > On Sun, Nov 29, 2015 at 11:31 PM, Imesh Gunaratne > wrot

Re: File handle leak in Thrift

Hi Shaheed, Let me clarify few things here, even though you might be already aware. - Maven dependency versions that you specify in your component's pom.xml for external dependencies should match the dependency that is actually bundled into the distribution via p2 feature management. - You need

Re: DataBridge continuously print info message in Integration test

Great.Thanks Akila On Tue, Dec 1, 2015 at 6:57 PM, Akila Ravihansa Perera wrote: > Hi Gayan, > This is because setEnabled method of ThriftStatisticsPublisher calls > init() method which causes receiverGroups array list to accumulate cep/das > nodes. It will try to create connections for each ent

Re: Cleaning up User Artifacts at Signup Removal

Sent a PR [1] with the fix. [1]. https://github.com/apache/stratos/pull/498/ On Sun, Nov 29, 2015 at 9:18 PM, Isuru Haththotuwa wrote: > > > On Fri, Nov 27, 2015 at 11:51 AM, Akila Ravihansa Perera < > raviha...@wso2.com> wrote: > >> Hi Isuru, >> >> Good thought. I'd suggest that we just rename

[GitHub] stratos pull request: Singup deletion cleanup

GitHub user isurulucky opened a pull request: https://github.com/apache/stratos/pull/498 Singup deletion cleanup You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/stratos singup_deletion_cleanup Alternatively you can review

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

Hi, The issue was due to a Thrift connection flood caused by unnecessary invocation of init() method in ThriftStatisticsPublisher. This is fixed now and Jenkins is back to normal in the latest build job [1]. I think we can proceed with further testing and doing the release build. [1] https://bui

Re: DataBridge continuously print info message in Integration test

Hi Gayan, This is because setEnabled method of ThriftStatisticsPublisher calls init() method which causes receiverGroups array list to accumulate cep/das nodes. It will try to create connections for each entry added. Ultimately this could result in a connection flood. I've fixed this in [1]. [1] h

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

See

Jenkins build is back to stable : Stratos-41x-Commit-Build #197

See

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

If the problem is due to too many logs getting accumulated, we might face this issue again. For the moment lets try to fix the test failure by fixing the connection issue to the Thrift server; that is the cause why lot of logs are there. I will check whether there is a known limitation in the Admin

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

Seems this integration failure[1] is happened due to the no of event logs we have in the server. When try to debug the code I couldn't read the logEvents object as there are so many server logs. I rescheduled that "IaasProviderAttributeTestCase" after the server restart test then it works fine. [

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

See

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

See