Re: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-25 Thread Ognjen Blagojevic
André, On 25.2.2013 14:53, André Warnier wrote: Yes, but as soon as Tomcat would try to write to (or read from) that connection, it would immediately get an error, no ? So to say that in the meantime "tomcat keeps on trying" one of these connections doesn't seem to fit, or ? In regular situat

Re: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-25 Thread André Warnier
Ognjen Blagojevic wrote: André, On 25.2.2013 10:34, André Warnier wrote: So, on the face of it, there seems to be a contradiction between you saying on the one hand that the LDAP server closes the connection, and on the other hand that netstat shows the connection still being active. TCP conn

Re: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-25 Thread Ognjen Blagojevic
André, On 25.2.2013 10:34, André Warnier wrote: So, on the face of it, there seems to be a contradiction between you saying on the one hand that the LDAP server closes the connection, and on the other hand that netstat shows the connection still being active. TCP connection is established unti

RE: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-25 Thread Tanmoy Chatterjee
: Question regarding JNDIRealm - tomcat 6.0.35 Tanmoy Chatterjee wrote: > We are not using openldap but eDirectory. Unfortunately we do not have access > to the ldap configurations...only information we have is that after about 2 > mins of idle connection, ldap drops the same from its

Re: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-25 Thread André Warnier
Tanmoy Chatterjee wrote: We are not using openldap but eDirectory. Unfortunately we do not have access to the ldap configurations...only information we have is that after about 2 mins of idle connection, ldap drops the same from its side. Bit if we see in app server side using netstat, we can

RE: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-25 Thread Tanmoy Chatterjee
@gmail.com] Sent: Wednesday, February 20, 2013 3:15 PM To: Tomcat Users List Subject: Re: Question regarding JNDIRealm - tomcat 6.0.35 2013/2/20 Tanmoy Chatterjee : > Thanks Cédric, I will try this and let you know. > Once Ldap closes the connection from it's end, tomcat indeed keeps on

Re: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-20 Thread Cédric Couralet
2013/2/20 Tanmoy Chatterjee : > Thanks Cédric, I will try this and let you know. > Once Ldap closes the connection from it's end, tomcat indeed keeps on trying > and finally establishes a new connectionbut the time spent in retrying > is too high (more than 4-5 minutes) and in that time...us

RE: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-20 Thread Tanmoy Chatterjee
--Original Message- From: Cédric Couralet [mailto:cedric.coura...@gmail.com] Sent: Wednesday, February 20, 2013 1:05 PM To: Tomcat Users List Subject: Re: Question regarding JNDIRealm - tomcat 6.0.35 2013/2/20 Tanmoy Chatterjee : > Hello Cédric, > The reason I want to do is as follows: &

Re: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-20 Thread Cédric Couralet
2013/2/20 Tanmoy Chatterjee : > Hello Cédric, > The reason I want to do is as follows: > I am facing the problem already expressed in > https://issues.apache.org/bugzilla/show_bug.cgi?id=33774 > I see that the bug status shows as Fixed, however I still get the same Issue > on the Stack mentioned

RE: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-20 Thread Tanmoy Chatterjee
ions on startup. Thanks -Original Message- From: Cédric Couralet [mailto:cedric.coura...@gmail.com] Sent: Wednesday, February 20, 2013 10:57 AM To: Tomcat Users List Subject: Re: Question regarding JNDIRealm - tomcat 6.0.35 2013/2/19 Tanmoy Chatterjee : > Hello, > Technical S

Re: Question regarding JNDIRealm - tomcat 6.0.35

2013-02-20 Thread Cédric Couralet
2013/2/19 Tanmoy Chatterjee : > Hello, > Technical Stack: Apache Tomcat v 6.0.35 > OS : RHEL 5.3 64 bits > java version "1.6.0_18" 32 bits > > I am using Realm className="org.apache.catalina.realm.JNDIRealm" for > connecting to LDAP. > > Is there any configuration to prevent the default connection