Screen hang when we edit ticket on filter view

Jurgen Dekeyser October 15, 2018

Hi,

When we use a filtered view to view out Jira Issues and we then click on the Edit button, the screen just hangs and nothing happens.

We are currently using Jira Software 7.12.0 on-premnise.

We have this problem with all browsers, with all users.

bug.jpg

2 answers

1 accepted

0 votes
Answer accepted
Jurgen Dekeyser October 19, 2018

Hi Shannon,

This problem is solved, this had to do with ARR on IIS.

I needed to alter the registry of the ARR webserver, this is the change that I did:

Add a registry key as shown below to increase the path length that IIS can handle. This is necessary for some gadgets and buttons to work correctly.

Path: "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters"
Type: DWORD 32-bit
Name: "UrlSegmentMaxLength"
Value: "1000" Hexadezimal

 

I've found this information on the following url: 

https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-microsoft-internet-information-services-iis-833931378.html

Best Regards,

Jurgen

Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 22, 2018

Hi Jurgen,

Sorry for the delay, and thank you for letting me know how you were able to solve it!

Take care, and have a pleasant week.

Regards,

Shannon

0 votes
Shannon S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 16, 2018

Hi Jurgen,

Can you please trigger the problem again, take a note of the time, and send us the lines from your logs that occur at the same time? This will help us to determine why your screen is hanging. Check the below article if you're not sure where to find the server logs:

Let me know if you have any trouble!

Regards,

Shannon

Jurgen Dekeyser October 19, 2018

Hi Shannon,

Sorry for the delay we triggered the problem again and the only line that we see in the 'atlassian-jira-gc-....' log file is;

2018-10-19T14:09:14.523+0200: 621545.880: [GC (Allocation Failure) [PSYoungGen: 313394K->5562K(364544K)] 1094788K->787218K(1202688K), 0.1114560 secs] [Times: user=0.28 sys=0.00, real=0.11 secs] 

 

In the 'jirasoftware....' log file we see:

19-Oct-2018 14:12:31.880 WARNING [https-jsse-nio-8081-exec-9] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira.flagstone.tech/rest/issueNav/latest/preferredSearchLayout, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
19-Oct-2018 14:12:31.974 WARNING [https-jsse-nio-8081-exec-5] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira.flagstone.tech/rest/issueNav/1/issueTable/stable, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

I must mention that our JIRA server is a seperate windows 2016 server with an WEB IIS server in front of it. We're using ARR to redirect the traffic from the public internet to the internal Jira server.

 

Best Regards,

Jurgen

Suggest an answer

Log in or Sign up to answer