Keep an object in CQ5 session for all users | Community
Skip to main content
Riju-Mahna
Riju-Mahna
Level 2
October 16, 2015
Solved

Keep an object in CQ5 session for all users

  • October 16, 2015
  • 5 replies
  • 2341 views

I need to read and fetch values from an XML file kept in the DAM. The file is 111 MB in size and takes forever to unmarshall and then equally long time to find the value I am looking for.

I am using JaxB to unmarshall the XML file and then iterating through the list. But most of the times I face timeouts and heapspace error while parsing it.

 

Is there any way to keep the unmarshalled object in the session and fetch it from there whenever a user needs to search some data in it ?

Any suggestions will be appreciated.

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 smacdonald2008
After talking with some Co workers; that volume  of data on a daily  basis  should be stored outside of JCR. For example place the data in MySql.       

5 replies

P
PaulMcMahon
Level 8
October 16, 2015

If Scott's suggestion to use the JCR doesn't work for you solving this problem is really more of a Java issue than a AEM on. If you create and OSGI service to handle searching the data you could unmarshall the file on system start up, store the unmarshalled object in a local variable of the service, and then any code that needs the XML data can call the OSGI service. In addition you might consider integrating redis or memcache (or something similar) to enhance the performance of you search of unmarshalled object.  

smacdonald2008
smacdonald2008
Level 10
October 16, 2015
You can also write an OSGI service to read the xml values and store the values in the JCR. When you need a value, retrieve the values from the JCR. That way, you are not parsing  the XML when you need a value. 
Riju-Mahna
Riju-MahnaAuthor
Level 2
October 16, 2015

I thought of doing that. So that we can make a JCR query every time we need to fetch some data.

But the file will have about 180,000 - 250,000 items (each item having a specific set of fields). Don't you think creating such a huge number of nodes in JCR will cause extra load on the JCR and can cause indexing issues in AEM6 ?
Just a hunch. I am not 100% sure of the impact of these many nodes being created/recreated daily. (The XML changes daily)

smacdonald2008
smacdonald2008
Level 10
October 16, 2015
  With this much data on a daily basis; you may want to consider writing an AEM sling scheduler service to run 1 a day and update nodes. This way, the data gets automatically  updated. For information about a scheduler service, see      https://helpx.adobe.com/experience-manager/using/aem-first-components1.html
smacdonald2008
smacdonald2008Accepted solution
Level 10
October 16, 2015
After talking with some Co workers; that volume  of data on a daily  basis  should be stored outside of JCR. For example place the data in MySql.       
Terms & ConditionsAccessibility statement

Loading footer...