[MGNLDMS-133] Get info.magnolia.module.dms.DMSDownloadServlet Error after upgrading from 3.0 to 3.5.8 Created: 19/Aug/08  Updated: 10/Sep/08  Resolved: 10/Sep/08

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

Type: Bug Priority: Major
Reporter: Sean Haas Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Upgrading from 3.0 to 3.5.8. Moved from derby to berkley db. Tomcat 5.5.26


Attachments: Text File log.txt    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When upgraded our site from version 3.0 to version 3.5.8. They site seems to be working well but when I watch the log files, it throws this:

ERROR info.magnolia.module.dms.DMSDownloadServlet DMSDownloadServlet.java(doGet:76) 19.08.2008 10:51:54 error during download
ClientAbortException: java.net.SocketException: Connection reset

It doesn't seem to affect anything, but if this continues, my log files are going to fill up pretty quick. Am I missing something? Attached is the complete stack trace.



 Comments   
Comment by Magnolia International [ 20/Aug/08 ]

This exception is triggered when the http request is interrupted by the client (browser or other component relaying the request on the network).
Does this happen with all files, only bigger ones, how big ?

Does this happen with all clients ?

Please check firewalls, proxies, etc, as they might interrupt your requests when they consider too long, too big, ...

http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/catalina/connector/ClientAbortException.html

Comment by Sean Haas [ 20/Aug/08 ]

We looked back through our logs in the 3.0 version and noticed it in there are well. Something interesting to note is that it happens at all hours of the day. Yesterday, it happened even during the middle of the night, but definitely not as frequent. It makes me think that it has to do with people just hitting any page on our site. An important note is that every page of our site hits the DMS to load the background images, even if there isn't any content on the page. Also, we are using mod proxy on port 80 to by pass any firewall issues.

Another question I have: Would this lead to memory problems? We have had problems with running out of memory even though there is a lot of memory.

Thanks
Sam

Comment by Magnolia International [ 10/Sep/08 ]

This should not cause memory problems with 3.6, as the new cache does not cache "broken" requests. With 3.5, well, I don't think it would cause memory issues either, but broken downloads are being cached as is. (MAGNOLIA-2057)

Please don't hesitate to reopen this issue if you have more concerns.

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