LDAP Driver 4.2.0.0 not working with Remote Loader Service

Today I upgraded both Remote Loader to 4.7.2 and the LDAp driver to version 4.2.0.0.

After the update of the driver any driver using the publisher cannot be started anymore. According to the trace file of the Remote Loader instance, the reson is that the ZoomDB cannot be initialized!

I guess the patch installer of the Remote Loader is missing something or there are mire manual tasks needed, than spelled out in the release notes of the driver!

DirXML: [06/04/19 11:31:05.94]: TRACE: DatabaseBuilder: Trying to instantiate DatabaseBuilder object from class 'com.microfocus.database.builder.ZoomDBBuilder'.
DirXML: [06/04/19 11:31:05.94]: TRACE: THM LDAP Driver: Could not initialize class com.microfocus.database.builder.ZoomDBBuilder
DirXML: [06/04/19 11:31:05.94]: TRACE: Remote Loader: PublicationShim.start() returned:
DirXML: [06/04/19 11:31:05.94]: TRACE: <nds dtdversion="2.0" ndsversion="8.x">
<source>
<product build="20190222_1226" instance="THM LDAP Driver" version="4.2.0.0">Identity Manager Driver for LDAP</product>
<contact>NetIQ Corporation</contact>
</source>
<output>
<status description="An unexpected error occurred in the publisher channel: Could not initialize class com.microfocus.database.builder.ZoomDBBuilder" level="fatal"/>
</output>
</nds>
DirXML: [06/04/19 11:31:05.94]:
DirXML Log Event -------------------
Driver = \IDM-TEST-TREE\thm\system\IDMDriverSet\THM LDAP Driver
Thread = Publisher
Level = fatal

I hope, that not other drivers using ZoomDB now are affected as well.

Kind regards,

Thorsten
Parents
  • I am guessing the version from which you upgraded used a JDBM/MapDB/ZoomDB
    version that may not be compatible anymore, and now the system will not
    start due to those seemingly-corrupt files. The files should have a
    GUID/UUID-like name, and with the Remote Loader (RL) stopped you can move
    them somewhere else and they will be recreated. This happens sometimes
    with upgrades, as other threads in here may show.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.
  • ab;2500512 wrote:
    I am guessing the version from which you upgraded used a JDBM/MapDB/ZoomDB
    version that may not be compatible anymore, and now the system will not
    start due to those seemingly-corrupt files. The files should have a
    GUID/UUID-like name, and with the Remote Loader (RL) stopped you can move
    them somewhere else and they will be recreated. This happens sometimes
    with upgrades, as other threads in here may show.

    --
    Good luck.

    If you find this post helpful and are logged into the web interface,
    show your appreciation and click on the star below.

    If you want to send me a private message, please let me know in the
    forum as I do not use the web interface often.


    Hello Aaron!

    I filed in an SR on this issue and since it was reproduceable M.F. created a defect on it!

    By the way: deleting the DB file did not solve the issue. But you are right it is reöated to the transition from MapDB to ZoomDB. For any reason the remote loder instance is not able to find the ZoomDB class even with the jar and so files available.

    So far threre seams to be no way to run the 4.2.0.0 version of the driver with a simple remote loader on Linux!

    Kind regards,

    Thorsten
  • We have the same issue and our setup is different in the following points:

    * without Remote Loader (running locally)
    * Windows

Reply Children