[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3884) Seam file upload 100% CPU in MultipartRequest

Takayoshi Kimura (JIRA) jira-events at lists.jboss.org
Wed Jan 7 02:36:03 EST 2009


Seam file upload 100% CPU in MultipartRequest
---------------------------------------------

                 Key: JBSEAM-3884
                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3884
             Project: Seam
          Issue Type: Bug
    Affects Versions: 2.1.1.GA
         Environment: JBoss EAP 4.3.0.GA (no CP)
Java VM: Java HotSpot(TM) Server VM 1.5.0_13-b05,Sun Microsystems Inc.
OS-System: Linux 2.6.9-67.EL,i386

and

JBoss EAP 4.2.0.GA (no CP)
Java VM: Java HotSpot(TM) 64-Bit Server VM 1.5.0_12-b04,Sun Microsystems Inc.
OS-System: Linux 2.6.9-34.ELsmp,amd64
            Reporter: Takayoshi Kimura


Sometimes org.jboss.seam.web.MultipartRequest#parseRequest() goes into an endless loop and takes 100% CPU when uploading a large file. The root cause is most likely due to the HttpServletRequest#getInputStream()#read() always returns 0.

The API docs for InputStream state:

"If the first byte cannot be read for any reason other than end of file, 
then an |IOException| is thrown. In particular, an |IOException| is 
thrown if the input stream has been closed."

It's similar problem to RF-3746: https://jira.jboss.org/jira/browse/RF-3746


-- 
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