enabling IFW SCOM connector debug to find Out of memory errors

Products

• CA Service Operations Insight (SOI)

Issue/Introduction

SCOM connector hangs and does not show any specific errors. This article provides information on how to enable debugging and troubleshoot out-of-memory issues .

Environment

SOI 4.2.x

IFW SCOM connector 

Resolution

1. Stop the IFW service from the Connector

2 . Open and edit file below

CA\SOIesources\ifw_IFW.xml

<Logger name="com.ca.sam.ifw.connectorproxy" level="DEBUG" additivity="false">
            <AppenderRef ref="SCOM"/>
        </Logger>
 <Logger name="com.ca.usm.ucf.scom" level="DEBUG" additivity="false">
            <AppenderRef ref="SCOM"/>
 </Logger>

3. Start the IFW service

4. Collect below logs.

CA\SOI\log

Additional Information

If you are seeing any out-of-memory issues from the IFW connector side, you can modify this file:

CA\SOI\jsw\conf\SAM-IntegrationServices.conf

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=4092

You need to look at the below log file from the connector instance for out-of-memory errors: 

CA\SOI\jsw\logs\SAM-IntegrationServices_wrapper.log

The heap dump file should be created in the folder below.

CA\SOI\jsw\bin