Hi Martin,
Found the reason why we didn't encounter these locking issue as we were
testing with default stratos pack which has
read.write.lock.monitor.enabled=false. The locking warning or issue is
raised only when you use read.write.lock.monitor.enabled=true. That's why
you were only facing these
Hi,
In the current Stratos implementation, the artifacts which are created by a
particular tenant is visible to all other tenants. I am going to implement
the tenant isolation mechanism, so that the artifacts will be only visible
to the tenant which has created the artifacts.
In order to implemen
Github user imesh commented on the pull request:
https://github.com/apache/stratos/pull/370#issuecomment-114015969
Thanks Anuruddha, that worked! I have now merged this pull request to
master branch.
---
If your project is set up for it, you can reply to this email and have your
repl
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/370
---
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 user imesh commented on the pull request:
https://github.com/apache/stratos/pull/373#issuecomment-114015786
Thanks Pubudu!! That worked, I have now merged this pull request to master
branch.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/stratos/pull/373
---
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
Thanks Asanka! Great work! Yes please arrange a hangout to analyze the
implementation details. I will also join.
Thanks
On Sun, Jun 21, 2015 at 2:54 PM, Asanka Sanjaya Herath
wrote:
> Hi Swapnil and Imesh,
>
> I have implemented a way to retrieve the instance ID my adding a new field
> to org.a
Hi Imesh,
I found the root cause for this issue.
ExecutorService executorService =
StratosThreadPool.getExecutorService("TEST_THREAD_POOL", 5);
We are using StratosThreadPool utility class to create or get already exist
executor service. "TEST_THREAD_POOL" is the identifier or the key we used
in
Yes I'm also seeing the same, we need to investigate this.
Thanks
On Sunday, June 21, 2015, Pubudu Gunatilaka wrote:
> Hi Devs,
>
> I ran the live test in python cartridge agent(PCA) and it was failed.
> There are 3 tests in the PCA and they run on based on the artifacts which
> is taken from a
Sorry Martin..I have only locally fixed the issue. I have pushed it now
only. Can you test with 1c21daaeea7b27ad0a0141a70b32e9443e78e309 when you
get chance? I will also continue testing with this fix.
Thanks,
Reka
On Mon, Jun 22, 2015 at 12:07 AM, Martin Eppel (meppel)
wrote:
> Btw,
>
>
>
> T
Btw,
This is my last commit I picked up from the stratos master:
commit 58bea52be814269416f70391fef50859aa5ae0a1
Author: lasinducharith
Date: Fri Jun 19 19:40:27 2015 +0530
From: Martin Eppel (meppel)
Sent: Sunday, June 21, 2015 10:28 AM
To: dev@stratos.apache.org; Reka Thirunavukkarasu
Cc: L
Hi Martin,
On Sun, Jun 21, 2015 at 10:58 PM, Martin Eppel (meppel)
wrote:
> Hi Reka,
>
>
>
> Here is *anothe*r example which fails, see application at [1.], attached
> log files and jsons. I run a few scenarios, the one which is failing is
> application with the name “s-g-c1-c2-c3” (last scena
Hi Martin,
Thanks for the information. I could find a locking issue while updating the
application in a hierarchical manner in your logs. I could fix the locking
issue. Since i'm unable to reproduce it, it is bit hard for me to verify
the fix. I will try further and update you on the progress...
Hi Devs,
I ran the live test in python cartridge agent(PCA) and it was failed. There
are 3 tests in the PCA and they run on based on the artifacts which is
taken from a public repo and a private repo. Each test uses defined
artifacts as parameters. When I ran all the 3 tests, which is the default
Github user anuruddhal commented on the pull request:
https://github.com/apache/stratos/pull/370#issuecomment-113911525
I have now updated branch with remote.
Can you please try again !
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Hi Asanka,
Thanks for your input.
I went through your changes. I also have figured out similar approach.
We will see how things go in hangout and what do you decide on this
approach.
Thanks and Regards,
Swapnil
On Sun, Jun 21, 2015 at 9:24 AM, Asanka Sanjaya Herath
wrote:
> Hi Swapnil and Im
Hi Imesh,
Thanks for the feedback.
Yes, as we have earlier communicated on how to expose instance id, I have
few changes to be done in my mind. I will make these changes and we can
then go through them to see if what I have done is correct or not and if
anything else needs to be done.
Okay, we w
Github user pubudu538 commented on the pull request:
https://github.com/apache/stratos/pull/373#issuecomment-113883396
Hi Imesh,
I reverted all the commits made to the branch and committed again. I think
now you should be able to merge. Sorry for the inconvenience caused.
Thank
Github user imesh commented on the pull request:
https://github.com/apache/stratos/pull/373#issuecomment-113879786
Thanks for the quick response! It looks like still we have a problem:
CONFLICT (content): Merge conflict in
components/org.apache.stratos.rest.endpoint/src/main/j
Hi Swapnil and Imesh,
I have implemented a way to retrieve the instance ID my adding a new field
to org.apache.stratos.load.balancer.common.domain.Member class and doing
relevant changes
to org.apache.stratos.cloud.controller.messaging.topology.TopologyBuilder
class.
You can see it by analyzing co
Github user pubudu538 commented on the pull request:
https://github.com/apache/stratos/pull/373#issuecomment-113879174
Hi Imesh, I updated my local branch and merged with the master. Can you
check now?
---
If your project is set up for it, you can reply to this email and have your
re
Hi Swapnil,
Thanks for the details, yes may be we can go ahead and add the Instance Id
to the Member definition in the messaging component Topology. We will also
need to add it to the load balancer Topology (load balancer has a separate
structure).
Please note that Autoscaler also use the term "I
Hi Imesh,
Yes we can do that. But it doesn't reduce the time taken by the method
call. It is more or less same as when filters are used.
I was wondering if Asanka also needs instance id for GCE load balancer
support and how he is doing it? Whether he can also use some mechanism like
this or he do
Great! Thanks Reka!
On Sun, Jun 21, 2015 at 8:34 AM, Reka Thirunavukkarasu
wrote:
> Hi Martin/Imesh,
>
> Sure..I will have a look on the logs. I will also go through the recent
> commits and try to revert the fix which added for nested group scaling as
> it is not needed for this release. As Ma
Github user imesh commented on the pull request:
https://github.com/apache/stratos/pull/373#issuecomment-113876446
Hi Pubudu, the merge process failed with the following error, can you
please try to update your local branch with the remote and update this pull
request?
Auto-m
Thanks Lahiru. I will check.
*T. Pranavan*
*BSc Eng Undergraduate| Department of Computer Science & Engineering
,University of Moratuwa*
*Mobile| *0775136836
On 21 June 2015 at 12:38, Lahiru Sandaruwan wrote:
> It seems you have to use CEP 3.0.0. Please check the thread "Stratos with
> external
It seems you have to use CEP 3.0.0. Please check the thread "Stratos with
external CEP 3.0.0".
Thanks.
On Sun, Jun 21, 2015 at 11:50 AM, Pranavan Theivendiram <
pranavan...@cse.mrt.ac.lk> wrote:
> Hi all,
>
> Please help me on $subject
>
> Thanks
> *T. Pranavan*
> *BSc Eng Undergraduate| Departm
27 matches
Mail list logo
