History | Log In     View a printable version of the current page.  
   HOME       BROWSE PROJECT       FIND ISSUES       PLANNING BOARD       TASK BOARD   
    QUICK SEARCH:  
Issue Details (XML | Word | Printable)

Key: JRA-8188
Type: Third-party issue Third-party issue
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Jeff Turner [Atlassian]
Reporter: Jeff Turner [Atlassian]
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JIRA

NullPointerException when setting up indexing (lock directory permission problems)

Created: 10/Oct/05 02:06 AM   Updated: 14/Sep/07 01:09 AM
Component/s: None
Affects Version/s: 3.3, 3.3.1, 3.3.2
Fix Version/s: 3.3.3

Time Tracking:
Not Specified

Environment: JIRA Standalone 3.3.x
Issue Links:
Reference
 

Participants: Abhishek Tripathi, Anton Mazkovoi [Atlassian], Jason Schroeder, Jeff Turner [Atlassian] and Neal Applebaum
Since last comment: 44 weeks, 1 day ago
Resolution Date: 11/Oct/05 08:12 PM
Labels:


 Description  « Hide
People are reporting that indexing is failing in the setup wizard and when reindexing, with the error:

"Could not activate indexing: Error: java.lang.NullPointerException"

In the logs, one sees:

2005-10-07 16:35:49,128 ERROR [jira.issue.index.DefaultIndexManager] !!! issueWriter was null - bad !!!
2005-10-07 16:35:49,128 ERROR [web.action.setup.Setup] Error activating indexing: com.atlassian.jira.issue.index.IndexException: Error: java.lang.NullPointerException
com.atlassian.jira.issue.index.IndexException: Error: java.lang.NullPointerException
at com.atlassian.jira.issue.index.DefaultIndexManager.indexIssuesAndComments(DefaultIndexManager.java:298)
at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:249)
at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexAll(DefaultIndexManager.java:189)
at com.atlassian.jira.issue.index.DefaultIndexManager.activate(DefaultIndexManager.java:124)
at com.atlassian.jira.web.action.setup.Setup.doExecute(Setup.java:308)
at webwork.action.ActionSupport.execute(ActionSupport.java:153)
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:47)
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132)
...
...
Caused by: java.lang.NullPointerException
at org.apache.lucene.store.FSDirectory.create(FSDirectory.java:149)
at org.apache.lucene.store.FSDirectory.<init>(FSDirectory.java:128)
at org.apache.lucene.store.FSDirectory.getDirectory(FSDirectory.java:102)
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:560)
at com.atlassian.jira.issue.index.DefaultIndexManager.indexIssuesAndComments(DefaultIndexManager.java:279)

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Jeff Turner [Atlassian] - 10/Oct/05 02:09 AM
This problem occurs when the temporary directory, which Lucene uses to create locks in, is not readable. In JIRA Standalone (bundled Tomcat), the temporary directory is temp\ in the root.

Better debugging from Lucene would help - see http://issues.apache.org/jira/browse/LUCENE-449


[ Permlink | « Hide ]
Jeff Turner [Atlassian] - 11/Oct/05 07:30 PM
This problem occurs when someone on Windows downloads the .tar.gz distribution and unpacks with WinZIP. Because the temp\ directory is empty in the distribution, WinZIP decides it is unnecessary and does not create it.

[ Permlink | « Hide ]
Jeff Turner [Atlassian] - 11/Oct/05 08:12 PM
Fixed by adding a dummy file in temp\ so it isn't empty.

Is there a wider problem though? Why are Windows people using the .tar.gz instead of the .zip? We had a report that the .zip is broken - is this true?


[ Permlink | « Hide ]
Jeff Turner [Atlassian] - 20/Oct/05 02:36 AM
WinZIP 9 does not extract the empty temp\ directory. WinZIP 8 does.

[ Permlink | « Hide ]
Neal Applebaum - 31/Oct/05 07:22 AM
I definitely unpacked the .ZIP version and not the tar.gz version when I experienced this error.
Using WinZip version 9.0 SR-1 (6224)

[ Permlink | « Hide ]
Anton Mazkovoi [Atlassian] - 31/Oct/05 04:19 PM
You are right, 9.0 SR-1 version of WinZip has the same problem with .zip file as with .tar.gz. This all should be fixed in JIRA 3.3.3.java -jar release/jira-soapclient-3.4-beta1-2.jar

[ Permlink | « Hide ]
Jason Schroeder - 01/Feb/06 11:44 PM
This problem manifests itself when the temp directory is pressent and the Unix owner/permissions of the directory make the directory unavailable to the tomcat process.

Please add some idiot processing at the server startup verifying that temp, work and logs are open for writing. This is not simply a zip-related problem.


[ Permlink | « Hide ]
Abhishek Tripathi - 13/Sep/07 11:40 AM
Hi Jeff,
I'm using JIRA 3.6.5.
When ever there is Jira outage, I find below error in the log file.

1)2007-09-13 16:06:55,287 ERROR [jira.issue.index.DefaultIndexManager] Giving up reindex - waited 30000 seconds
com.atlassian.jira.issue.index.IndexException
at com.atlassian.jira.issue.index.DefaultIndexManager.getIndexLock(DefaultIndexManager.java:545)
at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:300)
at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:272)
at com.atlassian.jira.issue.index.DefaultIndexManager.reIndex(DefaultIndexManager.java:462)
at com.atlassian.jira.event.listeners.search.IssueIndexListener.reIndex(IssueIndexListener.java:109)
at com.atlassian.jira.event.listeners.search.IssueIndexListener.reIndex(IssueIndexListener.java:119)
at com.atlassian.jira.event.listeners.search.IssueIndexListener.issueCommented(IssueIndexListener.java:75)
at com.atlassian.jira.event.issue.AbstractIssueEventListener.workflowEvent(AbstractIssueEventListener.java:106)
at com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:105)
at com.atlassian.jira.event.issue.IssueEventDispatcher.dispatchEvent(IssueEventDispatcher.java:80)
at com.atlassian.jira.web.action.issue.AddComment.alertSystemOfComment(AddComment.java:99)
at com.atlassian.jira.web.action.issue.AddComment.doExecute(AddComment.java:83)
at webwork.action.ActionSupport.execute(ActionSupport.java:153)
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:57)
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132)
at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:185)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)

2)2007-09-13 16:06:02,725 ERROR [atlassian.jira.workflow.SimpleWorkflowManager] An exception occurred
com.opensymphony.workflow.InvalidActionException: Action 4 is invalid
at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:528)
at com.atlassian.jira.workflow.SimpleWorkflowManager.doWorkflowAction(SimpleWorkflowManager.java:253)
at com.atlassian.jira.workflow.WorkflowTransitionUtilImpl.progress(WorkflowTransitionUtilImpl.java:271)
at com.atlassian.jira.web.action.workflow.SimpleWorkflowAction.doExecute(SimpleWorkflowAction.java:34)

3)13-Sep-2007 16:05:20 org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
2007-09-13 16:05:26,475 ERROR [[Catalina].[localhost].[/].[quicklink]] Servlet.service() for servlet quicklink threw exception
java.lang.OutOfMemoryError
2007-09-13 16:05:31,757 ERROR [webwork.util.ServletValueStack] METHOD: "unescapedText", exception:
java.lang.OutOfMemoryError
2007-09-13 16:05:31,757 ERROR [webwork.util.ServletValueStack] METHOD: "unescapedText", exception:
java.lang.OutOfMemoryError
2007-09-13 16:05:37,069 ERROR [[Catalina].[localhost].[/].[jsp]] Servlet.service() for servlet jsp threw exception

4)
2007-09-12 16:04:44,935 WARN [velocity] Warning! The iterative is an Iterator in the #foreach() loop at [0,0] in template templates/pivotreport/pivot-report.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.
2007-09-12 16:04:44,951 WARN [velocity] Warning! The iterative is an Iterator in the #foreach() loop at [0,0] in template templates/pivotreport/pivot-report.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.
2007-09-12 16:04:44,951 WARN [velocity] Warning! The iterative is an Iterator in the #foreach() loop at [0,0] in template templates/pivotreport/pivot-report.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.

it's a critical issue.
please advice what should do.

Regards,


[ Permlink | « Hide ]
Anton Mazkovoi [Atlassian] - 14/Sep/07 01:09 AM
Hi Abhishek,

Please create a support request in our support system:
http://support.atlassian.com
describe the problem and please attach all of your log files. The log files will be absolutely required to determine the cause of the problem.

Cheers,
Anton
Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.12.3-#302) - Bug/feature request - Atlassian news - Contact Administrators