Key Update Question

Document ID : KB000113785
Last Modified Date : 14/09/2018
Show Technical Document Details
Question:
We noticed looping between a Web Agent and the cookie provider.  In the agent log we see frequent key updates like the following:

2361/4160636896][Tue Sep 04 2018 11:50:23][CSmAdminManager.cpp:829][INFO] ADMIN: Received key update attribute 'KEY_UPDATE_PERSISTENT'. 
[2361/4160636896][Tue Sep 04 2018 11:50:23][CSmAdminManager.cpp:847][INFO] ADMIN: Successfully processed key update attribute 'PERSISTENT'. 
[2361/4160636896][Tue Sep 04 2018 11:50:23][CSmAdminManager.cpp:780][INFO] ADMIN: Received key update attribute 'KEY_UPDATE_LAST'. 
[2361/4160636896][Tue Sep 04 2018 11:50:23][CSmAdminManager.cpp:796][INFO] ADMIN: Successfully processed key update attribute 'LAST'. 
[2361/4160636896][Tue Sep 04 2018 11:50:23][CSmAdminManager.cpp:804][INFO] ADMIN: Received key update attribute 'KEY_UPDATE_CURRENT'. 
[2361/4160636896][Tue Sep 04 2018 11:50:23][CSmAdminManager.cpp:821][INFO] ADMIN: Successfully processed key update attribute 'CURRENT'. 
[2361/4160636896][Tue Sep 04 2018 11:50:23][CSmAdminManager.cpp:754][INFO] ADMIN: Received key update attribute 'KEY_UPDATE_NEXT'. 
[2361/4160636896][Tue Sep 04 2018 11:50:23][CSmAdminManager.cpp:771][INFO] ADMIN: Successfully processed key update attribute 'NEXT'. 

Are these messages related to the looping behavior we're seeing?
Answer:
No, these key updates are normal whenever an LLAWP instance initializes and are not related to the looping behavior observed between resource agent and cookie provider.