SimpelFSLock

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
3/22/2011 6:31:17 AM
Gravatar
Total Posts 31

SimpelFSLock

Hi,

I made a new site menu in mojoportal because I wanted some extra features.
Everything worked fine until I added a feature that allows me to set a minimum level and a maximum level.

Now the page loads forever, and if I look in the system log I see that I get a SimpelFsLock every second.

I have a local installation and a server installation of mojoportal. One time I copied the whole local version to the server. and now I see a path in the server log that goes to a file on the local installation but this doesn't exists on the server.

2011-03-22 12:23:52,012 ERROR mojoPortal.Business.WebHelpers.IndexWriterTask - System.IO.IOException: Lock obtain timed out: SimpleFSLock@C:\DATA\maakthetsimpel.nu\httpdocs\Data\Sites\21\index\write.lock
   at Lucene.Net.Store.Lock.Obtain(Int64 lockWaitTimeout)
   at Lucene.Net.Index.IndexReader.AquireWriteLock()
   at Lucene.Net.Index.IndexReader.DeleteDocument(Int32 docNum)
   at Lucene.Net.Index.IndexReader.DeleteDocuments(Term term)
   at mojoPortal.Business.WebHelpers.IndexWriterTask.ProcessQueue(DataTable q, String indexPath) in C:\Users\Laurence\Documents\Visual Studio 2010\Projects\Websignaal\mojoportal.mssqlonly\mojoPortal.Business.WebHelpers\Search\IndexWriterTask.cs:line 173

C:\DATA\maakthetsimpel.nu\httpdocs\Data\Sites\21\index\write.lock
is a file on the server installation.

C:\Users\Laurence\Documents\Visual Studio 2010\Projects\Websignaal\mojoportal.mssqlonly\mojoPortal.Business.WebHelpers\Search\IndexWriterTask.cs:line 173
is a file of my local installation.

Kind regards,

Laurence Mommers

 


 

3/22/2011 12:30:46 PM
Gravatar
Total Posts 18439

Re: SimpelFSLock

sounds like you are connecting to your server database from your local machine, so when you edit content from your local machine it stores the local path in the mp_IndexingQueue table when it serializes items for processing into the search index.

You should not connect to your server db and edit content from your local machine because it will cause problems like this. You should make a backup of your server db and restore it on your local machine for dev/testing.

You probably need to rebuild the search index and you may need to manually clear the mp_IndexingQueue table.

Hope it helps,

Joe

3/22/2011 12:38:02 PM
Gravatar
Total Posts 31

Re: SimpelFSLock

Hi,

I've check my connection strings one more time but, the server version and my local version are using 2 separated databases

Kind regards,

Laurence Mommers
 

3/22/2011 12:41:31 PM
Gravatar
Total Posts 18439

Re: SimpelFSLock

The only way that local path got serialized into the mp_IndexingQueue is if you were connected to it from your local machine. Possibly you restored the db on the server after editing content locally and there were rows created in the table before you restored it.

In any case clearing out that table and rebuilding the index should solve it.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.