Re: Is cancelled SSL connection bug fixed in Tomcat 4.1.31?

2005-06-09 Thread Mark Thomas

Mike,

Having I have had a look at the bug report and the message from Tomcat 
user and have found the cvs commit that fixes the problem.


http://marc.theaimsgroup.com/?l=tomcat-devm=104142933517556w=2

This fix is included in 4.1.19 onwards and all 5.0.x and 5.5.x releases.

HTH,

Mark

Mike Meehan wrote:

Hi,

Does anyone out there know if the Cancelled SSL connection cause Tomcat
to stumble bug is fixed for Tomcat 4.1.31?


The bug can be found here:
http://issues.apache.org/bugzilla/show_bug.cgi?id=17323

I can reproduce this issue with 4.1.18 but have yet to be able to
reproduce it with 4.1.31.  I don't want to assume that its fixed simply
because I haven't been able to reproduce it.   I'm comparing the two
versions of Tomcat using the same: physical server, web app, connector
settings,  keystore. 


I also saw a mailing list thread
(http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg79212.htm
l) that suggests the problem is in PoolTcpEndPoint.java.  I looked at
this source and compared between the two versions.  The
TcpWorkerThread.runIt() method was significantly reworked since 4.1.18
so I can't tell for sure if the problem has been eliminated. (if this is
in fact where the problem existed)

If it has not been fixed in 4.1.31, can anyone confirm if this is fixed
in 5.0?

Thanks,
Mike





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Is cancelled SSL connection bug fixed in Tomcat 4.1.31?

2005-06-08 Thread Mike Meehan
Hi,

Does anyone out there know if the Cancelled SSL connection cause Tomcat
to stumble bug is fixed for Tomcat 4.1.31?

The bug can be found here:
http://issues.apache.org/bugzilla/show_bug.cgi?id=17323

I can reproduce this issue with 4.1.18 but have yet to be able to
reproduce it with 4.1.31.  I don't want to assume that its fixed simply
because I haven't been able to reproduce it.   I'm comparing the two
versions of Tomcat using the same: physical server, web app, connector
settings,  keystore. 

I also saw a mailing list thread
(http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg79212.htm
l) that suggests the problem is in PoolTcpEndPoint.java.  I looked at
this source and compared between the two versions.  The
TcpWorkerThread.runIt() method was significantly reworked since 4.1.18
so I can't tell for sure if the problem has been eliminated. (if this is
in fact where the problem existed)

If it has not been fixed in 4.1.31, can anyone confirm if this is fixed
in 5.0?

Thanks,
Mike