Users are unable to transition or change the state of tickets

[IT EMN8]

When users try to transition tickets, the application hangs and will produce this error message

The JIRA server could not be contacted. This may be a temporary glitch or the server may be down.

Close this dialog and press refresh in your browser

This is only occurring on the transition of tickets.

[Ramiro Pointis]

Could be a problem with one of your plugins like here:

https://answers.atlassian.com/questions/89691/workflow-condition-is-not-working

Check there and also check if all of them are updated and compatible.

[Tansu Kahyaoglu]

Have you tried this solution: https://confluence.atlassian.com/display/JIRAKB/Unable+to+Transition+Issues+after+JIRA+Upgrade+Due+to+JIRA+Suite+Utilities+Plugin

[J. Caldwell]

Did you check your workflow? You may have a loop of sometime.

You can turn up the logging on the instance and see more content generated in the atlassian logs.

[IT EMN8]

Also, we recently set up an application link between our JIRA and our Confluence servers, and we are having issues querying JIRA tickets from Confluence (even though we can link the tickets). Not sure if this is related, but these two events started occurring around the same time.

Any insight that can be provided would be most appreciated.

Thanks.

[IT EMN8]

Last night we seemed to get a lot of entries that looked like this:

Jan 15, 2013 6:28:59 PM com.atlassian.plugins.rest.doclet.generators.resourcedoc .AtlassianWadlGeneratorResourceDocSupport createResource

INFO: Resource path of rest end point 'com.atlassian.jira.rest.v1.projectcategor ies.ProjectCategoriesResource' unchanged no mapping to rest plugin module descriptor found.

Jan 15, 2013 6:28:59 PM com.atlassian.plugins.rest.doclet.generators.resourcedoc .AtlassianWadlGeneratorResourceDocSupport createResource

INFO: Resource path of rest end point 'com.atlassian.jira.rest.v1.project.ProjectAvatarResource' unchanged no mapping to rest plugin module descriptor found.

Not sure if this is the root of the problem. I've done tail -f on today's log while I had a user reproduce the error, but it doesn't seem to leave a trail.

Is there more I can look at other than the catalina.out log?

Thanks.

[Timothy]

What's in the logs?