Release Notes for 1.36.1
Bug fixes
Fixed SQLServerException when triggering a rescan in Missing Attachment Scanner
This occurs if there are more than 2100 spaces and affects Microsoft SQL Server databases.
com.microsoft.sqlserver.jdbc.SQLServerException: The incoming request has too many parameters.
The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
Fixed IllegalArgumentException when loading Missing Attachment Scanner if attachment has been deleted
This occurs when the scanner initially detects attachment data as missing, and subsequently, the attachment is deleted from the page.
java.lang.IllegalArgumentException: The attachment cannot be null.
Fixed undefined space key in logs
The log file may have entries containing:
/rest/attachment-checker/1.0/space/undefined/status
This REST endpoint is for checking the space quota status. Additional check on the space key has been added before firing REST call.
Fixed inaccurate status displayed in Quota Summary
“Recalculation in progress…” may be displayed but no actual recalculation is executed.
Improved on long running SQL queries
This may happen if attachments are uploaded and/or space quota is updated during quota recalculation period.
Work items resolved
Type | Key | Summary | |
---|---|---|---|
1 | Bug | SQLServerException when triggering a rescan in Missing Attachment Scanner | |
2 | Bug | IllegalArgumentException when loading Missing Attachment Scanner if attachment has been deleted | |
3 | Bug | Undefined space key in logs | |
4 | Bug | Inaccurate status displayed in Quota Summary | |
5 | Bug | Long running SQL queries |