Fisheye returns a 413 request entity too large or 414 Request-URI Too Large
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
問題
A connection to Fisheye/Crucible gets rejected with a 413 error (request too large) or 414 Request-URI Too Large and a blank screen.
The following appears in the atlassian-fisheye-YYYY-mm-DD.log
2017-01-24 10:19:58,355 WARN [qtp1679077741-4187418 ] org.eclipse.jetty.http.HttpParser HttpParser-fill - HttpParser Full for SCEP@718438c3{l(/127.0.0.1:50133)<->r(/127.0.0.1:8060),d=true,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=1r}-{AsyncHttpConnection@5ac13d10,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-1,l=5842,c=-3},r=25} 原因
Fisheye sends large cookies for UI preferences. The default limit HEAD request size for the Jetty web server used by crucible is 4096 bytes. As the cookies include a list of every open review the user has edit privileges on, this list could grow to be quite large.
ソリューション
Increase the size for jetty.http.headerbuffersize to 8192 (or bigger depending on the cookie size) to solve the issue.
Properties can be set by passing them with the -D parameter to the JVM using the FISHEYE_OPTS Environment variables