Exception: Lucene.Net.Store.AlreadyClosedException: this IndexReader is closed
Hello
We are having the "Exception: Lucene.Net.Store.AlreadyClosedException: this IndexReader is closed" message very often. The page is only getting info from "Media" and displaying docs.
Anyone has any idea why?
In Umbraco 7, when you are retrieving details of Media programmatically, it's actually using the Internal Examine Search Index, to speed things up.
So it sounds like there maybe a problem with your InternalIndex being unbuilt or locked - and this might be to do with how the site is being hosted and whether you have the write settings for Examine and Temporary storage for the type of hosting you are using.
Normally in these circumstances recycling the app pool of the site (Examine works on a background thread so needs the app pool to be restarted, you can't just stop the website!) and then rebuilding the InternalIndex will resolve the issue but...
... if you are hosting the site in a cloud provider such as Azure Web App then there are specific configuration settings to make for Examine to avoid the indexes being locked when the underlying 'worker' fails over to use another server in the cloud, and confusingly these settings are different for different versions of V7.
Many thanks for your reply.
It is exactly as you mentioned the InternalIndex is locked or something and we need to restart the app pool. But this is happening rather frequently and affecting the site's performance.
Note that the website is not on Cloud, it is on 2 VMs. One for the web and one for SQL.
Do you have any idea how we can resolve this issue?
Exception: Lucene.Net.Store.AlreadyClosedException: this IndexReader is closed
Hello
We are having the "Exception: Lucene.Net.Store.AlreadyClosedException: this IndexReader is closed" message very often. The page is only getting info from "Media" and displaying docs. Anyone has any idea why?
Thanks
Hi aaeda
In Umbraco 7, when you are retrieving details of Media programmatically, it's actually using the Internal Examine Search Index, to speed things up.
So it sounds like there maybe a problem with your InternalIndex being unbuilt or locked - and this might be to do with how the site is being hosted and whether you have the write settings for Examine and Temporary storage for the type of hosting you are using.
Normally in these circumstances recycling the app pool of the site (Examine works on a background thread so needs the app pool to be restarted, you can't just stop the website!) and then rebuilding the InternalIndex will resolve the issue but...
... if you are hosting the site in a cloud provider such as Azure Web App then there are specific configuration settings to make for Examine to avoid the indexes being locked when the underlying 'worker' fails over to use another server in the cloud, and confusingly these settings are different for different versions of V7.
There is a document here that kind of explains:
https://our.umbraco.com/Documentation/Fundamentals/Setup/Server-Setup/azure-web-apps-v7
regards
Marc
Hello Marc
Many thanks for your reply. It is exactly as you mentioned the InternalIndex is locked or something and we need to restart the app pool. But this is happening rather frequently and affecting the site's performance. Note that the website is not on Cloud, it is on 2 VMs. One for the web and one for SQL. Do you have any idea how we can resolve this issue?
Thanks Regards A
Hello
The error below is also recurrent:
Umbraco.Core.UmbracoApplicationBase - Application shutdown. Details: HostingEnvironment
_shutDownMessage=HostingEnvironment initiated shutdown HostingEnvironment caused shutdown
Can you please help?
Thanks A
is working on a reply...