Ronny
Posts:29
| | 11/06/2007 4:38 PM |
| Hi John, Yesterday we were able to solve the download problem by adding the page blaster module and exclude the page. However, today we encountered another problem of not being able to upload large file (30 Mb). I already set everything in web.config to allow threshold for big files and it worked before we install this page blaster module...Any suggestion or help to fix this...Thanks in advance. | | | |
|
|
|
John Mitchell
Posts:3248
| | 11/06/2007 4:43 PM |
| Hi Ron,
PageBlaster should not interferre with uploads. It only filters output in the response.
Is it timing out? Are you sure the threshold is big enough for 30 MB? You can also look in the event view to see if it has more details about the error. | | | |
|
Ronny
Posts:29
| | 11/06/2007 4:44 PM |
| Hi John, Yes, it is timing out. Here is my web.config: httpRuntime useFullyQualifiedRedirectUrl="true" maxRequestLength="900000" requestLengthDiskThreshold="900000" executionTimeout="400"
And this is the error: DotNetNuke.Services.Exceptions.PageLoadException: Exception of type 'System.OutOfMemoryException' was thrown Could you also please help me to understand the difference in the exclude path where we have the option of: Compression, Cache, CompressionAndCache, and Replacement? As always, thanks very much. | | | |
|
John Mitchell
Posts:3248
| | 11/06/2007 5:13 PM |
| Ok, out of memory errors when uploading very large files is pretty common.
This happens because the server has to load the complete file into Memory.
PageBlaster does use some memory for it's cache, but I doubt that it is using very much. You can limit the amount of memory used by PageBlaster in the config file. By default it is only set to 25 MB though.
Those excludeFrom options are the operations that PageBlaster can do to the output. Generally speaking, anytime you have a problem with an output filter you will probably have a problem with all operations. Like in the case with downloads, the page just cannot handle any filters being applied to the output. So you will usually exclude from ALL.
Sometimes you may want to do replacements, and just not cache any output like if you were personalizing the page with the user's name. In that case you would only excludeFrom="Caching"
| | | |
|
Ronny
Posts:29
| | 11/06/2007 5:19 PM |
| Posted By John Mitchell on 11/06/2007 5:13 PM
You can limit the amount of memory used by PageBlaster in the config file. By default it is only set to 25 MB though. Can you tell me how to do this? Which file should I check for this? I went to Snapsis.PageBlaster.config file and I see disk-size-limit=100, what is that mean? Please help me here since customer keep calling me asking why they cannot upload image to the site. Thanks. | | | |
|
John Mitchell
Posts:3248
| | 11/06/2007 5:25 PM |
| In the Snapsis.PageBlaster.config file is a memory-size-limit attribute. Changing that is not going to help though.
What has probably happened is they are trying to keep uploading the image, but the application is out of memory, and when it gets that error it does not release the memory.
If you login as host, and then go to the Host Settings page and restart the application they will probably be able to upload it. | | | |
|
Ronny
Posts:29
| | 11/06/2007 5:33 PM |
| Hi John, I change the memory size limit to 10 and I did restart the application, but it still throw me the Exception of type 'System.OutOfMemoryException' was thrown". Do you have any other solution? What happened if the memory size limit I set to 0 and what is memory cache interval? Thanks in advance. | | | |
|
John Mitchell
Posts:3248
| | 11/06/2007 5:43 PM |
| memory-cach-interval is how long it stays in memory.
If you have it at only 10 MB it is not PageBlaster that is using the memory.
Are you on shared hosting? Most hosts won't allow a file that big to be uploaded. | | | |
|
Ronny
Posts:29
| | 11/06/2007 5:48 PM |
| Hi John, We have a dedicated server and also it works fine in the past for file up to 70 Mb. I will replace this upload module with the one from telerik which basically bypass the stored in memory. In the mean time, what should I do to check if this is not causing by PageBlaster module? Should I uninstall the whole module or can i just take off the line of code in web.config? Just to make sure that it is not because of PageBlaster module. Thanks. | | | |
|
John Mitchell
Posts:3248
| | 11/06/2007 5:53 PM |
| Yes, you can just comment the PageBlaster line in the HttpModules section of web.config and it won't be used at all.
The other upload component that streams to disk is a very good idea.
If you have a dedicated server you may also want to take a look at the application pool settings to see if the memory is limited there. | | | |
|
Ronny
Posts:29
| | 11/06/2007 5:55 PM |
| I was thinking about Compression module that I commented out in order of using PageBlaster module. What is the compression module do anyway? Is it because of that? I will check on the application pool as well as try to comment out the Page Blaster module. Thanks. | | | |
|
John Mitchell
Posts:3248
| | 11/06/2007 6:01 PM |
| The compression module compresses the output of the page before it is sent to the browser. That is also only an output filter.
The reason you comment that one out is because PageBlaster already does that, and you can't compress a page twice ;) (actually you could but it makes a mess out of it). | | | |
|
Ronny
Posts:29
| | 11/06/2007 6:01 PM |
| Posted By John Mitchell on 11/06/2007 5:53 PM
If you have a dedicated server you may also want to take a look at the application pool settings to see if the memory is limited there.
I check on the Application Pool and under Recycling tab, both option on the memory recycling is unchecked. Is there any other place should I check?
| | | |
|
John Mitchell
Posts:3248
| | 11/06/2007 6:06 PM |
| | No, that's the only place I know of. | | | |
|
Ronny
Posts:29
| | 11/06/2007 6:16 PM |
| Hi John, I just create a new app pool and assigned to it. Restart the IIS and it works fine now. So, I guess its nothing to do with Page Blaster module. Thanks very much. | | | |
|
John Mitchell
Posts:3248
| | 11/06/2007 6:21 PM |
| Interesting. That means that restarting the Application Pool may have helped. I guess restarting the application wasn't enough to free that memory.
Ok, I'd recommend getting that other component going if they are doing a lot of large uploads. until then, if it happens again the first thing you may want to try is the app pool recycle.
Thanks for letting me know. | | | |
|
Ronny
Posts:29
| | 11/06/2007 7:13 PM |
| Thanks for your help. | | | |
|
jerops
Posts:50
| | 01/27/2008 1:17 PM |
| Is there a way to have IIS 6.0 or DNN always stream uploaded files to disk and bypass uploading it to memory first? Thanks for your help. Jerry | | | |
|
John Mitchell
Posts:3248
| | 01/27/2008 3:31 PM |
| Hi Jerry,
No, you would need a third party component for that.
I believe there are DNN modules that handle large uploads also.
| | | |
|