Unable to create a new writer (write.lock)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: No Longer Reproducible
• Affects Version/s: 5.2.3
• Fix Version/s: --Sprint 12/11, 6.1.0 CE RC1
• Component/s: Frameworks > Search
• Labels: None
• Environment: Ubuntu 8.04, tomcat 6, LR 5.2.3
• Branch Version/s:
  5.2.x
• Similar Issues: Show 5 results ; ;

  LPS-19712	Unable to create a new organization
  LPS-24569	unable to create new portal instance
  LPS-8654	Lazy create StringServletResponse's inner Writer and OutputStream
  LPS-31324	Unable to create a new bookmark entry
  LPS-8479	StringServletResponse should reset the inner writer on recycling rather than creating a new one

ERROR [IndexWriterFactory:210] Unable to create a new writer
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: PhantomReadLock[write.lock/LUCENE_0]

In the table there is a registry wich name_ column is "write.lock", but I don't know why.

I delete the registry write.lock and reindex, reindex again but keep a record write.lock.

Thanks.

[Andy Chia]

you can set lockType=simple and unlockOnStartup=true;
also you can try to delete all index data before you reindex;

[Cynthia Wilburn]

Robert - Did Andy's suggestion provide a suitable solution for you? If not, are you able to download and reproduce this problem with 6.0.5 CE? We are doing some housekeeping and would like to update the affected version for this ticket if necessary. If you are unable to verify this in 6.0.5 CE yourself, might I suggest going to the community forums and seeing if another community member can help verify the problem? If it is still ongoing in 6.0.5 CE, we can prioritize it and you could potentially patch a fix from trunk to 5.2.3. In the meantime, I will keep this open to see if we can get some more input and check back.

Thanks again!

Cynthia

*Please see our updated wiki on reporting issues in JIRA if you need more detailed information:
http://www.liferay.com/community/wiki/-/wiki/1071674/JIRA/

[Mika Koivisto]

Please note that only one writer can get a write lock to lucene indices. If you are sharing the indices with several liferay instances only one can write and the other nodes must be read only.