Hi Ajith, The numbers do not suggest whether caching is working 100% of the time, or whether it is partial. A certain reduction indicates that this is at least partially working, but not totally. Would you mind reviewing the 38 select queries and determining what were the operations? If the 38 select calls resulted before the cache was populated, we are ok, but if it was not, we need to check what those were.
Thanks, Senaka. 2011/12/9 Ajith Vitharana <[email protected]> > Hi Senaka, > > I did a quick test to verify the registry resource cache in latest test > pack. > > Steps > ====== > 1) Upload two resource to "/_system/config/tt" > 2) Calculate number of SQL queries .(enable and disable resource caching > from registry.xml) > > The results was 38 SELECT query with enable cache and 127 SELECT query > with disable cache. > Therefore resource level caching working in latest pack. > > Thanks > -Ajith > > > On Fri, Dec 9, 2011 at 7:35 PM, Ajith Vitharana <[email protected]> wrote: > >> >> >> On Fri, Dec 9, 2011 at 3:59 PM, Senaka Fernando <[email protected]> wrote: >> >>> Hi again, >>> >>> I believe that we tested these scenarios on 4.1.0, so I'm wondering >>> whether this is a regression issue that was introduced in 4.1.1? >>> >> >> Hi Senaka, >> >> SELECT REG_PATH_ID, REG_NAME FROM REG_RESOURCE WHERE >> (REG_RESOURCE.REG_TENANT_ID=0) AND >> REG_MEDIA_TYPE='application/vnd.wso2-service+xml' >> >> This SQL query has executed to get the path list of services and we are >> not getting individual resources from database when listing the services. >> Therefore this is not a bug. >> >> Thanks >> Ajith >> >> >> >> >> >> >>> >>> Thanks, >>> Senaka. >>> >>> >>> On Fri, Dec 9, 2011 at 3:58 PM, Senaka Fernando <[email protected]> wrote: >>> >>>> Hi Evanthika, >>>> >>>> Thanks for reporting and this needs to be definitely fixed. >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> >>>> On Fri, Dec 9, 2011 at 3:36 PM, Evanthika Amarasiri <[email protected] >>>> > wrote: >>>> >>>>> Hi, >>>>> >>>>> Found a blocker [1] in latest G-Reg packs. >>>>> >>>>> [1] - https://wso2.org/jira/browse/CARBON-11824 >>>>> >>>>> Regards, >>>>> Evanthika >>>>> >>>>> >>>>> On Fri, Dec 9, 2011 at 1:53 PM, Senaka Fernando <[email protected]>wrote: >>>>> >>>>>> Hi again, >>>>>> >>>>>> So here is the summary. We have changes to caching core that was >>>>>> introduced after 3.2.2. But, we also have some issues with regard to some >>>>>> fixes that were done in 3.2.2 not appearing in 3.2.3. So, can we first of >>>>>> all, review the difference below and decide whether 3.2.3 is up-to-date >>>>>> and >>>>>> if not fix that? After that's done, we need to include 3.2.3 into the >>>>>> build >>>>>> so that products will have it. >>>>>> >>>>>> Thanks, >>>>>> Senaka. >>>>>> >>>>>> >>>>>> On Fri, Dec 9, 2011 at 1:35 PM, Senaka Fernando <[email protected]>wrote: >>>>>> >>>>>>> Hi Asela, >>>>>>> >>>>>>> But there are differences in 3.2.2 and 3.2.3. How did that happen? >>>>>>> Also, somethings have been added to 3.2.3 which means we need to use >>>>>>> 3.2.3 >>>>>>> and not 3.2.2. >>>>>>> >>>>>>> +++++++++++++++++++++++++++++++++++ >>>>>>> $ diff -r 3.2.3 3.2.2 >>>>>>> diff -r >>>>>>> 3.2.3/src/main/java/org/wso2/carbon/caching/core/identity/IdentityCacheEntry.java >>>>>>> 3.2.2/src/main/java/org/wso2/carbon/caching/core/identity/IdentityCacheEntry.java >>>>>>> 32a33 >>>>>>> > private String[] cacheEntryArray; >>>>>>> 54a56,59 >>>>>>> > public IdentityCacheEntry(String[] cacheEntryArray) { >>>>>>> > this.cacheEntryArray = cacheEntryArray; >>>>>>> > } >>>>>>> > >>>>>>> 77a83,86 >>>>>>> > >>>>>>> > public String[] getCacheEntryArray() { >>>>>>> > return cacheEntryArray; >>>>>>> > } >>>>>>> diff -r >>>>>>> 3.2.3/src/main/java/org/wso2/carbon/caching/infinispan/InfinispanCacheManager.java >>>>>>> 3.2.2/src/main/java/org/wso2/carbon/caching/infinispan/InfinispanCacheManager.java >>>>>>> 88,98d87 >>>>>>> < >>>>>>> < >>>>>>> < String tcpConfigFile = >>>>>>> cacheConfiguration.getProperty("configuration.tcp.configFile"); >>>>>>> < if (tcpConfigFile != null) { >>>>>>> < Properties props = new Properties(); >>>>>>> < props.setProperty("configurationFile", >>>>>>> tcpConfigFile.replace("${carbon.home}", >>>>>>> < carbonHome)); >>>>>>> < log.debug("Setting infinispan tcp configuration file"); >>>>>>> < globalConfiguration.setTransportProperties(props); >>>>>>> < } >>>>>>> < >>>>>>> 171d159 >>>>>>> < configuration.setUseLockStriping(false); >>>>>>> +++++++++++++++++++++++++++++++++++ >>>>>>> >>>>>>> Thanks, >>>>>>> Senaka. >>>>>>> >>>>>>> >>>>>>> On Fri, Dec 9, 2011 at 12:46 PM, Hasini Gunasinghe >>>>>>> <[email protected]>wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Dec 9, 2011 at 12:30 PM, Asela Pathberiya >>>>>>>> <[email protected]>wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Dec 9, 2011 at 11:57 AM, Senaka Fernando >>>>>>>>> <[email protected]>wrote: >>>>>>>>> >>>>>>>>>> Hi Asela, >>>>>>>>>> >>>>>>>>>> I see that 3.2.2 version of >>>>>>>>>> src/main/java/org/wso2/carbon/caching/core/identity/IdentityCacheEntry.java >>>>>>>>>> have differences over the 3.2.3 version. Can you sort these out and >>>>>>>>>> also >>>>>>>>>> add the 3.2.3 version of caching.core into the mainstream build? >>>>>>>>>> >>>>>>>>> >>>>>>>>> I am sorry. IdentityCacheEntry class has not been changed after Oct >>>>>>>>> 17 (before the 3.2.2 release). Identity components are >>>>>>>>> still referring to the 3.2.2 caching core. May be 3.2.3 caching core >>>>>>>>> has >>>>>>>>> been created before 3.2.2 release or old revision. >>>>>>>>> >>>>>>>>> +1, it is an issue with 3.2.3 version, not with 3.2.2 version. >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Hasini. >>>>>>>> >>>>>>>> Thanks, >>>>>>>>> Asela. >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Senaka. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Fri, Dec 9, 2011 at 11:49 AM, Hasini Gunasinghe < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Hi, >>>>>>>>>>> >>>>>>>>>>> In 3.2.3 branch, there is caching.core 3.2.3 version. >>>>>>>>>>> I see two issues with that: >>>>>>>>>>> 1. It is not included in latest product packs at [1], >>>>>>>>>>> 2. Seems like it is not a latest copy of 3.2.2 release.. so >>>>>>>>>>> some of the commits that has gone to 3.2.2 are not in 3.2.3 >>>>>>>>>>> component of it. >>>>>>>>>>> >>>>>>>>>>> I think this also should be fixed before the code freeze. Would >>>>>>>>>>> be great if some one who has been working with caching.core 3.2.3 >>>>>>>>>>> component >>>>>>>>>>> can please look into it. >>>>>>>>>>> >>>>>>>>>>> [1] >>>>>>>>>>> http://builder1.us1.wso2.org/~carbon320/releases/carbon/3.2.3/2011-12-07_05-46-09/ >>>>>>>>>>> >>>>>>>>>>> Thanks, >>>>>>>>>>> Hasini. >>>>>>>>>>> >>>>>>>>>>> On Fri, Dec 9, 2011 at 11:00 AM, Sumedha Rubasinghe < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>> >>>>>>>>>>>> G-Reg is having 8 blockers still. Senaka will reply on the >>>>>>>>>>>> possibility of completion. >>>>>>>>>>>> /sumedha >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Dec 9, 2011 at 10:26 AM, Prabath Siriwardena < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Hi folks, >>>>>>>>>>>>> >>>>>>>>>>>>> Carbon 3.2.3 branch will be frozen at 6 PM IST today.... >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Thanks & Regards, >>>>>>>>>>>>> Prabath >>>>>>>>>>>>> >>>>>>>>>>>>> http://blog.facilelogin.com >>>>>>>>>>>>> http://RampartFAQ.com >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Carbon-dev mailing list >>>>>>>>>>>>> [email protected] >>>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Carbon-dev mailing list >>>>>>>>>>>> [email protected] >>>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Carbon-dev mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Senaka Fernando* >>>>>>>>>> Product Manager - WSO2 Governance Registry; >>>>>>>>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >>>>>>>>>> Member; Apache Software Foundation; http://apache.org >>>>>>>>>> >>>>>>>>>> E-mail: senaka AT wso2.com >>>>>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>>>>>>>> Linked-In: http://linkedin.com/in/senakafernando >>>>>>>>>> >>>>>>>>>> *Lean . Enterprise . Middleware >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Carbon-dev mailing list >>>>>>>>> [email protected] >>>>>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Senaka Fernando* >>>>>>> Product Manager - WSO2 Governance Registry; >>>>>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >>>>>>> Member; Apache Software Foundation; http://apache.org >>>>>>> >>>>>>> E-mail: senaka AT wso2.com >>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>>>>> Linked-In: http://linkedin.com/in/senakafernando >>>>>>> >>>>>>> *Lean . Enterprise . Middleware >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Senaka Fernando* >>>>>> Product Manager - WSO2 Governance Registry; >>>>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >>>>>> Member; Apache Software Foundation; http://apache.org >>>>>> >>>>>> E-mail: senaka AT wso2.com >>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>>>> Linked-In: http://linkedin.com/in/senakafernando >>>>>> >>>>>> *Lean . Enterprise . Middleware >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Carbon-dev mailing list >>>>>> [email protected] >>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Carbon-dev mailing list >>>>> [email protected] >>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Senaka Fernando* >>>> Product Manager - WSO2 Governance Registry; >>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >>>> Member; Apache Software Foundation; http://apache.org >>>> >>>> E-mail: senaka AT wso2.com >>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>> Linked-In: http://linkedin.com/in/senakafernando >>>> >>>> *Lean . Enterprise . Middleware >>>> >>>> >>> >>> >>> -- >>> *Senaka Fernando* >>> Product Manager - WSO2 Governance Registry; >>> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >>> Member; Apache Software Foundation; http://apache.org >>> >>> E-mail: senaka AT wso2.com >>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>> Linked-In: http://linkedin.com/in/senakafernando >>> >>> *Lean . Enterprise . Middleware >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
