[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3448) MultipartFilter does not begin parsing until after transaction is started

Shane Bryzak (JIRA) jira-events at lists.jboss.org
Tue Sep 23 17:15:20 EDT 2008


     [ https://jira.jboss.org/jira/browse/JBSEAM-3448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shane Bryzak closed JBSEAM-3448.
--------------------------------

    Fix Version/s: 2.1.0.CR1
       Resolution: Done


The request is now pre-parsed by the filter.

> MultipartFilter does not begin parsing until after transaction is started
> -------------------------------------------------------------------------
>
>                 Key: JBSEAM-3448
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3448
>             Project: Seam
>          Issue Type: Bug
>            Reporter: Clint Popetz
>            Assignee: Shane Bryzak
>             Fix For: 2.1.0.CR1
>
>
> Currently the multipart filter creates the request wrapper upon detecting a multipart post, but does not actually begin processing until the first time someone asks it for a parameter.  This means that upon such a POST, multipart processing won't begin until after the transaction has been created by the SeamPhaseListener, and thus for large uploads (and/or slow network connections) it's very easy to exceed the transaction timeout, leading to failed uploads.
> I think that MultipartFilter should call getParam("") before invoking the rest of the chain so that the upload/parsing happen before the tx is created.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list