[MGNLDMS-106] DMSDownloadServlet - error during download when site is under heavy traffic Created: 06/Sep/07  Updated: 03/Jul/14  Resolved: 29/Nov/07

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2-rc2

Type: Bug Priority: Blocker
Reporter: zam6ak Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

3.1-SNAPSHOT
JBoss 4.0.5GA


Attachments: Text File dms-error-during-download.txt    
Issue Links:
relation
is related to MGNLDMS-185 DMSDownloadServlet logs error message... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When experiencing heavy traffic on public instances DMSDownloadServlet breaks off client connections causing errors (see attached stacktrace)
In brief conversation with Magnolia devs it is was indicated that this may have sometihnig to do with spooling process from the servlet to the client.



 Comments   
Comment by Philipp Bracher [ 07/Sep/07 ]

There are rumors that the exceptions are thrown if someone cancels the download.

Must be overlooked.

Comment by zam6ak [ 07/Sep/07 ]

Currently we don't serve any documents via DMS (where people can download them that is).
We do plan to do so once fckEditor is able to link to DMS docs....

However, what we use DMS for is to store common shared images (banners, logos, etc, etc) which are utilized in dialog selections.
For example, we have a dialog that allows user to "pick" a banner from DMS. If we ever wanted to change the banner we would just upload a new version and all the pages that have that particular banner would also be updated.

This is the use case scenario where we experience this error. When the page loads, it is referencing images from DMS - there is no downloading of the separate documents.
Granted, there could be a case where user cancels the page load which may cause this error, but we have so many of these error appearing in the log (literary they appear every few seconds) that I am not sure this is the case either.

I hope this info helps.

Comment by Jan Haderka [ 01/Oct/07 ]

Do you know what browser are users using when this error happens? IE cancels download of images when response is too slow and it thinks there's no update (i.e. after getting first few kb of the image). It should be easy to verify if that's the case - errors would not occur when using other browsers (i.e. FF).
If this is the case, the best solution would be perhaps to just catch the exception at info.magnolia.module.dms.DMSDownloadServlet.sendUnCompressed(DMSDownloadServlet.java:78)

Comment by zam6ak [ 01/Oct/07 ]

Jan

In my opinion, it should not matter what kind of browsers users have. Magnolia should be browser agnostic...
As for catching the exception and ignoring it - if that is the true solution to the problem then I am ok with it....

Comment by Jan Haderka [ 01/Oct/07 ]

Agreed. I've provided browser info only as a way to verify that this is a real problem here. We would not want to ignore the exception if something else was the cause.

Comment by Philipp Bracher [ 29/Nov/07 ]

added a better log message (info level) and close the stream nicely

Generated at Mon Feb 12 00:48:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.