[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Strange error LDAP Server Down (80)

Thanks ryanb for your kind response. I will definately check your

Let me tell my problem more in detail so probably you can throw more light.

I am using java servlets to access LDAP and I am using iPlanet web server
on which secure certificate is installed. I have development env. and
production env. on both these env. are similar in config.  (as per my
network admin)

Now application which is running on development env. never faced this
problem it is working completely fine without SERVER_DOWN error but in
production env. only I am getting this error. More strange is if error
comes and I refresh the page it goes.

What are your comments?



                      m (Ryan Barton)          To:       manoj.b.mane@Cummins.com                          
                                               cc:       OpenLDAP-software@OpenLDAP.org                    
                      01/15/03 07:30 PM        Subject:  Re: Strange error LDAP Server Down (80)           

manoj.b.mane@Cummins.com wrote:

>Sometimes whenver there is any kind of  LDAP operation my java programs
>throws error saying is server down(80) when actually server is not down.
>and this error is very unpredictable sometime it comes and sometime it
>does  not come. anybody faced similar kind of problem before  please let
>know if so.


Assuming that you've done the dilligence of checking the access log and
the like, this is probably not an OpenLDAP issue, but more of a Java
library issue.  If you are using connection pooling, you may be running
into connections that are falling off because of TCP timeouts or whatnot
(your app has opened a certain number of connections to the directory
server, but doesn't use them for "X" amount of time).  You can work
around the problem by either checking the connection your app will be
using, and making sure it is "live" before actually letting the app use
it, or change what you're using for connection pooling.  We've run into
this problem with the 4.16 versions and older of the Netscape Java SDK
(forthcoming versions fix this problem, and your application is assured
a "live" connection every time).

I'm making lots of assumptions here, but in the face of little
information, lots of assumptions are usually the inevitable product.


This e-mail transmission and any attachments to it are intended solely for
the use of the individual or entity to whom it is addressed and may contain
confidential and privileged information.  If you are not the intended
recipient, your use, forwarding, printing, storing, disseminating,
distribution, or copying of this communication is prohibited.  If you
received this communication in error, please notify the sender immediately
by replying to this message and delete it from your computer.