Running, Testing, and Debugging Processes › Debug a Process › Debug a Java Process

Debug a Java Process

The Java connector uses Apache Log4j to capture the connector’s log messages. When troubleshooting an issue with a Java process, debug it by enabling and then reviewing the log files. The log messages captured at the DEBUG level are very detailed and should help system engineers define the root cause of an issue.

Note: The paths to the log4j.xml and c2o.log files change when running the Java module on a CA Process Automation agent.

Follow these steps:

1. Locate the log4j.xml file at the following path:

   CA Process Automation_Installation_path\Domain\server\c2o\conf\log4j.xml
   
   

2. Set the Java module’s log4j threshold level to DEBUG.

   An example showing the specific section and line (shown in bold) of the log4j.xml file follows:

   <!-- A size based file rolling appender for C2O and JXTA Logs-->
     <appender name="C2OFILE" class="org.jboss.logging.appender.RollingFileAppender">
   	<errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
   	<param name="File" value="${jboss.server.home.dir}/log/c2o.log"/>
   	<param name="Threshold" value="DEBUG"/>
   	<param name="Append" value="true"/>
   	<param name="MaxFileSize" value="50000KB"/>
   	<param name="MaxBackupIndex" value="3"/>
   	<layout class="org.apache.log4j.PatternLayout">
   	  <param name="ConversionPattern" value="%d %-5p [%c] [%15.15t] %m%n"/>
   	</layout>            
     </appender>  
   
   

3. Insert the following section in the log4j.xml file:

   <category name="com.optinuity.c2o.servicegroup.javaobject">	
     <priority value="DEBUG" />
   </category> 
   
   

4. Open the Java connector’s messages captured in the c2o.log file located at the following path:

   CA Process Automation_Installation_path\Domain\server\c2o\log\c2o.log