Thanks for your reply..
Scenario :
Copying child nodes from particular node(/content/old/node1) and replacing child nodes under path /content/new/node1.Also doing add/modify/delete property under the node /content/new/node1 and its child nodes.
Similarly (/content/old/node2) to (/content/new/node2)
(/content/old/node3) to (/content/new/node3)
(/content/old/node4) to (/content/new/node4)
I am doing the above four operation at same time(creating job for each process /content/old/node1 to /content/new/node1). Four job is running parallel.
Initial call came to job class and it is directing to job service. In job service, I created resourceresolver
from resourceresolverfactory(org.apache.sling.api.resource) and made resourceresolver as global variable for creating session at various private lower level methods.
Example:
Private ResourceResolver resolver
Class Jobservice(){
public void mainmethod(){
resolver = resourceresolverfactory.getServiceResourceResolver(null);
String path = "/content/old/node1";
lowerMethod1(path)
}
private void lowerMethod1(String path){
Session session= resolver.adapt(Session.class);
Node destinationNode = session.getNode("/content/new/node1");
deleteAllCHildNodes(destinationNode);
updateProperty(destinationNode);
}
private void deleteAllCHildNodes(Node destNode){
Session session= resolver.adapt(Session.class);
---deleting all childnodes under destNode----
session.save();
}
Likewise I am doing different operation under /content/new/node1. I was getting concurrent access error and invaliditemstateexception(item doesi not exist anymore) at the different places in my code
because four jobs are running parallel and performing operation under the respective node. I came to know that sessions are
opening long time by google search(https://cqdump.wordpress.com/2015/03/02/aem-scaling-patterns-avoid-shared-sessions/) abt this issue.
Also changes done for node1 in session1(first job) will not be available in session2(opened in second job).
In order to avoid this error, I am creating resourceresolver and session at lower level methods and closing at the end of method itself(Session is opening for short duration) as below
Class Jobservice(){
public void mainmethod(){
ResourceResolver resolver = null;
Session session = null;
try {
resolver = resolverFactory.getServiceResourceResolver(null);
session = resolver.adaptTo(Session.class);
String path = "/content/old/node1";
lowerMethod1(path);
} catch (Exception e) {
Logging exception
} finally {
if (session != null && session.isLive()) {
session.logout();
}
if (resolver != null && resolver.isLive()) {
resolver.close();
}
}
}
private void lowerMethod1(String path){
ResourceResolver resolver = null;
Session session = null;
try {
resolver = resolverFactory.getServiceResourceResolver(null);
session = resolver.adaptTo(Session.class);
Node destinationNode = session.getNode("/content/new/node1");
deleteAllCHildNodes(destinationNode);
updateProperty(destinationNode);
} catch (Exception e) {
Logging exception
} finally {
if (session != null && session.isLive()) {
session.logout();
}
if (resolver != null && resolver.isLive()) {
resolver.close();
}
}
}
private void deleteAllCHildNodes(Node destNode){
ResourceResolver resolver = null;
Session session = null;
try {
resolver = resolverFactory.getServiceResourceResolver(null);
session= resolver.adapt(Session.class);
---deleting all childnodes under destNode----
session.save();
} catch (Exception e) {
Logging exception
} finally {
if (session != null && session.isLive()) {
session.logout();
}
if (resolver != null && resolver.isLive()) {
resolver.close();
}
}
}
Kindly share your thoughts on this one.. whether it is good practice to do create and close resourceresolver and session in single method and it will cause any performance issue because mostly maximum no of jobs(10) will run in parallel.
Please suggest any other ideas to handle the concurrent issue if my idea is not good.
