The jsp, Tomcat, and the ftp server are all on the same machine.
The files to be uploaded are on some remote user's machine. Yes,
I agree that FileUpload can certainly do this, but we've had some
issues uploading really big files using FileUpload and it was
suggested (by one of my bosses) that
You can't use the ftpclient from the client side in a jsp without having
a signed java applet or an application. Just to clarify, because from
the posting it doesn't sound like that is clear. The FileUpload class
and everything else runs on the backend in the jsp container, so the ftp
I was wondering if there are any tutorials or source examples of
using ftpClient to allow a remote user to upload files to an ftp
server using jsp form calling a servlet that is running on the
same system as the ftp server.
I've been able to upload the file when the servlet is running on
the
It sounds like your server is timing out and killing the session, but I'm not sure why
it would be different on the Solaris system.
I did some experiments with various large files. I first set my session timeout to 600
minutes. I then tested to see how long it took to upload the files from
At 11:16 AM 3/31/04 -0800, Bill Simpson wrote:
In addition, literally adding one
more byte to the file size causes this to fail. I've set the timeout time
to be ridiculously high and it doesn't make a difference. The addition of
one byte changes the amount of time from 2 minutes to the length of
Check out setSizeThreshold and setRepositoryPath in DiskFileUpload. Maybe this is
where your problem lies.
At 11:44 AM 3/31/04 -0800, Cindy Ballreich wrote:
At 11:16 AM 3/31/04 -0800, Bill Simpson wrote:
In addition, literally adding one
more byte to the file size causes this to fail. I've set
At 01:02 PM 2/18/04 -0300, Martin Marchetta wrote:
Does Tomcat have this problem? Anybody knows if it is a known bug?
Is it possible that your session is timing out? You might set a listener and see if
that's what's happening.
Just a thought.
Cindy
either direction efficiently.)
So, the short answer is FTP is prolly quicker because it just has to write
the bits - it gets external notification when there are no more bits to
write. With HTTP, the server has to process every bit to find when the last
one is received.
From: Cindy Ballreich
At 05:50 PM 6/9/03 -0700, Martin Cooper wrote:
If SizeLimitExceededException is thrown, that happens before parsing of
the multipart body even starts, since the size limit is based on the size
of the entire request.
So setSizeMax sets the total size of the request and not the maximum size of
In the event that the parseRequest(request) method of DiskFileUpload throws an
exception (FileUploadBase.SizeLimitExceededException for example), is there a way to
reject the FileItem that caused the exception and finish parsing the rest of the
request so that the other FileItems can be
At 02:26 PM 1/24/03 -0700, Linda Steckel wrote:
I too have a connection closing(? or something) problem.
Linda,
I saw some of your postings in the archives. It sounds like you are experiencing the
same issues I am. Please let me know if you find anything.
Cindy
--
To unsubscribe, e-mail:
Some time back I did an experiment using DBCP with Tomcat (JNDI) and MySQL. I was able
to get a beautiful connection pool, but the connection to the database seemed to die
after an extended period of idleness. Not having the time to deal with it, I went back
to my old connection pooling
Rodney,
Thanks for responding!
At 01:39 PM 1/23/03 -0800, Rodney Waldhoff wrote:
On Thu, 23 Jan 2003, Cindy Ballreich wrote:
I was unable to find your previous message (in any) in the archives.
There wasn't one. I posted a couple on the Tomcat-User list, but I had to move on to
other things
13 matches
Mail list logo
