Hi Nidhi,
Per engineering, this can be done from Agent side in DX SaaS environment.
Here are couple of options:
1. First of all, if the monitored application would have two instances running at the same time momentarily during its restart. Avoid the overlapped process instances by allowing the existing process to exit first before restarting a new one.
2. If the issue still continues, below are the agent properties that can be considered to increase the delay in autonaming to see if it would help mitigate the situation:
introscope.agent.agentAutoNamingMaximumConnectionDelayInSeconds=120
This property specifies the number of seconds that an agent waits for naming information before connecting to the Enterprise Manager.
Default:120
Example:introscope.agent.agentAutoNamingMaximumConnectionDelayInSeconds=120
Note:Restart the managed application for changes to this property to take effect.
introscope.agent.agentAutoRenamingIntervalInMinutes=
This property specifies the number of minutes that an agent waits before determining whether it has been renamed.
Default:10 (minutes)
Example:introscope.agent.agentAutoRenamingIntervalInMinutes=10
Note:Restart the managed application for changes to this property to take effect.
Original Message:
Sent: 05-05-2020 10:28 AM
From: Nidhi Chowdhry
Subject: APM Websphere agent name appended with %1
Hello everyone,
We have recently started using CA APM SaaS for our application. We have been able to register the agents, but the agent name appears to be appended with "%1" intermittently.
I was going through the threads related to this problem on the forum and I understand, this happens when we restart the WebSphere/java process and the EM doesn't disconnect from the agent in time to register the agent again.
The previous threads mentioned that adding the following property to EM should resolve the problem.
introscope.enterprisemanager.metadata.autoexpire=false
As we are using the SaaS version, and have no control over EM. Is there any alternate way to avoid this?
Thanks,
Nidhi