We also see this issue. We are running the publish instance in a virtual machine. Shutting down the publish instance and restarting the instance only sometimes do we see the error message. But once we see the issue it does not go away. We are running the instance in a 64bit Red Hat 6.2 virtual machine.
I did notice errors in the logs about open files. We tried changing the global soft and hard limits on open files for the user that is running the instance without success.
I even tried doing a chown -R on the publish folder thinking that something might have changed for the permissions inside the folder. No luck. We also tried another browser thinking it might be a browser issue. Same error
I did try removing the publish directory and then running the installer again which builds the publish folder and the publisher works. Again back to thinking something in the publish folder is getting corrupted.
If we find a solution I will make sure you let you know. This is a show stopper having ramdomly failures of publish instances wow not good
Check out http://dev.day.com/docs/en/cq/5-3/deploying/upgrading_crx.html step #10. I will be testing this today. You will have to go in and check that the bundles are started. If they are not you will have to start them manually. I will let you know my results
Please give a try to remove <Cluster></Cluster> in repository.xml and hope that will resolve the issue.
But thanks for your help.
Thanks & Regards,
I saw this issue once in CQ. But in my case the below bundle was missing:
Apache Felix Configuration Admin Service (org.apache.felix.configadmin)
Due to this some other bundles were not getting started.
Please check your bundles once from the felix console.
The index is corrupt. Please try this action plan it should resolve the issue
Please try to rebuild search index.
Here are the instructions.
1) Stop the server.
2) Delete crx-quickstart/repository/repository/index
3) Delete crx-quickstart/repository/workspaces/crx.default/index
4) Start the server.
When rebuilding the search index CQ will take longer to start. However it should be back to normal when it finishes.
That should fix your issue
Still happening :s
None of the fixes posted here solve this problem.
I got it after installing a update package to CQ 5.5, found in package share.
I too faced this problem multiple times. But every time it was resolved by starting the bundles that were not started, through Apache Felix console as mentioned in your post above.