N can only be sent after any pending data.
EJP
-Original Message-
From: Vincent Goelen [mailto:goel...@gmail.com]
Sent: Tuesday, 18 December 2012 3:52 AM
To: Tomcat Users List
Subject: Re: Tomcat 7 SSL Session ID
If you run the test.jsp page.. When you send a request and interrupt it
> Martin
> __ Please do not alter or
> otherwise disrupt this communication..thank you
> > Date: Mon, 17 Dec 2012 09:47:09 +0100
> > Subject: Re: Tomcat 7 SSL Session ID
> > From: goel...@gmail.com
> > To: users@tomcat.
this communication..thank you
> Date: Mon, 17 Dec 2012 09:47:09 +0100
> Subject: Re: Tomcat 7 SSL Session ID
> From: goel...@gmail.com
> To: users@tomcat.apache.org
>
> Hey,
>
> http://users.telenet.be/goelenv/SSLTomcat.zip
>
> in this link you can find a netbeans
Hey,
http://users.telenet.be/goelenv/SSLTomcat.zip
in this link you can find a netbeans project that will generate the fault..
The index.html page will send requests to the index.jsp page, the thread
sleep is just to emulate a long process of a request (like database things,
etc)
Kind regards,
V
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 12/10/12 10:22 AM, Martin Gainty wrote:
> we need to get your architect into this discussion
>
> Why is your code implementing 2 different Connections to
> accomplish this functionality when one Connection at a time will
> suffice?
You
.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
> Date: Mon, 10 Dec 2012 14:48:30 +0100
> Subject: Re: Tomcat 7 SSL Session ID
> From: goel...@gmail.com
> To: users@tomcat.apache.org
>
> There are no 2 different webapps
formation seulement et n'aura
> 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: Thu, 6 Dec 2012 11
uppose it is plausible that SSL discards it
> > on security grounds because of the broken connection.
> >
> > EJP
> >
> > _
> >
> > From: Vincent Goelen [mailto:goel...@gmail.com]
> > Sent: Wednesday, 5 December 2012 9:19 PM
> > To: Esmond Pitt
ption would have been thrown.
>
> Re loss of the SSL session, I suppose it is plausible that SSL discards it
> on security grounds because of the broken connection.
>
> EJP
>
> _
>
> From: Vincent Goelen [mailto:goel...@gmail.com]
> Sent: Wednesday, 5 December 2012
thrown.
Re loss of the SSL session, I suppose it is plausible that SSL discards it
on security grounds because of the broken connection.
EJP
_
From: Vincent Goelen [mailto:goel...@gmail.com]
Sent: Wednesday, 5 December 2012 9:19 PM
To: Esmond Pitt
Subject: Re: Tomcat 7 SSL Session ID
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 12/5/12 2:49 AM, André Warnier wrote:
> Esmond Pitt wrote:
>> Broken pipes don't invalidate the SSL session. They just break
>> the TCP connection. The SSL session persists, across multiple TCP
>> connections, until it is specifically invali
2012 11:27 AM
To: Tomcat Users List; goel...@gmail.com
Subject: RE: Tomcat 7 SSL Session ID
yes but he needs to achieve a reliable connection between himself and the
SSLServer (at least until key negotiation has completed) broken pipe(s) are
a bear to debug but you have a few tools available to
Esmond Pitt wrote:
Broken pipes don't invalidate the SSL session. They just break the TCP
connection. The SSL session persists, across multiple TCP connections, until
it is specifically invalidated by someone: for example, timed out by the
SSLSessionContext.
Ah. That would explain some other (
nhalt uebernehmen.
> From: esmond.p...@bigpond.com
> To: goel...@gmail.com; users@tomcat.apache.org
> Subject: RE: Tomcat 7 SSL Session ID
> Date: Wed, 5 Dec 2012 09:57:38 +1100
>
> Broken pipes don't invalidate the SSL session. They just break the TCP
> connection. Th
:goel...@gmail.com]
Sent: Wednesday, 5 December 2012 1:15 AM
To: Tomcat Users List
Subject: Re: Tomcat 7 SSL Session ID
Hey,
thanks for the help!
To be clear, I do not want a 0ms timeout... I'm doing research about how
"usable" the SSL session tracking option is for session management.
Thanks again for the fast response, sorry for being unclear about some
parts.. First time using the mailing list
I'm using Apache Tomcat Version 7.0.32 on a mac os x 10.7.5, I've tested it
on linux Virtual machine too, got same problems. I'm using JDK 1.6 (don't
think it has any importance here)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent,
On 12/4/12 9:15 AM, Vincent Goelen wrote:
> To be clear, I do not want a 0ms timeout... I'm doing research
> about how "usable" the SSL session tracking option is for session
> management... With the standard settings it seems very unstable t
Hey,
thanks for the help!
To be clear, I do not want a 0ms timeout... I'm doing research about how
"usable" the SSL session tracking option is for session management...
With the standard settings it seems very unstable to me, when sending alot
of parallel requests I get a broken socket error inva
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Vincent,
On 11/28/12 3:14 AM, Vincent Goelen wrote:
> When the keepAliveTimeout is not set to "0" I can see in the SSL
> debug logs the SSL session get's invalidated after some requests
> with a Broken Pipe exception. Is this because there are too man
Hey,
I'm doing some research about the SSL session tracking / SSL Session id's.
Now I'm having some problems when requests are send to the server in quick
succession, I notice the problem is fixed or at least less occuring when
the keepAlive server setting is set to 0..
When the keepAliveTimeout
20 matches
Mail list logo
