Communication Breakdown on long-time editing Description

[Thilo Brause]

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.

[Thilo Brause · Accepted solution]

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.

[Jorden Van Bogaert]

I find this comment right after installing this setup... Any chance you have found a solution in the meantime?

Our users are also having issues with pages/tabs that are idle for a couple of minutes resulting in the same.

[Thilo Brause]

The solution is to change the infrastructure and remove as many proxys, application firewalls and similar between your users and your server/instance.

[Bernhard Doleschel (Ease Solutions)]

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

[Thilo Brause]

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.

[Bernhard Doleschel (Ease Solutions)]

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.