DX Application Performance Management

Expand all | Collapse all

was agent autonaming

Jump to Best Answer
  • 1.  was agent autonaming

    Posted 08-19-2015 09:59 AM

    Hi All,

     

    do you have please any idea why some servers can get their agentnames based on the websphere app name and connect to the EM under this correct agentname while some others cant get it within 120s (configured in the agent profile) and therefore they connect to the EM under Agent%XY name and after 10mins (that is specified in their profile) they rename trheirselves to their correct WAS name

     

    so

    1. some agents connect to the EM under agent%XY name

    2. later they get their WAS name and therefore they rename theirselves in EM too (based on their name defined in WAS)

    3. EM unmounts the old agents (as they are not used)

     

    my issue is that there is a restart each night and these agents create a lot of historical metrics like this.

     

    1. i cant identify the difference between the minority and the rest of the servers.

    2. they use the same agent profile.

     

    im not sure whether to increase the introscope.agent.agentAutoNamingMaximumConnectionDelayInSeconds=120 property would be a good idea as the majority of the servers connect fine within 120s and we the customer's requirement is to have identical profiles on each WAS server.

     

    so any idea how to identify the difference or some best practice for autonaming would be welcomed.

     

    thank you,

    stefan

     

     

     

    and here is how the output looks like:

    "

    06:05:15.031 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%1
    06:05:15.042 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent" at "Node=Agent_396, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44047, Type=socket" using Agent protocol revision 1.0
    06:05:15.065 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%1" at "Node=Agent_404, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44060, Type=socket" using Agent protocol revision 1.0
    06:05:15.099 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%2
    06:05:15.109 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%3
    06:05:15.117 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%4
    06:05:15.120 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%5
    06:05:15.126 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%6
    06:05:15.127 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%7
    06:05:15.137 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%8
    06:05:15.213 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%9
    06:05:15.249 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%2" at "Node=Agent_399, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44054, Type=socket" using Agent protocol revision 1.0
    06:05:15.271 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%9" at "Node=Agent_405, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44061, Type=socket" using Agent protocol revision 1.0
    06:05:15.298 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%8" at "Node=Agent_401, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44056, Type=socket" using Agent protocol revision 1.0
    06:05:15.324 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%7" at "Node=Agent_402, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44058, Type=socket" using Agent protocol revision 1.0
    06:05:15.349 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%6" at "Node=Agent_397, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44052, Type=socket" using Agent protocol revision 1.0
    06:05:15.370 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%5" at "Node=Agent_403, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44059, Type=socket" using Agent protocol revision 1.0
    06:05:15.393 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%4" at "Node=Agent_398, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44053, Type=socket" using Agent protocol revision 1.0
    06:05:15.419 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%3" at "Node=Agent_400, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44055, Type=socket" using Agent protocol revision 1.0
    06:05:29.338 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%10
    06:05:29.340 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%11
    06:05:29.361 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%10" at "Node=Agent_407, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44065, Type=socket" using Agent protocol revision 1.0
    06:05:29.389 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%11" at "Node=Agent_406, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44062, Type=socket" using Agent protocol revision 1.0
    06:05:31.164 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%12
    06:05:31.188 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%12" at "Node=Agent_408, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44069, Type=socket" using Agent protocol revision 1.0
    06:05:31.220 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%13
    06:05:31.241 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%13" at "Node=Agent_409, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44070, Type=socket" using Agent protocol revision 1.0
    06:05:31.756 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%14
    06:05:31.778 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%14" at "Node=Agent_411, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44073, Type=socket" using Agent protocol revision 1.0
    06:05:31.847 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%15
    06:05:31.867 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%15" at "Node=Agent_410, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44072, Type=socket" using Agent protocol revision 1.0
    06:05:32.692 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%16
    06:05:32.719 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%16" at "Node=Agent_412, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44074, Type=socket" using Agent protocol revision 1.0
    06:05:40.800 [WARN] Non-unique Agent requested connection ("SuperDomain|s2886051|WebSphere|WebSphere Agent"). Re-assigning Agent Name: WebSphere Agent%17
    06:05:40.821 [INFO] Connected to Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%17" at "Node=Agent_413, Address=s2886051.cz.srv.acc.sys/10.242.128.13:44092, Type=socket" using Agent protocol revision 1.0
    06:14:46.600 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent" requested that its name be changed to "s2886051Cell02/WAS2-1".
    06:14:49.237 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%4" requested that its name be changed to "s2886051Cell02/PDS2-2".
    06:14:52.725 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%11" requested that its name be changed to "s2886051Cell02/TES1-1".
    06:14:52.832 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%10" requested that its name be changed to "s2886051Cell02/PDC1-3".
    06:14:53.915 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%7" requested that its name be changed to "s2886051Cell02/PDC2-3".
    06:14:53.957 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%9" requested that its name be changed to "s2886051Cell02/WAC1-1".
    06:14:54.001 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%6" requested that its name be changed to "s2886051Cell02/PDS2-1".
    06:14:54.018 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%5" requested that its name be changed to "s2886051Cell02/PDC2-2".
    06:14:54.028 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%8" requested that its name be changed to "s2886051Cell02/PDC1-2".
    06:14:54.204 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%3" requested that its name be changed to "s2886051Cell02/PDC1-1".
    06:14:54.472 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%1" requested that its name be changed to "s2886051Cell02/TEC2-1".
    06:14:54.861 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%13" requested that its name be changed to "s2886051Cell02/WAC2-1".
    06:14:54.890 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%12" requested that its name be changed to "s2886051Cell02/PDS1-2".
    06:14:55.033 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%2" requested that its name be changed to "s2886051Cell02/PDC2-1".
    06:14:55.266 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%14" requested that its name be changed to "s2886051Cell02/WAS1-1".
    06:14:56.164 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%16" requested that its name be changed to "s2886051Cell02/TES2-1".
    06:14:58.273 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%15" requested that its name be changed to "s2886051Cell02/PDS1-1".
    06:15:23.976 [INFO] Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%17" requested that its name be changed to "s2886051Cell02/TEC1-1".
    07:15:04.496 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%13" after no communication for 60 minute(s).
    07:15:04.501 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%13"
    07:15:04.501 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%10" after no communication for 60 minute(s).
    07:15:04.503 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%10"
    07:15:04.503 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%3" after no communication for 60 minute(s).
    07:15:04.506 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%3"
    07:15:04.506 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%11" after no communication for 60 minute(s).
    07:15:04.508 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%11"
    07:15:04.508 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%7" after no communication for 60 minute(s).
    07:15:04.510 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%7"
    07:15:04.510 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%14" after no communication for 60 minute(s).
    07:15:04.515 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%14"
    07:15:04.515 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent" after no communication for 60 minute(s).
    07:15:04.519 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent"
    07:15:04.520 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%4" after no communication for 60 minute(s).
    07:15:04.521 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%4"
    07:15:04.521 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%5" after no communication for 60 minute(s).
    07:15:04.523 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%5"
    07:15:04.523 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%6" after no communication for 60 minute(s).
    07:15:04.524 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%6"
    07:15:04.524 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%2" after no communication for 60 minute(s).
    07:15:04.526 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%2"
    07:15:04.526 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%15" after no communication for 60 minute(s).
    07:15:04.528 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%15"
    07:15:04.528 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%1" after no communication for 60 minute(s).
    07:15:04.529 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%1"
    07:15:04.529 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%8" after no communication for 60 minute(s).
    07:15:04.530 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%8"
    07:15:04.530 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%12" after no communication for 60 minute(s).
    07:15:04.532 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%12"
    07:15:04.532 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%16" after no communication for 60 minute(s).
    07:15:04.533 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%16"
    07:15:04.533 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%9" after no communication for 60 minute(s).
    07:15:04.536 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%9"
    07:16:04.496 [INFO] [TimerBean] Automatically unmounting Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%17" after no communication for 60 minute(s).
    07:16:04.497 [INFO] [TimerBean] Unmount completed of Agent "SuperDomain|s2886051|WebSphere|WebSphere Agent%17"
    
    
    

    "



  • 2.  Re: was agent autonaming
    Best Answer

    Posted 08-19-2015 12:50 PM

    Hi Stefan,

     

    the internal WAS startup seems to take longer for those servers. Check their agent logs when they get their names. Then set agentAutoNamingMaximumConnectionDelayInSeconds to a reasonable value for all you agents.

     

    What about having two profiles: one for the majority with 120s, one for the slow ones with whatever values that is needed?

     

    Ciao,

    Guenter



  • 3.  Re: was agent autonaming

    Posted 08-20-2015 03:29 AM

    Hi Guneter,

     

    thank you for your reply.

     

    yes, to increase the agentAutoNamingMaximumConnectionDelayInSeconds was my "backup" plan, but i thought/hoped maybe somebody could advice me something else.

     

    there are 2 reasons why i'd like to prevent to have 2 profiles

    1. the customer want to have everything in kind of standard because they have big environment and a standard helps them to manage it (this is the main reason as they really push on this)

    2. i will never know which profile to use (120s or more) before the agent installation, so i have to check the logs quite often and because their procedures, every change needs change request and long burucracy procedure.

     

    thank you,

    stefan