Thread running by long time

[Fernando dos Santos Garcia]

Dear Fidel,

We are starting with JIRA, and have JIRA Server installed in Amazon AWS that are using the JIRA Workflow Toolbox plugin and it's good, but we have performance problems.

Monitoring Server, we detected several "threads" launched by the Workflow Toolbox plugin and they are running for long time. This is killing our server.

Details:

JIRA Version: 6.4.5 WorkFlow Toolbox Version: 2.1.36

--------------------------------- LOG Server ---------------------------------------------

"http-bio-80-exec-320" #17647 daemon prio=5 os_prio=0 tid=0x00007f85ac22c000 nid=0x60d5 runnable [0x00007f84da957000] java.lang.Thread.State: RUNNABLE at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:153) at java.lang.StringCoding.decode(StringCoding.java:193) at java.lang.String.<init>(String.java:414) at org.apache.lucene.store.DataInput.readString(DataInput.java:182) at org.apache.lucene.index.FieldsReader.addField(FieldsReader.java:431) at org.apache.lucene.index.FieldsReader.doc(FieldsReader.java:261) at org.apache.lucene.index.SegmentReader.document(SegmentReader.java:471) at org.apache.lucene.index.DirectoryReader.document(DirectoryReader.java:564) at org.apache.lucene.index.IndexReader.document(IndexReader.java:844) at org.apache.lucene.search.IndexSearcher.doc(IndexSearcher.java:242) at com.atlassian.jira.index.DelegateSearcher.doc(DelegateSearcher.java:93) at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.search(LuceneSearchProvider.java:434) at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.search(LuceneSearchProvider.java:98) at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.search(LuceneSearchProvider.java:87) at com.atlassian.jira.bc.issue.search.DefaultSearchService.search(DefaultSearchService.java:117) at sun.reflect.GeneratedMethodAccessor2216.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:134) at com.sun.proxy.$Proxy429.search(Unknown Source) at sun.reflect.GeneratedMethodAccessor2216.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154) at com.sun.proxy.$Proxy429.search(Unknown Source) at com.fca.jira.plugins.workflowToolbox.JQLCondition.passesCondition(JQLCondition.java:84)

---

Sincerely,

Fernando Garcia Betha Sistemas Ltda Brazil [e-mail]

[Fidel Castro Armario]

Hi Fernando,

Versions 2.1.33 and 2.1.34 implemented delayed issue transition using a thread for each issue being transitioned, but since 2.1.35 uses only one thread for all the issues that need to be transitioned.

It also uses a different thread to reindexing the issues once transitioned.

None of these 2 threads live more that the time needed to transition and reindex the issues.

Version 2.1.35 has notably improved performance with respect to version 2.1.33 and 2.1.34.

Anyway, in the log file you show in the description of this issue I don't see any o those 2 threads.

I need the following information in order to diagnose your problem:

• Your server's whole log file, in order to investigate which threads are being created and how long do they live.
• Which features of the plugin are you mainly using: delayed transition, immediate transition, boolean validators, etc.

Regards,

Fidel

[Fidel Castro Armario]

Fernando, can you provide the information I asked you for in a former post? It's required to investigate the problem.

[Fidel Castro Armario]

After almost 2 months without the information required to investigate the problem, I close the issue. Please, reopen it if you keep needing support about this issue.