[Dev] [DAS] Aggregated feature for DAS capabilities

[Ayyoob Hamza]

Hi all,
We are planing to have DAS capabilities within the IoT-Server and EMM. And
our main idea is to be able to use DAS as an internal entity within the
IoT-Server/EMM or an external entity(ie. IoT server without analytics) by
switching through profiles. So wanted to know whether there is an
aggregated feature that does the task of providing DAS capabilities. if
there isn't any aggregated feature would it be feasible to create one ?.


Thanks,
*Ayyoob Hamza*
*Software Engineer*
WSO2 Inc.; http://wso2.com
email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

[Akila Ravihansa Perera]

All package installations should have a check whether package is already
installed. IMO, enforcing a module order to overcome this is not the proper
way to solve it.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

[Anuruddha Liyanarachchi]

Hi

When we include python in  PCA and configurator, won't it get installed by
> both the modules where i might give errors as it is already installed by
> the other module. Otherwise, we will need to add a check for whether the
> relevant library exists already or not.
> In order to overcome this, what if we define a module for python with all
> the relevant libraries and then include it as we need when defining node
> classes for relevant module. Eg:
> Class['stratos_base'] -> Class['java'] -> Class['*python*'] ->
> Class['configurator']-> Class['python_agent'] -> Class['wso2am']


+1. From this way we can reuse the python module in other cartridges as
well.

On Mon, Sep 7, 2015 at 11:04 AM, Gayan Gunarathne  wrote:

> Hi,
>
> On Mon, Sep 7, 2015 at 10:38 AM, Reka Thirunavukkarasu 
> wrote:
>
>> Hi
>>
>> When we include python in  PCA and configurator, won't it get installed
>> by both the modules where i might give errors as it is already installed by
>> the other module. Otherwise, we will need to add a check for whether the
>> relevant library exists already or not.
>>
> Yeah. We need to check whether  those are already exist or not.
>
>>
>> In order to overcome this, what if we define a module for python with all
>> the relevant libraries and then include it as we need when defining node
>> classes for relevant module. Eg:
>>
>> Class['stratos_base'] -> Class['java'] -> Class['*python*'] ->
>> Class['configurator']-> Class['python_agent'] -> Class['wso2am']
>>
>
> +1. I think this is the way for long run.
>
>>
>> WDYT?
>>
>> Thanks,
>> Reka
>>
>>
>> On Sun, Sep 6, 2015 at 11:50 PM, Imesh Gunaratne  wrote:
>>
>>> On Sun, Sep 6, 2015 at 11:27 AM, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
 Hi,

 IMO we can define 'python-dev', 'python-pip' libraries in stratos base
 since they are required by configurator which is a mandatory module.

>>>
>>> Why do we use "python-dev" instead of "python"?
>>>
>>> It would be better to include them in the Configurator and PCA modules
>>> specifically. I do not see any reason to include them in the base module.
>>>
>>> On Sun, Sep 6, 2015 at 11:27 AM, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
 Hi,

 IMO we can define 'python-dev', 'python-pip' libraries in stratos base
 since they are required by configurator which is a mandatory module.
 Therefore,
 In configurator module we can inlcude jinja2;
 In PCA module we can include PCA related python dependencies 
 *(**paho,psutil,gittle,pexpect,yapsy
 etc.);*

 WDYT ?


 On Sun, Sep 6, 2015 at 11:02 AM, Gayan Gunarathne 
 wrote:

> It is ok to redefined the python-pip module in configurator module
> since currently it is used in PCA and configurator only.
>
> But this might be a issue with other python libraries as well if that
> commonly used among the python modules.Also if there is several python
> modules exists we need to redefined the libraries everywhere.IMO we may
> need to include separate module for python and that module we can include
> the common libraries for python.
>
> Thanks,
> Gayan
>
> On Sun, Sep 6, 2015 at 9:25 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Raj,
>>
>> Yes, I meant python-pip should not be removed from PCA module but
>> should be installed for configurator as well.
>>
>> I think it should be redefined for configurator module since
>> python-pip is not a compulsory package. We can use Java agent without it.
>>
>> Thanks.
>>
>> On Sun, Sep 6, 2015 at 6:17 AM, Rajkumar Rajaratnam <
>> rajkum...@wso2.com> wrote:
>>
>>>
>>>
>>> On Sun, Sep 6, 2015 at 7:45 AM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 Hi Raj,

 I think we should not remove python-pip from PCA module since
 those dependencies should be installed for PCA to function.

>>>
>>> ​In the very similar way, python-pip should be installed for
>>> configurator to function as well :). So if I am using java agent 
>>> instead of
>>> python agent, how would configurator work without python-pip? IMO, we 
>>> can
>>> either move python-pip to stratos_base or use [1] to redfine python-pip
>>> package in configurator if it is not already defined anywhere else.
>>>
>>> [1]
>>> http://stackoverflow.com/questions/15266347/puppet-test-if-a-package-already-defined
>>>
>>> Thanks,
>>> Raj.
>>>

 @Anuruddha: I still see that jinja2 is packed from PCA module [1].
 Shall we move this to configurator module?

 [1]
 https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/python_agent/manifests/initialize.pp#L57

 Thanks.

 On Sat, Sep 5, 2015 at 3:21 PM, Anuruddh

Re: [Dev] Carbon-deployment 4.5.2 released to staging

[KasunG Gajasinghe]

Released from the staging.

On Fri, Sep 4, 2015 at 8:24 PM, Niranjan Karunanandham 
wrote:

> Hi Kasun,
>
> I was successfully able to build the AS pack with the carbon-deployment
> 4.5.2 (staging url). I did a basic testing by uploading a webapp and
> testing it.
>
> Regards,
> Nira
>
> On Fri, Sep 4, 2015 at 7:11 PM, KasunG Gajasinghe  wrote:
>
>> Hi,
>>
>> Please find the staging url -
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbondeployment-044/
>>
>> Thanks.
>>
>> --
>>
>> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
>> email: kasung AT spamfree wso2.com
>> linked-in: http://lk.linkedin.com/in/gajasinghe
>> blog: http://kasunbg.org
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>



-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

[Gayan Gunarathne]

Hi,

On Mon, Sep 7, 2015 at 10:38 AM, Reka Thirunavukkarasu 
wrote:

> Hi
>
> When we include python in  PCA and configurator, won't it get installed by
> both the modules where i might give errors as it is already installed by
> the other module. Otherwise, we will need to add a check for whether the
> relevant library exists already or not.
>
Yeah. We need to check whether  those are already exist or not.

>
> In order to overcome this, what if we define a module for python with all
> the relevant libraries and then include it as we need when defining node
> classes for relevant module. Eg:
>
> Class['stratos_base'] -> Class['java'] -> Class['*python*'] ->
> Class['configurator']-> Class['python_agent'] -> Class['wso2am']
>

+1. I think this is the way for long run.

>
> WDYT?
>
> Thanks,
> Reka
>
>
> On Sun, Sep 6, 2015 at 11:50 PM, Imesh Gunaratne  wrote:
>
>> On Sun, Sep 6, 2015 at 11:27 AM, Anuruddha Liyanarachchi <
>> anurudd...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> IMO we can define 'python-dev', 'python-pip' libraries in stratos base
>>> since they are required by configurator which is a mandatory module.
>>>
>>
>> Why do we use "python-dev" instead of "python"?
>>
>> It would be better to include them in the Configurator and PCA modules
>> specifically. I do not see any reason to include them in the base module.
>>
>> On Sun, Sep 6, 2015 at 11:27 AM, Anuruddha Liyanarachchi <
>> anurudd...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> IMO we can define 'python-dev', 'python-pip' libraries in stratos base
>>> since they are required by configurator which is a mandatory module.
>>> Therefore,
>>> In configurator module we can inlcude jinja2;
>>> In PCA module we can include PCA related python dependencies 
>>> *(**paho,psutil,gittle,pexpect,yapsy
>>> etc.);*
>>>
>>> WDYT ?
>>>
>>>
>>> On Sun, Sep 6, 2015 at 11:02 AM, Gayan Gunarathne 
>>> wrote:
>>>
 It is ok to redefined the python-pip module in configurator module
 since currently it is used in PCA and configurator only.

 But this might be a issue with other python libraries as well if that
 commonly used among the python modules.Also if there is several python
 modules exists we need to redefined the libraries everywhere.IMO we may
 need to include separate module for python and that module we can include
 the common libraries for python.

 Thanks,
 Gayan

 On Sun, Sep 6, 2015 at 9:25 AM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> Hi Raj,
>
> Yes, I meant python-pip should not be removed from PCA module but
> should be installed for configurator as well.
>
> I think it should be redefined for configurator module since
> python-pip is not a compulsory package. We can use Java agent without it.
>
> Thanks.
>
> On Sun, Sep 6, 2015 at 6:17 AM, Rajkumar Rajaratnam <
> rajkum...@wso2.com> wrote:
>
>>
>>
>> On Sun, Sep 6, 2015 at 7:45 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Raj,
>>>
>>> I think we should not remove python-pip from PCA module since those
>>> dependencies should be installed for PCA to function.
>>>
>>
>> ​In the very similar way, python-pip should be installed for
>> configurator to function as well :). So if I am using java agent instead 
>> of
>> python agent, how would configurator work without python-pip? IMO, we can
>> either move python-pip to stratos_base or use [1] to redfine python-pip
>> package in configurator if it is not already defined anywhere else.
>>
>> [1]
>> http://stackoverflow.com/questions/15266347/puppet-test-if-a-package-already-defined
>>
>> Thanks,
>> Raj.
>>
>>>
>>> @Anuruddha: I still see that jinja2 is packed from PCA module [1].
>>> Shall we move this to configurator module?
>>>
>>> [1]
>>> https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/python_agent/manifests/initialize.pp#L57
>>>
>>> Thanks.
>>>
>>> On Sat, Sep 5, 2015 at 3:21 PM, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
 Hi Raj,

 Thanks for pointing this out. I have now added the jinja2
 dependency to configurator module and removed from PCA. [1]

 [1]
 https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/configurator/manifests/init.pp#L32

 On Sat, Sep 5, 2015 at 3:14 PM, Rajkumar Rajaratnam <
 rajkum...@wso2.com> wrote:

> Hi,
>
> I think python-pip & jinja2 should be installed by configurator
> puppet module, not by python agent.
>
> I am using vagrant, puppet and configurator to setup my
> development environment, but I am not using python agent. Since 
> $subject is
> not done, I had to modify configurator puppet module

Re: [Dev] [DAS] unable to purge data

[Nirmal Fernando]

Hi Sachith,

This error message seems to have few grammatical errors and formatting
errors. Please correct them.

On Mon, Sep 7, 2015 at 10:58 AM, Sachith Withana  wrote:

> Hi Rukshan,
>
> That error message is there because you haven't added a value to the
> second field ( Purge Record older than (days) field).
>
> I just tested the data purging it seems to work fine.
>
> Do you want to purge all the data?
>
> On Sat, Sep 5, 2015 at 11:03 AM, Rukshan Premathunga 
> wrote:
>
>> Hi,
>>
>> i tried data purging function in DAS data_explorer. But i get the
>> following error.
>> please find the attached screenshot.
>>
>>
>> ​
>> Thanks and Regards.
>>
>> --
>> Rukshan Chathuranga.
>> Software Engineer.
>> WSO2, Inc.
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] unable to purge data

[Sachith Withana]

Hi Rukshan,

That error message is there because you haven't added a value to the second
field ( Purge Record older than (days) field).

I just tested the data purging it seems to work fine.

Do you want to purge all the data?

On Sat, Sep 5, 2015 at 11:03 AM, Rukshan Premathunga 
wrote:

> Hi,
>
> i tried data purging function in DAS data_explorer. But i get the
> following error.
> please find the attached screenshot.
>
>
> ​
> Thanks and Regards.
>
> --
> Rukshan Chathuranga.
> Software Engineer.
> WSO2, Inc.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sachith Withana
Software Engineer; WSO2 Inc.; http://wso2.com
E-mail: sachith AT wso2.com
M: +94715518127
Linked-In: https://lk.linkedin.com/in/sachithwithana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

[Reka Thirunavukkarasu]

Hi

When we include python in  PCA and configurator, won't it get installed by
both the modules where i might give errors as it is already installed by
the other module. Otherwise, we will need to add a check for whether the
relevant library exists already or not.

In order to overcome this, what if we define a module for python with all
the relevant libraries and then include it as we need when defining node
classes for relevant module. Eg:

Class['stratos_base'] -> Class['java'] -> Class['*python*'] ->
Class['configurator']-> Class['python_agent'] -> Class['wso2am']

WDYT?

Thanks,
Reka


On Sun, Sep 6, 2015 at 11:50 PM, Imesh Gunaratne  wrote:

> On Sun, Sep 6, 2015 at 11:27 AM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi,
>>
>> IMO we can define 'python-dev', 'python-pip' libraries in stratos base
>> since they are required by configurator which is a mandatory module.
>>
>
> Why do we use "python-dev" instead of "python"?
>
> It would be better to include them in the Configurator and PCA modules
> specifically. I do not see any reason to include them in the base module.
>
> On Sun, Sep 6, 2015 at 11:27 AM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi,
>>
>> IMO we can define 'python-dev', 'python-pip' libraries in stratos base
>> since they are required by configurator which is a mandatory module.
>> Therefore,
>> In configurator module we can inlcude jinja2;
>> In PCA module we can include PCA related python dependencies 
>> *(**paho,psutil,gittle,pexpect,yapsy
>> etc.);*
>>
>> WDYT ?
>>
>>
>> On Sun, Sep 6, 2015 at 11:02 AM, Gayan Gunarathne 
>> wrote:
>>
>>> It is ok to redefined the python-pip module in configurator module since
>>> currently it is used in PCA and configurator only.
>>>
>>> But this might be a issue with other python libraries as well if that
>>> commonly used among the python modules.Also if there is several python
>>> modules exists we need to redefined the libraries everywhere.IMO we may
>>> need to include separate module for python and that module we can include
>>> the common libraries for python.
>>>
>>> Thanks,
>>> Gayan
>>>
>>> On Sun, Sep 6, 2015 at 9:25 AM, Akila Ravihansa Perera <
>>> raviha...@wso2.com> wrote:
>>>
 Hi Raj,

 Yes, I meant python-pip should not be removed from PCA module but
 should be installed for configurator as well.

 I think it should be redefined for configurator module since python-pip
 is not a compulsory package. We can use Java agent without it.

 Thanks.

 On Sun, Sep 6, 2015 at 6:17 AM, Rajkumar Rajaratnam >>> > wrote:

>
>
> On Sun, Sep 6, 2015 at 7:45 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi Raj,
>>
>> I think we should not remove python-pip from PCA module since those
>> dependencies should be installed for PCA to function.
>>
>
> ​In the very similar way, python-pip should be installed for
> configurator to function as well :). So if I am using java agent instead 
> of
> python agent, how would configurator work without python-pip? IMO, we can
> either move python-pip to stratos_base or use [1] to redfine python-pip
> package in configurator if it is not already defined anywhere else.
>
> [1]
> http://stackoverflow.com/questions/15266347/puppet-test-if-a-package-already-defined
>
> Thanks,
> Raj.
>
>>
>> @Anuruddha: I still see that jinja2 is packed from PCA module [1].
>> Shall we move this to configurator module?
>>
>> [1]
>> https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/python_agent/manifests/initialize.pp#L57
>>
>> Thanks.
>>
>> On Sat, Sep 5, 2015 at 3:21 PM, Anuruddha Liyanarachchi <
>> anurudd...@wso2.com> wrote:
>>
>>> Hi Raj,
>>>
>>> Thanks for pointing this out. I have now added the jinja2 dependency
>>> to configurator module and removed from PCA. [1]
>>>
>>> [1]
>>> https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/configurator/manifests/init.pp#L32
>>>
>>> On Sat, Sep 5, 2015 at 3:14 PM, Rajkumar Rajaratnam <
>>> rajkum...@wso2.com> wrote:
>>>
 Hi,

 I think python-pip & jinja2 should be installed by configurator
 puppet module, not by python agent.

 I am using vagrant, puppet and configurator to setup my development
 environment, but I am not using python agent. Since $subject is not 
 done, I
 had to modify configurator puppet module.

 It would be better if we do the $subject.

 Thanks,
 Raj.

 --
 Rajkumar Rajaratnam
 Committer & PMC Member, Apache Stratos
 Software Engineer, WSO2

 Mobile : +94777568639
 Blog : rajkumarr.com

 ___

Re: [Dev] [VOTE] Release WSO2 Governance Registry 5.0.0 RC3

[Rajith Roshan]

Hi,

I tested following scenarios when config and governance registries are
mounted.


   - Add new RXTs
   - Advanced search in Management Console
   - Activity search in Management Console
   - Life cycle promote and demote in management console
   - Add new tenant
   - CAR app deployment
   - Secure Vault Tool in management console
   - Upload WSDLs using gar and zip files in management console
   - Upload schemas using gar and zip files in management console
   - Upload policy using zip files in management console.


[+] stable

Thanks!


On Mon, Sep 7, 2015 at 8:57 AM, Prasanna Dangalla  wrote:

> Hi
>
> I tested,
>
>- Tags in publisher end
>- Notes in publisher end
>- Soap service creation in publisher end
>- WSDL upload from URL and through a file in publisher end
>- Diff view in publisher end
>- Dependency graph in publisher end
>- Asset listing in publisher, store end
>- Asset rating in store end
>- Lifecycle promote demote in publisher end
>- Lifecycle addition from management console
>- RXT addition from management console
>
>
> Stable pack for release
>
> [+] stable
>
>
>
> On Fri, Sep 4, 2015 at 4:58 PM, Chandana Napagoda 
> wrote:
>
>> Hi Devs,
>>
>> *This is the RC3 release candidate of WSO2 Governance Registry 5.0.0 *
>>
>> This release fixes the following issues:
>>
>> https://wso2.org/jira/browse/REGISTRY-2927?filter=12388
>>
>> Please download, test and vote. Please refer the release verification
>> guide for detailed information on verifying this release.
>>
>> *Source & binary distribution files:*
>>
>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-042/org/wso2/greg/wso2greg/5.0.0/
>>
>> *Maven staging repo:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-042/
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/product-greg/releases/tag/v5.0.0-rc3
>>
>>
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (explain why)
>>
>> Thanks and Regards
>> G-Reg team
>>
>> --
>> *Chandana Napagoda*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.org
>>
>> *Email  :  chand...@wso2.com **Mobile : +94718169299
>> <%2B94718169299>*
>>
>> *Blog  :http://cnapagoda.blogspot.com *
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Prasanna Dangalla
> Software Engineer, WSO2, Inc.; http://wso2.com/
> lean.enterprise.middleware
>
> cell: +94 777 55 80 30 | +94 718 11 27 51
> twitter: @prasa77
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 <%2B94-71-554-8430>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Greg 5.0.0 Beta] Can't change the notification settings under options section of store

[Shafreen Anfar]

On Sun, Sep 6, 2015 at 3:34 AM, Chandana Napagoda  wrote:

> HI Shafreen,
>
> We couldn't reproduce this issue with mentioned steps. Shall we have a
> offline discussion to review this?
>

Yeah. Let me know when you I have some free time :)


>
> Regards,
> Chandana
>
> On Sat, Sep 5, 2015 at 1:25 AM, Shafreen Anfar  wrote:
>
>> Hi Chandana,
>>
>> Any update on this ?
>>
>>
>> On Tue, Aug 25, 2015 at 9:45 AM, Shafreen Anfar 
>> wrote:
>>
>>> Hi All,
>>>
>>> I just created a Rest service. Then went to the store and tried to
>>> change the notification settings. Even though I click on the icon (apple
>>> like button), it does't do anything. In the console I could see the below
>>> error.
>>>
>>> [2015-08-25 10:36:41,826] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,110] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,114] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,600] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,602] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,603] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,608] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,897] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,902] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,903] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,910] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,912] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,916] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,921] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:43,921] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>> [2015-08-25 10:36:51,895] ERROR {rxt.core} -  Unable to locate
>>> assetResources for tenant: -1234 and type: undefined
>>>
>>>
>>> --
>>> Regards,
>>> *Shafreen*
>>> Software Engineer
>>> WSO2 Inc
>>> Mobile : 077-556-395-1
>>>
>>
>>
>>
>> --
>> Regards,
>> *Shafreen*
>> Software Engineer
>> WSO2 Inc
>> Mobile : 077-556-395-1
>>
>
>
>
> --
> *Chandana Napagoda*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile : +94718169299
> <%2B94718169299>*
>
> *Blog  :http://cnapagoda.blogspot.com *
>
>


-- 
Regards,
*Shafreen*
Software Engineer
WSO2 Inc
Mobile : 077-556-395-1
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to define version ranges for orbit bundles

[Sameera Jayasoma]

Hi Aruna,

On Fri, Sep 4, 2015 at 11:40 AM, Aruna Karunarathna  wrote:

> Hi Sameera,
>
> Small question,
>
> What if there is same bundle with multiple versions?.. Maybe packing with
> some features?.
>

Only one bundle should be loaded to the runtime most of the time. But if
they are incompatible(API level) versions and there are dependent bundles,
then we have to load those two bundles to the runtime.

e.g. log4j 1.x and log4j 2.x.

Thanks,
Sameera.

>
> sample.bundle_1.6.1.wso2v14, sample.bundle_1.6.1.wso2v15? Theoretically there
> shouldn't be a problem right?..
> But we can't guarantee which bundle gets wired at the run-time, and we
> need a specific fix from a specific wso2 version?
>
> Regards,
> Aruna
>
> On Fri, Sep 4, 2015 at 11:32 AM, Aruna Karunarathna 
> wrote:
>
>>
>>
>> On Fri, Sep 4, 2015 at 11:22 AM, Sameera Jayasoma 
>> wrote:
>>
>>> Hi Rajith,
>>>
>>> The correct one should be  [1.6.1, 1.7) AFAIK.
>>>
>> Yep, this should be the correct way.
>>
>>>
>>> Niranjan please update the document.
>>>
>>> Thanks,
>>> Sameera.
>>>
>>> On Fri, Sep 4, 2015 at 11:02 AM, Rajith Vitharana 
>>> wrote:
>>>
 Hi,

 How should we do the $subject? Asking this since in carbon commons
 axis2 version range is defined as in [1] don't we follow the same concept
 for orbit bundles? shouldn't this be as [2]?

 [1] - [1.6.1.wso2v14,
 1.7.0)
 [2] - [1.6, 1.7)

 Thanks,

 --
 Rajith Vitharana

 Software Engineer,
 WSO2 Inc. : wso2.com
 Mobile : +94715883223
 Blog : http://lankavitharana.blogspot.com/

>>>
>>>
>>>
>>> --
>>> 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
>>>
>>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *| Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.wso2.com
>>
>>
>
>
>
> --
>
> *Aruna Sujith Karunarathna *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>



-- 
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 Governance Registry 5.0.0 RC3

[Prasanna Dangalla]

Hi

I tested,

   - Tags in publisher end
   - Notes in publisher end
   - Soap service creation in publisher end
   - WSDL upload from URL and through a file in publisher end
   - Diff view in publisher end
   - Dependency graph in publisher end
   - Asset listing in publisher, store end
   - Asset rating in store end
   - Lifecycle promote demote in publisher end
   - Lifecycle addition from management console
   - RXT addition from management console


Stable pack for release

[+] stable



On Fri, Sep 4, 2015 at 4:58 PM, Chandana Napagoda  wrote:

> Hi Devs,
>
> *This is the RC3 release candidate of WSO2 Governance Registry 5.0.0 *
>
> This release fixes the following issues:
>
> https://wso2.org/jira/browse/REGISTRY-2927?filter=12388
>
> Please download, test and vote. Please refer the release verification
> guide for detailed information on verifying this release.
>
> *Source & binary distribution files:*
>
> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-042/org/wso2/greg/wso2greg/5.0.0/
>
> *Maven staging repo:*
> http://maven.wso2.org/nexus/content/repositories/orgwso2greg-042/
>
> *The tag to be voted upon:*
> https://github.com/wso2/product-greg/releases/tag/v5.0.0-rc3
>
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (explain why)
>
> Thanks and Regards
> G-Reg team
>
> --
> *Chandana Napagoda*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile : +94718169299
> <%2B94718169299>*
>
> *Blog  :http://cnapagoda.blogspot.com *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Prasanna Dangalla
Software Engineer, WSO2, Inc.; http://wso2.com/
lean.enterprise.middleware

cell: +94 777 55 80 30 | +94 718 11 27 51
twitter: @prasa77
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Error in creating system tables: Specified key was too long

[Mohanadarshan Vivekanandalingam]

On Sun, Sep 6, 2015 at 2:06 PM, Niranda Perera  wrote:

> Hi Pubudu,
>
>
Hi Niranda,


> can you delete the mysql databases and create them as follows. this
> resolved a similar problem in the windows env.
>
> create database  character set latin1;
>
> please to the thread [1]
>

Sorry, I don't think above is a correct fix (IMO, It is just a
workaround).. There are various reasons where a user needs to use different
charsets.. Please check whether that specific constraint is required or not
(allocated size and all). I think, In IS also we have came across similar
issue. Please check, how they resolved the issue.

Thanks,
Mohan



>
> rgds
>
> [1] [Dev] MySQL error while executing dbscripts in windows env
>
> On Sun, Sep 6, 2015 at 9:38 PM, Niranda Perera  wrote:
>
>> Hi Pubudu,
>>
>> I got the same error in the windows env. I'm working on it. will update
>> you soon
>>
>> cheers
>>
>> On Sun, Sep 6, 2015 at 9:31 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Niranda,
>>>
>>> Actually I am running on docker. Both DAS and mysql are docker
>>> containers which run on Debian.
>>>
>>> Thank you!
>>>
>>> On Sun, Sep 6, 2015 at 7:04 PM, Niranda Perera  wrote:
>>>
 Hi Pubudu,

 are you using the windows env?

 On Sun, Sep 6, 2015 at 3:52 PM, Pubudu Gunatilaka 
 wrote:

> Hi,
>
> I am using one of the nightly built DAS packs from last week. I have
> used a mysql database for analytic file system and at the server start up 
> I
> am getting following error message.
>
> TID: [-1234] [] [2015-09-06 09:01:51,489] ERROR
> {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent} -
>  Error in activating analytics data service: Error in creating analytics
> data service from configuration: Error in creating system tables: 
> Specified
> key was too long; max key length is 767 bytes
> {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent}
> org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsException:
> Error in creating analytics data service from configuration: Error in
> creating system tables: Specified key was too long; max key length is 767
> bytes
> at
> org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceImpl.(AnalyticsDataServiceImpl.java:137)
> at
> org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent.activate(AnalyticsDataServiceComponent.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
> at
> org.wso2.carbon.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessor

Re: [Dev] [DAS] Error in creating system tables: Specified key was too long

[Pubudu Gunatilaka]

Hi Niranda,

This approach solved the issue.

Thank you!

On Mon, Sep 7, 2015 at 12:36 AM, Niranda Perera  wrote:

> Hi Pubudu,
>
> can you delete the mysql databases and create them as follows. this
> resolved a similar problem in the windows env.
>
> create database  character set latin1;
>
> please to the thread [1]
>
> rgds
>
> [1] [Dev] MySQL error while executing dbscripts in windows env
>
> On Sun, Sep 6, 2015 at 9:38 PM, Niranda Perera  wrote:
>
>> Hi Pubudu,
>>
>> I got the same error in the windows env. I'm working on it. will update
>> you soon
>>
>> cheers
>>
>> On Sun, Sep 6, 2015 at 9:31 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Niranda,
>>>
>>> Actually I am running on docker. Both DAS and mysql are docker
>>> containers which run on Debian.
>>>
>>> Thank you!
>>>
>>> On Sun, Sep 6, 2015 at 7:04 PM, Niranda Perera  wrote:
>>>
 Hi Pubudu,

 are you using the windows env?

 On Sun, Sep 6, 2015 at 3:52 PM, Pubudu Gunatilaka 
 wrote:

> Hi,
>
> I am using one of the nightly built DAS packs from last week. I have
> used a mysql database for analytic file system and at the server start up 
> I
> am getting following error message.
>
> TID: [-1234] [] [2015-09-06 09:01:51,489] ERROR
> {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent} -
>  Error in activating analytics data service: Error in creating analytics
> data service from configuration: Error in creating system tables: 
> Specified
> key was too long; max key length is 767 bytes
> {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent}
> org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsException:
> Error in creating analytics data service from configuration: Error in
> creating system tables: Specified key was too long; max key length is 767
> bytes
> at
> org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceImpl.(AnalyticsDataServiceImpl.java:137)
> at
> org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent.activate(AnalyticsDataServiceComponent.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
> at
> org.wso2.carbon.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp

Re: [Dev] MySQL error while executing dbscripts in windows env

[Gokul Balakrishnan]

Hi Niranda,

IMO we should fix this properly, by setting the type to VARCHAR(255) rather
than VARCHAR(256) for fields with unique indices, in the place where the
tables are created. This is because we can't mandate users to have a
specific character set (especially latin1). Setting the engine to MyISAM
during table creation would also solve this but that is also not
recommended.

Thanks,

On Monday, 7 September 2015, Niranda Perera  wrote:

> HI Hemika,
>
> it worked! thank you :-)
>
> On Mon, Sep 7, 2015 at 12:19 AM, Hemika Kodikara  > wrote:
>
>> Hi Niranda,
>>
>> As far as I can remember this is coming due to a db collation issue.
>>
>> You can fix it by changing Collation from UTF-8 to latin.
>>
>> ex :
>> create database  character set latin1;
>>
>> Regards,
>> Hemika
>>
>> Hemika Kodikara
>> Software Engineer
>> WSO2 Inc.
>> lean . enterprise . middleware
>> http://wso2.com
>>
>> Mobile : +9477762
>>
>> On Mon, Sep 7, 2015 at 12:09 AM, Niranda Perera > > wrote:
>>
>>> Hi all,
>>>
>>> I'm testing DAS 3.0.0 in the windows env (windows 8.1 & java 1.8.0) with
>>> MySQL as the carbon_db.
>>>
>>> I tried, executing the mysql setup dbscript and I get the following error
>>>
>>> 23:41:09 CREATE INDEX REG_PATH_IND_BY_PATH_VALUE USING HASH ON
>>> REG_PATH(REG_PATH_VALUE, REG_TENANT_ID) Error Code: 1071. Specified key
>>> was too long; max key length is 767 bytes 0.078 sec
>>>
>>> this error has already been reported [1] and when I check the script
>>> also, it mentions this CARBON JIRA.
>>>
>>> however, this error does not occur in the linux (ubuntu) env.
>>>
>>> would like to know how to proceed with this?
>>>
>>> rgds
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-5917
>>>
>>> --
>>> *Niranda Perera*
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94-71-554-8430
>>> Twitter: @n1r44 
>>> https://pythagoreanscript.wordpress.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org 
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>


-- 
Gokul Balakrishnan
Senior Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS] Error in creating system tables: Specified key was too long

[Niranda Perera]

Hi Pubudu,

can you delete the mysql databases and create them as follows. this
resolved a similar problem in the windows env.

create database  character set latin1;

please to the thread [1]

rgds

[1] [Dev] MySQL error while executing dbscripts in windows env

On Sun, Sep 6, 2015 at 9:38 PM, Niranda Perera  wrote:

> Hi Pubudu,
>
> I got the same error in the windows env. I'm working on it. will update
> you soon
>
> cheers
>
> On Sun, Sep 6, 2015 at 9:31 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Niranda,
>>
>> Actually I am running on docker. Both DAS and mysql are docker containers
>> which run on Debian.
>>
>> Thank you!
>>
>> On Sun, Sep 6, 2015 at 7:04 PM, Niranda Perera  wrote:
>>
>>> Hi Pubudu,
>>>
>>> are you using the windows env?
>>>
>>> On Sun, Sep 6, 2015 at 3:52 PM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi,

 I am using one of the nightly built DAS packs from last week. I have
 used a mysql database for analytic file system and at the server start up I
 am getting following error message.

 TID: [-1234] [] [2015-09-06 09:01:51,489] ERROR
 {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent} -
  Error in activating analytics data service: Error in creating analytics
 data service from configuration: Error in creating system tables: Specified
 key was too long; max key length is 767 bytes
 {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent}
 org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsException:
 Error in creating analytics data service from configuration: Error in
 creating system tables: Specified key was too long; max key length is 767
 bytes
 at
 org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceImpl.(AnalyticsDataServiceImpl.java:137)
 at
 org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent.activate(AnalyticsDataServiceComponent.java:62)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
 at
 org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
 at
 org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
 at
 org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
 at
 org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
 at
 org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
 at
 org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
 at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
 at
 org.wso2.carbon.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:106)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:606)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
 at
 org.eclipse.equ

Re: [Dev] MySQL error while executing dbscripts in windows env

[Niranda Perera]

HI Hemika,

it worked! thank you :-)

On Mon, Sep 7, 2015 at 12:19 AM, Hemika Kodikara  wrote:

> Hi Niranda,
>
> As far as I can remember this is coming due to a db collation issue.
>
> You can fix it by changing Collation from UTF-8 to latin.
>
> ex :
> create database  character set latin1;
>
> Regards,
> Hemika
>
> Hemika Kodikara
> Software Engineer
> WSO2 Inc.
> lean . enterprise . middleware
> http://wso2.com
>
> Mobile : +9477762
>
> On Mon, Sep 7, 2015 at 12:09 AM, Niranda Perera  wrote:
>
>> Hi all,
>>
>> I'm testing DAS 3.0.0 in the windows env (windows 8.1 & java 1.8.0) with
>> MySQL as the carbon_db.
>>
>> I tried, executing the mysql setup dbscript and I get the following error
>>
>> 23:41:09 CREATE INDEX REG_PATH_IND_BY_PATH_VALUE USING HASH ON
>> REG_PATH(REG_PATH_VALUE, REG_TENANT_ID) Error Code: 1071. Specified key
>> was too long; max key length is 767 bytes 0.078 sec
>>
>> this error has already been reported [1] and when I check the script
>> also, it mentions this CARBON JIRA.
>>
>> however, this error does not occur in the linux (ubuntu) env.
>>
>> would like to know how to proceed with this?
>>
>> rgds
>>
>> [1] https://wso2.org/jira/browse/CARBON-5917
>>
>> --
>> *Niranda Perera*
>> Software Engineer, WSO2 Inc.
>> Mobile: +94-71-554-8430
>> Twitter: @n1r44 
>> https://pythagoreanscript.wordpress.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MySQL error while executing dbscripts in windows env

[Hemika Kodikara]

Hi Niranda,

As far as I can remember this is coming due to a db collation issue.

You can fix it by changing Collation from UTF-8 to latin.

ex :
create database  character set latin1;

Regards,
Hemika

Hemika Kodikara
Software Engineer
WSO2 Inc.
lean . enterprise . middleware
http://wso2.com

Mobile : +9477762

On Mon, Sep 7, 2015 at 12:09 AM, Niranda Perera  wrote:

> Hi all,
>
> I'm testing DAS 3.0.0 in the windows env (windows 8.1 & java 1.8.0) with
> MySQL as the carbon_db.
>
> I tried, executing the mysql setup dbscript and I get the following error
>
> 23:41:09 CREATE INDEX REG_PATH_IND_BY_PATH_VALUE USING HASH ON
> REG_PATH(REG_PATH_VALUE, REG_TENANT_ID) Error Code: 1071. Specified key
> was too long; max key length is 767 bytes 0.078 sec
>
> this error has already been reported [1] and when I check the script also,
> it mentions this CARBON JIRA.
>
> however, this error does not occur in the linux (ubuntu) env.
>
> would like to know how to proceed with this?
>
> rgds
>
> [1] https://wso2.org/jira/browse/CARBON-5917
>
> --
> *Niranda Perera*
> Software Engineer, WSO2 Inc.
> Mobile: +94-71-554-8430
> Twitter: @n1r44 
> https://pythagoreanscript.wordpress.com/
>
> ___
> 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

[Dev] MySQL error while executing dbscripts in windows env

[Niranda Perera]

Hi all,

I'm testing DAS 3.0.0 in the windows env (windows 8.1 & java 1.8.0) with
MySQL as the carbon_db.

I tried, executing the mysql setup dbscript and I get the following error

23:41:09 CREATE INDEX REG_PATH_IND_BY_PATH_VALUE USING HASH ON
REG_PATH(REG_PATH_VALUE, REG_TENANT_ID) Error Code: 1071. Specified key was
too long; max key length is 767 bytes 0.078 sec

this error has already been reported [1] and when I check the script also,
it mentions this CARBON JIRA.

however, this error does not occur in the linux (ubuntu) env.

would like to know how to proceed with this?

rgds

[1] https://wso2.org/jira/browse/CARBON-5917

-- 
*Niranda Perera*
Software Engineer, WSO2 Inc.
Mobile: +94-71-554-8430
Twitter: @n1r44 
https://pythagoreanscript.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] python-pip & jinja2 should be installed by configurator puppet module

[Imesh Gunaratne]

On Sun, Sep 6, 2015 at 11:27 AM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi,
>
> IMO we can define 'python-dev', 'python-pip' libraries in stratos base
> since they are required by configurator which is a mandatory module.
>

Why do we use "python-dev" instead of "python"?

It would be better to include them in the Configurator and PCA modules
specifically. I do not see any reason to include them in the base module.

On Sun, Sep 6, 2015 at 11:27 AM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi,
>
> IMO we can define 'python-dev', 'python-pip' libraries in stratos base
> since they are required by configurator which is a mandatory module.
> Therefore,
> In configurator module we can inlcude jinja2;
> In PCA module we can include PCA related python dependencies 
> *(**paho,psutil,gittle,pexpect,yapsy
> etc.);*
>
> WDYT ?
>
>
> On Sun, Sep 6, 2015 at 11:02 AM, Gayan Gunarathne  wrote:
>
>> It is ok to redefined the python-pip module in configurator module since
>> currently it is used in PCA and configurator only.
>>
>> But this might be a issue with other python libraries as well if that
>> commonly used among the python modules.Also if there is several python
>> modules exists we need to redefined the libraries everywhere.IMO we may
>> need to include separate module for python and that module we can include
>> the common libraries for python.
>>
>> Thanks,
>> Gayan
>>
>> On Sun, Sep 6, 2015 at 9:25 AM, Akila Ravihansa Perera <
>> raviha...@wso2.com> wrote:
>>
>>> Hi Raj,
>>>
>>> Yes, I meant python-pip should not be removed from PCA module but should
>>> be installed for configurator as well.
>>>
>>> I think it should be redefined for configurator module since python-pip
>>> is not a compulsory package. We can use Java agent without it.
>>>
>>> Thanks.
>>>
>>> On Sun, Sep 6, 2015 at 6:17 AM, Rajkumar Rajaratnam 
>>> wrote:
>>>


 On Sun, Sep 6, 2015 at 7:45 AM, Akila Ravihansa Perera <
 raviha...@wso2.com> wrote:

> Hi Raj,
>
> I think we should not remove python-pip from PCA module since those
> dependencies should be installed for PCA to function.
>

 ​In the very similar way, python-pip should be installed for
 configurator to function as well :). So if I am using java agent instead of
 python agent, how would configurator work without python-pip? IMO, we can
 either move python-pip to stratos_base or use [1] to redfine python-pip
 package in configurator if it is not already defined anywhere else.

 [1]
 http://stackoverflow.com/questions/15266347/puppet-test-if-a-package-already-defined

 Thanks,
 Raj.

>
> @Anuruddha: I still see that jinja2 is packed from PCA module [1].
> Shall we move this to configurator module?
>
> [1]
> https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/python_agent/manifests/initialize.pp#L57
>
> Thanks.
>
> On Sat, Sep 5, 2015 at 3:21 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi Raj,
>>
>> Thanks for pointing this out. I have now added the jinja2 dependency
>> to configurator module and removed from PCA. [1]
>>
>> [1]
>> https://github.com/wso2/product-private-paas/blob/master/cartridges/vm/puppet/modules/configurator/manifests/init.pp#L32
>>
>> On Sat, Sep 5, 2015 at 3:14 PM, Rajkumar Rajaratnam <
>> rajkum...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> I think python-pip & jinja2 should be installed by configurator
>>> puppet module, not by python agent.
>>>
>>> I am using vagrant, puppet and configurator to setup my development
>>> environment, but I am not using python agent. Since $subject is not 
>>> done, I
>>> had to modify configurator puppet module.
>>>
>>> It would be better if we do the $subject.
>>>
>>> Thanks,
>>> Raj.
>>>
>>> --
>>> Rajkumar Rajaratnam
>>> Committer & PMC Member, Apache Stratos
>>> Software Engineer, WSO2
>>>
>>> Mobile : +94777568639
>>> Blog : rajkumarr.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Thanks and Regards,*
>> Anuruddha Lanka Liyanarachchi
>> Software Engineer - WSO2
>> Mobile : +94 (0) 712762611
>> Tel  : +94 112 145 345
>> a nurudd...@wso2.com
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



 --
 Rajkumar Rajaratnam
 Committer & PMC Member, Apache Stratos
 Software Engineer, WSO2

 Mobile : +9

Re: [Dev] [DAS] Error in creating system tables: Specified key was too long

[Niranda Perera]

Hi Pubudu,

I got the same error in the windows env. I'm working on it. will update you
soon

cheers

On Sun, Sep 6, 2015 at 9:31 PM, Pubudu Gunatilaka  wrote:

> Hi Niranda,
>
> Actually I am running on docker. Both DAS and mysql are docker containers
> which run on Debian.
>
> Thank you!
>
> On Sun, Sep 6, 2015 at 7:04 PM, Niranda Perera  wrote:
>
>> Hi Pubudu,
>>
>> are you using the windows env?
>>
>> On Sun, Sep 6, 2015 at 3:52 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi,
>>>
>>> I am using one of the nightly built DAS packs from last week. I have
>>> used a mysql database for analytic file system and at the server start up I
>>> am getting following error message.
>>>
>>> TID: [-1234] [] [2015-09-06 09:01:51,489] ERROR
>>> {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent} -
>>>  Error in activating analytics data service: Error in creating analytics
>>> data service from configuration: Error in creating system tables: Specified
>>> key was too long; max key length is 767 bytes
>>> {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent}
>>> org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsException:
>>> Error in creating analytics data service from configuration: Error in
>>> creating system tables: Specified key was too long; max key length is 767
>>> bytes
>>> at
>>> org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceImpl.(AnalyticsDataServiceImpl.java:137)
>>> at
>>> org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent.activate(AnalyticsDataServiceComponent.java:62)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>> at
>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>> at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
>>> at
>>> org.wso2.carbon.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:106)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>> at
>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>> at
>>> org.eclipse.osgi.framework.internal.core.Bund

Re: [Dev] [DAS] Error in creating system tables: Specified key was too long

[Pubudu Gunatilaka]

Hi Niranda,

Actually I am running on docker. Both DAS and mysql are docker containers
which run on Debian.

Thank you!

On Sun, Sep 6, 2015 at 7:04 PM, Niranda Perera  wrote:

> Hi Pubudu,
>
> are you using the windows env?
>
> On Sun, Sep 6, 2015 at 3:52 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi,
>>
>> I am using one of the nightly built DAS packs from last week. I have used
>> a mysql database for analytic file system and at the server start up I am
>> getting following error message.
>>
>> TID: [-1234] [] [2015-09-06 09:01:51,489] ERROR
>> {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent} -
>>  Error in activating analytics data service: Error in creating analytics
>> data service from configuration: Error in creating system tables: Specified
>> key was too long; max key length is 767 bytes
>> {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent}
>> org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsException:
>> Error in creating analytics data service from configuration: Error in
>> creating system tables: Specified key was too long; max key length is 767
>> bytes
>> at
>> org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceImpl.(AnalyticsDataServiceImpl.java:137)
>> at
>> org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent.activate(AnalyticsDataServiceComponent.java:62)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>> at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
>> at
>> org.wso2.carbon.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:106)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>> at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> at
>> org.ec

Re: [Dev] [DAS] Error in creating system tables: Specified key was too long

[Niranda Perera]

Hi Pubudu,

are you using the windows env?

On Sun, Sep 6, 2015 at 3:52 PM, Pubudu Gunatilaka  wrote:

> Hi,
>
> I am using one of the nightly built DAS packs from last week. I have used
> a mysql database for analytic file system and at the server start up I am
> getting following error message.
>
> TID: [-1234] [] [2015-09-06 09:01:51,489] ERROR
> {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent} -
>  Error in activating analytics data service: Error in creating analytics
> data service from configuration: Error in creating system tables: Specified
> key was too long; max key length is 767 bytes
> {org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent}
> org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsException:
> Error in creating analytics data service from configuration: Error in
> creating system tables: Specified key was too long; max key length is 767
> bytes
> at
> org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceImpl.(AnalyticsDataServiceImpl.java:137)
> at
> org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent.activate(AnalyticsDataServiceComponent.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
> at
> org.wso2.carbon.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:106)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceReg

[Dev] [DAS] Error in creating system tables: Specified key was too long

[Pubudu Gunatilaka]

Hi,

I am using one of the nightly built DAS packs from last week. I have used a
mysql database for analytic file system and at the server start up I am
getting following error message.

TID: [-1234] [] [2015-09-06 09:01:51,489] ERROR
{org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent} -
 Error in activating analytics data service: Error in creating analytics
data service from configuration: Error in creating system tables: Specified
key was too long; max key length is 767 bytes
{org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent}
org.wso2.carbon.analytics.datasource.commons.exception.AnalyticsException:
Error in creating analytics data service from configuration: Error in
creating system tables: Specified key was too long; max key length is 767
bytes
at
org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceImpl.(AnalyticsDataServiceImpl.java:137)
at
org.wso2.carbon.analytics.dataservice.AnalyticsDataServiceComponent.activate(AnalyticsDataServiceComponent.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
at
org.wso2.carbon.ntask.core.internal.TasksDSComponent.activate(TasksDSComponent.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at
org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at
org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at
org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
at
org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
at
org.eclipse.osgi.fra

Re: [Dev] [Greg 5.0.0 Beta] Can't change the notification settings under options section of store

[Chandana Napagoda]

HI Shafreen,

We couldn't reproduce this issue with mentioned steps. Shall we have a
offline discussion to review this?

Regards,
Chandana

On Sat, Sep 5, 2015 at 1:25 AM, Shafreen Anfar  wrote:

> Hi Chandana,
>
> Any update on this ?
>
>
> On Tue, Aug 25, 2015 at 9:45 AM, Shafreen Anfar  wrote:
>
>> Hi All,
>>
>> I just created a Rest service. Then went to the store and tried to change
>> the notification settings. Even though I click on the icon (apple like
>> button), it does't do anything. In the console I could see the below error.
>>
>> [2015-08-25 10:36:41,826] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,110] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,114] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,600] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,602] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,603] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,608] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,897] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,902] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,903] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,910] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,912] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,916] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,921] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:43,921] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>> [2015-08-25 10:36:51,895] ERROR {rxt.core} -  Unable to locate
>> assetResources for tenant: -1234 and type: undefined
>>
>>
>> --
>> Regards,
>> *Shafreen*
>> Software Engineer
>> WSO2 Inc
>> Mobile : 077-556-395-1
>>
>
>
>
> --
> Regards,
> *Shafreen*
> Software Engineer
> WSO2 Inc
> Mobile : 077-556-395-1
>



-- 
*Chandana Napagoda*
Senior Software Engineer
WSO2 Inc. - http://wso2.org

*Email  :  chand...@wso2.com **Mobile : +94718169299*

*Blog  :http://cnapagoda.blogspot.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev