Documentation for FishEye 3.0.x. Documentation for other versions is available too.

FishEye and Crucible use a number of Java Virtual Machine system properties. Most of these are properties set by the virtual machine itself or the FishEye/Crucible launch script. Users can configure the following properties to control low level aspects of FishEye & Crucible's operation. For example:

Setting a Larger Header Buffer Size

jetty.http.headerbuffersize - This controls the size (in bytes) of the largest HTTP header that FishEye (version 1.6.5 onwards) will allow through its embedded servlet engine, Jetty. Some authentication systems require larger header values.

 

Properties can be set by passing them with the -D parameter to the JVM using the FISHEYE_OPTS environment variable or by adding them to FISHEYE_INST/system.properties. This file can be created as a plain text file (it follows the Java .properties format) if it doesn't already exist.

(info) The recommended approach is to add the property to FISHEYE_INST/system.properties. Add this as a new text file, using the Java .properties format. For example:

#System Properties file for FishEye/Crucible
jetty.http.headerbuffersize=8192

Verify the setting by using the command-line tool jinfo <pid> after the application starts up.

(info) Users integrating FishEye with Single Sign On applications may require an adjustment to the JVM properties, specifically the HTTP header size. This may also be useful in other circumstances where FishEye's default HTTP header is too small (at 4096 bytes).

 

  • No labels