Issues are not getting updated

Susweta Sarkar March 15, 2018

Hi Team,

When ever a new issue is created or deleted it is not getting updated in the dashboard. Initially post indexing everything used to get updated. However, now we are receiving the following issues:
We have even replaced the plugins also, post which only for some days it works fine. 

java.lang.IllegalMonitorStateException
at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(ReentrantLock.java:127)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1239)
at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:431)
at com.atlassian.jira.util.LuceneUtils$UtilConcurrentLock.release(LuceneUtils.java:260)
at org.apache.lucene.index.IndexWriter.unlock(IndexWriter.java:5739)
at com.atlassian.jira.index.WriterWrapper.clearWriteLock(WriterWrapper.java:124)
at com.atlassian.jira.index.WriterOutOfMemory$2.handle(WriterOutOfMemory.java:45)
at com.atlassian.jira.index.WriterOutOfMemory.addDocuments(WriterOutOfMemory.java:69)
at com.atlassian.jira.index.Operations$Create.perform(Operations.java:125)
at com.atlassian.jira.index.Operations$Completion.perform(Operations.java:196)
at com.atlassian.jira.index.DefaultIndexEngine$FlushPolicy.perform(DefaultIndexEngine.java:74)
at com.atlassian.jira.index.DefaultIndexEngine.write(DefaultIndexEngine.java:151)
at com.atlassian.jira.index.DefaultIndex.perform(DefaultIndex.java:34)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$IndexIssuesOperation.perform(DefaultIssueIndexer.java:377)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$4$1.get(DefaultIssueIndexer.java:257)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$4$1.get(DefaultIssueIndexer.java:253)
at com.atlassian.jira.index.SimpleIndexingStrategy.get(SimpleIndexingStrategy.java:9)
at com.atlassian.jira.index.SimpleIndexingStrategy.get(SimpleIndexingStrategy.java:5)
at com.atlassian.jira.index.MultiThreadedIndexingStrategy$1.call(MultiThreadedIndexingStrategy.java:39)
at com.atlassian.jira.index.MultiThreadedIndexingStrategy$1.call(MultiThreadedIndexingStrategy.java:36)
at com.atlassian.jira.util.concurrent.BoundedExecutor$2.call(BoundedExecutor.java:70)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForTenant(DefaultMultiTenantManager.java:61)
at com.atlassian.multitenant.juc.MultiTenantExecutors$WrappedRunnable.run(MultiTenantExecutors.java:160)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

Kindly suggest

1 comment

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 15, 2018

Your server is running out of memory when you update issues.

You need to increase the heap size for Jira's Tomcat.

Susweta Sarkar March 15, 2018

Hi Nic,

We have already increased the memory to 1024 MB and still we are facing the same issue. Till what value can we increase the memory size. Please find below the screen shots for your reference.

20180316-113646(eSpace).png20180316-113655(eSpace).png

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 16, 2018

1024m is good for a small low use system, up to 25 users and a few thousand issues in a couple of projects.  If you're bigger than that, then increase the memory to the recommended size for your site (see https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html )

If the error persists, then you've got a broken add-on or function configured.

Susweta Sarkar March 19, 2018

Hi Nic,

Requesting for your support:

For memory problem we have changed 32 bit machine to 64 bit machine. However, now whatever we installed in C drive is missing. Hence, SQL database is missing now.

Is there any solution for getting data back from jira as we not able to see any of the old projects in JIRA.

We do have the JIRA folder in D drive so we can see some zip files in this path ->D:\ICP JIRA2\Atlassian\Application Data\JIRA\export. But while importing we are getting an error. Please find below the screenshots:

20180320-115325(eSpace) 1.png20180320-120153(eSpace) 3.png

Susweta Sarkar March 19, 2018

20180320-115347(eSpace) 2.pngThese are the errors, kindly help.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events