Error after upgrading Jira add on to 6.3.2.1

Getting following error after updating Jira Agile to version 6.3.2.1

" Communications breakdown

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 happens when trying to edit or delete workflows, as well as when trying to edit project categories.

We are running Jira on Redhat 6 with tomcat. I have tried rebooting the server several times, reindexing, and different web browsers. I still receive this error, but only when dealing with workflows and project categories.

Has anyone else run into this problem since the upgrade?

Kind regards,

Miguel

1 answer

0 votes

Can you look at the atlassian-jira.log file? There must be some helpful error in that log file.

I am assuming one of the plugins, that provide workflow conditions/validators/post functions is either missing or not compatible with the new version.

These are the logs from when I updated and noticed the issue.

Sep 27, 2013 3:21:31 PM com.sun.jersey.spi.inject.Errors processErrorMessages
WARNING: The following warnings have been detected with resource and/or provider classes:
WARNING: A sub-resource method, public javax.ws.rs.core.Response is.origo.jira.plugin.rest.WorklogsResource.addHoursEmpty(javax.servlet.http.HttpServletRequest) throws java.lang.Exception, with URI template, "/", is treated as a resource method
Sep 27, 2013 3:21:34 PM com.sun.jersey.spi.inject.Errors processErrorMessages
WARNING: The following warnings have been detected with resource and/or provider classes:
WARNING: A sub-resource method, public javax.ws.rs.core.Response is.origo.jira.plugin.rest.WorklogsResource.addHoursEmpty(javax.servlet.http.HttpServletRequest) throws java.lang.Exception, with URI template, "/", is treated as a resource method
Sep 27, 2013 3:21:43 PM com.sun.jersey.spi.inject.Errors processErrorMessages
WARNING: The following warnings have been detected with resource and/or provider classes:
WARNING: A sub-resource method, public javax.ws.rs.core.Response is.origo.jira

Hope this helps.

Kind regards,

Miguel

They are warnings. Are you noticing this again when you get the communication error? Or is there some other error when you reproduce the issue?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,714 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you