Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.
Hi Chathurika, Issues mentioned in the previous mail are fixed in the latest 17/08/2014 pack[1]. There are some updates done to the migration tool readme.txt file as well. You can proceed with the migration testing. For the issue APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please read the comments in the jira (these instructions are added to the readme.txt). [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ Thanks, Chamila. On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As per the pack released on 05/08/2014 following is the status 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue status - inprogress. This is the main scenario of the migration. Thus the fix for this is crucial to proceed with the proper user scenario based testing 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue status - reopened. This issue corrupts the entire database. 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue status - reopened. The resources added before the migration is not copied correctly 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue status - reopened (due to APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be verified until APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed. Since the above mentioned issues are blocking, the migration testing cannot be proceeded for the 05/08/2014 pack Thank You On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The ticket has been resolved, please continue with testing On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Seems the stack trace is different from what was originally reported for this ticket, can we have a closer look at this? Please ping me when you get back to your seat. Thanks On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com wrote: Hi We started to test the migration with the 05/08/2014 pack and APIMANAGER-2529 is reopened. This is currently blocking the testing Thank You On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage chali...@wso2.com wrote: Hi, We have covered entire cycle of testing with 29th pack.But untill we get the above mentioned issues fixed,we cannot proceed with migration testing in API Manager 1.7.1 further. Thank you On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As of today (01.08.2014) the migration test is being done with the API Manager pack (29/07/2014) The issue APIMANAGER-2559 is now fixed and thus closed after verifying in the above mentioned pack. Furthermore a smoke test was done in the windows environment for the migration as well as for basic API Manager scenarios. Thank You On Thu, Jul 31, 2014 at 6:09 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All I conducted a test on windows environment to verify APIMANAGER-2559 This is issue is fixed for super tenant but not for other tenants due to APIMANAGER-2529. Both of the above issues are reopened since it's blocking tenant related data migration. Thanks and best regards On Wed, Jul 30, 2014 at 6:06 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All I am going to conduct a testing round in Windows to verify APIMANAGER-2559. Will circle back to you once i am done. Thank You On Wed, Jul 30, 2014 at 6:03 PM, Chalitha Waldeniyage chali...@wso2.com wrote: Hi All We are currently carrying on the $subject and please find the update as of 30.07.2014 *QA Personal* : Chalitha Waldeniyage and Chathurika De Silva *Environment details*: Operating System : Linux Java Version/Java VM :jdk1.7.0 (Oracle) Packs : APIM 1.7.1 DBMS: mysql and oracle Browser : Firefox 29.0 and Chrome 35.0 Set up :Stand alone pack *Issues reported - Priority (Blocker)* APIMANAGER-2529 - This issue is blocking the actual migration process but a workaround has been given.The latest documentation should be updated accordingly APIMANAGER-2534 - This issue is related to missing information after the migration APIMANAGER-2535 - HTTP verbs are not correctly copied to the migrated APIs. APIMANAGER-2672 - When versions are created. HTTP verbs are not correctly copied for them APIMANAGER-2662 - Cannot invoke an API which is in state published after migration. *Problems encountered: specific to oracle* Oracle database script of API Manager 1.6.0 should be updated to work with workflows. This is blocking the migration testing related to workflows. In summary as of today, the migration test scenarios cannot be fully covered due to above reported issues. Thank you, -- *Chalitha Maheshwari* Software Engineer-QA, WSO2 Inc. *E-mail:* chali...@wso2.com *Mobile: *+94710 411 112 -- *Chathurika Erandi* Software Engineer, WSO2
Re: [Dev] Cassanda 2.0
Hi, I tried to discuss this few months back but haven't got any positive reply(no reply at all). Hope we can carry this discussion forward. AFAIK at the moment we support external Cassandra 2.0, but have to make this a platform-wide story. Regards, UdaraR On Mon, Aug 18, 2014 at 11:22 AM, Darshana Akalanka Pagoda Arachchi darsha...@wso2.com wrote: Hi all, Isn't it time to move to cassandra 2.0.x with cql 3.1.x. What's new in Cassandra | DataStax Cassandra 2.0 Documentation http://www.datastax.com/documentation/cassandra/2.0/cassandra/features/features_key_c.html http://cassandra.apache.org/doc/cql3/CQL.html#changes This will allow us to simplify some of the data models specially because of the 'SELECT DISTINCT' support on partition keys. WDYT? -- *Darshana Akalanka Pagoda Arachchi,* *Software Engineer* *078-4721791* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CEP][stratos] Stratos single jvm cep aggregate functions issue
Hi Asiri, From the queries listed, it seems that you are using partitioned queries. If so, the aggregate will be given for each partition. Can you attach the relevant trace logs when the above issue occurs? The trace logs might help understand more what is happening underneath. Also, I think stratos uses CEP 3.0.0 instead of CEP 3.1.0. Therefore can you check with a CEP 3.0.0 standalone pack as well? However, no major changes were done to Siddhi when moving from CEP 3.0.0 to CEP 3.1.0. So Siddhi should behave exactly the same in both versions. Thanks, Lasantha On 17 August 2014 11:54, Asiri Liyana Arachchi asiriw...@gmail.com wrote: Hi all, I'm using this [1] execution plan inside stratos single jvm installation. select cluster_id,network_partition_id,avg(active_instances_count) as instances_count, avg(in_flight_request_count) as count , *sum(served_request_count) as served_count* insert into average_in_flight_requests *sum* doesn't give expected output. I've checked the same query with a standalone cep 3.1.0 and it gave desired results. for an example : served_request_count =10 sent for four times to CEP within a minute then the out put(served_count) is 80 (most of the time) or 60 where it should be 40. I'm using stratos pack 4.0.0-rc4 (release ) Can't figure out why this is happening. Any ideas? Thanks in advance. Regards, Asiri [1] : from avg_rif_stat select cluster_id, network_partition_id,active_instances_count, in_flight_request_count,served_request_count, stratos:concat(cluster_id, '-' , network_partition_id) as avg_rif_cluster_network insert into avg_rif_concat; define partition avg_rif_cluster_partition by avg_rif_concat.avg_rif_cluster_network; from avg_rif_concat#window.timeBatch(1 min) select cluster_id,network_partition_id,avg(active_instances_count) as instances_count, avg(in_flight_request_count) as count , sum(served_request_count) as served_count insert into average_in_flight_requests partition by avg_rif_cluster_partition; from average_in_flight_requests select cluster_id, network_partition_id,instances_count, served_count, stratos:divider(served_count , instances_count) as requests_per_instance insert into served_requests_per_instance; from served_requests_per_instance#window.timeBatch(10 min) select cluster_id,network_partition_id, avg(requests_per_instance) as average_served_count insert into average_served_request_count; ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.
Hi Chamila As i understand regarding APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two workarounds. 1. As mentioned in the readme.txt., edit *each* api xml in the APIM_1.7.0/repository/deployment/server/synapse-config/default/api directory. Replace handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/ with handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler 2. Manually go to implement tab in the edit mode of *each* of the APIs and click manage If a customer wants to migrate hundreds of APIs, is it a feasible solution from the customer's perspective? Ideally when a customer migrates from an older version, they should be able to work with their data as they worked before the migration. Since invoking an API is the core functionality of API Manager, is it really feasible in asking the customer to follow above 1st or 2nd method? From the customer/user perspective above given solution cannot be accepted. In my opinion this should be handled by our side without asking the customer/user to take extra effort in bringing his migrated data to work properly. Thank You Erandi On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, Issues mentioned in the previous mail are fixed in the latest 17/08/2014 pack[1]. There are some updates done to the migration tool readme.txt file as well. You can proceed with the migration testing. For the issue APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please read the comments in the jira (these instructions are added to the readme.txt). [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ Thanks, Chamila. On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As per the pack released on 05/08/2014 following is the status 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue status - inprogress. This is the main scenario of the migration. Thus the fix for this is crucial to proceed with the proper user scenario based testing 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue status - reopened. This issue corrupts the entire database. 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue status - reopened. The resources added before the migration is not copied correctly 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue status - reopened (due to APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be verified until APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed. Since the above mentioned issues are blocking, the migration testing cannot be proceeded for the 05/08/2014 pack Thank You On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The ticket has been resolved, please continue with testing On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Seems the stack trace is different from what was originally reported for this ticket, can we have a closer look at this? Please ping me when you get back to your seat. Thanks On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com wrote: Hi We started to test the migration with the 05/08/2014 pack and APIMANAGER-2529 is reopened. This is currently blocking the testing Thank You On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage chali...@wso2.com wrote: Hi, We have covered entire cycle of testing with 29th pack.But untill we get the above mentioned issues fixed,we cannot proceed with migration testing in API Manager 1.7.1 further. Thank you On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As of today (01.08.2014) the migration test is being done with the API Manager pack (29/07/2014) The issue APIMANAGER-2559 is now fixed and thus closed after verifying in the above mentioned pack. Furthermore a smoke test was done in the windows environment for the migration as well as for basic API Manager scenarios. Thank You On Thu, Jul 31, 2014 at 6:09 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All I conducted a test on windows environment to verify APIMANAGER-2559 This is issue is fixed for super tenant but not for other tenants due to APIMANAGER-2529. Both of the above issues are reopened since it's blocking tenant related data migration. Thanks and best regards On Wed, Jul 30, 2014 at 6:06 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All I am going to conduct a testing round in Windows to verify APIMANAGER-2559. Will circle back to you once i am done. Thank You On Wed, Jul 30, 2014 at 6:03 PM, Chalitha Waldeniyage chali...@wso2.com wrote: Hi
[Dev] WSO2 AppFactory 2.0.1 Milestone 4 Released!
WSO2 AppFactory 2.0.1 Milestone 4 Released! WSO2 AppFactory team is pleased to announce the release of version 2.0.1 M4 of the WSO2 App Factory. WSO2 App Factory is a multi-tenant, elastic and self-service enterprise platform that enables multiple project teams to collaboratively create, run and manage enterprise applications. Combining complete application lifecycle management and Platform-as-a-Service (PaaS) capabilities, WSO2 App Factory makes it possible to develop, test, deploy to production and retire applications with a single click. It also provides an easy way to discover and consume apps and APIs through a user-friendly storefront. The key feature for this release is BYOAT. The distribution is available to download at [1] . Bug fixes in this release can be found at [2]. Puppet manifests for App Factory can be found at [3]. We encourage you to report issues, documentation faults and feature requests regarding WSO2 AppFactory through the public WSO2 AppFactory JIRA https://wso2.org/jira/browse/APPFAC. [1] https://svn.wso2.org/repos/wso2/scratch/appfactorycc_tags/2.0.1-M4/packs/wso2appfactory-2.0.1.zip [2] *https://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+APPFAC+AND+fixVersion+%3D+%222.0.1-M4%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESCmode=hide https://wso2.org/jira/secure/IssueNavigator.jspa?reset=truejqlQuery=project+%3D+APPFAC+AND+fixVersion+%3D+%222.0.1-M4%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESCmode=hide* [3] https://svn.wso2.org/repos/wso2/scratch/appfactorycc_tags/2.0.1-M4/appfactory_2.0.0/products/appfactory/2.0.1/modules/puppet-manifests/ -- WSO2 AppFactory Team -- -- ~Regards *Manisha Eleperuma* Software Engineer WSO2, Inc.: http://wso2.com lean.enterprise.middleware *blog: http://manisha-eleperuma.blogspot.com/ http://manisha-eleperuma.blogspot.com/* *mobile: +94 71 8279777* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [CEP][stratos] Stratos single jvm cep aggregate functions issue
Hi Asiri, If you are using stratos 4.0.0-RC4, then the concat operation in CEP might be missing. CEP 3.1.0 supports the concat where CEP 3.0.0 doesn't support it. We have added a extension to support concat with CEP 3.0.0 in Private PaaS. You can find the sample extension in [1]. Can you add this extension to Stratos 4.0.0-rc4 and try the same? You will need to add the class to STRATOS_HOME/repository/conf/siddhi/siddi.extesion as [2]. [1] https://github.com/wso2/private-paas/blob/master/source/extensions/cep/stratos-cep-extension/src/main/java/org/apache/stratos/cep/extension/ConcatWindowProcessor.java [2] https://github.com/wso2/private-paas/blob/master/source/products/stratos/modules/distribution/src/main/conf/siddhi/siddhi.extension Thanks, Reka On Mon, Aug 18, 2014 at 12:10 PM, Lasantha Fernando lasan...@wso2.com wrote: Hi Asiri, From the queries listed, it seems that you are using partitioned queries. If so, the aggregate will be given for each partition. Can you attach the relevant trace logs when the above issue occurs? The trace logs might help understand more what is happening underneath. Also, I think stratos uses CEP 3.0.0 instead of CEP 3.1.0. Therefore can you check with a CEP 3.0.0 standalone pack as well? However, no major changes were done to Siddhi when moving from CEP 3.0.0 to CEP 3.1.0. So Siddhi should behave exactly the same in both versions. Thanks, Lasantha On 17 August 2014 11:54, Asiri Liyana Arachchi asiriw...@gmail.com wrote: Hi all, I'm using this [1] execution plan inside stratos single jvm installation. select cluster_id,network_partition_id,avg(active_instances_count) as instances_count, avg(in_flight_request_count) as count , *sum(served_request_count) as served_count* insert into average_in_flight_requests *sum* doesn't give expected output. I've checked the same query with a standalone cep 3.1.0 and it gave desired results. for an example : served_request_count =10 sent for four times to CEP within a minute then the out put(served_count) is 80 (most of the time) or 60 where it should be 40. I'm using stratos pack 4.0.0-rc4 (release ) Can't figure out why this is happening. Any ideas? Thanks in advance. Regards, Asiri [1] : from avg_rif_stat select cluster_id, network_partition_id,active_instances_count, in_flight_request_count,served_request_count, stratos:concat(cluster_id, '-' , network_partition_id) as avg_rif_cluster_network insert into avg_rif_concat; define partition avg_rif_cluster_partition by avg_rif_concat.avg_rif_cluster_network; from avg_rif_concat#window.timeBatch(1 min) select cluster_id,network_partition_id,avg(active_instances_count) as instances_count, avg(in_flight_request_count) as count , sum(served_request_count) as served_count insert into average_in_flight_requests partition by avg_rif_cluster_partition; from average_in_flight_requests select cluster_id, network_partition_id,instances_count, served_count, stratos:divider(served_count , instances_count) as requests_per_instance insert into served_requests_per_instance; from served_requests_per_instance#window.timeBatch(10 min) select cluster_id,network_partition_id, avg(requests_per_instance) as average_served_count insert into average_served_request_count; ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Lasantha Fernando* Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: lasan...@wso2.com mobile: (+94) 71 5247551 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Reka Thirunavukkarasu Senior Software Engineer, WSO2, Inc.:http://wso2.com, Mobile: +94776442007 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.
We should be able to write a simple script or java client to do this right? Thanks, NuwanD. On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila As i understand regarding APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two workarounds. 1. As mentioned in the readme.txt., edit *each* api xml in the APIM_1.7.0/repository/deployment/server/synapse-config/default/api directory. Replace handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/ with handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler 2. Manually go to implement tab in the edit mode of *each* of the APIs and click manage If a customer wants to migrate hundreds of APIs, is it a feasible solution from the customer's perspective? Ideally when a customer migrates from an older version, they should be able to work with their data as they worked before the migration. Since invoking an API is the core functionality of API Manager, is it really feasible in asking the customer to follow above 1st or 2nd method? From the customer/user perspective above given solution cannot be accepted. In my opinion this should be handled by our side without asking the customer/user to take extra effort in bringing his migrated data to work properly. Thank You Erandi On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, Issues mentioned in the previous mail are fixed in the latest 17/08/2014 pack[1]. There are some updates done to the migration tool readme.txt file as well. You can proceed with the migration testing. For the issue APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please read the comments in the jira (these instructions are added to the readme.txt). [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ Thanks, Chamila. On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As per the pack released on 05/08/2014 following is the status 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue status - inprogress. This is the main scenario of the migration. Thus the fix for this is crucial to proceed with the proper user scenario based testing 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue status - reopened. This issue corrupts the entire database. 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue status - reopened. The resources added before the migration is not copied correctly 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue status - reopened (due to APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be verified until APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed. Since the above mentioned issues are blocking, the migration testing cannot be proceeded for the 05/08/2014 pack Thank You On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The ticket has been resolved, please continue with testing On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Seems the stack trace is different from what was originally reported for this ticket, can we have a closer look at this? Please ping me when you get back to your seat. Thanks On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com wrote: Hi We started to test the migration with the 05/08/2014 pack and APIMANAGER-2529 is reopened. This is currently blocking the testing Thank You On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage chali...@wso2.com wrote: Hi, We have covered entire cycle of testing with 29th pack.But untill we get the above mentioned issues fixed,we cannot proceed with migration testing in API Manager 1.7.1 further. Thank you On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As of today (01.08.2014) the migration test is being done with the API Manager pack (29/07/2014) The issue APIMANAGER-2559 is now fixed and thus closed after verifying in the above mentioned pack. Furthermore a smoke test was done in the windows environment for the migration as well as for basic API Manager scenarios. Thank You On Thu, Jul 31, 2014 at 6:09 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All I conducted a test on windows environment to verify APIMANAGER-2559 This is issue is fixed for super tenant but not for other tenants due to APIMANAGER-2529. Both of the above issues are reopened since it's blocking tenant related data migration. Thanks and best regards On Wed, Jul 30, 2014 at 6:06 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All I am
Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.
I'll create a small java client to modify the apis in the synapse-config/default/api folder. Thanks, Chamila. On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote: We should be able to write a simple script or java client to do this right? Thanks, NuwanD. On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila As i understand regarding APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two workarounds. 1. As mentioned in the readme.txt., edit *each* api xml in the APIM_1.7.0/repository/deployment/server/synapse-config/default/api directory. Replace handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/ with handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler 2. Manually go to implement tab in the edit mode of *each* of the APIs and click manage If a customer wants to migrate hundreds of APIs, is it a feasible solution from the customer's perspective? Ideally when a customer migrates from an older version, they should be able to work with their data as they worked before the migration. Since invoking an API is the core functionality of API Manager, is it really feasible in asking the customer to follow above 1st or 2nd method? From the customer/user perspective above given solution cannot be accepted. In my opinion this should be handled by our side without asking the customer/user to take extra effort in bringing his migrated data to work properly. Thank You Erandi On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, Issues mentioned in the previous mail are fixed in the latest 17/08/2014 pack[1]. There are some updates done to the migration tool readme.txt file as well. You can proceed with the migration testing. For the issue APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please read the comments in the jira (these instructions are added to the readme.txt). [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ Thanks, Chamila. On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As per the pack released on 05/08/2014 following is the status 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue status - inprogress. This is the main scenario of the migration. Thus the fix for this is crucial to proceed with the proper user scenario based testing 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue status - reopened. This issue corrupts the entire database. 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue status - reopened. The resources added before the migration is not copied correctly 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue status - reopened (due to APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be verified until APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed. Since the above mentioned issues are blocking, the migration testing cannot be proceeded for the 05/08/2014 pack Thank You On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The ticket has been resolved, please continue with testing On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Seems the stack trace is different from what was originally reported for this ticket, can we have a closer look at this? Please ping me when you get back to your seat. Thanks On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com wrote: Hi We started to test the migration with the 05/08/2014 pack and APIMANAGER-2529 is reopened. This is currently blocking the testing Thank You On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage chali...@wso2.com wrote: Hi, We have covered entire cycle of testing with 29th pack.But untill we get the above mentioned issues fixed,we cannot proceed with migration testing in API Manager 1.7.1 further. Thank you On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As of today (01.08.2014) the migration test is being done with the API Manager pack (29/07/2014) The issue APIMANAGER-2559 is now fixed and thus closed after verifying in the above mentioned pack. Furthermore a smoke test was done in the windows environment for the migration as well as for basic API Manager scenarios. Thank You On Thu, Jul 31, 2014 at 6:09 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All I conducted a test on windows environment to verify APIMANAGER-2559 This is issue is fixed for super tenant but not for other tenants due to APIMANAGER-2529. Both of the above issues are
Re: [Dev] Patch for kernel 4.2.0
Hi Ajith, Merged the pull reqeuest , https://github.com/wso2-dev/carbon4-kernel/pull/74 Thanks, Shameera. On Fri, Aug 15, 2014 at 11:53 AM, Ajith Vitharana aji...@wso2.com wrote: On Wed, Aug 13, 2014 at 7:44 AM, Shameera Rathnayaka shame...@wso2.com wrote: Hi Ajith, Applied patch to kernel patch0009 , BTW i moved above JIRA to WSO2 CARBON[1] as it solve carbon kernel component. Please send a pull request to carbon kernel 4.3.0 git repo. Please merge [1]. [1]https://github.com/wso2-dev/carbon4-kernel/pull/66 Thanks Ajith [1] https://wso2.org/jira/browse/CARBON-14912 Thanks, Shameera. On Tue, Aug 12, 2014 at 9:35 PM, Ajith Vitharana aji...@wso2.com wrote: [Adding dev group.] On Tue, Aug 12, 2014 at 9:32 PM, Ajith Vitharana aji...@wso2.com wrote: Hi Shameera, Please commit the patch [1] to registry.core. [1]https://wso2.org/jira/browse/REGISTRY-2262 Thanks Ajith. -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.org shame...@apache.org* *phone: +9471 922 1454 %2B9471%20922%201454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94772217350 -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.org shame...@apache.org* *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Staus update: API manager 1.7.1 Migration testing 1.6.0 to 1.7.0.
Hi Chamila I have reopened the issue APIMANAGER-2662 because this issue should be fixed and shipped in a newer revision or as a patch itself. Thank You On Mon, Aug 18, 2014 at 1:27 PM, Chamila Adhikarinayake chami...@wso2.com wrote: I'll create a small java client to modify the apis in the synapse-config/default/api folder. Thanks, Chamila. On Mon, Aug 18, 2014 at 12:31 PM, Nuwan Dias nuw...@wso2.com wrote: We should be able to write a simple script or java client to do this right? Thanks, NuwanD. On Mon, Aug 18, 2014 at 12:15 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi Chamila As i understand regarding APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 following are the two workarounds. 1. As mentioned in the readme.txt., edit *each* api xml in the APIM_1.7.0/repository/deployment/server/synapse-config/default/api directory. Replace handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler/ with handler class=org.wso2.carbon.apimgt.usage.publisher.APIMgtGoogleAnalyticsTrackingHandler property name=configKey value=gov:/apimgt/statistics/ga-config.xml/ /handler 2. Manually go to implement tab in the edit mode of *each* of the APIs and click manage If a customer wants to migrate hundreds of APIs, is it a feasible solution from the customer's perspective? Ideally when a customer migrates from an older version, they should be able to work with their data as they worked before the migration. Since invoking an API is the core functionality of API Manager, is it really feasible in asking the customer to follow above 1st or 2nd method? From the customer/user perspective above given solution cannot be accepted. In my opinion this should be handled by our side without asking the customer/user to take extra effort in bringing his migrated data to work properly. Thank You Erandi On Mon, Aug 18, 2014 at 11:40 AM, Chamila Adhikarinayake chami...@wso2.com wrote: Hi Chathurika, Issues mentioned in the previous mail are fixed in the latest 17/08/2014 pack[1]. There are some updates done to the migration tool readme.txt file as well. You can proceed with the migration testing. For the issue APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 please read the comments in the jira (these instructions are added to the readme.txt). [1] https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ Thanks, Chamila. On Wed, Aug 13, 2014 at 5:05 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As per the pack released on 05/08/2014 following is the status 1. APIMANAGER-2662 https://wso2.org/jira/browse/APIMANAGER-2662 - issue status - inprogress. This is the main scenario of the migration. Thus the fix for this is crucial to proceed with the proper user scenario based testing 2. APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 - issue status - reopened. This issue corrupts the entire database. 3. APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669 - issue status - reopened. The resources added before the migration is not copied correctly 3. APIMANAGER-2672 https://wso2.org/jira/browse/APIMANAGER-2672 - issue status - reopened (due to APIMANAGER-2669 https://wso2.org/jira/browse/APIMANAGER-2669) . This issue cannot be verified until APIMANAGER-2698 https://wso2.org/jira/browse/APIMANAGER-2698 is fixed. Since the above mentioned issues are blocking, the migration testing cannot be proceeded for the 05/08/2014 pack Thank You On Mon, Aug 11, 2014 at 2:26 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The ticket has been resolved, please continue with testing On 11 August 2014 12:49, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Seems the stack trace is different from what was originally reported for this ticket, can we have a closer look at this? Please ping me when you get back to your seat. Thanks On 11 August 2014 12:30, Chathurika De Silva chathuri...@wso2.com wrote: Hi We started to test the migration with the 05/08/2014 pack and APIMANAGER-2529 is reopened. This is currently blocking the testing Thank You On Tue, Aug 5, 2014 at 10:26 AM, Chalitha Waldeniyage chali...@wso2.com wrote: Hi, We have covered entire cycle of testing with 29th pack.But untill we get the above mentioned issues fixed,we cannot proceed with migration testing in API Manager 1.7.1 further. Thank you On Fri, Aug 1, 2014 at 6:10 PM, Chathurika De Silva chathuri...@wso2.com wrote: Hi All As of today (01.08.2014) the migration test is being done with the API Manager pack (29/07/2014) The issue APIMANAGER-2559 is now fixed and thus closed after verifying in the above mentioned pack. Furthermore a smoke test was done in the windows environment for the migration as well as for basic API Manager scenarios. Thank You On Thu, Jul 31, 2014 at 6:09 PM, Chathurika
[Dev] [CARBON] Uses of ant localize task in the $CARBON_HOME/bin/build.xml
Hi all, I am working on [1] to use the proposed patch on carbon4-kernel to fix Ant localize task error when multiple resources files are present. I am trying to understand what is the purpose of this task. According to the readme, localize task generates language bundles in the $CARBON_HOME/repository/components/dropins to be picked at a locale change. Can someone explain in what kind of scenarios we are using this target? Any help is much appreciated. [1] https://wso2.org/jira/browse/CARBON-14564 Thanks. /Gayashan -- *Gayashan Amarasinghe* Software Engineer | Platform TG WSO2, Inc. | http://wso2.com lean. enterprise. middleware Mobile : +94718314517 Blog : gayashan-a.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DSS]The process of DSS will be killed after running for a period of time
Hi Harsha: Yes，my environment is linux 5.5 running in a XEN virtual machine. When that problem happened, other people was doing some heavy test on the same virtual machine, it resume too much memory. I think in this situation, it is normal that the process of BRS being killed, and I still want to know whether there are logs to save the situation, allowing developers to know about that. stevegyc From: Harsha Kumara Date: 2014-08-08 17:17 To: stevegyc CC: dev Subject: Re: Re: [Dev] [DSS]The process of DSS will be killed after running for a period of time Hi stevegyc, Sure let us know about that status. Server may run out of memory depends on your application. So if it consume more memory, try increase the heap memory in the wso2server.sh. Thanks, Harsha On Fri, Aug 8, 2014 at 12:31 PM, stevegyc steve...@163.com wrote: Hi Harsha Thank you for your advise. Now I am trying DSS in another environment and find out whether it will be killed again. In the server logs, wso2server.sh: line 300: 8634 killed is displayed. I checked the source in wso2server.sh as following. when the state is START_EXIT_STATUS, it can not run to line 300(done) and to be killed, is it right? (line 262)START_EXIT_STATUS=121 status=$START_EXIT_STATUS #To monitor a Carbon server in remote JMX mode on linux host machines, set the below system property. # -Djava.rmi.server.hostname=your.IP.goes.here while [ $status = $START_EXIT_STATUS ] do $JAVACMD \ -Xbootclasspath/a:$CARBON_XBOOTCLASSPATH \ -Xms256m -Xmx1024m -XX:MaxPermSize=256m \ -XX:+HeapDumpOnOutOfMemoryError \ -XX:HeapDumpPath=$CARBON_HOME/repository/logs/heap-dump.hprof \ $JAVA_OPTS \ -Dcom.sun.management.jmxremote \ -classpath $CARBON_CLASSPATH \ -Djava.endorsed.dirs=$JAVA_ENDORSED_DIRS \ -Djava.io.tmpdir=$CARBON_HOME/tmp \ -Dcatalina.base=$CARBON_HOME/lib/tomcat \ -Dwso2.server.standalone=true \ -Dcarbon.registry.root=/ \ -Djava.command=$JAVACMD \ -Dcarbon.home=$CARBON_HOME \ -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager \ -Dcarbon.config.dir.path=$CARBON_HOME/repository/conf \ -Djava.util.logging.config.file=$CARBON_HOME/repository/conf/etc/logging-bridge.properties \ -Dcomponents.repo=$CARBON_HOME/repository/components/plugins \ -Dconf.location=$CARBON_HOME/repository/conf\ -Dcom.atomikos.icatch.file=$CARBON_HOME/lib/transactions.properties \ -Dcom.atomikos.icatch.hide_init_file_path=true \ -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true \ -Dcom.sun.jndi.ldap.connect.pool.authentication=simple \ -Dcom.sun.jndi.ldap.connect.pool.timeout=3000 \ -Dorg.terracotta.quartz.skipUpdateCheck=true \ -Djava.security.egd=file:/dev/./urandom \ -Dfile.encoding=UTF8 \ org.wso2.carbon.bootstrap.Bootstrap $* status=$? (line 300)done a period time means it is not a fixed time, sometimes it is several days and sometimes it is several hours. stevegyc Hi Stevegyc It's stranged. Process may be killed due to ran out of memory,disk space and etc. So it would be great if you can provide more details about it. May be you find more info from server logs. What you mean by sever state has changed in wso2server.sh and roughly how many days you mean by long period time ? Thanks, Harsha On Thu, Aug 7, 2014 at 3:15 PM, stevegyc steve...@163.com wrote: Hi: Recently I found after running for a period of time, The process of DSS will be killed. In the log, the following information is displayed: wso2server.sh: line 300: 8634 killed. I checked the file wso2server.sh, it seems like somehow the state has changed. Had anyone encountered this problem? stevegyc ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error after adding Touchpoint to p2.inf
Hi Waruna,
I have also encountered across the same issue yesterday. As I noticed
installing a feature with the above touchpoint via the feature-manager UI
works fine. The issue occurs only when you install it via p2-profile-gen. I
suspect that it might be because p2-profile-gen couldn't find the custom
touchpoint we wrote. So, we need to find a way to make it visible at
p2-profile-gen.
KasunG
On Mon, Aug 18, 2014 at 2:00 PM, Waruna Jayaweera waru...@wso2.com wrote:
Hi,
I just added following touchpoint to feature p2.inf file referring [1].
instructions.configure = \
org.wso2.carbon.p2.touchpoint.addXMLElement(file:${installFolder}/../../../repository/conf/tomcat/webapp-classloading-environments.xml,xpath:/Classloading/ExclusiveEnvironments,element:ExclusiveEnvironmentNameJ2EE/Name/ExclusiveEnvironment);
\
Then build failed with following error.
An error occurred while configuring the installed items
session context was:(profile=default,
phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
-- [R]org.wso2.carbon.bpel.server.feature.group 4.3.0.SNAPSHOT,
action=org.eclipse.equinox.internal.p2.engine.MissingAction).
*No action found for: org.wso2.carbon.p2.touchpoint.addXMLElement.*
I may be missing another configuration when using touchpoint to modify
file. What I am missing here?
[1]
https://docs.wso2.com/display/Carbon420/Adding+and+Removing+XML+Element+Touchpoint+Actions
--
Regards,
Waruna Lakshitha Jayaweera
Software Engineer
WSO2 Inc; http://wso2.com
phone: +94713255198
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*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] Build failure in chunk-13 ntask component
Hi Gokul, Merged the Hazelcast upgrade request to the kernel git repo, please re apply ntask. It isn't that easy to merge a fix like this as we need to think about all the downstream builds. However sorry for the delay and inconvenience this made. Thanks, Shameera. On Fri, Aug 15, 2014 at 4:43 PM, Gokul Balakrishnan go...@wso2.com wrote: The Hz pull request was 6 days old and should by rights have been merged, unless there was some compelling reason stopping it (if there was, it was never communicated). Since the change was already propagated to SVN (and was causing a build failure) I made the fix and sent the corresponding pull request to the carbon-utils. IMO the discrepancy between SVN and Git is what causes situations like this. @Kernel team please let us know once the pull request has been merged so that we can re-apply the fix for ntask. On 15 August 2014 16:27, Gayashan Amarasinghe gayas...@wso2.com wrote: Hi Gokul, On Fri, Aug 15, 2014 at 3:39 PM, Gokul Balakrishnan go...@wso2.com wrote: I've reverted the change to ntask in Git so that the build will pass for the time being, but it will have to be made again once the version upgrade is merged; so IMO this is not the correct way to deal this situation, as we should have merged the Hz version upgrade pull request instead. +1, Agree with you on this. We need to find a better process to handle scenarios like this. (I have came across the same scenario when fixing [1].) Anyway it shouldn't have been merged to utils since the HZ upgrade was not there in the first place. As KasunG has mentioned it might take some time to get this merged to kernel. [1] https://wso2.org/jira/browse/CARBON-14867 Any reason why we haven't done so? On 15 August 2014 15:30, Gayashan Amarasinghe gayas...@wso2.com wrote: Hi Gokul, Hazelcast upgrade [1] has not been merged to the wso2-dev/carbon4-kernel yet. I did check with the hazelcast upgrade on a local merge and carbon-utils (with your changes on ntask) get built without an issue. So might need to revert the changes done to carbon-utils until the relevant hz changes are merged to kernel. [1] https://github.com/wso2-dev/carbon4-kernel/pull/62 Thanks. /Gayashan On Fri, Aug 15, 2014 at 2:58 PM, Gokul Balakrishnan go...@wso2.com wrote: Hi Kasun, Has the Hazelcast upgrade in question not been done in the git repo, because the fix causes build failures in the ntask component under wso2-dev (as per mail Build Failure in Carbon-utils)? Can you please clarify? Thanks, On 14 August 2014 11:40, Gokul Balakrishnan go...@wso2.com wrote: Fixed in r206532. On 14 August 2014 09:36, Sinthuja Ragendran sinth...@wso2.com wrote: Hi, Still the issue exists. Please fix it ASAP, since we need to get the pack out for testing. Thanks, Sinthuja On Wed, Aug 13, 2014 at 10:48 AM, Shameera Rathnayaka shame...@wso2.com wrote: Hi Kasun, Please fix this, This is downstream build error with hazelcast upgrade. Cheers, Shameera. On Wed, Aug 13, 2014 at 9:53 AM, Dinusha Senanayaka dinu...@wso2.com wrote: Hi, Getting following build failure. Should be relate with patch0009 updates ? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile (default-compile) on project org.wso2.carbon.ntask.core: Compilation failure [ERROR] /opt/checkout_chunk13/platform/branches/turing/components/ntask/org.wso2.carbon.ntask.core/4.2.4/src/main/java/org/wso2/carbon/ntask/core/impl/clustered/ClusterGroupCommunicator.java:[45,7] org.wso2.carbon.ntask.core.impl.clustered.ClusterGroupCommunicator is not abstract and does not override abstract method memberAttributeChanged(com.hazelcast.core.MemberAttributeEvent) in com.hazelcast.core.MembershipListener Regards, Dinusha. -- Dinusha Dilrukshi Senior Software Engineer WSO2 Inc.: http://wso2.com/ Mobile: +94725255071 Blog: http://dinushasblog.blogspot.com/ -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com shame...@wso2.com , shameera AT apache.org shame...@apache.org* *phone: +9471 922 1454 %2B9471%20922%201454* *Linked in : * http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Sinthuja Rajendran* Senior Software Engineer http://wso2.com/ WSO2, Inc.:http://wso2.com Blog: http://sinthu-rajan.blogspot.com/ Mobile: +94774273955 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Balakrishnan Gokulakrishnan* Software Engineer, WSO2, Inc. http://wso2.com Mob: +94 77 593 5789 | +1 650 272 9927 -- *Balakrishnan Gokulakrishnan* Software Engineer, WSO2, Inc. http://wso2.com Mob: +94 77 593 5789 | +1 650 272 9927
[Dev] Fwd: Service Pack for Carbon Kernel 4.2.0
Moving this discussion to dev@ Hi Sameera, Are we going to implement this approach immediately? We observed that recent EAM (Enterprise App Manager) pack is bit bulky. The compressed distribution is 401 MB and it becomes 746M when extracted and started . After removing the kernel patches the size becomes 426M. Regards, Pavithra -- Forwarded message -- From: Sameera Jayasoma same...@wso2.com Date: Fri, Jul 25, 2014 at 10:48 AM Subject: Service Pack for Carbon Kernel 4.2.0 Hi Folks, We are in the process of creating a service pack out of all the nine Carbon kernel patches. From now onwards, products which will be released from 4.2.0 branch do not need to pack all the nine patches. They can simply pack the servicepack001. This will reduce the size of product distributions as well. Please holler if there are any problems on this approach to the support patching process. Thanks, Sameera. -- Sameera Jayasoma, Software Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware -- *Pavithra Madurangi* Associate Technical Lead - QA. WSO2 Inc.: http://wso2.com/ Mobile: +94777207357 / +94773814110 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: Service Pack for Carbon Kernel 4.2.0
The same can be seen with API-M packs as well. The fresh pack is 341M. The 3rd July packs were just 301M. We noticed that this is due to the kernal patches and we believe that it's a good idea to consider about the Kernal SP. Regards, Evanthika On Mon, Aug 18, 2014 at 3:59 PM, Pavithra Madurangi pavit...@wso2.com wrote: Moving this discussion to dev@ Hi Sameera, Are we going to implement this approach immediately? We observed that recent EAM (Enterprise App Manager) pack is bit bulky. The compressed distribution is 401 MB and it becomes 746M when extracted and started . After removing the kernel patches the size becomes 426M. Regards, Pavithra -- Forwarded message -- From: Sameera Jayasoma same...@wso2.com Date: Fri, Jul 25, 2014 at 10:48 AM Subject: Service Pack for Carbon Kernel 4.2.0 Hi Folks, We are in the process of creating a service pack out of all the nine Carbon kernel patches. From now onwards, products which will be released from 4.2.0 branch do not need to pack all the nine patches. They can simply pack the servicepack001. This will reduce the size of product distributions as well. Please holler if there are any problems on this approach to the support patching process. Thanks, Sameera. -- Sameera Jayasoma, Software Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware -- *Pavithra Madurangi* Associate Technical Lead - QA. WSO2 Inc.: http://wso2.com/ Mobile: +94777207357 / +94773814110 ___ 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
Re: [Dev] Fwd: Service Pack for Carbon Kernel 4.2.0
On Mon, Aug 18, 2014 at 4:05 PM, Evanthika Amarasiri evanth...@wso2.com wrote: The same can be seen with API-M packs as well. The fresh pack is 341M. The 3rd July packs were just 301M. Correction. The fresh 1.7.1 distribution, built today [1] is 341M. What was given for QA on the 3rd July was only 301M. The size of the packs seems to be increasing every milestone due to kernal patches. [1] - https://svn.wso2.org/repos/wso2/scratch/chunk13-release/17-08-2014/ We noticed that this is due to the kernal patches and we believe that it's a good idea to consider about the Kernal SP. Regards, Evanthika On Mon, Aug 18, 2014 at 3:59 PM, Pavithra Madurangi pavit...@wso2.com wrote: Moving this discussion to dev@ Hi Sameera, Are we going to implement this approach immediately? We observed that recent EAM (Enterprise App Manager) pack is bit bulky. The compressed distribution is 401 MB and it becomes 746M when extracted and started . After removing the kernel patches the size becomes 426M. Regards, Pavithra -- Forwarded message -- From: Sameera Jayasoma same...@wso2.com Date: Fri, Jul 25, 2014 at 10:48 AM Subject: Service Pack for Carbon Kernel 4.2.0 Hi Folks, We are in the process of creating a service pack out of all the nine Carbon kernel patches. From now onwards, products which will be released from 4.2.0 branch do not need to pack all the nine patches. They can simply pack the servicepack001. This will reduce the size of product distributions as well. Please holler if there are any problems on this approach to the support patching process. Thanks, Sameera. -- Sameera Jayasoma, Software Architect, WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://sameera.adahas.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware -- *Pavithra Madurangi* Associate Technical Lead - QA. WSO2 Inc.: http://wso2.com/ Mobile: +94777207357 / +94773814110 ___ 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
Re: [Dev] [GREG] Getting multiple notifications for resource update
Hi Senaka, On Mon, Aug 18, 2014 at 5:26 PM, Danesh Kuruppu dan...@wso2.com wrote: Hi Senaka, In the current system, event capturing is done through handlers. We couldn't come up with a solution through handlers. As we went through the code and the complexity of change should be done in order to achieve this with the RegistryEventHandler and the handler architecture is bit complected. Hence we thought of go for a different solution where we introduce a new subscription type in governance level and we allow subscribe in artifact listing page where other subscriptions will remain the same. As Danesh's figure we will do subscribing and unsubscribing using the list view. We understand that this will complicate the list view but if we add this in the resource level then the normal subscription story will break. There will be complications with the following areas. 1. How to show different event and notification types. We are planning to have a pop-up which has the similar view as our normal subscription 2. Managing existing subscriptions. As I mentioned in 1 since we use the similar view as our normal subscription it will come with the view and delete option for existing subscription. Also there is a problem of notifying in governance API since governance API can be use as a client library, need to find a solution. thanks Eranda Current suggested solution is, We are giving another subscribe button in artifact level(in List view) which is used for subscribe Artifact update and delete [Please find the attached screenshot]. other subscriptions(check/uncheck LC, remove LC, approve LC etc) are not going to change and are done in resource level. So user can subscribe to update and delete notifications in Artifact level and they will handle separately. Please give feedback on this. Thanks On Fri, Aug 15, 2014 at 8:50 PM, Shavantha Weerasinghe shavan...@wso2.com wrote: Hi Danesh For notifications cant we have an option where the user gets to select which group of resources user wants to update by ticking to enable and generate notifications for only that area. Will that be extra work for the user Regards On Aug 15, 2014 6:09 PM, Senaka Fernando sen...@wso2.com wrote: Hi Danesh, Yes, this is problem that we need to fix. I think we need to find a way to mask notifications for certain operations. Ideally the association processing is a part of the update and doesn't require separate notifications. But, this functionality of masking should not just be specific to this use-case, but generically usable for any similar scenario. Before having the call, can you do some research and propose a solution to this? Based on that, lets discuss. Thanks, Senaka. On Fri, Aug 15, 2014 at 1:11 PM, Danesh Kuruppu dan...@wso2.com wrote: Hi Senaka, With the current implementation, If user subscribe to a resource which have multiple associations attached to it, user will receive multiple update notifications for a single update. This is because resource update have multiple repository update and for every repository update system generates update notification. We need to find a way to send single update notification for this. Can we have a call on this please. Thanks Danesh Kuruppu Software Engineer WSO2 Inc, Mobile: +94 (77) 1690552 -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +44 782 741 1966 %2B44%20782%20741%201966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware ___ 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 -- Danesh Kuruppu Software Engineer WSO2 Inc, Mobile: +94 (77) 1690552 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GREG] Getting multiple notifications for resource update
Hi Danesh, Eranda, I think we are doing too much here. Before going ahead with this kind of different subscription model, we need to understand the requirement here. At least I'm not clear on that. Do you want it to be configurable as to whether people want to subscribe for association updates etc? or do you want to simply stop people getting multiple notifications? Also, we cannot literally get rid of the handler approach. Its either a handler or it has to be burnt into the kernel. I personally don't think the kernel needs this massive feature and if we take that approach we'll be tailoring the kernel to suit components. But, lets try to clarify the above before trying to do anything new. Thanks, Senaka. On Mon, Aug 18, 2014 at 1:28 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Senaka, On Mon, Aug 18, 2014 at 5:26 PM, Danesh Kuruppu dan...@wso2.com wrote: Hi Senaka, In the current system, event capturing is done through handlers. We couldn't come up with a solution through handlers. As we went through the code and the complexity of change should be done in order to achieve this with the RegistryEventHandler and the handler architecture is bit complected. Hence we thought of go for a different solution where we introduce a new subscription type in governance level and we allow subscribe in artifact listing page where other subscriptions will remain the same. As Danesh's figure we will do subscribing and unsubscribing using the list view. We understand that this will complicate the list view but if we add this in the resource level then the normal subscription story will break. There will be complications with the following areas. 1. How to show different event and notification types. We are planning to have a pop-up which has the similar view as our normal subscription 2. Managing existing subscriptions. As I mentioned in 1 since we use the similar view as our normal subscription it will come with the view and delete option for existing subscription. Also there is a problem of notifying in governance API since governance API can be use as a client library, need to find a solution. thanks Eranda Current suggested solution is, We are giving another subscribe button in artifact level(in List view) which is used for subscribe Artifact update and delete [Please find the attached screenshot]. other subscriptions(check/uncheck LC, remove LC, approve LC etc) are not going to change and are done in resource level. So user can subscribe to update and delete notifications in Artifact level and they will handle separately. Please give feedback on this. Thanks On Fri, Aug 15, 2014 at 8:50 PM, Shavantha Weerasinghe shavan...@wso2.com wrote: Hi Danesh For notifications cant we have an option where the user gets to select which group of resources user wants to update by ticking to enable and generate notifications for only that area. Will that be extra work for the user Regards On Aug 15, 2014 6:09 PM, Senaka Fernando sen...@wso2.com wrote: Hi Danesh, Yes, this is problem that we need to fix. I think we need to find a way to mask notifications for certain operations. Ideally the association processing is a part of the update and doesn't require separate notifications. But, this functionality of masking should not just be specific to this use-case, but generically usable for any similar scenario. Before having the call, can you do some research and propose a solution to this? Based on that, lets discuss. Thanks, Senaka. On Fri, Aug 15, 2014 at 1:11 PM, Danesh Kuruppu dan...@wso2.com wrote: Hi Senaka, With the current implementation, If user subscribe to a resource which have multiple associations attached to it, user will receive multiple update notifications for a single update. This is because resource update have multiple repository update and for every repository update system generates update notification. We need to find a way to send single update notification for this. Can we have a call on this please. Thanks Danesh Kuruppu Software Engineer WSO2 Inc, Mobile: +94 (77) 1690552 -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +44 782 741 1966 %2B44%20782%20741%201966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware ___ 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 -- Danesh Kuruppu Software Engineer WSO2 Inc, Mobile: +94 (77) 1690552
Re: [Dev] [GREG] Getting multiple notifications for resource update
Hi Senaka, Requirement here is that when we do a artifact update the subscriber getting massive number of mails saying resource updated where the number depends on the number of associations and properties/hidden properties. thanks Eranda On Mon, Aug 18, 2014 at 6:02 PM, Senaka Fernando sen...@wso2.com wrote: Hi Danesh, Eranda, I think we are doing too much here. Before going ahead with this kind of different subscription model, we need to understand the requirement here. At least I'm not clear on that. Do you want it to be configurable as to whether people want to subscribe for association updates etc? or do you want to simply stop people getting multiple notifications? Also, we cannot literally get rid of the handler approach. Its either a handler or it has to be burnt into the kernel. I personally don't think the kernel needs this massive feature and if we take that approach we'll be tailoring the kernel to suit components. But, lets try to clarify the above before trying to do anything new. Thanks, Senaka. On Mon, Aug 18, 2014 at 1:28 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Senaka, On Mon, Aug 18, 2014 at 5:26 PM, Danesh Kuruppu dan...@wso2.com wrote: Hi Senaka, In the current system, event capturing is done through handlers. We couldn't come up with a solution through handlers. As we went through the code and the complexity of change should be done in order to achieve this with the RegistryEventHandler and the handler architecture is bit complected. Hence we thought of go for a different solution where we introduce a new subscription type in governance level and we allow subscribe in artifact listing page where other subscriptions will remain the same. As Danesh's figure we will do subscribing and unsubscribing using the list view. We understand that this will complicate the list view but if we add this in the resource level then the normal subscription story will break. There will be complications with the following areas. 1. How to show different event and notification types. We are planning to have a pop-up which has the similar view as our normal subscription 2. Managing existing subscriptions. As I mentioned in 1 since we use the similar view as our normal subscription it will come with the view and delete option for existing subscription. Also there is a problem of notifying in governance API since governance API can be use as a client library, need to find a solution. thanks Eranda Current suggested solution is, We are giving another subscribe button in artifact level(in List view) which is used for subscribe Artifact update and delete [Please find the attached screenshot]. other subscriptions(check/uncheck LC, remove LC, approve LC etc) are not going to change and are done in resource level. So user can subscribe to update and delete notifications in Artifact level and they will handle separately. Please give feedback on this. Thanks On Fri, Aug 15, 2014 at 8:50 PM, Shavantha Weerasinghe shavan...@wso2.com wrote: Hi Danesh For notifications cant we have an option where the user gets to select which group of resources user wants to update by ticking to enable and generate notifications for only that area. Will that be extra work for the user Regards On Aug 15, 2014 6:09 PM, Senaka Fernando sen...@wso2.com wrote: Hi Danesh, Yes, this is problem that we need to fix. I think we need to find a way to mask notifications for certain operations. Ideally the association processing is a part of the update and doesn't require separate notifications. But, this functionality of masking should not just be specific to this use-case, but generically usable for any similar scenario. Before having the call, can you do some research and propose a solution to this? Based on that, lets discuss. Thanks, Senaka. On Fri, Aug 15, 2014 at 1:11 PM, Danesh Kuruppu dan...@wso2.com wrote: Hi Senaka, With the current implementation, If user subscribe to a resource which have multiple associations attached to it, user will receive multiple update notifications for a single update. This is because resource update have multiple repository update and for every repository update system generates update notification. We need to find a way to send single update notification for this. Can we have a call on this please. Thanks Danesh Kuruppu Software Engineer WSO2 Inc, Mobile: +94 (77) 1690552 -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +44 782 741 1966 %2B44%20782%20741%201966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware
Re: [Dev] WSO2 Committers += Dilini Muthumala
Congratz...!!! On Mon, Aug 18, 2014 at 11:00 AM, Dunith Dhanushka dun...@wso2.com wrote: Congrats Dilini! On Mon, Aug 18, 2014 at 10:58 AM, Gimantha Bandara giman...@wso2.com wrote: Congratz Dilini On Mon, Aug 18, 2014 at 10:44 AM, Sewwandi Perera sewwa...@wso2.com wrote: Congratulations Dilini...!!! :) On Mon, Aug 18, 2014 at 10:28 AM, Abimaran Kugathasan abima...@wso2.com wrote: Congrats Dilini! On Mon, Aug 18, 2014 at 9:16 AM, Manula Chathurika Thantriwatte manu...@wso2.com wrote: Congratulations !!! On Sun, Aug 17, 2014 at 9:46 AM, Supun Sethunga sup...@wso2.com wrote: Congratulations Dilini! On Sun, Aug 17, 2014 at 8:53 AM, Chalitha Waldeniyage chali...@wso2.com wrote: Congratulations.. Dilini.. :) On Sat, Aug 16, 2014 at 10:47 AM, Malintha Adikari malin...@wso2.com wrote: Congratulations Dilini! On Fri, Aug 15, 2014 at 10:52 PM, Chamil Jeewantha cha...@wso2.com wrote: Congratulations! On Fri, Aug 15, 2014 at 8:43 PM, Amal Gunatilake am...@wso2.com wrote: Congratz Dilini! Thank you Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware On Fri, Aug 15, 2014 at 11:46 AM, Waruna Jayaweera waru...@wso2.com wrote: Congratulations..! On Fri, Aug 15, 2014 at 11:28 AM, Milinda Perera milin...@wso2.com wrote: Congratulations dilini On Fri, Aug 15, 2014 at 11:17 AM, Gayashan Amarasinghe gayas...@wso2.com wrote: Congratulations Dilini! On Fri, Aug 15, 2014 at 11:03 AM, Seshika Fernando sesh...@wso2.com wrote: SUPERB! Congrats dilini! On Fri, Aug 15, 2014 at 10:45 AM, Kalpa Welivitigoda kal...@wso2.com wrote: Congratulations Dilini ! On Fri, Aug 15, 2014 at 10:38 AM, Dakshika Jayathilaka daksh...@wso2.com wrote: Congratulations.. ! *Dakshika Jayathilaka* Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Fri, Aug 15, 2014 at 5:07 AM, Melan Nimesh me...@apache.org wrote: Congratulations Dilini !!! On Fri, Aug 15, 2014 at 10:14 AM, Aruna Karunarathna ar...@wso2.com wrote: Congratzz Dilini..!!! On Fri, Aug 15, 2014 at 10:12 AM, Sohani Weerasinghe soh...@wso2.com wrote: Congratulations Sohani Weerasinghe Software Engineer WSO2, Inc: http://wso2.com Mobile : +94 716439774 Blog :http://christinetechtips.blogspot.com/ Twitter : https://twitter.com/sohanichristine On Fri, Aug 15, 2014 at 9:50 AM, Susinda Perera susi...@wso2.com wrote: Congratulations.. ! On Fri, Aug 15, 2014 at 9:47 AM, Sriskandarajah Suhothayan s...@wso2.com wrote: Hi All, It's my pleasure to announce Dilini Muthumala as a WSO2 Committer. Dilini has been a valuable contributor for WSO2 CEP product and in recognition of her contributions to WSO2, she has been voted as a WSO2Committer. Dilini, Congratulations and Keep up the good work! Thanks and Regards, Suho -- *S. Suhothayan* Technical Lead Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * http://wso2.com/* lean . enterprise . middleware *cell: (+94) 779 756 757 %28%2B94%29%20779%20756%20757 | blog: http://suhothayan.blogspot.com/ http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan http://lk.linkedin.com/in/suhothayan* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 ___ 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 -- * 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 ___ 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 mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Kalpa Welivitigoda Software Engineer, WSO2 Inc. http://wso2.com Email: kal...@wso2.com Mobile: +94776509215 ___ 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 -- *Gayashan Amarasinghe* Software Engineer | Platform
Re: [Dev] [GREG] Getting multiple notifications for resource update
Hi Eranda, Alright. So, just stop the duplication. Ideally, the handler should only be triggered once. And, AFAIU, this is doable with the association-update and recursive delete handlers (and other utility handlers of similar sort) can set some flag within themselves preventing the eventing handlers from firing events for those. Won't this work? Thanks, Senaka. On Mon, Aug 18, 2014 at 1:42 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Senaka, Requirement here is that when we do a artifact update the subscriber getting massive number of mails saying resource updated where the number depends on the number of associations and properties/hidden properties. thanks Eranda On Mon, Aug 18, 2014 at 6:02 PM, Senaka Fernando sen...@wso2.com wrote: Hi Danesh, Eranda, I think we are doing too much here. Before going ahead with this kind of different subscription model, we need to understand the requirement here. At least I'm not clear on that. Do you want it to be configurable as to whether people want to subscribe for association updates etc? or do you want to simply stop people getting multiple notifications? Also, we cannot literally get rid of the handler approach. Its either a handler or it has to be burnt into the kernel. I personally don't think the kernel needs this massive feature and if we take that approach we'll be tailoring the kernel to suit components. But, lets try to clarify the above before trying to do anything new. Thanks, Senaka. On Mon, Aug 18, 2014 at 1:28 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Senaka, On Mon, Aug 18, 2014 at 5:26 PM, Danesh Kuruppu dan...@wso2.com wrote: Hi Senaka, In the current system, event capturing is done through handlers. We couldn't come up with a solution through handlers. As we went through the code and the complexity of change should be done in order to achieve this with the RegistryEventHandler and the handler architecture is bit complected. Hence we thought of go for a different solution where we introduce a new subscription type in governance level and we allow subscribe in artifact listing page where other subscriptions will remain the same. As Danesh's figure we will do subscribing and unsubscribing using the list view. We understand that this will complicate the list view but if we add this in the resource level then the normal subscription story will break. There will be complications with the following areas. 1. How to show different event and notification types. We are planning to have a pop-up which has the similar view as our normal subscription 2. Managing existing subscriptions. As I mentioned in 1 since we use the similar view as our normal subscription it will come with the view and delete option for existing subscription. Also there is a problem of notifying in governance API since governance API can be use as a client library, need to find a solution. thanks Eranda Current suggested solution is, We are giving another subscribe button in artifact level(in List view) which is used for subscribe Artifact update and delete [Please find the attached screenshot]. other subscriptions(check/uncheck LC, remove LC, approve LC etc) are not going to change and are done in resource level. So user can subscribe to update and delete notifications in Artifact level and they will handle separately. Please give feedback on this. Thanks On Fri, Aug 15, 2014 at 8:50 PM, Shavantha Weerasinghe shavan...@wso2.com wrote: Hi Danesh For notifications cant we have an option where the user gets to select which group of resources user wants to update by ticking to enable and generate notifications for only that area. Will that be extra work for the user Regards On Aug 15, 2014 6:09 PM, Senaka Fernando sen...@wso2.com wrote: Hi Danesh, Yes, this is problem that we need to fix. I think we need to find a way to mask notifications for certain operations. Ideally the association processing is a part of the update and doesn't require separate notifications. But, this functionality of masking should not just be specific to this use-case, but generically usable for any similar scenario. Before having the call, can you do some research and propose a solution to this? Based on that, lets discuss. Thanks, Senaka. On Fri, Aug 15, 2014 at 1:11 PM, Danesh Kuruppu dan...@wso2.com wrote: Hi Senaka, With the current implementation, If user subscribe to a resource which have multiple associations attached to it, user will receive multiple update notifications for a single update. This is because resource update have multiple repository update and for every repository update system generates update notification. We need to find a way to send single update notification for this. Can we have a call on this please. Thanks Danesh Kuruppu Software Engineer WSO2 Inc, Mobile: +94 (77) 1690552 -- *[image:
[Dev] [APPFAC] Error while AF startup
Hi,
I am getting the following error while trying to start the Appfactroy with
the latest release (2.0.1-M4)
What would be the cause for this?.
ERROR {org.apache.cassandra.service.CassandraDaemon} - Exception
encountered during startup
java.lang.RuntimeException: No other nodes seen! Unable to bootstrap.If
you intended to start a single-node cluster, you should make sure your
broadcast_address (or listen_address) is listed as a seed. Otherwise, you
need to determine why the seed being contacted has no knowledge of the rest
of the cluster. Usually, this can be solved by giving all nodes the same
seed list.
at
org.apache.cassandra.dht.BootStrapper.getBootstrapSource(BootStrapper.java:154)
at
org.apache.cassandra.dht.BootStrapper.getBalancedToken(BootStrapper.java:135)
at
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:115)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:709)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:586)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:483)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:348)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:447)
at
org.wso2.carbon.cassandra.server.CassandraServerController$1.run(CassandraServerController.java:48)
at java.lang.Thread.run(Thread.java:745)
java.lang.RuntimeException: No other nodes seen! Unable to bootstrap.If
you intended to start a single-node cluster, you should make sure your
broadcast_address (or listen_address) is listed as a seed. Otherwise, you
need to determine why the seed being contacted has no knowledge of the rest
of the cluster. Usually, this can be solved by giving all nodes the same
seed list.
at
org.apache.cassandra.dht.BootStrapper.getBootstrapSource(BootStrapper.java:154)
at
org.apache.cassandra.dht.BootStrapper.getBalancedToken(BootStrapper.java:135)
at
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:115)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:709)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:586)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:483)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:348)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:447)
at
org.wso2.carbon.cassandra.server.CassandraServerController$1.run(CassandraServerController.java:48)
at java.lang.Thread.run(Thread.java:745)
Regards,
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APPFAC] Error while AF startup
Hi Anuruddha,
Did you do any changes to cassandra.yaml? Seems something wrong there.
Thanks,
Harsha
On Mon, Aug 18, 2014 at 6:32 PM, Anuruddha Premalal anurud...@wso2.com
wrote:
Hi,
I am getting the following error while trying to start the Appfactroy with
the latest release (2.0.1-M4)
What would be the cause for this?.
ERROR {org.apache.cassandra.service.CassandraDaemon} - Exception
encountered during startup
java.lang.RuntimeException: No other nodes seen! Unable to bootstrap.If
you intended to start a single-node cluster, you should make sure your
broadcast_address (or listen_address) is listed as a seed. Otherwise, you
need to determine why the seed being contacted has no knowledge of the rest
of the cluster. Usually, this can be solved by giving all nodes the same
seed list.
at
org.apache.cassandra.dht.BootStrapper.getBootstrapSource(BootStrapper.java:154)
at
org.apache.cassandra.dht.BootStrapper.getBalancedToken(BootStrapper.java:135)
at
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:115)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:709)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:586)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:483)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:348)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:447)
at
org.wso2.carbon.cassandra.server.CassandraServerController$1.run(CassandraServerController.java:48)
at java.lang.Thread.run(Thread.java:745)
java.lang.RuntimeException: No other nodes seen! Unable to bootstrap.If
you intended to start a single-node cluster, you should make sure your
broadcast_address (or listen_address) is listed as a seed. Otherwise, you
need to determine why the seed being contacted has no knowledge of the rest
of the cluster. Usually, this can be solved by giving all nodes the same
seed list.
at
org.apache.cassandra.dht.BootStrapper.getBootstrapSource(BootStrapper.java:154)
at
org.apache.cassandra.dht.BootStrapper.getBalancedToken(BootStrapper.java:135)
at
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:115)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:709)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:586)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:483)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:348)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:447)
at
org.wso2.carbon.cassandra.server.CassandraServerController$1.run(CassandraServerController.java:48)
at java.lang.Thread.run(Thread.java:745)
Regards,
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Installing org.wso2.carbon.apimgt.store feature failed
Please merge the pull [1] request which solves this failure. thanks Eranda [1]. https://github.com/wso2-dev/carbon-apimgt/pull/2 On Wed, Aug 13, 2014 at 10:38 AM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Nuwan, I am getting the following error when I tried to build G-Reg p2. What can be the reason for this? An error occurred while configuring the installed items session context was:(profile=default, phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null -- [R]org.wso2.carbon.apimgt.store.feature.group 4.3.0.SNAPSHOT, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction). I/O Error while copying /home/eranda/greg-repo/myrepos/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components/default/../features/org.wso2.carbon.apimgt.store_4.3.0.SNAPSHOT/admin-dashboard - see details. Caused by: java.io.IOException: Source: /home/eranda/greg-repo/myrepos/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components/default/../features/org.wso2.carbon.apimgt.store_4.3.0.SNAPSHOT/admin-dashboarddoes not exists thanks Eranda -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APPFAC] Error while AF startup
HI Anuruddha,
As Harsha said. Your repository/conf/etc/cassandra.yaml contains following
part. As the exception suggests try giving the same seed list. seems like
difference seeds in the cluster.
seed_provider:
# Addresses of hosts that are deemed contact points.
# Cassandra nodes use this list of hosts to find each other and learn
# the topology of the ring. You must change this if you are running
# multiple nodes!
- class_name: org.apache.cassandra.locator.SimpleSeedProvider
parameters:
# seeds is actually a comma-delimited list of addresses.
# Ex: ip1,ip2,ip3
- seeds: 10.0.30.31
Thanks,
--Rajith
On Mon, Aug 18, 2014 at 6:48 PM, Harsha Kumara hars...@wso2.com wrote:
Hi Anuruddha,
Did you do any changes to cassandra.yaml? Seems something wrong there.
Thanks,
Harsha
On Mon, Aug 18, 2014 at 6:32 PM, Anuruddha Premalal anurud...@wso2.com
wrote:
Hi,
I am getting the following error while trying to start the Appfactroy
with the latest release (2.0.1-M4)
What would be the cause for this?.
ERROR {org.apache.cassandra.service.CassandraDaemon} - Exception
encountered during startup
java.lang.RuntimeException: No other nodes seen! Unable to bootstrap.If
you intended to start a single-node cluster, you should make sure your
broadcast_address (or listen_address) is listed as a seed. Otherwise, you
need to determine why the seed being contacted has no knowledge of the rest
of the cluster. Usually, this can be solved by giving all nodes the same
seed list.
at
org.apache.cassandra.dht.BootStrapper.getBootstrapSource(BootStrapper.java:154)
at
org.apache.cassandra.dht.BootStrapper.getBalancedToken(BootStrapper.java:135)
at
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:115)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:709)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:586)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:483)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:348)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:447)
at
org.wso2.carbon.cassandra.server.CassandraServerController$1.run(CassandraServerController.java:48)
at java.lang.Thread.run(Thread.java:745)
java.lang.RuntimeException: No other nodes seen! Unable to bootstrap.If
you intended to start a single-node cluster, you should make sure your
broadcast_address (or listen_address) is listed as a seed. Otherwise, you
need to determine why the seed being contacted has no knowledge of the rest
of the cluster. Usually, this can be solved by giving all nodes the same
seed list.
at
org.apache.cassandra.dht.BootStrapper.getBootstrapSource(BootStrapper.java:154)
at
org.apache.cassandra.dht.BootStrapper.getBalancedToken(BootStrapper.java:135)
at
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:115)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:709)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:586)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:483)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:348)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:447)
at
org.wso2.carbon.cassandra.server.CassandraServerController$1.run(CassandraServerController.java:48)
at java.lang.Thread.run(Thread.java:745)
Regards,
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Rajith Siriwardana*
Software Engineer | Cloud Team
WSO2 Inc. ; http://wso2.com
*lean. enterprise. middleware*
--
*http://people.apache.org/~siriwardana
http://people.apache.org/~siriwardana*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GREG] Getting multiple notifications for resource update
Hi Senaka, Earlier we had an idea of having a flag and problem was how we could handle the flag inside multiple request. Suggestions we had earlier, Suggestion 01: Keep a flag in requestContext to track event firing. *This is impossible because inside one request, there are multiple requests and each request trigger eventing handler.* Suggestion 02: Keep a ThreadLocal flag to track event firing. *Problem with this is we couldn't clearing identify the boundaries of one user request. We need to put the flag down at the end of the request which we couldn't find easily. * Suggestion 03: Keep a flag in requestContext and whenever new request create inside the main request, transfer the flag status of the previous request to the new request. transferor is a threadlocal variable. Here each time we invoke registry call, we set the value of the threadlocal variable to the current flag status of the requestContext and inside registry call we set the flag value of the new requestContext to the value in threadLocal variable. *This is too complex solution. we need to find out all registry call and set the variable manually.* Suggestion 04 : Keep a threadLocal stack to track the request flow. Here each time we create request, we put it in the stack and at the end of the registry call we remove that request from the stack. typical request flow e.g.: Put | Add Request Stack Size 1 Put | Add Request Stack Size 2 Remove Association | Add Request Stack Size 3 Remove Association | Remove Request Stack Size 3 Remove Association | Add Request Stack Size 3 Put | Add Request Stack Size 4 Put | Remove Request Stack Size 4 Remove Association | Remove Request Stack Size 3 Put | Add Request Stack Size 3 Put | Remove Request Stack Size 3 Add Association | Add Request Stack Size 3 Add Association | Remove Request Stack Size 3 Put | Remove Request Stack Size 2 Put | Remove Request Stack Size 1 the Stack size reach the zero means we are at the end of the user request. we can trigger eventing handler to generate notification. *Currently this works for me, but don't know whether this is a feasible solution.* Thanks On Mon, Aug 18, 2014 at 6:25 PM, Senaka Fernando sen...@wso2.com wrote: Hi Eranda, Alright. So, just stop the duplication. Ideally, the handler should only be triggered once. And, AFAIU, this is doable with the association-update and recursive delete handlers (and other utility handlers of similar sort) can set some flag within themselves preventing the eventing handlers from firing events for those. Won't this work? Thanks, Senaka. On Mon, Aug 18, 2014 at 1:42 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Senaka, Requirement here is that when we do a artifact update the subscriber getting massive number of mails saying resource updated where the number depends on the number of associations and properties/hidden properties. thanks Eranda On Mon, Aug 18, 2014 at 6:02 PM, Senaka Fernando sen...@wso2.com wrote: Hi Danesh, Eranda, I think we are doing too much here. Before going ahead with this kind of different subscription model, we need to understand the requirement here. At least I'm not clear on that. Do you want it to be configurable as to whether people want to subscribe for association updates etc? or do you want to simply stop people getting multiple notifications? Also, we cannot literally get rid of the handler approach. Its either a handler or it has to be burnt into the kernel. I personally don't think the kernel needs this massive feature and if we take that approach we'll be tailoring the kernel to suit components. But, lets try to clarify the above before trying to do anything new. Thanks, Senaka. On Mon, Aug 18, 2014 at 1:28 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Senaka, On Mon, Aug 18, 2014 at 5:26 PM, Danesh Kuruppu dan...@wso2.com wrote: Hi Senaka, In the current system, event capturing is done through handlers. We couldn't come up with a solution through handlers. As we went through the code and the complexity of change should be done in order to achieve this with the RegistryEventHandler and the handler architecture is bit complected. Hence we thought of go for a different solution where we introduce a new subscription type in governance level and we allow subscribe in artifact listing page where other subscriptions will remain the same. As Danesh's figure we will do subscribing and unsubscribing using the list view. We understand that this will complicate the list view but if we add this in the resource level then the normal subscription story will break. There will be complications with the following areas. 1. How to show different event and notification types. We are planning to have a pop-up which has the similar view as our normal subscription 2. Managing existing subscriptions. As I mentioned in 1 since we use the similar view as our normal
Re: [Dev] Cassanda 2.0
Yes, we are planning to move to Cassandra 2.0, but there are some discussions going on whether we are going to go with datastax version of Cassandra. Also WSO2 Cassandra contains modifications done for implement multitenancy it may take some time upgrade it as 2.0 may contains significant changes. Will update the thread as it goes. On Mon, Aug 18, 2014 at 11:50 AM, Udara Rathnayake uda...@wso2.com wrote: Hi, I tried to discuss this few months back but haven't got any positive reply(no reply at all). Hope we can carry this discussion forward. AFAIK at the moment we support external Cassandra 2.0, but have to make this a platform-wide story. Regards, UdaraR On Mon, Aug 18, 2014 at 11:22 AM, Darshana Akalanka Pagoda Arachchi darsha...@wso2.com wrote: Hi all, Isn't it time to move to cassandra 2.0.x with cql 3.1.x. What's new in Cassandra | DataStax Cassandra 2.0 Documentation http://www.datastax.com/documentation/cassandra/2.0/cassandra/features/features_key_c.html http://cassandra.apache.org/doc/cql3/CQL.html#changes This will allow us to simplify some of the data models specially because of the 'SELECT DISTINCT' support on partition keys. WDYT? -- *Darshana Akalanka Pagoda Arachchi,* *Software Engineer* *078-4721791* ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Udara Rathnayake* Software Engineer WSO2 Inc. : http://wso2.com Mobile : +94 772207239 Twitter : http://twitter.com/udarakr Blog: http://udarakr.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Harsha Kumara Software Engineer, WSO2 Inc. Mobile: +94775505618 Blog:harshcreationz.blogspot.com ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [GREG] Getting multiple notifications for resource update
Hi Danesh, I also think #4 is proper. This is the way we track transaction commit/rollback status as well, so if you take a look @ the semantics of commit, this should be similar. So, ideally every supposedly unit operation, which happens to invoke other operations will increment the counter before invoking the subsequent operation and decrement the counter after it completes. This approach however, needs to be done @ every handler, component, kernel etc. Suggestion 05: Another trick though I'm not sure about the possibility is to track the transaction depth counter. This counter too will have information as to how far deep you are inside a transaction. Which is similar to the counter you are talking about. One catch is that the mount handler pushes this counter into a stack when it goes into a JDBC mount to make it possible to have transactions across DBs. To handle this AFAIU, you can also check whether the mount handler's stack is empty or not. But, I don't see it to be good idea to have this accessed outside of the kernel, so may be introduce a method inside the Transaction API of the kernel to explain whether you are within the terminal operation of a nested query or whether you are infact inside a nested operation. Thanks, Senaka. On Mon, Aug 18, 2014 at 8:05 PM, Danesh Kuruppu dan...@wso2.com wrote: Hi Senaka, Earlier we had an idea of having a flag and problem was how we could handle the flag inside multiple request. Suggestions we had earlier, Suggestion 01: Keep a flag in requestContext to track event firing. *This is impossible because inside one request, there are multiple requests and each request trigger eventing handler.* Suggestion 02: Keep a ThreadLocal flag to track event firing. *Problem with this is we couldn't clearing identify the boundaries of one user request. We need to put the flag down at the end of the request which we couldn't find easily. * Suggestion 03: Keep a flag in requestContext and whenever new request create inside the main request, transfer the flag status of the previous request to the new request. transferor is a threadlocal variable. Here each time we invoke registry call, we set the value of the threadlocal variable to the current flag status of the requestContext and inside registry call we set the flag value of the new requestContext to the value in threadLocal variable. *This is too complex solution. we need to find out all registry call and set the variable manually.* Suggestion 04 : Keep a threadLocal stack to track the request flow. Here each time we create request, we put it in the stack and at the end of the registry call we remove that request from the stack. typical request flow e.g.: Put | Add Request Stack Size 1 Put | Add Request Stack Size 2 Remove Association | Add Request Stack Size 3 Remove Association | Remove Request Stack Size 3 Remove Association | Add Request Stack Size 3 Put | Add Request Stack Size 4 Put | Remove Request Stack Size 4 Remove Association | Remove Request Stack Size 3 Put | Add Request Stack Size 3 Put | Remove Request Stack Size 3 Add Association | Add Request Stack Size 3 Add Association | Remove Request Stack Size 3 Put | Remove Request Stack Size 2 Put | Remove Request Stack Size 1 the Stack size reach the zero means we are at the end of the user request. we can trigger eventing handler to generate notification. *Currently this works for me, but don't know whether this is a feasible solution.* Thanks On Mon, Aug 18, 2014 at 6:25 PM, Senaka Fernando sen...@wso2.com wrote: Hi Eranda, Alright. So, just stop the duplication. Ideally, the handler should only be triggered once. And, AFAIU, this is doable with the association-update and recursive delete handlers (and other utility handlers of similar sort) can set some flag within themselves preventing the eventing handlers from firing events for those. Won't this work? Thanks, Senaka. On Mon, Aug 18, 2014 at 1:42 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Senaka, Requirement here is that when we do a artifact update the subscriber getting massive number of mails saying resource updated where the number depends on the number of associations and properties/hidden properties. thanks Eranda On Mon, Aug 18, 2014 at 6:02 PM, Senaka Fernando sen...@wso2.com wrote: Hi Danesh, Eranda, I think we are doing too much here. Before going ahead with this kind of different subscription model, we need to understand the requirement here. At least I'm not clear on that. Do you want it to be configurable as to whether people want to subscribe for association updates etc? or do you want to simply stop people getting multiple notifications? Also, we cannot literally get rid of the handler approach. Its either a handler or it has to be burnt into the kernel. I personally don't think the kernel needs this massive feature and if we take that approach we'll be
Re: [Dev] Registry GET call happens within a transaction
Hi Subash, Ah! forgot to discuss this today when we chatted. Subash the get() itself is a call spanning across multiple tables and for the sake of a DB-neutral implementation we have kept the queries basic. So this means we handle some joins etc at application-level. This is why it has to be transactional. But, I was under the impression that the cache solves this issue altogether with the get() doing nothing @ Embedded Registry level. Isn't this the case or are you talking about first call slow-down? Thanks, Senaka. On Mon, Aug 18, 2014 at 6:36 AM, Subash Chaturanga sub...@wso2.com wrote: Hi Senaka et al, Is there any particular reason for doing $subject ? Because transactional db connection is always heavy and many applications doing the GET quite frequently. IMO we should not be doing a read in a transactional manner. Pls correct me if I am missing something. I am referring EmbeddedRegitry#get. -- Thanks /subash *Subash Chaturanga* Senior Software Engineer Lead WSO2 Governance Registry Platform TG; WSO2 Inc. http://wso2.com Contact: email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388; ext: 51736*; *M: +44 782 741 1966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Registry GET call happens within a transaction
Senaka, I don't think doing a SELECT inside transaction here is required. We just read the committed data @ the time of reading. That's it. We never SELECT records for UPDATES (which is one occurrence where doing a SELECT inside transaction is useful). Another common usecase if to read uncommitted data. But we use neither of these scenarios. So I believe there is not need to read within transaction blocks. On Tue, Aug 19, 2014 at 3:49 AM, Senaka Fernando sen...@wso2.com wrote: Hi Subash, Ah! forgot to discuss this today when we chatted. Subash the get() itself is a call spanning across multiple tables and for the sake of a DB-neutral implementation we have kept the queries basic. So this means we handle some joins etc at application-level. This is why it has to be transactional. But, I was under the impression that the cache solves this issue altogether with the get() doing nothing @ Embedded Registry level. Isn't this the case or are you talking about first call slow-down? Thanks, Senaka. On Mon, Aug 18, 2014 at 6:36 AM, Subash Chaturanga sub...@wso2.com wrote: Hi Senaka et al, Is there any particular reason for doing $subject ? Because transactional db connection is always heavy and many applications doing the GET quite frequently. IMO we should not be doing a read in a transactional manner. Pls correct me if I am missing something. I am referring EmbeddedRegitry#get. -- Thanks /subash *Subash Chaturanga* Senior Software Engineer Lead WSO2 Governance Registry Platform TG; WSO2 Inc. http://wso2.com Contact: email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +44 782 741 1966 %2B44%20782%20741%201966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando* Lean . Enterprise . Middleware -- /sumedha m: +94 773017743 b : bit.ly/sumedha ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Registry GET call happens within a transaction
Hi Sumedha, Alright but this SELECT is across different tables, and I also happened to find this, [1]. So, unless you are in a transaction, if somebody updates while you read, you can end up having messed up data right? [1] http://stackoverflow.com/questions/1976686/is-there-a-difference-between-a-select-statement-inside-a-transaction-and-one-th Thanks, Senaka. On Mon, Aug 18, 2014 at 11:29 PM, Sumedha Rubasinghe sume...@wso2.com wrote: Senaka, I don't think doing a SELECT inside transaction here is required. We just read the committed data @ the time of reading. That's it. We never SELECT records for UPDATES (which is one occurrence where doing a SELECT inside transaction is useful). Another common usecase if to read uncommitted data. But we use neither of these scenarios. So I believe there is not need to read within transaction blocks. On Tue, Aug 19, 2014 at 3:49 AM, Senaka Fernando sen...@wso2.com wrote: Hi Subash, Ah! forgot to discuss this today when we chatted. Subash the get() itself is a call spanning across multiple tables and for the sake of a DB-neutral implementation we have kept the queries basic. So this means we handle some joins etc at application-level. This is why it has to be transactional. But, I was under the impression that the cache solves this issue altogether with the get() doing nothing @ Embedded Registry level. Isn't this the case or are you talking about first call slow-down? Thanks, Senaka. On Mon, Aug 18, 2014 at 6:36 AM, Subash Chaturanga sub...@wso2.com wrote: Hi Senaka et al, Is there any particular reason for doing $subject ? Because transactional db connection is always heavy and many applications doing the GET quite frequently. IMO we should not be doing a read in a transactional manner. Pls correct me if I am missing something. I am referring EmbeddedRegitry#get. -- Thanks /subash *Subash Chaturanga* Senior Software Engineer Lead WSO2 Governance Registry Platform TG; WSO2 Inc. http://wso2.com Contact: email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +44 782 741 1966 %2B44%20782%20741%201966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando* Lean . Enterprise . Middleware -- /sumedha m: +94 773017743 b : bit.ly/sumedha -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388; ext: 51736*; *M: +44 782 741 1966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Registry GET call happens within a transaction
Further to above, since we have row-locking I'm hopeful that we cannot endup with a dirty read as explained in [1], with the current setup. Am I missing something? [1] http://msdn.microsoft.com/en-us/library/ms173763.aspx Thanks, Senaka. On Mon, Aug 18, 2014 at 11:36 PM, Senaka Fernando sen...@wso2.com wrote: Hi Sumedha, Alright but this SELECT is across different tables, and I also happened to find this, [1]. So, unless you are in a transaction, if somebody updates while you read, you can end up having messed up data right? [1] http://stackoverflow.com/questions/1976686/is-there-a-difference-between-a-select-statement-inside-a-transaction-and-one-th Thanks, Senaka. On Mon, Aug 18, 2014 at 11:29 PM, Sumedha Rubasinghe sume...@wso2.com wrote: Senaka, I don't think doing a SELECT inside transaction here is required. We just read the committed data @ the time of reading. That's it. We never SELECT records for UPDATES (which is one occurrence where doing a SELECT inside transaction is useful). Another common usecase if to read uncommitted data. But we use neither of these scenarios. So I believe there is not need to read within transaction blocks. On Tue, Aug 19, 2014 at 3:49 AM, Senaka Fernando sen...@wso2.com wrote: Hi Subash, Ah! forgot to discuss this today when we chatted. Subash the get() itself is a call spanning across multiple tables and for the sake of a DB-neutral implementation we have kept the queries basic. So this means we handle some joins etc at application-level. This is why it has to be transactional. But, I was under the impression that the cache solves this issue altogether with the get() doing nothing @ Embedded Registry level. Isn't this the case or are you talking about first call slow-down? Thanks, Senaka. On Mon, Aug 18, 2014 at 6:36 AM, Subash Chaturanga sub...@wso2.com wrote: Hi Senaka et al, Is there any particular reason for doing $subject ? Because transactional db connection is always heavy and many applications doing the GET quite frequently. IMO we should not be doing a read in a transactional manner. Pls correct me if I am missing something. I am referring EmbeddedRegitry#get. -- Thanks /subash *Subash Chaturanga* Senior Software Engineer Lead WSO2 Governance Registry Platform TG; WSO2 Inc. http://wso2.com Contact: email: sub...@wso2.com blog: http://subashsdm.blogspot.com/ twitter: @subash89 phone: +9477 2225922 Lean . Enterprise . Middleware -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +44 782 741 1966 %2B44%20782%20741%201966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando* Lean . Enterprise . Middleware -- /sumedha m: +94 773017743 b : bit.ly/sumedha -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +44 782 741 1966 %2B44%20782%20741%201966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware -- *[image: http://wso2.com] http://wso2.com Senaka Fernando* Software Architect; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org http://apache.orgE-mail: senaka AT wso2.com http://wso2.com**P: +1 408 754 7388 %2B1%20408%20754%207388; ext: 51736*; *M: +44 782 741 1966 %2B44%20782%20741%201966 Linked-In: http://linkedin.com/in/senakafernando http://linkedin.com/in/senakafernando*Lean . Enterprise . Middleware ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Detect Server Running
When automating wso2 product runs, how do I detect that the server is up? Is there some status value to wait for before a client tries to connect? Regards, Daya -- Daya Atapattu WSO2 Inc. Phone: +94 77 047 4730, +1 203 484 7099 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Installing org.wso2.carbon.apimgt.store feature failed
Thanks Sumedha for committing. I have some few other concerns here. I have added .gitignore file since git removes empty directories. Since you have added the content of admin-dashboard we are no longer needed that file. There were some svn metadata files. I have created a patch and sent a pull request. Can you please merge it. thanks Eranda On Mon, Aug 18, 2014 at 7:21 PM, Eranda Sooriyabandara era...@wso2.com wrote: Please merge the pull [1] request which solves this failure. thanks Eranda [1]. https://github.com/wso2-dev/carbon-apimgt/pull/2 On Wed, Aug 13, 2014 at 10:38 AM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Nuwan, I am getting the following error when I tried to build G-Reg p2. What can be the reason for this? An error occurred while configuring the installed items session context was:(profile=default, phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null -- [R]org.wso2.carbon.apimgt.store.feature.group 4.3.0.SNAPSHOT, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction). I/O Error while copying /home/eranda/greg-repo/myrepos/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components/default/../features/org.wso2.carbon.apimgt.store_4.3.0.SNAPSHOT/admin-dashboard - see details. Caused by: java.io.IOException: Source: /home/eranda/greg-repo/myrepos/product-greg/modules/p2-profile-gen/target/wso2carbon-core-4.3.0-SNAPSHOT/repository/components/default/../features/org.wso2.carbon.apimgt.store_4.3.0.SNAPSHOT/admin-dashboarddoes not exists thanks Eranda -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APPFAC] Error while AF startup
Hi Harsha, Rajith,
Thanks for the input.
I had to set my listen_address: and seeds to the same ip. previously it was
as follows
*listen_address: localhost*
*seed_provider:*
*- class_name: org.apache.cassandra.locator.SimpleSeedProvider*
* parameters:*
* - seeds: 127.0.0.1*
Had to change listen_address to 127.0.0.1 to get this resolved. This
happened even with correct host configurations;where localhost pointing to
127.0.0.1
Regards,
Anuruddha.
On Mon, Aug 18, 2014 at 7:33 PM, Rajith Siriwardena raj...@wso2.com wrote:
HI Anuruddha,
As Harsha said. Your repository/conf/etc/cassandra.yaml contains
following part. As the exception suggests try giving the same seed list.
seems like difference seeds in the cluster.
seed_provider:
# Addresses of hosts that are deemed contact points.
# Cassandra nodes use this list of hosts to find each other and learn
# the topology of the ring. You must change this if you are running
# multiple nodes!
- class_name: org.apache.cassandra.locator.SimpleSeedProvider
parameters:
# seeds is actually a comma-delimited list of addresses.
# Ex: ip1,ip2,ip3
- seeds: 10.0.30.31
Thanks,
--Rajith
On Mon, Aug 18, 2014 at 6:48 PM, Harsha Kumara hars...@wso2.com wrote:
Hi Anuruddha,
Did you do any changes to cassandra.yaml? Seems something wrong there.
Thanks,
Harsha
On Mon, Aug 18, 2014 at 6:32 PM, Anuruddha Premalal anurud...@wso2.com
wrote:
Hi,
I am getting the following error while trying to start the Appfactroy
with the latest release (2.0.1-M4)
What would be the cause for this?.
ERROR {org.apache.cassandra.service.CassandraDaemon} - Exception
encountered during startup
java.lang.RuntimeException: No other nodes seen! Unable to bootstrap.If
you intended to start a single-node cluster, you should make sure your
broadcast_address (or listen_address) is listed as a seed. Otherwise, you
need to determine why the seed being contacted has no knowledge of the rest
of the cluster. Usually, this can be solved by giving all nodes the same
seed list.
at
org.apache.cassandra.dht.BootStrapper.getBootstrapSource(BootStrapper.java:154)
at
org.apache.cassandra.dht.BootStrapper.getBalancedToken(BootStrapper.java:135)
at
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:115)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:709)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:586)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:483)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:348)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:447)
at
org.wso2.carbon.cassandra.server.CassandraServerController$1.run(CassandraServerController.java:48)
at java.lang.Thread.run(Thread.java:745)
java.lang.RuntimeException: No other nodes seen! Unable to bootstrap.If
you intended to start a single-node cluster, you should make sure your
broadcast_address (or listen_address) is listed as a seed. Otherwise, you
need to determine why the seed being contacted has no knowledge of the rest
of the cluster. Usually, this can be solved by giving all nodes the same
seed list.
at
org.apache.cassandra.dht.BootStrapper.getBootstrapSource(BootStrapper.java:154)
at
org.apache.cassandra.dht.BootStrapper.getBalancedToken(BootStrapper.java:135)
at
org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(BootStrapper.java:115)
at
org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:709)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:586)
at
org.apache.cassandra.service.StorageService.initServer(StorageService.java:483)
at
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:348)
at
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:447)
at
org.wso2.carbon.cassandra.server.CassandraServerController$1.run(CassandraServerController.java:48)
at java.lang.Thread.run(Thread.java:745)
Regards,
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile : +94710461070
Web site : www.regilandvalley.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Rajith Siriwardana*
Software Engineer | Cloud Team
WSO2 Inc. ; http://wso2.com
*lean. enterprise. middleware*
--
*http://people.apache.org/~siriwardana
http://people.apache.org/~siriwardana*
--
*Anuruddha Premalal*
Software Eng. | WSO2 Inc.
Mobile :
[Dev] [CARBON] Multiple issues arising when fixing CARBON-14807 - Logging incorrect tenant ID in wso2carbon.log
Hi all,
I am working on [1] and this issue is occurring due to correct tenant
information not being available in the thread local
PrivilegedCarbonContext. This works well for the tenants, but in super
tenant's domain there are certain threads without proper tenant
information. I have added super tenant information for the code segments
invoked by super tenant.
I have multiple questions regarding fixing this.
diff --git
a/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/init/CarbonServerManager.java
b/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/init/CarbonServerManager.java
index 581ebc8..b3c59a4 100644
---
a/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/init/CarbonServerManager.java
+++
b/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/init/CarbonServerManager.java
@@ -889,6 +889,13 @@ public final class CarbonServerManager implements
Controllable {
}
shutdownHook = new Thread() {
public void run() {
+// During shutdown we assume it is triggered by super
tenant
+PrivilegedCarbonContext privilegedCarbonContext =
PrivilegedCarbonContext
+.getThreadLocalCarbonContext();
+privilegedCarbonContext
+
.setTenantDomain(MultitenantConstants.SUPER_TENANT_DOMAIN_NAME);
+
privilegedCarbonContext.setTenantId(MultitenantConstants.SUPER_TENANT_ID);
+
log.info(Shutdown hook triggered);
isShutdownTriggeredByShutdownHook = true;
shutdownGracefully();
diff --git
a/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/internal/CarbonCoreActivator.java
b/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/internal/CarbonCoreActivator.java
index 1d8d027..a1d0ab9 100644
---
a/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/internal/CarbonCoreActivator.java
+++
b/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/internal/CarbonCoreActivator.java
@@ -20,6 +20,8 @@ import org.apache.commons.logging.LogFactory;
import org.bouncycastle.jce.provider.BouncyCastleProvider;
import org.osgi.framework.BundleActivator;
import org.osgi.framework.BundleContext;
+import org.wso2.carbon.context.PrivilegedCarbonContext;
+import org.wso2.carbon.utils.multitenancy.MultitenantConstants;
import java.io.File;
import java.lang.management.ManagementPermission;
@@ -39,6 +41,12 @@ public class CarbonCoreActivator implements
BundleActivator {
if (secMan != null) {
secMan.checkPermission(new ManagementPermission(control));
}
+// We assume it's super tenant during the deployment time
+PrivilegedCarbonContext privilegedCarbonContext =
PrivilegedCarbonContext
+.getThreadLocalCarbonContext();
+
privilegedCarbonContext.setTenantDomain(MultitenantConstants.SUPER_TENANT_DOMAIN_NAME);
+
privilegedCarbonContext.setTenantId(MultitenantConstants.SUPER_TENANT_ID);
+
dataHolder.setBundleContext(context);
log.info(Starting WSO2 Carbon...);
log.info(Operating System : + System.getProperty(os.name) +
+
diff --git
a/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/internal/CarbonCoreServiceComponent.java
b/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/internal/CarbonCoreServiceComponent.java
index 8d2d8e8..125d94a 100644
---
a/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/internal/CarbonCoreServiceComponent.java
+++
b/core/org.wso2.carbon.core/src/main/java/org/wso2/carbon/core/internal/CarbonCoreServiceComponent.java
@@ -29,6 +29,7 @@ import
org.wso2.carbon.registry.core.service.RegistryService;
import org.wso2.carbon.registry.core.service.TenantRegistryLoader;
import org.wso2.carbon.user.core.service.RealmService;
import org.wso2.carbon.core.clustering.api.CoordinatedActivity;
+import org.wso2.carbon.utils.multitenancy.MultitenantConstants;
import java.util.ArrayList;
import java.util.List;
@@ -85,6 +86,11 @@ public class CarbonCoreServiceComponent {
protected void deactivate(ComponentContext ctxt) {
try {
+// We assume it's super tenant during component deactivate time
+PrivilegedCarbonContext privilegedCarbonContext =
PrivilegedCarbonContext
+.getThreadLocalCarbonContext();
+
privilegedCarbonContext.setTenantDomain(MultitenantConstants.SUPER_TENANT_DOMAIN_NAME);
+
privilegedCarbonContext.setTenantId(MultitenantConstants.SUPER_TENANT_ID);
carbonServerManager.stop();
} catch (Throwable e) {
log.error(Failed clean up Carbon core, e);
As you can see there's same code segment repeated in these scenarios. Isn't
it reasonable to add a setThreadLocalTenantAsSuperTenant() method to PCC to
cover this?
Additionally there are some logs printed by other threads invoked by
external components (adding the PrivilegedCarbonContext information to
these threads seems not appropriate). And as a
[Dev] Run soap ui projects within maven project
HI, I have configured sample project to run above task. The objective of this would be a user can create and configure multiple soapui projects and run within a test run. So that it will output the results of them as well. I integrated this in AS product integration as well and working fine. The output of the soapui project automated test cases are available as junit reports and not in testng. Are there any more improvements that can be done? -- Waruna Perera Senior Software Engineer - Test Automation Mobile: +94 77 3867037 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Run soap ui projects within maven project
Hi Waruna, Please add a sample soap UI project to App server in order demonstrate the functionality. So others can use it as a reference for future test cases. Also provide a guide on how to configure SoapUI tests to run in integration test phase. I think we can configure Jenkins to read the Junit reports and get the result to Jenkins dashboard. If it is not the case, we might need to implement a Junit report parser and get the result integrated with TestNG. @QA Team - Please note on this feature, you can easily integrated your SOAPUi test projects to build system now. Thanks, Krishantha. On Tue, Aug 19, 2014 at 10:40 AM, Waruna Perera waru...@wso2.com wrote: HI, I have configured sample project to run above task. The objective of this would be a user can create and configure multiple soapui projects and run within a test run. So that it will output the results of them as well. I integrated this in AS product integration as well and working fine. The output of the soapui project automated test cases are available as junit reports and not in testng. Are there any more improvements that can be done? -- Waruna Perera Senior Software Engineer - Test Automation Mobile: +94 77 3867037 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Run soap ui projects within maven project
Hi, I have pushed a sample maven project on github[1] which includes soapui project as well. Guide for integrate provided as well [2]. [1] https://github.com/warunap/SoupuiRunner [2] https://docs.google.com/a/wso2.com/document/d/1cgyh9TRlXSkAtp1Pu8_WDDOaw3_tmdokTFBbBop55V4 I will find more on what you have suggested in the with reports. Thanks On Tue, Aug 19, 2014 at 10:50 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi Waruna, Please add a sample soap UI project to App server in order demonstrate the functionality. So others can use it as a reference for future test cases. Also provide a guide on how to configure SoapUI tests to run in integration test phase. I think we can configure Jenkins to read the Junit reports and get the result to Jenkins dashboard. If it is not the case, we might need to implement a Junit report parser and get the result integrated with TestNG. @QA Team - Please note on this feature, you can easily integrated your SOAPUi test projects to build system now. Thanks, Krishantha. On Tue, Aug 19, 2014 at 10:40 AM, Waruna Perera waru...@wso2.com wrote: HI, I have configured sample project to run above task. The objective of this would be a user can create and configure multiple soapui projects and run within a test run. So that it will output the results of them as well. I integrated this in AS product integration as well and working fine. The output of the soapui project automated test cases are available as junit reports and not in testng. Are there any more improvements that can be done? -- Waruna Perera Senior Software Engineer - Test Automation Mobile: +94 77 3867037 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Krishantha Samaraweera Senior Technical Lead - Test Automation Mobile: +94 77 7759918 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. -- Waruna Perera Senior Software Engineer - Test Automation Mobile: +94 77 3867037 WSO2, Inc.; http://wso2.com/ lean . enterprise . middlewear. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [ApplicationServer] ConnectionTimeout vs SocketTimeout
Hi, I want to increase response timeout of ApplicationServer since default timeout is not enough with due to slowness of the backend endpoint. I found ConnectionTimeout and SocketTimeout as suspectable properties mentioned in the documentation [1]. What is/are the difference between both parameters? [1] https://docs.wso2.com/display/AS521/HTTP+Servlet+Transport -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] Problems sending numeric keys in JSON Payloads
Hi,
If any of the above does not work use a class mediator to do generate the
json payload required.
eg:-
public boolean mediate(MessageContext mc) {
StringBuilder sb = new StringBuilder();
//generate the required payload
org.apache.axis2.context.MessageContext axis2MC =
((Axis2MessageContext)mc).getAxis2MessageContext();
JsonUtil.newJsonPayload(axis2MC, sb.toString(), true, true);
return true;
}
[1] https://docs.wso2.com/display/ESB481/Class+Mediator
Best Regards,
Malaka
On Wed, Aug 13, 2014 at 1:18 PM, Jay janaka.n.ranathu...@gmail.com wrote:
Hi Malaka,
My initial payload is as follows:
payloadFactory media-type=xml
format
jsonObject xmlns=
nameJanaka/name
descriptionDesc/description
statusopen/status
leadUserA/leadUser
currencyLKR/currency
cust114520/cust
?xml-multiple?tags/tags
/jsonObject
/format
args /
/payloadFactory
In script I'm adding some additional parameters (value and tags.tags should
be send as array even if there are only one) to above payload as:
**
This will work properly if user send tags in request. But my problem is if
user doesn't send tags parameter tags element will remove from payload
and
?xml-multiple? is applying to value element and it will send as array
which back end will not accept. I have two options,
[1]. Remove ?xml-multiple? from payload if user doesn't send any tags
[2]. Add PIs in Script mediator other than in payloadFactory.
What is your idea to solve this problem?
Regards,
Janaka
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/ESB-Problems-sending-numeric-keys-in-JSON-Payloads-tp99789p101325.html
Sent from the WSO2 Development mailing list archive at Nabble.com.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
Best Regards,
Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/
WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/
http://wso2.com/about/team/malaka-silva/
Save a tree -Conserve nature Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ApplicationServer] ConnectionTimeout vs SocketTimeout
Hi Udara, As per tomcat documentation [2] correct parameter should be ConnectionTimeout. Not sure why [1] lists SocketTimeout since its not mentioned in [2]. [2] http://tomcat.apache.org/tomcat-7.0-doc/config/http.html thanks, On Tue, Aug 19, 2014 at 11:09 AM, Udara Liyanage ud...@wso2.com wrote: Hi, I want to increase response timeout of ApplicationServer since default timeout is not enough with due to slowness of the backend endpoint. I found ConnectionTimeout and SocketTimeout as suspectable properties mentioned in the documentation [1]. What is/are the difference between both parameters? [1] https://docs.wso2.com/display/AS521/HTTP+Servlet+Transport -- Udara Liyanage Software Engineer WSO2, Inc.: http://wso2.com lean. enterprise. middleware web: http://udaraliyanage.wordpress.com phone: +94 71 443 6897 -- Supun Malinga, Senior Software Engineer, WSO2 Inc. http://wso2.com email: sup...@wso2.com sup...@wso2.com mobile: +94 (0)71 56 91 321 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
