IssueService transitioning an Issue multiple times validation error

[Sandor Krisztian Andre]

Hi I am faced with a strange problem. I am using the IssueService to transition an issue in the standard way. First validate then check the validation result then transition. I use the resulting MutableIssue to transition the issue again. This all works in my dev instance but it results in a failed validation in my test instance. If I execute the command again then the issue makes the second transition. Can this be a timeout issue (the test instance is much slower)

[Volodymyr Krupach]

You are welcome .

To be sure about IssueService you  can check the JIRA sources.

[Sandor Krisztian Andre]

I have no access to the log, but the issue is solved I think. I didn't call isValid() on the transition result and as it seems the IssueService.transition is asynchronous therefor the previous transition hasn't finished yet when the next one was called(on a heavily loaded system). I believe isValid() will only return when the transition has completed and thus can act as sync mechanism. I still need to test this on the test system.

Thank you for your help!

[Volodymyr Krupach]

Did you check the logs?

[Sandor Krisztian Andre]

I have no access to the test instance and can't easily install a new revision which would print the Error. The dev and test instances have the same workflow, configuration, conditions, rights, project schema and data, I made sure of it. The difference is performance, the test system is heavily loaded. I strongly suspect that the only explanation to this behavior is a race condition. Is it possible that the previous transition has not yet completed yet when the next is called (this implies some async implementation on db level or otherwise) and then the second transition is blocked? How can I make sure that the previous transition has finished before I call the next one?

[Volodymyr Krupach]

First of all you need to check the validation errors. Production and dev have different workflows and so it can work on the dev and return errors on the test instance.