Generic list - ACS commons - NOT Updated | Community
Skip to main content
H
harishdev
Level 2
January 13, 2022
Solved

Generic list - ACS commons - NOT Updated

  • January 13, 2022
  • 2 replies
  • 1509 views

Hello All,

I am using ACS commons 5.0.6 on AEM 6.4.
I am using Generic list to store keys and Title.

 

When i update the Title & try to access  the newly modified Title via API genericlist.lookupTitle()
I still am seeing only the old value.

Has someone encountered the issue ?
Please let me know if you have any solutions.

 

NOTE: This issue is happening on publish instance.

 

Thanks

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by harishdev

Hello All ,

Thanks for responding.

I finally found the solution to the problem, whose details is as below.

1. My code snippet initially looks something like this


2. The above was somehow closing the session quicker than expected, resulting in a warning

Unclosed session detected   

 3. Hence the old content was somehow being picked from the memory. The solution was simply as below,

 

Hope this helps anyone who encounters a similar issue.

 

Thanks

2 replies

Ravi_Pampana
Community Advisor
Ravi_PampanaCommunity Advisor
Community Advisor
January 14, 2022

Hi,

 

Did you verify the changes moved to publish instance under the path /etc/acs-commons/lists ? If the changes are not reflecting only in publisher then it might be the changes are not moved to publish instance.

    H
    harishdevAuthor
    Level 2
    January 14, 2022

    Hi Ravi ,

     

    I did verify and infact tried to reopen & save directly on publish.
    However the API still shows the old data.

    It refreshes only after a server restart.

     

    Thanks

      H
      harishdevAuthorAccepted solution
      Level 2
      February 8, 2022

      Hello All ,

      Thanks for responding.

      I finally found the solution to the problem, whose details is as below.

      1. My code snippet initially looks something like this


      2. The above was somehow closing the session quicker than expected, resulting in a warning

      Unclosed session detected   

       3. Hence the old content was somehow being picked from the memory. The solution was simply as below,

       

      Hope this helps anyone who encounters a similar issue.

       

      Thanks

        Terms & ConditionsAccessibility statement

        Loading footer...