Domino on Linux/Unix, Troubleshooting, Best Practices, Tips and more ...

 
alt

Daniel Nashed

 

    Deadlock on Serverstartup with certain Extension Managers in Domino 8.5.1

    Daniel Nashed  26 November 2009 00:02:45

    There has been some confusion about this issue which has been posted in Ulrich's blog (http://www.eknori.de/2009-11-13/disable_log_dbgroup/)

    Multiple ISVs including myself contacted Ulrich offline about the info he got from another ISV and it turned out that this issue only affects some very specific Extension-Managers.

    After checking with support we finally got clarification published in the following TN (http://www.ibm.com/support/docview.wss?&uid=swg21410986).
    The problem occurred due to optimization some very specific optimization in low level Domino code.

    I have been in touch with a coulple of ISVs who ran into this issue to check what actually caused this issue.
    The problem seem mainly to occur when Extension-Managers use NSF or other C-API calls in the init phase of the DLL (MainEntryPoint).
    The C-API documentation states that no C-API calls are allowed in this routine but many applications use calls in this area.

    What is interesting is that other business partners suffer from the issue when another partner's Extension Manager is installed.

    The suggested Notes.ini entry mentioned in the TN (DISABLE_LOG_DBGROUP=1) is a work-around which causes the old not optimized behavior until the application is changed.
    IBM is working on another fix for 8.5.2 which hopefully solves this issue.

    But this clearly is one of the good examples why we should do only what the C-API states as supported (features vs. behaviors).

    On the other side this shows that IBM still tries to help customers and ISVs to get their applications working.

    Let me know what you think about this ...

    -- Daniel

    Links

      Archives


      • [HCL Domino]
      • [Domino on Linux]
      • [Nash!Com]
      • [Daniel Nashed]