Important Log Files for Portal Application

If you run a Portal application based on SAP Web AS, you may find an error on your running process. Mostly the errors are logged into a log files of Java server process. A Portal application usually identified by prefix http://<hostname>:<port>/irj/… Here’s the important log files location :

1. <drive>:\usr\sap\<SID>\DVEBMGS<inst_no>\j2ee\
   cluster\serverX\log\defaultTrace.xx.trc
2. <drive>:\usr\sap\<SID>\DVEBMGS<inst_no>\j2ee\
   cluster\serverX\log\applications.x.log

X: server process number, start from 0,1,2 .. X
xx:default trace number which will be overwritten between 0-19 by default. the most updated can be displayed with the latest timestamp in OS.

The thing is not all people can read what is inside the log files since this is generated roughly from Java process, but those texts are very helpful to predict the portal application. The logs also display some Java class which is used by application. for example :

#1.5#001185E9BA0D0090000031F90000524C00046B19DB1815A0#1243658700982#com.sapportals.wcm.repository.manager.cm.persistence.BasicPersistenceDB#sap.com/irj#com.sapportals.wcm.repository.manager.cm.persistence.BasicPersistenceDB#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [0384ffffffd20071ffffffb2]#n/a##0ff0c3b04a1111deb8c3001185e9ba0d#Thread[ThreadPool.Worker1,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###Exception occured during garbage collection: com.sapportals.wcm.repository.manager.cm.persistence.PersistenceException: SQLException: Cannot change transaction isolation during distributed transaction and when the connection is shared. DataSource name: “SAPSR3DB”, current isolation level is “TRANSACTION_READ_UNCOMMITTED”, new isolation level is “TRANSACTION_READ_COMMITTED”.#

Yes, of course you need to practice how to solve the issue. There will be a hundreds or even a thousands of variation of the error. Well , prepare your time to learn then