gt;> pas n'importe quel effet légalement obligatoire. Étant donné que les email
>> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
>> aucune responsabilité pour le contenu fourni.
>>
>>
>>
>>
>>
>>> Date:
l effet légalement obligatoire. Étant donné que les email
> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
> aucune responsabilité pour le contenu fourni.
>
>
>
>
> > Date: Sat, 19 Sep 2009 20:27:25 -0400
> > Subject: Re: Does tomcat log closed connect
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> Date: Sat, 19 Sep 2009 20:27:25 -0400
> Subject: Re: Does tomcat log closed connection
> From: jithu.m...@
And the communication is done on the SSL port 8443.
On Sat, Sep 19, 2009 at 8:26 PM, jithu mada wrote:
> Hi David,
>
> these are the connector elements we have in our server.xml file
>
>
> maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
>enableLook
Hi David,
these are the connector elements we have in our server.xml file
The client is a .NET client here is the sequence of communication before the
connection is closed
1) The client sends a request to our application to create a session.
2) Tomcat sees the client is not log
jithu mada wrote:
> Hi,
>
> I am using Tomcat 5.0.27 on AIX.
>
> Its abruptly closing a connection after processing a user request
> successfully.
>
> Wanted to know does it log anywhere why is it closing the connection or do
> we need to change any settings to make it log closed connections.
>
> T
