waiting on a com.sun.jndi.ldap.LdapRequest

[Scott Battaglia]

We run LDAPS here at Rutgers and haven't experienced any problems.  We use
CAS 3.0.5 and Sun ONE's LDAP servers.

-Scott

On 8/31/07, Holger Koch <hoko at gmx.de> wrote:
>
> Scott Battaglia <scott.battaglia at ...> writes:
>
> It would appear that the LDAP server is not always responding to a read
> request. You can try setting a read timeout on the
> connection.
>
> Hi,
>
> maybe you are right:
>
> * but i configured a list with 3 different LDAP Server (1 Master, 2
> Slaves).
> These are very stable because they will be used for a lot of other
> application
> * the problem does not occured with LDAP
> * i see in the ldap log slapd.log the following if cas works right:
>
> daemon: conn=34682 fd=14 connection from IP=172.21.206.140:58462 (IP=::
> 636)
> accepted.
> conn=34682 op=0 BIND dn="CN=HOLGERKOCH,OU=APACHE_BAHNNET,O=DB AG,C=DE"
> method=128
> ber_flush: 14 bytes to sd 14
> conn=34682 op=0 RESULT tag=97 err=0 text=
> conn=34682 op=1 UNBIND
> conn=-1 fd=14 closed
>
> and the following if cas "hangs":
>
> daemon: conn=34683 fd=14 connection from IP=172.21.206.140:58963 (IP=::
> 636)
> accepted.
>
> * here is the communication, that i see with tcpdump:
>
> nagoya.unix.db.de is the CAS server
> gtest3.unix.db.de is the LDAP test server (for this test i configured only
> one
> ldap server)
>
>
> nagoya.unix.db.de -> gtest3.unix.db.de TCP D=636 S=44409 Syn
> Seq=2388477971
> Len=0 Win=5840 Options=<mss 1460,sackOK,tstamp 528982942 0,nop,wscale 0>
> gtest3.unix.db.de -> nagoya.unix.db.de TCP D=44409 S=636 Syn
> Ack=2388477972
> Seq=500357282 Len=0 Win=24616 Options=<nop,nop,tstamp 487831210
> 528982942,nop,wscale 0,nop,nop,sackOK,mss 1460>
> nagoya.unix.db.de -> gtest3.unix.db.de TCP D=636 S=44409     Ack=500357283
> Seq=2388477972 Len=0 Win=5840 Options=<nop,nop,tstamp 528982942 487831210>
> nagoya.unix.db.de -> gtest3.unix.db.de TCP D=636 S=44409     Ack=500357283
> Seq=2388477972 Len=110 Win=5840 Options=<nop,nop,tstamp 528982943
> 487831210>
> gtest3.unix.db.de -> nagoya.unix.db.de TCP D=44409 S=636
> Ack=2388478082
> Seq=500357283 Len=0 Win=24616 Options=<nop,nop,tstamp 487831210 528982943>
> gtest3.unix.db.de -> nagoya.unix.db.de TCP D=44409 S=636
> Ack=2388478082
> Seq=500357283 Len=122 Win=24616 Options=<nop,nop,tstamp 487831210
> 528982943>
> nagoya.unix.db.de -> gtest3.unix.db.de TCP D=636 S=44409     Ack=500357405
> Seq=2388478082 Len=0 Win=5840 Options=<nop,nop,tstamp 528982944 487831210>
> nagoya.unix.db.de -> gtest3.unix.db.de TCP D=636 S=44409     Ack=500357405
> Seq=2388478082 Len=6 Win=5840 Options=<nop,nop,tstamp 528982945 487831210>
> gtest3.unix.db.de -> nagoya.unix.db.de TCP D=44409 S=636
> Ack=2388478088
> Seq=500357405 Len=0 Win=24616 Options=<nop,nop,tstamp 487831210 528982945>
> nagoya.unix.db.de -> gtest3.unix.db.de TCP D=636 S=44409     Ack=500357405
> Seq=2388478088 Len=124 Win=5840 Options=<nop,nop,tstamp 528982945
> 487831210>
> gtest3.unix.db.de -> nagoya.unix.db.de TCP D=44409 S=636
> Ack=2388478212
> Seq=500357405 Len=0 Win=24616 Options=<nop,nop,tstamp 487831221 528982945>
>
>
> The last package is send from the ldap server to the cas server. I wait 5
> minutes. There are no resends of some tcp packages or something. It seems
> to me
> that the cas server don't send the query. If it works, there a nearly
> double
> count of packages.
>
>
> I've tried to install cas3.0.7 and 3.1 with jdk-1.5.0_10, jdk-1.5.0_12 and
> tomcat-5.5.17, tomcat-5.5.23. Always the same problem.
>
>
> best regards
>
> Holger Koch
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>



-- 
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20070903/1c1af00b/attachment.html