[jboss-dev-forums] [Design of Kosmos] - Re: serviceResultUpdaterJob not traversing repository

[sstuart4]

I tried that, but to no avail...

I added a few debug lines to the ServiceResultUpdateJob inside the executeInternal() method as follows:


  |         log.info("Running scheduled update job...");
  | 
  |         log.info("************************ Cache ************************************");
  |         log.info("getSize: " + cache.getSize());
  | 
  |         log.info("************************ Data Store ************************************");
  |         log.info("getDiskStoreSize: " + cache.getDiskStoreSize());
  | 
  |         // iterate through the current content of the cache
  |         for(Iterator it = cache.getKeys().iterator(); it.hasNext();) {
  | 

This was the output of the log file when I restarted the server:


  | 2006-07-21 11:30:40,235 INFO  [hu.midori.kosmos.server.ServiceResultUpdaterJob] Running scheduled update job...
  | 2006-07-21 11:30:40,235 INFO  [hu.midori.kosmos.server.ServiceResultUpdaterJob] ************************ Cache ************************************
  | 2006-07-21 11:30:40,236 INFO  [hu.midori.kosmos.server.ServiceResultUpdaterJob] getSize: 0
  | 2006-07-21 11:30:40,236 INFO  [hu.midori.kosmos.server.ServiceResultUpdaterJob] ************************ Data Store ************************************
  | 2006-07-21 11:30:40,236 INFO  [hu.midori.kosmos.server.ServiceResultUpdaterJob] getDiskStoreSize: 0
  | 2006-07-21 11:30:40,236 INFO  [hu.midori.kosmos.server.ServiceResultUpdaterJob] Update job completed.
  | 

I guess my question now is why would the cache size be empty and the disk store size also? If it is due to my changes in ehcache.xml, it should be trying to traverse the repo now, right?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959957#3959957

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959957