Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

[AEM Gems Webinar] Accelerating Experience Manager as a Cloud Service development with Rapid Development Environments
SOLVED

Generic list - ACS commons - NOT Updated

Avatar

Level 2

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

 

1 Accepted Solution

Avatar

Correct answer by
Level 2

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

Screenshot 2022-02-07 at 1.48.54 PM.png
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,
Screenshot 2022-02-07 at 1.49.16 PM.png

 

Hope this helps anyone who encounters a similar issue.

 

Thanks

View solution in original post

0 Replies

Avatar

Community Advisor

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.

Avatar

Level 2

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

Avatar

Correct answer by
Level 2

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

Screenshot 2022-02-07 at 1.48.54 PM.png
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,
Screenshot 2022-02-07 at 1.49.16 PM.png

 

Hope this helps anyone who encounters a similar issue.

 

Thanks