Hi, For API Manager we do not require usage agent or throttling agent since we have our own handlers/components to handle usage metering and throttling. So IMO we can remove those from APIM P2. And usage agent component measure service/webapp/registry usage against tenants and in APIM we do not have such use case. Throttling agent also will work in same manner. However we might need other components listed above because those can affect our core functionality.
Thanks, sanjeewa. On Tue, Nov 18, 2014 at 12:34 PM, Chanika Geeganage <[email protected]> wrote: > The pack contains CC non-refactored components. Some of them are, > > 1. In the org.wso2.carbon.registry.eventing 4.2.1 the CC refactoring is > done. But the org.wso2.carbon.deployment.synchronizer.server.feature 4.2.2 > (which is the latest) [1] ships org.wso2.carbon.registry.eventing 4.2.0 > which is not CC refactored. > > 2. The org.wso2.carbon.logging.service 4.2.2 [2] is not refactored > > 3. org.wso2.carbon.usage.agent 2.2.0 is not refactored as Danushka said. > > [1] > https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/features/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer.server.feature/4.2.2/pom.xml > > [2] > https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/logging/org.wso2.carbon.logging.service/4.2.2/src/main/java/org/wso2/carbon/logging/util/FileHandler.java > > Fixing this is bit urgent for the DSS 3.2.2 release > > On Tue, Nov 18, 2014 at 11:30 AM, Chanika Geeganage <[email protected]> > wrote: > >> This issue exists in DSS 3.2.2 pack as well. >> https://wso2.org/jira/browse/DS-993 >> >> On Tue, Nov 18, 2014 at 11:28 AM, Nuwan Dias <[email protected]> wrote: >> >>> APIM 1.8.0 packs all the kernel patches up to patch0009 (latest). So >>> there's nothing missing in terms of kernel patches. >>> >>> Is this fix entirely in the kernel patches or is there anything else >>> required? >>> >>> On Tue, Nov 18, 2014 at 11:17 AM, Evanthika Amarasiri < >>> [email protected]> wrote: >>> >>>> In the pack, there are patches up to patch0009. If this is a bug, the >>>> fix should be included in the next API-M pack. AM team, please note. >>>> >>>> Regards, >>>> Evanthika >>>> >>>> On Tue, Nov 18, 2014 at 10:59 AM, Danushka Fernando <[email protected] >>>> > wrote: >>>> >>>>> BTW just found an issue. >>>>> >>>>> There is a missing CC refactoring in stratos usage agent component. >>>>> Apply the diff [1] to [2] and patch and try. >>>>> >>>>> [1] >>>>> https://wso2.org/jira/secure/attachment/31124/org.wso2.carbon.usage.agent.diff >>>>> [2] >>>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/components/stratos/usage/org.wso2.carbon.usage.agent/2.2.0 >>>>> >>>>> Thanks & Regards >>>>> Danushka Fernando >>>>> Software Engineer >>>>> WSO2 inc. http://wso2.com/ >>>>> Mobile : +94716332729 >>>>> >>>>> On Tue, Nov 18, 2014 at 10:58 AM, Danushka Fernando < >>>>> [email protected]> wrote: >>>>> >>>>>> Can you check what are the kernel patches included in the pack. And >>>>>> also check what are the registry feature versions packed. It should be >>>>>> 4.2.2 or later IIRC. >>>>>> >>>>>> Thanks & Regards >>>>>> Danushka Fernando >>>>>> Software Engineer >>>>>> WSO2 inc. http://wso2.com/ >>>>>> Mobile : +94716332729 >>>>>> >>>>>> On Tue, Nov 18, 2014 at 10:04 AM, Kala Weerawardana <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Hi Danushka, >>>>>>> >>>>>>> I tested this in 1.8.0 release packs. >>>>>>> >>>>>>> On Mon, Nov 17, 2014 at 8:32 PM, Danushka Fernando < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Hi Kala,Lakshman >>>>>>>> Actual issue is at tenant loading time. Due to a missing CC >>>>>>>> refactoring sometimes flow goes through a wrong path and we can see a >>>>>>>> weird >>>>>>>> error when tenant loads. And tenant axis configuration load fails. The >>>>>>>> null >>>>>>>> pointer caused by that since tenant cleanup task is accessing the last >>>>>>>> accessed time from tenant axis configuration. >>>>>>>> @Kala : What is your APIM version? If it is 1.6 apply the patch >>>>>>>> mentioned in [1] and try. Cannot remember whether this fix is there in >>>>>>>> 1.7 >>>>>>>> or not. >>>>>>>> >>>>>>>> [1] >>>>>>>> https://wso2.org/jira/secure/attachment/31122/org.wso2.carbon.server.admin.diff >>>>>>>> >>>>>>>> Thanks & Regards >>>>>>>> Danushka Fernando >>>>>>>> Software Engineer >>>>>>>> WSO2 inc. http://wso2.com/ >>>>>>>> Mobile : +94716332729 >>>>>>>> >>>>>>>> On Mon, Nov 17, 2014 at 5:14 PM, Lakshman Udayakantha < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> Hi Kala, >>>>>>>>> >>>>>>>>> Seems like the issue is resolved in carbon 4.3.0. see the linked >>>>>>>>> issue[1]. It is look like API manager carbon core version 4.2.0. >>>>>>>>> that's why >>>>>>>>> you get this error. >>>>>>>>> >>>>>>>>> [1] https://wso2.org/jira/browse/CARBON-14504 >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> >>>>>>>>> On Mon, Nov 17, 2014 at 1:31 PM, Kala Weerawardana <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> Created a new tenant >>>>>>>>>> Tried to log in to the publisher with it >>>>>>>>>> Had to try couple of times to log in >>>>>>>>>> And then after some redirecting process the tenant was able to >>>>>>>>>> log in to the publisher >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Tried to create an API yet the process was not done properly >>>>>>>>>> >>>>>>>>>> Tried to log in to the Store >>>>>>>>>> Could not log in >>>>>>>>>> >>>>>>>>>> A NullPointerException keep on occurring when tenant cleanup >>>>>>>>>> happens >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> TID: [0] [AM] [2014-11-17 00:14:38,328] INFO >>>>>>>>>> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} - >>>>>>>>>> Starting to >>>>>>>>>> clean tenant : domainone.com >>>>>>>>>> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} >>>>>>>>>> >>>>>>>>>> TID: [0] [AM] [2014-11-17 00:14:38,329] ERROR >>>>>>>>>> {org.wso2.carbon.core.multitenancy.MultitenantServerManager} - Error >>>>>>>>>> occurred while executing tenant cleanup >>>>>>>>>> {org.wso2.carbon.core.multitenancy.MultitenantServerManager} >>>>>>>>>> >>>>>>>>>> java.lang.NullPointerException >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> org.wso2.carbon.core.multitenancy.TenantAxisConfigurator.cleanup(TenantAxisConfigurator.java:512) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.terminateTenantConfigContext(TenantAxisUtils.java:490) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.cleanupTenants(TenantAxisUtils.java:441) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> org.wso2.carbon.core.multitenancy.MultitenantServerManager$TenantCleanupTask.run(MultitenantServerManager.java:73) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>>>>>>>> >>>>>>>>>> at java.lang.Thread.run(Thread.java:745) >>>>>>>>>> >>>>>>>>>> TID: [0] [AM] [2014-11-17 00:15:14,188] INFO >>>>>>>>>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} - >>>>>>>>>> LDAP >>>>>>>>>> connection created successfully in read-write mode >>>>>>>>>> {org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} >>>>>>>>>> >>>>>>>>>> TID: [0] [AM] [2014-11-17 00:15:38,328] INFO >>>>>>>>>> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} - >>>>>>>>>> Starting to >>>>>>>>>> clean tenant : domainone.com >>>>>>>>>> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} >>>>>>>>>> >>>>>>>>>> TID: [0] [AM] [2014-11-17 00:15:38,329] ERROR >>>>>>>>>> {org.wso2.carbon.core.multitenancy.MultitenantServerManager} - Error >>>>>>>>>> occurred while executing tenant cleanup >>>>>>>>>> {org.wso2.carbon.core.multitenancy.MultitenantServerManager} >>>>>>>>>> >>>>>>>>>> java.lang.NullPointerException >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> org.wso2.carbon.core.multitenancy.TenantAxisConfigurator.cleanup(TenantAxisConfigurator.java:512) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.terminateTenantConfigContext(TenantAxisUtils.java:490) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.cleanupTenants(TenantAxisUtils.java:441) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> org.wso2.carbon.core.multitenancy.MultitenantServerManager$TenantCleanupTask.run(MultitenantServerManager.java:73) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>>>>>>>>> >>>>>>>>>> at >>>>>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>>>>>>>>> >>>>>>>>>> at java.lang.Thread.run(Thread.java:745) >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> This is related to this issue >>>>>>>>>> https://wso2.org/jira/browse/APIMANAGER-2369 >>>>>>>>>> <https://wso2.org/jira/browse/APIMANAGER-2369> >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Kala >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Kala C. Weerawardana >>>>>>>>>> *Software Engineer - QA Team* >>>>>>>>>> *WSO2 Inc. * >>>>>>>>>> Mobile : +94 (0) 716189886 +94 (0) 772877683 >>>>>>>>>> [email protected] >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Dev mailing list >>>>>>>>>> [email protected] >>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Lakshman Udayakantha >>>>>>>>> WSO2 Inc. www.wso2.com >>>>>>>>> lean.enterprise.middleware >>>>>>>>> Mobile: *0711241005 <0711241005>* >>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Dev mailing list >>>>>>>>> [email protected] >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Kala C. Weerawardana >>>>>>> *Software Engineer - QA Team* >>>>>>> *WSO2 Inc. * >>>>>>> Mobile : +94 (0) 716189886 +94 (0) 772877683 >>>>>>> [email protected] >>>>>>> >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Associate Tech Lead - WSO2, Inc. http://wso2.com >>> email : [email protected] >>> Phone : +94 777 775 729 >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Best Regards.. >> >> Chanika Geeganage >> Software Engineer >> Mobile : +94773522586 >> WSO2, Inc.; http://wso2.com >> >> > > > -- > Best Regards.. > > Chanika Geeganage > Software Engineer > Mobile : +94773522586 > WSO2, Inc.; http://wso2.com > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
