LDAP Connection exceptions in Clarity version 14.2

[Anon Anon]

We have a custom java job in clarity that makes LDAP connection to Active Directory and then updates resources in clarity. When we run this job in clarity version 13.0.1 it is working fine with no java exceptions in job log. But when we run the same job in clarity version 14.2 and check the job logs it shows many exceptions during LDAP read phase. The other parts of code are working fine except ldap read part. Clarity v13.0.1 has java 1.6 and Clarity v14.2 has java 1.7  So for clarity 14.2 we compiled the code in java 1.7 and for clarity 13.0.1 we compiled it in java 1.6.

 

What can be possible reason for the same code throwing exceptions in new 14.2 version of clarity.

 

Regards,

Ankur

[Uruj]

Hi Ankur,

 

What I understood is that there are few exceptions that are appearing and otherwise it is working as desired. Could you please share the list of exceptions that you are receiving.

 

Regards,

Uruj

[Anon Anon]

Hi Uruj,

 

Following exceptions are thrown:

1) NullPointerException on NamingEnumeration object.

2) javax.namimg.PartialResultException

 

Regards,

Ankur

[Suman Pramanik]

Hi Ankur

 

There is an out of the box job for LDAP sync, I am trying to understand the need for custom job? If the Job is throwing exception then you need to debug the Java code and see why its throwing an exception. Also you can put an trace on the job to see if you get some clues

 

Regards

Suman Pramanik 

 

[Anon Anon]

Hi Suman,

 

We checked the java code and it is working correctly in clarity version 13.0.1 and clarity version 13.3 .Clarity 13.3 also uses java 1.7 like clarity 14.2.

We are getting these exceptions in clarity 14.2 only.

 

Regards,

Ankur

[Nick Darlington]

As SumanPramanik says, and as I replied to a similar thread here: Java Job Error

 

A java developer that owns/maintains this source code needs to debug it to ascertain the cause and solution.

 

Certainly a change in 3rd party libraries (and the JDK is itself a collection of libraries) requires the testing and updating of source code to become compliant and operate correctly prior to upgrade and use on a production environment.  The scope of what could change between one version and the next is considerable, but the testing should uncover the main issues and the job code can then be updated accordingly.