Repository exception in com.day.cq.tagging.impl.JcrTagImpl

Hi @pardeepg4829047 ,

The exception you're encountering, javax.jcr.RepositoryException: This session has been closed., typically indicates that the JCR session being used to access repository data has been closed prematurely. This can happen due to various reasons, such as session timeouts, explicit closure of the session, or issues with session management.

Here are a few steps you can take to troubleshoot and potentially resolve this issue:

1. Session Management:

   • Review the code where JCR sessions are being obtained and used. Ensure that sessions are being properly managed, i.e., being opened when needed, used, and then closed appropriately.
   • Make sure that no session is being used after it has been closed.

2. Session Timeout:

   • Check if there's a session timeout configured in your application or server settings. Sessions should be closed before they time out to prevent this exception.

3. Exception Handling:

   • Implement proper exception handling in your code to catch and handle exceptions related to JCR sessions. This can help in identifying the root cause of the session closure.

4. Logging:

   • Enable debug logging for JCR-related classes or packages. This can provide more detailed information about the sequence of events leading up to the session closure and help pinpoint the issue.

5. Review Custom Code:

   • Look into any custom code (like the PallPageContent class mentioned in the stack trace) that interacts with JCR sessions or tagging functionality. Ensure that it's handling sessions correctly and not causing premature closure.

6. Environment Differences:

   • Since the issue is specific to the publish instance, compare the configuration and environment settings between your author and publish instances. There might be differences in session management or resource availability that could be causing the problem.

7. Vendor Support:

   • If you're unable to identify the issue or resolve it based on the above steps, consider reaching out to the vendor's support team for assistance. They might be able to provide further insights or solutions specific to your setup.

By investigating these areas, you should be able to diagnose the cause of the session closure and take appropriate actions to address it.

The answer is in the logs,

com.day.cq.tagging.impl.JcrTagImpl Could not retrieve node path

So in this case, either your repository does not have the correct permissions in the publisher to find the cq:tag node, OR, the tag just never exists.