Thanks for the anwser, but:
- The servlet is not garbage collected. When I check it in the mornig, after all
night of inactivity, the servlet is active.
- Yesterday, I included a connection pooling class. Thus, the servlet re-starts
the connection.But I get a "connection reset by peer" error, when trying first
access. The second access works fine.
Any idea?
Regards,
Xavier
Randy Layman wrote:
> The answer is no - Tomcat knows nothing about your socket
> connections and therefore can't close them. A couple of things come to mind
> - first the Oracle drivers might be releasing the connection, check their
> documentation about this. Also, what is the behavior if your servlet is
> garbage collected? Could it be that your servlet is being garbage collected
> and therefore you are somehow half-way closing the connection?
>
> Randy
>
> -----Original Message-----
> From: Xavier Escandell [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 22, 2001 8:01 AM
> To: [EMAIL PROTECTED]
> Subject: Broken pipe error
>
> Hi:
> I get "broken pipe error" when trying to re-execute a servlet after
> several hours of innactivity. Then I must re-start Tomcat to get all
> running again.
> The servlet is connected to a database using oracle thin driver, these
> connection is still active.
> So my question is:
> It is possible that the socket between Tomcat and database is being
> closed by Tomcat?
> If the answer is yes, how can I configure these timeout.
>
> Regards.
> Xavier Escandell.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
