Enable Hazelcast debug to determine cluster related issues in WebUI (WCC)

Products

• Autosys Workload Automation

Issue/Introduction

Steps to enable Hazelcast debug to determine cluster related issues in WebUI (WCC) during collector and main application connection issues, OR for communication issues between WebUI nodes

Environment

AutoSys Workload Automation

Resolution

1. Backup two files first
   1. <CA_WCC_INSTALL_LOCATION>/tomcat/conf/log4j2.xml  and  
   2. <CA_WCC_INSTALL_LOCATION>/collectors/WCC_COLLECTOR/conf/log4j2.xml
      
      
2. Edit the original file, <CA_WCC_INSTALL_LOCATION>/tomcat/conf/log4j2.xml  and uncomment the line below
   <!-- <Logger name="com.hazelcast" level="DEBUG" /> -->
   
   it should look like
   
   <Logger name="com.hazelcast" level="DEBUG" />


3. Save the file
   
   
4. Edit the original file, <CA_WCC_INSTALL_LOCATION>/collectors/WCC_COLLECTOR/conf/log4j2.xml  and look for <Loggers>
   
   ADD a line right below the line  <Loggers>  

<Logger name="com.hazelcast" level="DEBUG" />


5. It should now look something like: 

  <Loggers>

    <Logger name="com.hazelcast" level="DEBUG" />

   <!-- Reduce the apache logging -->


6. Save the file
   
   
7. Restart CA-wcc-services 
   
   
8. CA-wcc.log and WCC-COLLECTOR.log now would contain the necessary hazelcast logging that helps troubleshoot issues
   
   
9. To disable the debug,  restore the backup log4j2.xml files above from step#1  and restart CA-wcc-services