Yes, sorry. link can be found here:
http://myfaces.apache.org/issue.html thanks, Martin On 11/5/05, Robert Parsons <[EMAIL PROTECTED]> wrote: > I assume jira is some bug tracking system. Will do when I get a chance. > > > > Martin Marinschek wrote: > Can you open a jira issue for this in which you describe the problem? > > regards, > > Martin > > On 11/5/05, Robert Parsons <[EMAIL PROTECTED]> wrote: > > > I have been unable to find the exact cause but I have managed to stop the > problem for the moment and I dont have the time to muck around with it any > longer. It seems to be that it was allocating memory for the maximum file > size that could be uploaded. If I had the max upload size at 50mb, but a > disk threshold of around 5mb, it would run out of memory, even for very > small files. By putting the disk threshold to 0mb it seems to always use the > disk and I dont get any memory problems at all, even uploading 80mb files > with a VM memory size of 64mb (which should be possible of course). So i'm > happy for the time being. > > I dont know if this is a problem in the way that the MultipartFilter > operates or a problem with using the mutli-part filter in combination with > facelets or some other issue. Has anyone successfully used the Tomahawk file > upload component with Facelets? > > I'm running MyFaces 1.1.1 (with same-version of Tomahawk) and Facelets > 1.0d. > > Thanks, > -Robert. > > > > Robert Parsons wrote: > Hi, > > I have tried to profile the application and try and catch the error but > nothing is working. For one thing I suck at profiling as I have no idea what > i'm doing :S. I downloaded JProfiler and it has many nice screens but I cant > seem to make it do anything usefull. I tried using NetBeans debugger to > break on any ServletException or OutOfMemoryError and it didnt catch either > :S. > > Any ideas of how I could track this thing down? > > Thanks, > -Robert > > > Martin Marinschek wrote: > Sounds very interesting. > > Can you profile through what the extensions filter is doing? The > question is when this amount of memory is built up, if in the > extension filter or later in the JSF life-cycle, I can't imagine where > this would be. > > regards, > > Martin > > On 11/3/05, Robert Parsons <[EMAIL PROTECTED]> wrote: > > > Hi, > > Sorry to bother everyone again. I have been trying to use the file upload > component of MyFaces (Tomahawk), but my JVM is using up an incredible amount > of memory to process each upload request. With a max memory size of 64mb it > (the server) would almost certainly run out of heap space. On 120mb I could > upload the file but if I uploaded 2 in quick succession it would almost > certainly run out. With 1GB of memory I could always upload a file, but > uploading files in quick succession took the memory usage super high from > 120mb,200mb,500mb! Oh and by the way these files were no more than 2mb each, > and you didn't even have to upload a file to use up the memory, just submit > the form. > > Sureley this much memory should not be need to upload such tiny files. Is > this a problem with the upload component (or the extension filter) or is it > something i'm doing wrong? In my web.xml the maximum upload size is set to > 50mb and a use-the-disk threshold of 10mb. > > The exception see back from tomcat is: > > exception: > javax.servlet.ServletException: Filter execution threw an exception > > org.apache.myfaces.component.html.util.MultipartFilter.doFilter(MultipartFilter.java:102) > > root cause: > java.lang.OutOfMemoryError: Java heap space > > Any ideas? > > Thanks, > -Robert. > > > > -- > > http://www.irian.at > Your JSF powerhouse - > JSF Trainings in English and German > > > > > > > > > -- > > http://www.irian.at > Your JSF powerhouse - > JSF Trainings in English and German > > > > > -- http://www.irian.at Your JSF powerhouse - JSF Trainings in English and German
