Gets Block the server while doing transition

Issue #508 resolved
rTrack Support created an issue

Hi Fidel , I face the issue mostly doing the transitions . I attached the workflow as xml also . Queue 1 :ES SINGLE QUEUE DEMO WORKFLOW Queue 2 :ES BASE QUEUE WORKFLOW FROM THE QUEUE TWO I PUT THE STATUS AS PENDING CLARIFICATION . IF I PUT PC THEN IN THE QUEUE ONE Clarified and Reopen option will be enable . IN THAT I WILL CHANGE THE PENDING WITH FIELD AND DO THE TRASITION . This needs to get reflected on the other queue .That is queue b as clarified and reopen .

I have attached the log file too .

while doing the transition 281 only it gets blocked . Please check this .

Comments (56)

  1. rTrack Support reporter

    if you need any other clarification please let me know . its urgent .i have to complete the task by today ..

  2. Fidel Castro Armario repo owner


    The problems has relation with a Calculated Number Field which is using function timesOfTransition(). How many of these fields do you have using that function? Please, attach screenshots of the configurations (i.e., math expressions) of these fields.

    The problem occurs when trying to index issue DS-63 on 'customfield_20460'. Please, tell me:

    1. The custom field type of field with code 20460.
    2. Which value has that field on issue DS-63?
    3. Is the history of that issue very long?

    Please, do a full reindex of your JIRA instance: Adminsitration > System > Indexing.

  3. rTrack Support reporter

    Hi , Field name :Times of Reopen Count Math / Numeric Expression :count(timesOfTransition("Pending", "In Progress"))

  4. rTrack Support reporter

    I done the reindexing two days back only . It is production envronment only . I cant reindex everyday due to number of projects in higher count .

  5. Fidel Castro Armario repo owner
    1. Which is the custom field type of field with code 20460?
    2. Which value has that field on issue DS-63?
  6. Fidel Castro Armario repo owner

    I'm trying to reproduce the problem without success. It might be related with a bug in JIRA itself. I suggest you to remove the calculated field and use a Number custom field instead, and to give value to it using a post-function. This is the alternative solution step by step:

    1. Remove field Times of Reopen Count.
    2. Create a Number custom field with the same name. Set default value to zero.
    3. Add "Mathematical and date-time expression calculator" post-function to transition from Pending to In Progress status with the following configuration:

    4. Target field: the Number field called Times of Reopen Count.

    5. Formula:
    {nnnnn} + 1

    replacing nnnnn with field code of the Number field called Times of Reopen Count.

  7. Fidel Castro Armario repo owner

    I'm not able to reproduce the problem. In my case the calculated number field works as expected.

    In your case, is it also failing in test environment?

  8. rTrack Support reporter

    This issue is not occuring all of the time . Some time only it gets down the process of the server .

  9. rTrack Support reporter

    I have checked this to simulate once again . Suspended query in the sql (blocked by ) (@P0 nvarchar(4000),@P1 bigint,@P2 nvarchar(4000))SELECT ID, ENTITY_NAME, ENTITY_ID, PROPERTY_KEY, CREATED, UPDATED, json_value FROM dbo.entity_property WHERE ENTITY_NAME= @P0 AND ENTITY_ID= @P1 AND PROPERTY_KEY= @P2

  10. Fidel Castro Armario repo owner

    It seems to be a bug of JIRA, since the plugin uses the API and never execute SQL queries directly to the DB.

    I recommend you to implement the alternative solution based on Number custom field and "Mathematical and date-time expression calculator" post-function.

    I'm investigating the problem, but since you are pressed to have the system working today, the better option for you is to use the alternative solution.

  11. rTrack Support reporter

    Any how i removed that math expression for that custom field .After that also it results with suspended process .

  12. Fidel Castro Armario repo owner

    Maybe you have more than one Calculated Number Field using function timesOfTransition(). Is it possible?

    BTW, I think that the stack trace of your last attachment is not complete. I was expecting a fragment like:

        at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(
        at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.findByAnd(
        at com.atlassian.jira.issue.changehistory.DefaultChangeHistoryManager.getAllChangeItems(
        at com.fca.jira.plugins.workflowToolbox.parser.ParserToolbox.timesOfTransitionExecution(
        at com.fca.jira.plugins.workflowToolbox.parser.ParserValueProvider.timesOfTransitionExecution(
        at com.fca.jira.plugins.workflowToolbox.parser.Parser.NumberListPrimary(
        at com.fca.jira.plugins.workflowToolbox.parser.Parser.NumberListTerminus(
        at com.fca.jira.plugins.workflowToolbox.parser.Parser.NumberListPreTerminus(
        at com.fca.jira.plugins.workflowToolbox.parser.Parser.NumberList(
        at com.fca.jira.plugins.workflowToolbox.parser.Parser.MathPrimary(
        at com.fca.jira.plugins.workflowToolbox.parser.Parser.MathTerminus(
        at com.fca.jira.plugins.workflowToolbox.parser.Parser.MathPreTerminus(
        at com.fca.jira.plugins.workflowToolbox.parser.Parser.MathExpression(
        at com.fca.jira.plugins.workflowToolbox.parser.Parser.evaluateMathExpression(
        at com.fca.jira.plugins.workflowToolbox.parser.Parser.getMathValue(
        at com.fca.jira.plugins.workflowToolbox.fields.calculatedNumber.CalculatedNumberField.getValueFromIssue(
        at com.fca.jira.plugins.workflowToolbox.fields.calculatedNumber.CalculatedNumberField.getValueFromIssue(
        at com.atlassian.jira.issue.fields.CustomFieldImpl.getValue(
        at com.atlassian.jira.issue.index.indexers.impl.NumberCustomFieldIndexer.addDocumentFields(
        at com.atlassian.jira.issue.index.indexers.impl.NumberCustomFieldIndexer.addDocumentFieldsSearchable(
        at com.atlassian.jira.issue.index.indexers.impl.AbstractCustomFieldIndexer.addIndex(

    Please, attach the full stack.

  13. rTrack Support reporter

    Even though i deleted that custom field at now . more than that i am not using any other transition count using jwt .

  14. Fidel Castro Armario repo owner

    Are you keep having the problem?

    In affirmative case, please, attach a FULL stack trace error.

  15. Fidel Castro Armario repo owner

    The problems now doesn't seem to be related with the plugin. I don't see any reference to the plugin in the stack trace.

    Please, run the integrity checker of on your JIRA instance: Administration > System > Integrity Checker. Let me know if you find any inconsistency.

  16. rTrack Support reporter

    Already i have done the integrity checker and reindexing two days back only . K fine . I will check . i need one clarification also . i used the calculated text field to find the linked issues issue id value in a field . it is working .but i cant see the values in the backend . Where you are storing those values in which tables .

  17. Fidel Castro Armario repo owner

    Those values are not stored, but they are calculated on the fly, i.e., each time you ask for the value of the field, it's calculated. This is the same for all the calculate fields.

  18. rTrack Support reporter

    we are not using the tempo add on . The above log is from our log or else different .

  19. Fidel Castro Armario repo owner

    Sorry so much, you are right. I have opened a log file which is not from you. I delete my previous post.

  20. Fidel Castro Armario repo owner

    I think that you are experiencing multiple error, some of them related with database connection. I think that the error related with the Calculated Number Field is caused by this previous problem.

    I think that you'd better ask for support to Atlassian, and send me a link to the issue. I will collaborate in the resolution.

    I'm available for a video-conference at Skype. My user is fidel100r. We can talk about the problem if you wish.

  21. Fidel Castro Armario repo owner

    Well, don't know the cause but you have some problems related with SQL exceptions, maybe caused by closed database connections. This is an example:

    2017-02-13 12:38:08,206 http-bio-80-exec-1020 ERROR P1247 756x880432x2 12rifz1 /secure/CommentAssignIssue.jspa [opensymphony.workflow.basic.BasicWorkflow] Error checking available actions
    com.opensymphony.workflow.StoreException: Could not find workflow instance #680343: root cause: SQL Exception while executing the following:SELECT NAME, INITIALIZED, STATE FROM dbo.OS_WFENTRY WHERE ID=? (I/O Error: Connection reset by peer: socket write error)
        at com.opensymphony.workflow.spi.ofbiz.OfbizWorkflowStore.findEntry(
        at com.opensymphony.workflow.AbstractWorkflow.getAvailableAutoActions(
        at com.opensymphony.workflow.AbstractWorkflow.transitionWorkflow(
        at com.opensymphony.workflow.AbstractWorkflow.doAction(
  22. rTrack Support reporter

    CUSTOMFIELD_20202 : Magna Team Tickets (Calculated Text Field (by JWT)) Text Expression :toString(filterByProject(linkedIssues("initiates (issue trigerred another issue)"), "CJP"))

  23. rTrack Support reporter

    CUSTOMFIELD_20201 : Dw Team Tickets (Calculated Text Field (by JWT)) Text Expression :toString(filterByProject(linkedIssues("initiates (issue trigerred another issue)"), "RDP"))

  24. Fidel Castro Armario repo owner

    Can you please try version 2.2.32_beta_2?

    This version is almost identical to version 2.2.31, but with a small improvement and a tentative modification for fixing this issue.

  25. Fidel Castro Armario repo owner

    Yes, you can use it in production environment. That version has passed all the regression tests successfully.

  26. rTrack Support reporter


  27. Fidel Castro Armario repo owner

    The indexing policy is implemented by JIRA. JIRA reindexes issues when a transition is executed of a field is updated. All the fields of an issue are indexed.

    The modification I have done is to tell JIRA explicitly that it's a calculated field, and this way prevent JIRA from indexing Calculated Text Fields, since it doesn't make sense indexing fields whose values can change on the fly.

  28. rTrack Support reporter

    k fine . i uploaded the jar file in the production environment . But it shows v.undefined in the addons page . Shall i need to re update the jar file once u release in official .

  29. Fidel Castro Armario repo owner

    Can you please attach a screenshot of showing the version as undefined?

    When the official version is released, you should uninstall the beta version and install the official version using the Universal Plugin Manager: Administration > Add-ons > Find new add-ons.

  30. rTrack Support reporter

    Now it is showing like this . But yesterday showed like v.undefined only . previously i was using 2.30 and then i upload manually 2.31 jar file and then i uploaded the jar file which was beta version of yours . beta version.png

  31. Fidel Castro Armario repo owner

    That's expected information.

    As I told you before, when the official version is released, you should uninstall the beta version and install the official version using the Universal Plugin Manager: Administration > Add-ons > Find new add-ons.

  32. rTrack Support reporter

    By uploading the new version will change the older version right . or how i uninstall the beta version .Bcs its live enviornment .

  33. Fidel Castro Armario repo owner

    You should uninstall the beta version, and then install the official versions. The reason is that the nomenclature used for beta versions is not recognized by Universal Plugin Manager.

    If you simply try to upload the new version onto the beta version, the beta version will remain installed.

  34. rTrack Support reporter

    Then how can i uninstall that thing . if i uninstall all the conditions and post functions will not get work out right ..

  35. rTrack Support reporter

    simply now i have installed beta version 2.32_2 once after the official announcement i will upload 2.32 official jar file .and then need to update the next version right ..

  36. Fidel Castro Armario repo owner

    Universal Plugin Manager doesn't allow to upload a version onto a beta_version. You have to uninstall the beta before uploading the official one. This will imply a brief interruption in the service of the plugin, but if you have the JAR of the official version previously downloaded, that out of service time won't be longer than 1 minute.

    You can practice on before on stage environment.

  37. rTrack Support reporter

    The functions present in the older workflows will not get affect am i right ?? . U mean if i click uninstall then the workflow toolbox will get removed .Then i have to manually upload the jar file right ?? . My upm is also not working .Due to that i am always downloading the new version and uploading the jar file manually only .

  38. Fidel Castro Armario repo owner

    The configurations in your workflows (conditions, validations, post-function and calculated fields) will be kept untouched after uninstalling the beta version and installing the official one.

    If your UPM doesn't install versions from the market directly, you can always download de JAR file and upload manually.

  39. Log in to comment