The UIM connector has been using high CPU and after a restart of the
Ca SOI Integration Services
The connector is stuck in ‘initializing’ for hours.
CPU is high for the java process.
Release : SOI 4.2 CU4
UIM nimsoft connector - all supported versions
Old connector log shows that the connector is fetching 504 CI's from UIM at start up:
Line 15484: 2023-01-17 06:42:21,568 INFO [CA:[email protected]_CatalystConnector] impl.NSConnector - Number of CIs returning: 504
To fetching 1.5 million in the current logs.
Enabled debug for connector (see bottom)
And in the transformer log we saw that the majority of CI's being sent over were application type HOSTNAME:websphere_mq
Did a SQL query on the UIM db:
SELECT COUNT(*) FROM CM_CONFIGURATION_ITEM
SELECT COUNT FROM CM_CONFIGURATION_ITEM where ci_name LIKE '%MERCATOR%'
So it turns out someone enabled 2 WebSphere probes that dropped 1.34 million CI's into the db and the SOI connector is trying to parse all of them and getting hung.
Disabled the unwanted websphere probes.
Clean up the UIM database:
Restart the SOI connector.
To enable debug for the connector to see what it is getting and what it is doing with it:
C:\Program Files (x86)\CA\Catalyst\CatalystConnector\container\etc\log4j-ei.properties
# EI log
Edited for debug
# EI log
Changes are read on-the-fly no restarts needed
Logs are in
C:\Program Files (x86)\CA\Catalyst\CatalystConnector\container\data\log
C:\Program Files (x86)\CA\Catalyst\CatalystConnector\container\data\log\EIDebugData