SAM Integration Service was running 32 bit java which has a limitation to use 1 GIG of RAM by default. As soon as the java process reached its allocation it was crashing and a new java process was spawning. This is the reason the connector was staying in "initializing" state and never coming to online. The following error appears in the CA\SOI\jsw\logs\SAM-IntegrationServices_wrapper.log file "java.lang.OutOfMemoryError: Java heap space"
To resolve the issue update the CA\SOI\jsw\conf\SAM-IntegrationServices.conf to run java in 64 bit mode which has max memory set to 4 GIG. - Stop CA SOI Integration Service - Edit SAM-IntegrationServices.conf - Look for the following line and remove the first # sign from the line
# #include ../conf/IFW-wrapper-jvm-64.conf Save the file Start CA SOI Integration Service
- Save the file - Start CA SOI Integration Service NOTE: If you already have the java set to use 64 bit and you are still getting the same error means you'll have to raise the setting to more than 4 GIG in IFW-wrapper-jvm-64.conf and to do that - Stop CA SOI Integration Service - Edit IFW-wrapper-jvm-64.conf - Go to the line that reads wrapper.java.maxmemory=4096 and raise the value to 5120 or 6144 - Save the file and Start CA SOI Integration Service