You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Jochen Wiedmann (JIRA)" <ji...@apache.org> on 2007/01/12 09:25:27 UTC
[jira] Commented: (FILEUPLOAD-124) Error while uploading the file -
in Clusterd in Environment
[ https://issues.apache.org/jira/browse/FILEUPLOAD-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464117 ]
Jochen Wiedmann commented on FILEUPLOAD-124:
--------------------------------------------
> org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Stream ended unexpectedly
> at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:429)
This error message can be cause by
a) An aborted input stream. For example, the client browsers user may have pressed "Stop" or
switched to another URL. In your case, it might also occur that the load balancer switched
the cluster machine. (Which would, of course, be an error in the cluster, so that's unlikely.)
b) An error in the multipart/form-data parser of commons-fileupload. This is also unlikely.
Nevertheless, it is possible. However, for obvious reasons, this cannot be analyzed
without you providing an example of the data causing the problem. For example, you might
use Wireshark or a similar tool to catch network traffic. Or, if possible, extend your logging
to trace the clients input stream.
> But how and why do the files end up on other servers 'B'.
This is a question, which is completely unrelated to the commons-fileupload library. Ask your clusters vendor or whoever might know the cluster.
I'll wait for some weeks, whether you are able to provide more data. If not, I'll intend to close this bug as "Invalid".
> Error while uploading the file - in Clusterd in Environment
> -----------------------------------------------------------
>
> Key: FILEUPLOAD-124
> URL: https://issues.apache.org/jira/browse/FILEUPLOAD-124
> Project: Commons FileUpload
> Issue Type: Bug
> Environment: In the Integration Environment
> Reporter: Ramdeepak
>
> This happens once in a while, We use the WebLogic proxy itself for loadbalancing.
> The Weblogic servers are configured in Clustered mode.
> I have made my Deployments on a machine 'A'.
> But how and why do the files end up on other servers 'B'.
> ( The logs are from machine 'B' ).
> Exception :
> =========
> org.apache.commons.fileupload.FileUploadException: Processing of multipart/form-data request failed. Stream ended unexpectedly
> at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:429)
> at com.nol.core.RequestParameterValue.<init>(RequestParameterValue.java:110)
> at com.nol.core.servlet.NolFrontController.doService(NolFrontController.java:187)
> at com.nol.core.servlet.NolFrontController.doPost(NolFrontController.java:177)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1072)
> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
> at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
> at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
> at com.nol.core.servlet.UserFilter.doFilter(UserFilter.java:300)
> at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
> at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6987)
> at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
> at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3892)
> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org