Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Communication Breakdown on long-time editing Description

In my environment some projects use Jira to define requirements to software. As they belive in big and complete requriements, they spend a long time in the description field of the issue editing details. 

However it happens very often, that when they want to save their insertions/changes the Client responded with a "Communication Breakdown"-error. 

And this behaviour is persistent for over a month now, but only appears if someone writes for a long time in the description of one issue.

None of the known and discussed problems for Communication Breakdown seem to apply here. Does anybody have an idea?

 

It may be some kind of infrastructure problem - it appeared right after we made Jira available only over an Microsoft-ApplicationProxy, to enable users outside of our internal network to use Jira.

2 answers

1 accepted

0 votes
Answer accepted

The solution of this problem was found: It is the Microsoft-ApplicationProxy which is in Front of our installation and some of its "security"-Features.

After weeks of work our internal teams gave up. It is not possible to solve this problem.

=> Never try to combine a MS-Appproxy with Jira Server. These technologies simply doesn't fit together.

Hello Thilo, 

I guess your colleagues run in a authentication timeout. After a while your login has expired (to release server load) and your user account is not logged in anymore. The timer is reset when you execute any actions within Jira (as long it´s not expired). Two options:

  • when the error occurs: open another browser tab to Jira and login again. Go back to the tab with the error and try to save the content again.
  • your Jira administrator can extend the timeout. please see the knowledge base.

Hope this helps. Best Regards, Bernhard

Dear Bernhard,

negative. The problem appears before the Jira-Session ran into a Timeout.

Also a Jira-Session-Timeout is handled gracefully by Jira itself - the content of the transaction is shown to the user (for saving externaly) and a reauthentication is enforced. No "Communication Breakdown" in that case.

Then I´ve now further idea yet. May you check your installed add-ons (and deactivate one-by-one) if one of them is the root cause.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.13.8
TAGS
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

880 views 14 20
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you