Agent not connecting with APM command center - SAAS (agent -20.1)

Article Id: 195067
Status: Published
Updated On: 14-07-2020 12:19
Products:
CA Application Performance Management Agent (APM / Wily / Introscope) , CA Application Performance Management (APM / Wily / Introscope) , INTROSCOPE , DX Application Performance Management
Issue/Introduction:

Hi Team,

There are two agents which we are connecting to SAAS, but not connecting with ACC. For one server there was error like below.  I tried to change the port in bundle.properties and IntroscopeAgent.profile for ACC but it has also the same error. For other server, we see controller is started still that is not connecting to ACC. Kindly advise.

IntroscopeAgent.AccControllerManagementService] Starting ACC Controller Management Service
6/29/20 08:29:23 AM EDT [ERROR] [IntroscopeAgent.AccControllerManagementService] Got exception while starting ACC Controller Process: 14
6/29/20 08:29:23 AM EDT [ERROR] [IntroscopeAgent.AccControllerManagementService] AccControllerWatcher - Failed to launch ACC Controller Process

Environment:

Release : 14.6

Component : APM Agents

Resolution:

1) Enable introscope.agent.acc.controller.service.skipEnvVarFilter
2) The ACC Controller Process couldn't start due to the ArrayIndexOutOfBoundsException thrown from bladelogic BlSecurityManager.checkExec.


[ERROR] [IntroscopeAgent.AccControllerManagementService] Got exception while starting ACC Controller Process: 14
[DEBUG] [IntroscopeAgent.AccControllerManagementService] AccControllerWatcher - Exception:
[DEBUG] [IntroscopeAgent.AccControllerManagementService] java.lang.ArrayIndexOutOfBoundsException: 14
java.lang.ArrayIndexOutOfBoundsException: 14
at com.bladelogic.om.infra.app.security.BlSecurityManager.getFirstBladelogicStackTraceElement(BlSecurityManager.java:112)
at com.bladelogic.om.infra.app.security.BlSecurityManager.isInvokedByMethod(BlSecurityManager.java:118)
at com.bladelogic.om.infra.app.security.BlSecurityManager.checkExec(BlSecurityManager.java:215)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1018)
at com.wily.introscope.acc.controller.service.core.BaseControllerProcess.start(BaseControllerProcess.java:95)
at com.wily.introscope.acc.controller.service.core.BaseControllerService.startControllerProcess(BaseControllerService.java:94)
at com.wily.introscope.acc.controller.service.core.BaseControllerService.access$1(BaseControllerService.java:84)
at com.wily.introscope.acc.controller.service.core.BaseControllerService$WatcherTask.ITimestampedRunnable_execute(BaseControllerService.java:201)
at com.wily.util.heartbeat.IntervalHeartbeat$BehaviorNode.execute(IntervalHeartbeat.java:972)
at com.wily.util.heartbeat.IntervalHeartbeat.executeNextBehaviorAndCalculateSleepTime(IntervalHeartbeat.java:491)
at com.wily.util.heartbeat.IntervalHeartbeat.access$2(IntervalHeartbeat.java:445)
at com.wily.util.heartbeat.IntervalHeartbeat$HeartbeatRunnable.run(IntervalHeartbeat.java:668)
at java.lang.Thread.run(Thread.java:748)



Seems Bladelogic is blocking new process being created. Engage Bladelogic support if this occurs.