Roberto's Tech Stuff

If you already have a JDK version installed on your machine, but then you change it to another version (for example, after installing latest java patch for jdk 1.6 which includes a fix for TLSv1.2 ), you will probably get something like this when starting up your instance: 11:15:09,925 WARNING [config] Unable to process deployment descriptor for context '/DCS-CSR-UI' 11:15:09,925 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/DCS-CSR-UI' 11:15:09,959 INFO  [TomcatDeployment] deploy, ctxPath=/DCS-CSR 11:15:09,976 WARNING [config] Unable to process deployment descriptor for context '/DCS-CSR' 11:15:09,977 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/DCS-CSR' 11:15:10,001 INFO  [TomcatDeployment] deploy, ctxPath=/ServiceFramework 11:15:10,014 WARNING [config] Unable to process deployment descriptor for context '/ServiceFramework' 11:15:10,014 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for ...

Whenever you find an error like this (for category-product relationship for example) ERROR [nucleusNamespace.atg.commerce.catalog.ProductCatalog-ver]  Error reading list or array index from the database. Expected: "0", got "1". The following property was not read: " {fixedChildProducts,pType=List,IDesc=[ItemDesc: category],table=dcs_cat_chldprd,cols=child_prd_id   ,pBI=atg.beans.MergedDynamicBeanInfo@5409e0ad,pIDesc=null   ,cType=interface atg.repository.RepositoryItem,cBI=[ItemDesc: product],cIDesc=[ItemDesc: product],colHandle=null}", for item id: "2350:36". This means the data base table holding this property does not have sequential integers starting with 0 in its multi-column. This should only happen if the database table was modifie d directly (outside of Dynamo).: java.lang.Exception It means sequence_num column doesn't contain a consecutive sequence number for the category on all of its products, this is, if category has ...

When you get that constraint violation error it means indexing jobs on CSC are stepping on each other or even themselves, if you happen to have a schedule without catch up and even running too often then you'll be seeing a lot errors lik this: ERROR [nucleusNamespace.atg.textsearch.indexing.job.IndexingJob] (pool-103-thread-1) ORA-00001: unique constraint (DRESS_CORE.SRCH_ORDER_TOKENS_P) violated And eventually you'll get an error like this: ERROR [nucleusNamespace.atg.dynamo.messaging.SqlJmsProvider] (ServerService Thread Pool -- 102) null: java.sql.SQLExc eption: javax.resource.ResourceException: IJ000451: The connection manager is shutdown: java:/ATGAgentDS So just update the schedule for the indexing components: /atg/commerce/textsearch/schedule/OrderIncrementalScheduleConfig schedule=calendar * * * * * 0,2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56,58 /atg/userprofiling/textsearch/schedule/ProfileIncrement...

If you're getting an error like this: java.lang.UnsupportedClassVersionError: _dasadmin_3__UTF_s8/_index : Unsupported major.minor version 51.0 ..... ..... [PageCompileServlet] Error compiling page: /index.jhtml : can't load class: _dasadmin_3__UTF_s8._index You need to change the javac from your machine, in order to match the java version used for building the code. For Ubuntu: 1. Open the terminal and run this: sudo update-alternatives --install /usr/bin/java java /opt/java/jdk1.6.0_25 1 2. It will install the jdk, now you need to select it from the alternatives sudo update-alternatives --config java 3. And select the one corresponding to the jdk you require 4. Then you must do the same for javac sudo update-alternatives --install /usr/bin/javac javac /opt/java/jdk1.6.0_25/bin/javac 1 5. And update the config within alternatives too: sudo update-alternatives --config javac 6. And select the one corresponding to the jdk you require 7. Remember to updat...