ATG Topics

I encountered this issue while trying to run an ear module  from our application, the console logs are given below After researching a while,it seems that we need to add a specific permission,'modifyThread' in the java policy file if its not there. I had tweaked the java.policy file(location - jdk_xxx->jre->lib->security->java.policy) and added the below entry Be sure to take a back up of your policy file before doing  such changes,as there are chances your original file may get corrupt if something goes wrong. Now restart your Server and load your application, This solved the issue !!! if anybody has other thoughts,please share it here. Next tip

Console Log: In Weblogic Server Console logs we are getting the exception which says access is denied with the AccessControlException. This exception occurs when both the weblogic server and ACC is running  and we try to shutdown the weblogic server via shutdown scripts .The reason being the ATG control center is  running in some ther ports being initiated by the weblogic thread. To resolve the issue you have to tweak the weblogic policy file bea/wlserver_XX/server/lib/weblogic.policy file Add the below entry grant { permission javax.management.MBeanPermission "*", "*"; Now restart your Server and ACC to verify.Ideally this will resolve the issue !!! Next tip

XAConnection java.sql.SQLException Logs: /atg/dynamo/messaging/SqlJmsProvider    ---     java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_NOTA start() failed on resource 'XXX_DS': XAER_NOTA : The XID is not valid. Fix: Tweak the configuration file of weblogic server and add an entry after the datasource params. jdbc-xa-params> <xa-set-transaction-timeout>true</xa-set-transaction-timeout> </jdbc-xa-params> Make sure you are taking backup of the original configuration file,chances are there while doing modification you may accidently corrupt the orignial file.After doing the necesary changes bounce the Server once,to verify the issue. Still if you are encountering the issue you have to increase the jta values.refer the section to do so Next tip

PermGen or Permanent Generation space is a part of Heap where it stores the Class definitions.By default JVM will take the value as 32m,if we have not set this explicitly,so this is comparitively very less. the issue stated here points that there is no enough Perm Gen space avaialable as per your current JVM settings,so increase it to avoid this issue.Again you need to select appropriate values based on your  development environment,how much hardware support etc. You need to modify this in any webLogic startup Script,i had modified this in setDomain.env file. Increase the heap size to MEM_ARGS=-Xms _ _ _ m -Xmx _ _ _ _ , here i have given values as 512 and 1024 respectievly. Set the Perm size MaxPermSize=_ _ _m,the value given here is 512 . Ideally the Max PermGen value allocated to JVM will be 50% of the Max Heap Size(Xmx). Also typically in a development environment ,if you are using one Admin Server to manage multiple Managed Servers and all your appli...

Java Transaction Timeout Issues We need to basically moidfy the transaction timeout parameter which by default is set as 30seconds by weblogic, many requests might  get timedout  between this very short period,so depends upon your requirement choose the best value that works for your development environment.I had modified it to 600. Two way you can achive this. one is again tweaking the configuratin file and another way to modify it through the admin console. Increase the transaction timeout seconds through console( Services->JTA),or modify in config.xml. If you are modifying the configuration file make sure to take  a backup copy,restart the server,ideally you may not further experience this issue.   Next tip

Avoid NullPointer Exception due to ATG caching of request attributes If you are following best practices while developing ATG applications,you have to be careful enough to avoid any nullpointer exception which crops up during ATG caching of request attributes. The solution  is pretty straight forward,you have to tweak your weblogic configuraion file a bit to add the entry like below. Set  the keep-alive-enabled property to false, in your config.xml. Make sure to take a backup of your original config.xml and restart the server to reflect these modifications. Next tip

For Running ACC in seperate VM ,you will experience some issues related to  authorisation,users with DAS are not impacted by this. So if you are using weblogic server there is an easy fix for this,you have to tweak your configuration file and add an entry to resolve this issue, below is the modification you have to do in your config.xml file. Take a backup copy of your original configuration file,this will save you once the original file is corrupted.restart the server,start your ACC in seperate VM from the component browser/adminUI,ideally you may not experience this issue further. Next tip