error at restore dbbackup's file

[virtual]

Hi, i cannot to restore  dbbackup's file.
Executing a command for restoring
(http://localhost:8080/atleap/rw/core/backup/restore.ru.do?org.apache.struts.taglib.html.TOKEN=f2745dea9d05b369830ed9faea38c93c&date=15.08.2008+14%3A15%3A51)

i receive a long error stack:
java.lang.RuntimeException: Cannot open index for write in D:\java\atleap-0.56\work\searchindex
        at com.blandware.atleap.search.SearchManager.getIndexWriter(SearchManager.java:975)
        at com.blandware.atleap.search.SearchManager.getIndexWriter(SearchManager.java:986)
        at com.blandware.atleap.search.SearchManager.indexPageFields(SearchManager.java:532)
        at com.blandware.atleap.search.SearchManager.indexActionPage(SearchManager.java:339)
        at com.blandware.atleap.search.SearchManager.indexPage(SearchManager.java:268)
        at com.blandware.atleap.search.SearchManager.reIndexAll(SearchManager.java:1123)
        at com.blandware.atleap.webapp.action.core.backup.RestoreActionSupport.doAfterRestore(RestoreActionSupport.java:70)
        at com.blandware.atleap.webapp.action.core.backup.RestoreAction.execute(RestoreAction.java:108)
        at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
        at com.blandware.atleap.webapp.struts.ContentTilesRequestProcessor.process(ContentTilesRequestProcessor.java:254)
        at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
        at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
...

and, yes, there are a write.lock-file in D:\java\atleap-0.56\work\searchindex.
What can be done?
Conditions: WinXP, hsqldb, tomcat6

[Jérémy Lal-3]

wipe the work/ directory
redeploy

virtual a écrit :

> Hi, i cannot to restore  dbbackup's file.
> Executing a command for restoring
> (http://localhost:8080/atleap/rw/core/backup/restore.ru.do?org.apache.struts.taglib.html.TOKEN=f2745dea9d05b369830ed9faea38c93c&date=15.08.2008+14%3A15%3A51)
>
> i receive a long error stack:
> java.lang.RuntimeException: Cannot open index for write in
> D:\java\atleap-0.56\work\searchindex
> at
> com.blandware.atleap.search.SearchManager.getIndexWriter(SearchManager.java:975)
> at
> com.blandware.atleap.search.SearchManager.getIndexWriter(SearchManager.java:986)
> at
> com.blandware.atleap.search.SearchManager.indexPageFields(SearchManager.java:532)
> at
> com.blandware.atleap.search.SearchManager.indexActionPage(SearchManager.java:339)
> at
> com.blandware.atleap.search.SearchManager.indexPage(SearchManager.java:268)
> at
> com.blandware.atleap.search.SearchManager.reIndexAll(SearchManager.java:1123)
> at
> com.blandware.atleap.webapp.action.core.backup.RestoreActionSupport.doAfterRestore(RestoreActionSupport.java:70)
> at
> com.blandware.atleap.webapp.action.core.backup.RestoreAction.execute(RestoreAction.java:108)
> at
> org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
> at
> com.blandware.atleap.webapp.struts.ContentTilesRequestProcessor.process(ContentTilesRequestProcessor.java:254)
> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
> at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
> ...
>
> and, yes, there are a write.lock-file in
> D:\java\atleap-0.56\work\searchindex.
> What can be done?
> Conditions: WinXP, hsqldb, tomcat6
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Roman Puchkovskiy-2]

Hi.

First of all, the restore process itself has completed successfully. The
problem is caused by reindex task which is called after the DB has been
restored.
Looks like Lucene is the initial source of exception. Some ideas:
1. does D:\java\atleap-0.56\work\searchindex directory actually exist?
2. isn't there a permission issue (for instance, the directory cannot be
read/written...)?
3. didn't you try stopping AtLeap and cleaning
D:\java\atleap-0.56\work\searchindex directory manually?

Our code is posting an ERROR to the log file before throwing this
exception (it's thrown in SearchManager.java:975). Could you please look
at the log file (by default, it's logs/atleap.log) and post the full
info about the exception here?

Roman Puchkovskiy

virtual writes:

> Hi, i cannot to restore  dbbackup's file.
> Executing a command for restoring
> (http://localhost:8080/atleap/rw/core/backup/restore.ru.do?org.apache.struts.taglib.html.TOKEN=f2745dea9d05b369830ed9faea38c93c&date=15.08.2008+14%3A15%3A51)
>
> i receive a long error stack:
> java.lang.RuntimeException: Cannot open index for write in
> D:\java\atleap-0.56\work\searchindex
> at
> com.blandware.atleap.search.SearchManager.getIndexWriter(SearchManager.java:975)
> at
> com.blandware.atleap.search.SearchManager.getIndexWriter(SearchManager.java:986)
> at
> com.blandware.atleap.search.SearchManager.indexPageFields(SearchManager.java:532)
> at
> com.blandware.atleap.search.SearchManager.indexActionPage(SearchManager.java:339)
> at
> com.blandware.atleap.search.SearchManager.indexPage(SearchManager.java:268)
> at
> com.blandware.atleap.search.SearchManager.reIndexAll(SearchManager.java:1123)
> at
> com.blandware.atleap.webapp.action.core.backup.RestoreActionSupport.doAfterRestore(RestoreActionSupport.java:70)
> at
> com.blandware.atleap.webapp.action.core.backup.RestoreAction.execute(RestoreAction.java:108)
> at
> org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:421)
> at
> com.blandware.atleap.webapp.struts.ContentTilesRequestProcessor.process(ContentTilesRequestProcessor.java:254)
> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1164)
> at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:397)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
> ...
>
> and, yes, there are a write.lock-file in
> D:\java\atleap-0.56\work\searchindex.
> What can be done?
> Conditions: WinXP, hsqldb, tomcat6
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[virtual]

Roman Puchkovskiy-2 wrote:

Hi.

First of all, the restore process itself has completed successfully. The
problem is caused by reindex task which is called after the DB has been
restored.
Looks like Lucene is the initial source of exception. Some ideas:
1. does D:\java\atleap-0.56\work\searchindex directory actually exist?
2. isn't there a permission issue (for instance, the directory cannot be
read/written...)?
3. didn't you try stopping AtLeap and cleaning
D:\java\atleap-0.56\work\searchindex directory manually?

Our code is posting an ERROR to the log file before throwing this
exception (it's thrown in SearchManager.java:975). Could you please look
at the log file (by default, it's logs/atleap.log) and post the full
info about the exception here?

Roman Puchkovskiy

virtual writes:
A part of big error-stack in logs/atleap.log:atleap.log
2008-08-15 17:29:16,421 INFO http-8080-1 com.blandware.atleap.service.core.impl.MailTemplateManagerImpl - Mail templates initialized
2008-08-15 17:29:20,484 INFO http-8080-1 com.blandware.atleap.webapp.util.core.ApplicationResources - Application resources synchronized
2008-08-15 17:29:20,484 INFO http-8080-1 com.blandware.atleap.webapp.util.core.CacheUtil - All cache of web layer flushed
2008-08-15 17:30:53,906 ERROR http-8080-1 com.blandware.atleap.search.SearchManager - Cannot open index for write in D:\java\atleap-0.56\work\searchindex
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@D:\java\atleap-0.56\work\searchindex\write.lock
        at org.apache.lucene.store.Lock.obtain(Lock.java:70)
        at org.apache.lucene.index.IndexWriter.init(IndexWriter.java:598)
        at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:385)
        at com.blandware.atleap.search.SearchManager.getIndexWriter(SearchManager.java:969)
        at com.blandware.atleap.search.SearchManager.getIndexWriter(SearchManager.java:986)
        at com.blandware.atleap.search.SearchManager.indexPageFields(SearchManager.java:532)
        at com.blandware.atleap.search.SearchManager.indexActionPage(SearchManager.java:339)
        at com.blandware.atleap.search.SearchManager.indexPage(SearchManager.java:268)
        at com.blandware.atleap.search.SearchManager.indexAll(SearchManager.java:1146)
        at com.blandware.atleap.search.SearchManager.initialize(SearchManager.java:1084)

Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@D:\java\atleap-0.56\work\searchindex\write.lock
        at org.apache.lucene.store.Lock.obtain(Lock.java:70)
        at org.apache.lucene.index.IndexWriter.init(IndexWriter.java:598)
        at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:385)
        at com.blandware.atleap.search.SearchManager.getIndexWriter(SearchManager.java:969)
        ... 85 more

and in the end of stack:

        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@D:\java\atleap-0.56\work\searchindex\write.lock
        at org.apache.lucene.store.Lock.obtain(Lock.java:70)
        at org.apache.lucene.index.IndexWriter.init(IndexWriter.java:598)
        at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:385)
        at com.blandware.atleap.search.SearchManager.getIndexWriter(SearchManager.java:969)
        ... 85 more

The matter is in the timing but where it is?

And another question - how to eliminate binding to directories?

D:\java\atleap-0.56\ - for developing. But after deploying i think  there shouldn't be any binding at the provider's server.
Thank you for quick reaction.

> Conditions: WinXP, hsqldb, tomcat6
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]