Increasing the maximum size of a file attachment in a review
Please note that the below changes will not take effect when uploading attachments to reviews through the REST API
Uploading a file larger than the allotted 10MB limit results in the following error message:
Your browser sent a request that this server could not understand.
DEBUG [qtp98826337-2732 ] fisheye ProfilingServletFilter-logRequest - start request POST /fisheye/cru/PROJ3-10/edit-patch/?command=upload sessionid=11md2ap348asl18b4ro7m5w4w7 ERROR [qtp98826337-2732 ] com.opensymphony.webwork.interceptor.FileUploadInterceptor FileUploadInterceptor-acceptFile - File too large: upload "upload_bfd79be2_5b1e_47dc_94ed_326ecd2dde1e_00000018.tmp" 138452783
A file larger than 10MB was uploaded.
Please be advised that altering these configuration files is officially unsupported. The limit of 10MB on file uploads is enforced for performance reasons. If this limit is set to a high value and a large diff is uploaded, it is possible that Crucible can choke on the upload as this has not been tested – keep this in mind.
The limit can be changed by manipulating the value (the parameter is set in bytes) in
<Fisheye/Crucible installation directory>/content/WEB-INF/classes/xwork-crucible.xml. For example:
<action name="edit-upload" class="com.cenqua.crucible.actions.create.AddFileAction"> <interceptor-ref name="fileUpload"> <param name="maximumSize">10485760</param> </interceptor-ref> .... <action name="edit-patch" class="com.cenqua.crucible.actions.create.AddPatchAction"> <interceptor-ref name="fileUpload"> <param name="maximumSize">10485760</param> </interceptor-ref>
The procedure to achieve this is:
- Stop Fisheye/Crucible
- Change the xwork-crucible.xml file with the desired value
- Start Fisheye/Crucible