Issue 1895 - Session Resumption problems with JSSE-OpenLDAP
Summary: Session Resumption problems with JSSE-OpenLDAP
Status: VERIFIED FIXED
Alias: None
Product: OpenLDAP
Classification: Unclassified
Component: slapd (show other issues)
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: OpenLDAP project
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-18 12:40 UTC by thomas.maesing@gmx.de
Modified: 2014-08-01 21:05 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description thomas.maesing@gmx.de 2002-06-18 12:40:45 UTC
Full_Name: Guest User
Version: 2.0.23
OS: Redhat 7.3 Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (195.145.160.217)


Hi,
I have problems with JNDI and Openldap inside a Realm of Tomcat 4 using SSL. 
There has also been a discussion due to this problem on the software list.The
following happens:

1. JNDI has established a connection.

2. This connection is closed. Then a new connection is opened.

3. Then the system hangs.

4. After shutdown of Openldap I get a  Exception performing authentication
javax.naming.CommunicationException: Request: 1cancelled
    at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:47),

sometimes I get a socket closed Exception instead.

5. Openldap sends warning messages for open TLS connections to be closed.

6. Tomcat recovers and works fine.

So it seems that indeed Openldap doesn�t dropp the TCP Connection correctly.

The log files, the java Class and the tomcat configuration are attached. It
should
be no problem fast to install Tomcat 4.0.3 and test the realm. If you need more
information please contact me. 

Best regards

Thomas 

Comment 1 thomas.maesing@gmx.de 2002-06-19 11:04:16 UTC
Hi,

I have copied the relevant files to
"ftp.openldap.org/incoming/resumption_problem.tgz".
If you need further information please contact me.

Best regards

Thomas

> 
> *** THIS IS AN AUTOMATICALLY GENERATED REPLY ***
> 
> Thanks for your report to openldap-its@OpenLDAP.org.  Your report
> has been placed into our Issue Tracking System and has been assigned
> the tracking number ITS#1895.
> 
> One of our support engineers will look at your report in due course.
> Note that this may take some time because our support engineers
> are volunteers.  They only work on OpenLDAP when they have spare
> time.
> 
> If you need to provide additional information in regards to your
> issue report, you may do so by replying to this message.  Note that
> any mail sent to openldap-its@openldap.org with (ITS#1895)
> in the subject will automatically be attached to the issue report.
> 
> 	mailto:openldap-its@openldap.org?subject=(ITS#1895)
> 
> You may follow the progress of this report by loading the following
> URL in a web browser:
>     http://www.OpenLDAP.org/its/index.cgi?findid=1895
> 
> Please remember to retain your issue tracking number (ITS#1895)
> on any further messages you send to us regarding this report.  If
> you don't then you'll just waste our time and yours because we
> won't be able to properly track the report.
> 
> Please note that the Issue Tracking System is not intended to
> be used to seek help in the proper use of OpenLDAP Software.
> Such requests will be closed.
> 
> OpenLDAP Software is user supported.
> 	http://www.OpenLDAP.org/support/
> 
> --------------
> Copyright 2002 The OpenLDAP Foundation, All Rights Reserved.
> 

-- 
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net

Comment 2 Howard Chu 2002-09-03 19:13:30 UTC
This is a known bug in Sun's JSSE implementation. See
http://www.openldap.org/lists/openldap-software/200202/msg00383.html for a
workaround. As this is not an OpenLDAP bug, this issue will be closed.
Comment 3 Howard Chu 2002-09-03 19:13:55 UTC
changed notes
changed state Open to Feedback
Comment 4 Kurt Zeilenga 2002-09-19 15:30:33 UTC
changed state Feedback to Closed
Comment 5 Howard Chu 2004-12-06 01:34:06 UTC
moved from Incoming to Archive.Incoming
Comment 6 OpenLDAP project 2014-08-01 21:05:40 UTC
Sun JSSE bug