You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Maulin Shah, MD" <ma...@gmail.com> on 2004/11/01 23:35:31 UTC
strange upload component problem
I have been using the upload component without any problems on my local machine.
However, when I deploy my application to my webserver, whenever I try
to use the upload component for anything bigger than 3Kb i get a
FileUploadException (full trace below).
I have already tried the two "max size" fixes:
DefaultMultipartDecoder.getSharedInstance().setMaxSize(-1);
and
<extension name="org.apache.tapestry.multipart-decoder"
class="org.apache.tapestry.multipart.DefaultMultipartDecoder">
<configure property-name="maxSize" type="double" value="-1"/>
<!-- where the value is the maximum size you want to allow -->
</extension>
I am trying to upload a 150kb file, not something huge. It reliably
works locally, but dies on the server. Any thoughts?
Thanks SO MUCH in advance. (by the way, i started using tapestry about
2 months ago... i rocks!)
--
Maulin Shah, MD
Associate Director and Instructor
Residency Programs in Internal Medicine
Baylor College of Medicine
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: strange upload component problem
Posted by "Maulin Shah, MD" <ma...@gmail.com>.
woops:
org.apache.tapestry.ApplicationRuntimeException
Unable to decode request: Processing of multipart/form-data request
failed. Stream ended unexpectedly
org.apache.commons.fileupload.FileUploadException
Processing of multipart/form-data request failed. Stream ended unexpectedly
Stack Trace:
org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:429)
org.apache.commons.fileupload.DiskFileUpload.parseRequest(DiskFileUpload.java:245)
org.apache.tapestry.multipart.DefaultMultipartDecoder.decode(DefaultMultipartDecoder.java:159)
org.apache.tapestry.request.RequestContext.getDecoder(RequestContext.java:1077)
org.apache.tapestry.request.RequestContext.getParameter(RequestContext.java:440)
org.apache.tapestry.engine.AbstractEngine.extractServiceName(AbstractEngine.java:2016)
org.apache.tapestry.engine.AbstractEngine.service(AbstractEngine.java:847)
org.apache.tapestry.ApplicationServlet.doService(ApplicationServlet.java:197)
org.apache.tapestry.ApplicationServlet.doPost(ApplicationServlet.java:326)
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:300)
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:374)
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
java.lang.Thread.run(Thread.java:534)
On Mon, 1 Nov 2004 18:53:06 -0600, Shawn Church <sh...@boxity.com> wrote:
> Seems to be missing the stack trace.
>
> Shawn
>
>
>
> -----Original Message-----
> From: Maulin Shah, MD [mailto:maulinpshah@gmail.com]
> Sent: Monday, November 01, 2004 4:36 PM
> To: tapestry-user@jakarta.apache.org
> Subject: strange upload component problem
>
> I have been using the upload component without any problems on my local
> machine.
>
> However, when I deploy my application to my webserver, whenever I try
> to use the upload component for anything bigger than 3Kb i get a
> FileUploadException (full trace below).
>
> I have already tried the two "max size" fixes:
>
> DefaultMultipartDecoder.getSharedInstance().setMaxSize(-1);
>
> and
>
> <extension name="org.apache.tapestry.multipart-decoder"
> class="org.apache.tapestry.multipart.DefaultMultipartDecoder">
> <configure property-name="maxSize" type="double" value="-1"/>
> <!-- where the value is the maximum size you want to allow -->
> </extension>
>
> I am trying to upload a 150kb file, not something huge. It reliably
> works locally, but dies on the server. Any thoughts?
>
> Thanks SO MUCH in advance. (by the way, i started using tapestry about
> 2 months ago... i rocks!)
>
> --
> Maulin Shah, MD
> Associate Director and Instructor
> Residency Programs in Internal Medicine
> Baylor College of Medicine
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
Maulin Shah, MD
Associate Director and Instructor
Residency Programs in Internal Medicine
Baylor College of Medicine
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: strange upload component problem
Posted by "Maulin Shah, MD" <ma...@gmail.com>.
for better or worse -- i figured it out.
my webserver runs iis and tomcat.
tomcat is piped through iis using isapi, per tomcat's website.
if i put in the url:
www.mycompany.com/context
it routes it to
www.mycompany.com:8080/context
however, if i do the upload directly, without the routing (ie
www.mycompany.com:8080/context as my url)
then the upload works fine.
clearly this is a tomcat/IIS/apache-commons issue, not a tapestry one.
sorry to clog up the bandwidth...
maulin
On Mon, 1 Nov 2004 18:53:06 -0600, Shawn Church <sh...@boxity.com> wrote:
> Seems to be missing the stack trace.
>
> Shawn
>
>
>
> -----Original Message-----
> From: Maulin Shah, MD [mailto:maulinpshah@gmail.com]
> Sent: Monday, November 01, 2004 4:36 PM
> To: tapestry-user@jakarta.apache.org
> Subject: strange upload component problem
>
> I have been using the upload component without any problems on my local
> machine.
>
> However, when I deploy my application to my webserver, whenever I try
> to use the upload component for anything bigger than 3Kb i get a
> FileUploadException (full trace below).
>
> I have already tried the two "max size" fixes:
>
> DefaultMultipartDecoder.getSharedInstance().setMaxSize(-1);
>
> and
>
> <extension name="org.apache.tapestry.multipart-decoder"
> class="org.apache.tapestry.multipart.DefaultMultipartDecoder">
> <configure property-name="maxSize" type="double" value="-1"/>
> <!-- where the value is the maximum size you want to allow -->
> </extension>
>
> I am trying to upload a 150kb file, not something huge. It reliably
> works locally, but dies on the server. Any thoughts?
>
> Thanks SO MUCH in advance. (by the way, i started using tapestry about
> 2 months ago... i rocks!)
>
> --
> Maulin Shah, MD
> Associate Director and Instructor
> Residency Programs in Internal Medicine
> Baylor College of Medicine
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
--
Maulin Shah, MD
Associate Director and Instructor
Residency Programs in Internal Medicine
Baylor College of Medicine
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
RE: strange upload component problem
Posted by Shawn Church <sh...@boxity.com>.
Seems to be missing the stack trace.
Shawn
-----Original Message-----
From: Maulin Shah, MD [mailto:maulinpshah@gmail.com]
Sent: Monday, November 01, 2004 4:36 PM
To: tapestry-user@jakarta.apache.org
Subject: strange upload component problem
I have been using the upload component without any problems on my local
machine.
However, when I deploy my application to my webserver, whenever I try
to use the upload component for anything bigger than 3Kb i get a
FileUploadException (full trace below).
I have already tried the two "max size" fixes:
DefaultMultipartDecoder.getSharedInstance().setMaxSize(-1);
and
<extension name="org.apache.tapestry.multipart-decoder"
class="org.apache.tapestry.multipart.DefaultMultipartDecoder">
<configure property-name="maxSize" type="double" value="-1"/>
<!-- where the value is the maximum size you want to allow -->
</extension>
I am trying to upload a 150kb file, not something huge. It reliably
works locally, but dies on the server. Any thoughts?
Thanks SO MUCH in advance. (by the way, i started using tapestry about
2 months ago... i rocks!)
--
Maulin Shah, MD
Associate Director and Instructor
Residency Programs in Internal Medicine
Baylor College of Medicine
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org