How long is a thread in use when modem user hits servlet? (repost from misc group)

Question

I'm developing an application that will go out to many users on the
internet. Most will be using modems and so my data center will have to
trickle packets to them because of their low modem bandwidth. Each
transaction is short lived, under 100ms, but I'm concerned that the
execution thread in weblogic will be tied up for several seconds while the
data served is tricked down over the modem.
- Is the weblogic execution thread returned when a servlet call returns, or
only when the stream back through the web server has been emptyied?
- Will in fact calls to write to the output stream (or flushes at least) of
the servlet block until the TCPIP stack returns with data sent OK - ie block
until all the data is sent over the modem?
- If I use buffered output streams with large enough buffers to hold all
served data, and don't flush them before returning with the servlet call,
what does weblogic do? Will weblogic hold the execution thread until it can
empty the buffer, hence be delayed by the modem?
- Does putting netscape enterprise server between weblogic and the client
fix this - will enterprise server buffer the data?
- Does setting keep alive in weblogic or enterprise server have any effect
on this problem?
Thanks.
Mark Johnson
Markj
Mark Johnson.
Encirq Corporation, San Francisco CA, [phone]x116
http://www.encirq.com/ [email protected]
The information contained in this message is CONFIDENTIAL. It is intended
only to be read by the individual or entity named above or their designee.
If the reader of this message is not the intended recipient, you are on
notice that any distribution of this message, in any form, is strictly
prohibited. If you have received this message in error, please immediately
notify the sender and/or Encirq Corporation by telephone at 415-284-9800 and
delete or destroy any copy of this message.

Answer 1

Thanks for your reply!!!
jwenting wrote:
no, your code is NOT correct.
It doesn't "upload" anything, as I stated before.It is working perfectly fine if the destination folder is connected to the server machine (which is not the case now).
>
Look into multipart MIME requests, Jakarta Commons File Upload, and things like that to actually upload files to a server instead of insisting on reading them directly from the client's filesystem in your servlet and wondering why that doesn't work if the servlet container is running on a different computer from the client.I AM using Jakarta Commons File Upload. The problem is when I try to access the destination folder(which is in client machine), it can't find as it is searching for the corresponding folder in the server.
>
Unless and until you do that, you're wasting our time and your own.I thought someone could help me i giving me some pointers which I missed. Thanks again!!
Edited by: AnishThomas on Mar 14, 2008 8:13 AM