JIRA Workflow Toolbox crash

[Дмитрий Ольхов]

Hello!

We have an issue with plugin JIRA Workflow Toolbox ver. 2.2.40 on JIRA 6.4.5 in test environment.

We do load tests with HP LR. During the test number of virtual users is growing. Total number is not above 50. There are fault cases with different number of active virtual users. Suddenly, test crashes because of functional error. I mean somewhere in postfunctions… Now I can’t do the same operation even manualy.

Then, I only delete the plugin and install it again (stop/start doesn’t help). And it helps. Everything works fine…. till the next time.

Please help to resolve this problem. May be there are special keys to collect some debug information for you.

[Fidel Castro Armario]

Hi @olhd,

Thanks for reporting the error. Please, try version 2.2.42_beta_4, and let me know whether it solves the problem.

Thanks,

Fidel

[Fidel Castro Armario]

Hi @olhd,

Did you try the beta version?

[Дмитрий Ольхов]

Hi! Plugin works and didn't crash. Now test continues till JIRA out of memory error. I'm not sure that this is because of plugin. Any way, can you recommend some way to research this issue? Thank you!

[Fidel Castro Armario]

You can send to [e-mail] a support zip. You can generate it at Administration > System > Support Tools.

I think that you should ask for support at Atlassian.

[Дмитрий Ольхов]

... and we have many selectissue.plugin.util.CustomFieldUtils Nullpointer exceptions in log now

[Дмитрий Ольхов]

you mean i need generate zip just after test?

[Fidel Castro Armario]

Hi @olhd,

I have found many GenericDataSourceException in your log file. Some examples are:

Target exception: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, LINKNAME, INWARD, OUTWARD, pstyle FROM issuelinktype (Нарушение протокола)

and

2017-08-31 15:06:00,240 atlassian-scheduler-quartz1.local_Worker-2 ERROR ServiceRunner     [org.quartz.core.ErrorLogger] Job (SchedulerServiceJobs.com.atlassian.jira.service.DefaultServiceManager threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT DISTINCT ID FROM rundetails WHERE JOB_ID=? (Нарушение протокола)]
    at org.quartz.core.JobRunShell.run(JobRunShell.java:234)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Caused by: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT DISTINCT ID FROM rundetails WHERE JOB_ID=? (Нарушение протокола)

There are also some DataAccessException. Examples:

2017-08-31 15:06:00,251 http-bio-8080-exec-602 ERROR usertest6 905x1699223x1 rnwg8v 10.85.45.50 /secure/QuickCreateIssue.jspa [innovalog.jmcf.fields.CalculatedTextField] CalculatedTextField: error evaluating formula of field "Заказчик из основания" of issue ASJIRA1-18733: 
Sourced file: inline evaluation of: ``  import com.atlassian.jira.component.ComponentAccessor;  import com.atlassian.j . . . '' : Method Invocation searchService.search : at Line: 19 : in file: inline evaluation of: ``  import com.atlassian.jira.component.ComponentAccessor;  import com.atlassian.j . . . '' : searchService .search ( jiraUser , parsingResult .getQuery ( ) , PagerFilter .getUnlimitedFilter ( ) ) 
Target exception: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, LINKNAME, INWARD, OUTWARD, pstyle FROM issuelinktype (Нарушение протокола)

Please, do the following checkings in your JIRA instance:

1. Integrity Checking: Administration > System > Integrity checker
2. Instance Health: Administration > System > Support Tools > Instance Health

Please, let me know if you find any problem in your JIRA instance.

[Fidel Castro Armario]

Fixed the initial problem you described in just released version 2.2.42.

Please, do the checks I described in my previous post.