Catalog Maintenace Service Console Output

-
12:55:11,015 INFO [CatalogMaintenanceService] Service CatalogMaintenance - processing functions: AGS_GENPROPERTIES
12:55:11,104 INFO [CatalogMaintenanceService] Service Lock CatalogMaintenance obtained for service CatalogMaintenance.
12:55:11,110 INFO [AncestorGeneratorService] Service AncestorGenerator - processing functions: AGS_GENPROPERTIES
12:55:11,110 INFO [AncestorGeneratorService] TreeWalkUpdateService:performService starting.
12:55:11,110 INFO [AncestorGeneratorService] Update Catalogs: started at Mon Jun 18 12:55:11 IST 2012
12:55:11,116 INFO [AncestorGeneratorService] Executing count queries for base catalogs, categories and folders.
12:55:11,118 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree starting to process base catalogs.
12:55:11,118 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree ended processing of base catalogs.
12:55:11,120 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree starting to process base categories.
12:55:11,365 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree ended processing base categories.
12:55:11,367 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree starting to process base catalog folders.
12:55:11,367 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree ended processing of base catalog folders.
12:55:11,367 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree starting to update repository for catalogs and categories.
12:55:11,516 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree update to repository ended for catalogs and categories.
12:55:11,516 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree starting to update repository for products and skus.
12:55:11,518 INFO [AncestorGeneratorService] updateProducts: starting to process products.
12:55:11,518 INFO [AncestorGeneratorService] Product range builder loop
12:55:11,519 INFO [AncestorGeneratorService] Execution of rangebean query starting at:0 using query:all with starting index:0
12:55:11,546 INFO [AncestorGeneratorService] Execution of rangebean query completed.
12:55:11,655 INFO [AncestorGeneratorService] Creating UpdateProductRange object:missing_product - prod2001
12:55:11,657 INFO [AncestorGeneratorService] Update thread started for range missing_product to prod2009
12:55:12,054 INFO [AncestorGeneratorService] Finished update of data.
12:55:12,076 INFO [AncestorGeneratorService] updateProducts: finished processing product requests.
12:55:12,077 INFO [AncestorGeneratorService] updateSkus: starting to process skus.
12:55:12,092 INFO [AncestorGeneratorService] Sku range builder loop
12:55:12,092 INFO [AncestorGeneratorService] Execution of rangebean query starting at:0 using query:all with starting index:0
12:55:12,108 INFO [AncestorGeneratorService] Execution of rangebean query completed.
12:55:12,118 INFO [AncestorGeneratorService] Creating UpdateSkuRange object:missing_product_sku - sku50001
12:55:12,120 INFO [AncestorGeneratorService] Update thread started for range missing_product_sku to sku50111
12:55:12,121 INFO [AncestorGeneratorService] Sku Range calculation completed.
12:55:13,541 INFO [AncestorGeneratorService] Finished update of data.
12:55:13,559 INFO [AncestorGeneratorService] updateSkus: finished thread.
12:55:13,559 INFO [AncestorGeneratorService] updateSkus: finished processing skus.
12:55:13,559 INFO [AncestorGeneratorService] TreeWalkUpdateService:processTree update to repository ended for products and skus.
12:55:13,559 INFO [AncestorGeneratorService] Update Catalogs: ended at Mon Jun 18 12:55:13 IST 2012
12:55:13,559 INFO [AncestorGeneratorService] Update Catalogs: total processing time is seconds: 2
12:55:13,559 INFO [AncestorGeneratorService] TreeWalkUpdateService:performService finished in 2 seconds.
12:55:13,560 INFO [CatalogMaintenanceService] Service Lock CatalogMaintenance released for service CatalogMaintenance.

See different ways to update catalog structure

Comments

Post a Comment

Popular posts from this blog

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more