Re: [Bodington-developers] More LDAP Fun and Games

> hadn't been distracted by just trying to get
> message through at all
yes, I can sympathise with you there. The sf sites/lists are going to pot=
.

> the main problem that
> prompted the posting has been resolved and the Novell API is not to
> blame
Can you tell us what the original problem was Jon? First of all it was al=
l
chaos and doom in the openldap api. Now it's not. It was only yesterday
that you said a switch to jndi was essential. Now it's not?

Sounds like you may have sorted a problem with ad interfacing - would be
nice to know what it was.

What do you get if you turn on java.net.debug=3Dall?
Are you using sasl/tls etc?

> I can supply the test program to anyone who would
> like to give a go.
go on then, mail it to the list.

--=20
Alistair Young
Senior Software Engineer
UHI@Sabhal M=F2r Ostaig
Isle of Skye
Scotland

>
> O.K. the original problem we had was pinned down and resolved. (Would
> have told you earlier if I hadn't been distracted by just trying to get
> message through at all.) By that time I had rewritten the code to use
> the JNDI API but I'm pretty sure that we could have got the Novell code
> to stop throwing the exceptions we observed.  However, I'm still alarme=
d
> by the results of the test we ran outside of Bodington....
>
> The loop was connecting, making a search for the DN of a record matchin=
g
> a given user name and disconnecting. I put Thread.currentThread.sleep()
> between every API call and at the end of the main loop. Although a dela=
y
> of a whole second between API calls reduced the rate of exceptions to
> less than one in several hundred cycles they didn't go away completely.
> The thing that really bothers me is that none of the exceptions thrown
> resulted in a meaningful error condition or result message in the
> application itself - just nasty looking stack traces uncontrollably
> pumped out to standard error by the Novell API worker threads. That sor=
t
> of thing should NEVER happen in a well written API - if there is an
> error condition it ought to be signaled properly to the application
> level. The test was carried out using my laptop as the client (plugged
> into the campus ethernet) and about three of the Active Directory
> servers on campus. I can supply the test program to anyone who would
> like to give a go.
>
> To repeat the key finding since my last posting - the main problem that
> prompted the posting has been resolved and the Novell API is not to
> blame but we have an inexplicable problem occurring in a test scenario
> which reduces my confidence in the Novell solution.  So far the JNDI
> distributed with JDK 1.5 works fine with Active Directory although I
> haven't yet subjected it to the testing under load that we tried on the
> Novell API.
>
>
>
> -----------------------------------------------------------------------=
--
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>