Details
-
Support Request
-
Resolution: Fixed
-
Highest
-
None
-
3.2.1
Description
We plan to implement Jira in our company and for this we must prove that regular updates from our old issue tracking system are possible. For this I am writing a Jira service that should get all the issues that have changed in the old system and create/update the issues in Jira.
For the update I have to check whether an issue has already been imported or not, thus I need to search a Jira issue by a custom field value. I use the code proposed in JRA-7031but then the service crashes when I re-index all bugs after the import.
The simplest code (not very functional ) to demonstrate this behavior:
public void run() {
SearchRequest sr = new SearchRequest(true); // search without security checks
sr.addParameter(new ProjectParameter(new Long(10001))); // id of existing project
try
catch (Exception e)
{ // ignore }}
This leads to the following problem:
[INFO] Http11Protocol - -Initialisation de Coyote HTTP/1.1 sur le port 8080
DTmarrage du service Tomcat-Standalone
Apache Tomcat/4.1.29
[INFO] RAMJobStore - RAMJobStore initialized.
[INFO] StdSchedulerFactory - Quartz scheduler 'JiraQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
[INFO] StdSchedulerFactory - Quartz scheduler version: 1.4.5
2005-06-21 19:34:52,482 INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Starting JIRA Enterprise Edition, Version: 3.2-#89
2005-06-21 19:34:52,482 INFO [atlassian.jira.upgrade.ConsistencyCheckImpl] Configured to use database: hsql
[INFO] QuartzScheduler - Scheduler JiraQuartzScheduler_$_NON_CLUSTERED started.
[Filter: profiling] Using parameter [jira_profile]
[Filter: profiling] defaulting to off [autostart=false]
[Filter: profiling] Turning filter off [jira_profile=off]
[WARN] ServletDispatcher - Unable to find 'webwork.multipart.saveDir' property setting. Defaulting to javax.servlet.context.tempdir
[INFO] ServletDispatcher - Action dispatcher initialized
[INFO] Http11Protocol - -DTmarrage de Coyote HTTP/1.1 sur le port 8080
2005-06-21 19:34:55,420 INFO [sims.jira.service.WatsonUpdateService] started 1
[ERROR] LuceneUtils - Problem with path D:\atlassian-jira-enterprise-3.2-standalone\index/issues: Cannot delete _1.cfs <
java.io.IOException: Cannot delete _1.cfs>java.io.IOException: Cannot delete _1.cfs
at org.apache.lucene.store.FSDirectory.create(FSDirectory.java:144)
at org.apache.lucene.store.FSDirectory.getDirectory(FSDirectory.java:105)
at org.apache.lucene.store.FSDirectory.getDirectory(FSDirectory.java:83)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:173)
at com.atlassian.jira.util.LuceneUtils.getIndexWriter(LuceneUtils.java:46)
at com.atlassian.jira.issue.index.DefaultIndexManager.getIndexWriter(DefaultIndexManager.java:556)
at com.atlassian.jira.issue.index.DefaultIndexManager.indexIssuesAndComments(DefaultIndexManager.java:275)
at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:245)
at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexAll(DefaultIndexManager.java:185)
at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexAll(DefaultIndexManager.java:137)
at com.sims.jira.service.WatsonUpdateService.run(WatsonUpdateService.java:176)
at com.atlassian.jira.service.JiraServiceContainer.run(JiraServiceContainer.java:59)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:50)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)
2005-06-21 19:34:55,904 ERROR [jira.issue.index.DefaultIndexManager] !!! issueWriter was null - bad !!!
Any ideas why I cannot search issues and the reIndex the database?!?