• Extlib on AIX issues

    By Jason Boulianne 1 decade ago

    Has anyone run into a issue running the extension library on AIX 1.6? We are trying to install the 8.5.3.20120605-0921 extlib on a AIX 1.6 server running Domino 8.5.3 FP2



    We have installed the extlib into the update site, added the ini parameter as we have on our windows machines but when http starts we get the following:



    10/03/2012 06:32:21 HTTP Server: Using Web Configuration View

    10/03/2012 06:32:23 JVM: Java Virtual Machine initialized.

    10/03/2012 06:32:23 HTTP Server: Java Virtual Machine loaded

    10/03/2012 06:32:23 HTTP Server: DSAPI Domino Off-Line Services HTTP extension Loaded successfully

    10/03/2012 06:32:23 Servlet engine initialization was successful

    10/03/2012 06:32:32 HTTP JVM: CLFAD0330I: NSF Based plugins are being installed in the OSGi runtime. For more information please consult the log

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:32 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:33 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:33 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:33 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:33 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:33 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:33 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:33 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:33 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:33 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:33 HTTP JVM: null. For more detailed information, please consult error-log-0.xml located in/domdata/domino/workspace/logs

    10/03/2012 06:32:34 XSP Command Manager initialized

    10/03/2012 06:32:35 HTTP Server: Started



    Checking the error-log-0.xml we get the following line over and over



    SEVERE

        <br/>
    

    com.ibm.domino.internal.protocol.osginsf.OSGiNSFUrlConnection



    getInputStream

    <br/>
    <br/>
    



    WARNING

        <br/>
    <br/>
    <br/>
    

    com.ibm.domino.internal.protocol.osginsf.OSGiNSFUrlConnection

    <br/>
    <br/>
    

    getInputStream





    We have checked the security for the db and the server and everything is properly configured





    as I have mentioned we have out windows server running the extension library on 8.5.3 just fine, it is just AIX running 8.5.3 FP2 thast is causing us headaches.



    Would FP2 on the AIX box be causing us issues?



    Any Help would be appreciated

    • not on AIX but see same error on local windows server

      By Jim Romaine 1 decade ago

      I don't an answer, but a suggestion perhaps?



      I have a local development windows machine that I am seeing the same errors on:



      com.ibm.domino.internal.protocol.osginsf.OSGiNSFUrlConnection

      com.ibm.domino.internal.protocol.osginsf.OSGiNSFUrlConnection



      that I am trying to resolve. The local machine has ext lib installed whereas a different replica had 8.5.3 UP1 on it. I don't know if that would cause this type of conflict, but will be something I will later check out as I get further along with resolving some of the other issues in my case.



      Good Luck.