JWT hangs up

[Andrey Kiyanovsky]

Hi Fidel,

I have a workflow assigned to standard issue type. Accidently I was using Parent's field in post-functions. It was saved for the firs time, but now I can't open this transition - JIRA and JWT hang up (page is not displayed) with the following log records:

2016-04-11 10:17:55,286 ajp-apr-8009-exec-46 ERROR andreyki 617x398912x1 s9d4ft 193.111.60.7 /secure/WorkflowUIDispatcher.jspa [plugins.workflowToolbox.shared.GeneralizedField] #*** OPT ION FOR Parent's Deployed:

[Andrey Kiyanovsky]

I tried to re-assign this workflow to subtask issue type only, but it didn't help. BTW, this is a global reflexive transition.

[Andrey Kiyanovsky]

The page keeps loading without any response, Chrome shows "waiting for .. JIRA URL...".

[Andrey Kiyanovsky]

I had to export the workflow, cut off the following code and import, now it works, here is the code where it hangs up:

Set a field as a function of other fields

[%{00067} != "" and {00058} != 0 and {00059} = 0 and {00060} = 0]Open

[%{00067} != "" and {00059} != 0 and {00060} = 0 and {00064} = 0]To Do

[%{00067} != "" and ({00059} != 0 or ({00058} != 0 and {00064} != 0))]In Progress

a[%{00067} != "" and {00058} = 0 and {00059} = 0 and {00060} = 0 and {00064} != 0 and indexOf(availableItems(%{12902}, %{00061}),%{00062}) != count(availableItems%{12902}, %{00061})]first(availableItems(%{12901},nthElement(availableItems(%{12902}, %{00061}),indexOf(availableItems(%{12902}, %{00061}),%{00062})+1)))

It's strange, I can't see parent's fields here.

[Andrey Kiyanovsky]

Just checked CFs scope - they are assigned to all issue types, link.

[Andrey Kiyanovsky]

I've just looked through all the exported XML and did not find a field with the code 51400 (Parent's Deployed CF). I don't have a clue why it throw error for "Parent's Deployed" field.

[Fidel Castro Armario]

Hi Andrey,

Can you, please, send the whole log file to [e-mail]?

Thanks.

[Andrey Kiyanovsky]

I've just checked the log, this error message is not connected to this bug! It hangs up without error messages.

[Fidel Castro Armario]

Can you, please, send me the XML file of the falling workflow?

[Andrey Kiyanovsky]

Sent

[Andrey Kiyanovsky]

If you could shed light on this error message too, it'd be helpful.

[Andrey Kiyanovsky]

BTW, I'm using JWT 2.2.10_beta_2 with the new availableItems function, where it most likely hangs.

[Fidel Castro Armario]

Andrey, the XML file you attached doesn't contain post-function "Set field as a function of other fields" that was causing the problem. I think that you attached the workflow once you has removed the failing post-funcion. I need the original XML file if you still have it.

A pair of questions:

• Which version of JIRA are you using?
• Can you attach a screenshot with the configuration of file %{12902}? I would like to see the different options available in this field.

[Andrey Kiyanovsky]

Fidel,

1. You are right, it was edited XML, failing XML (2.0) is attached (post-function Update).
2. CF 12902
3. JIRA version v6.4.11.

[Fidel Castro Armario]

Hi Andrey,

I have released version 2.2.10_beta_3 fixing the problem, that was caused by a problem in the parser linked to function "indexOf()".

I advise to restart the JIRA servers affected by the problem, since there might be threads alive wasting CPU time due to infinite loops.

This fix also improves performance in expressions using indexOf() function.

By the way, your last setting rule wasn't correctly formed. Use the following one:

a[%{00067} != "" and {00058} = 0 and {00059} = 0 and {00060} = 0 and {00064} != 0 and indexOf(%{00062}, availableItems(%{12902}, %{00061})) != count(availableItems(%{12902}, %{00061}))]first(availableItems(%{12901}, nthElement(availableItems(%{12902}, %{00061}), indexOf(%{00062}, availableItems(%{12902}, %{00061}))+1)))

[Andrey Kiyanovsky]

Thanks a lot for such a prompt fix, Fidel! I'll check and let you know.

[Andrey Kiyanovsky]

It works, Fidel, thank you!

Do you any ideas regarding error message? What can it be related to?

[Fidel Castro Armario]

Hi Andrey,

The error message has been removed. It was a introduced for tracing purpose during development, and I forgot to remove it.

[Fidel Castro Armario]

Fixed in just released version 2.2.10.