0

When I have a running sling instance I get a funny Exception during job execution of

org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler@6dd08975 : Exception while talking to repository (org.apache.sling.api.resource.PersistenceException: Unable to commit changes to session.) java.lang.RuntimeException: Exception while talking to repository (org.apache.sling.api.resource.PersistenceException: Unable to commit changes to session.)

What tools/techniques should I use to make it beat with a right rate ?

aksu
  • 5,221
  • 5
  • 24
  • 39
Sunny M0nkey
  • 15
  • 2
  • 1
    Looks like a bug, do you have a scenario that would allow us to reproduce it? Please indicate the relevant versions or svn revision numbers. – Bertrand Delacretaz Jan 30 '14 at 08:57
  • Yep, use CQ 5.6.1. Prepare 4-5 content packages of about 800MB. And from different browser tab start installing them. At the same time launch Tree Activation on the paths that are still being added. Result: reproduced reliably. – Sunny M0nkey Jan 30 '14 at 15:19
  • Ok, I have mentioned this issue on the sling dev mailing list, let's see if someone has more info about it ( http://mail-archives.apache.org/mod_mbox/sling-dev/ ) – Bertrand Delacretaz Jan 31 '14 at 09:39

0 Answers0