----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
There's no reason to create a thread to write to the ServletOutputStream --
JServ should already have created a new thread to handle the initial
request. I'm sure that JServ flushes and closes the output stream
after your doGet() or doPost() method returns -- so the socket is
indeed invalid when your thread tries to write to it.
Either just write your data to the client in the context of the original
request, or have your thread save its work to the session object -- your
applet would then have to make a later request to get the completed data.
- Fernando
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jesus
> Escanero
> Sent: Monday, September 18, 2000 2:55 AM
> To: Java Apache Users
> Subject: Problems with sessions...
>
>
> ----------------------------------------------------------------
> BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
> WHEN YOU POST, include all relevant version numbers, log files,
> and configuration files. Don't make us guess your problem!!!
> ----------------------------------------------------------------
>
>
> Hi everyone!
>
> I have a problem and I wish you could help me to
> solve it.
>
> I'm using:
> Apache 1.3.12 +
> ApacheJServ-1.1.1 +
> jdk 1.2 +
> jsdk 2.0 +
> mod_ssl-2.6.4-1.3.12 +
> openssl-0.9.5a
>
> in Read Hat Linux 6.2 .
>
> The application connects an applet with a servlet in
> order to make request and get responses of
> information.
> In order to increase the posibilities of the server
> (request being computing), when a request arrives to
> the servlet engine (ApJServ), the servlet pass it to a
> thread in order to get an answer (so thgew servlet can
> receive more requests from other applets). To know how
> to send it to the client, it also passes to the thread
> the OutputStream of the HttpServletResponse.
>
> The problem is that when the thread wants to send
> the answer (in a static method of the servelt), it
> writes to the output stream of the ServletResponse.
> But I get a "bad file descriptor", probably because
> the servlet engine has killed the process associated
> to that fd.
>
> I don't think it's an specific problem of Apache +
> JServ, isn't it? I've also tried with HttpSession
> but I haven't found anything.
>
> How can it be solved? is the only way to mantain the
> servlet waiting for the answer?
>
> Thanks for all
>
> Jesus Escanero
>
> _______________________________________________________________
> Do You Yahoo!?
> Consiga gratis su dirección @yahoo.es en http://correo.yahoo.es
>
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search Archives:
> <http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
