[kepler-dev] JNI problem?

Christopher Brooks cxh at eecs.berkeley.edu
Wed Nov 10 15:57:26 PST 2004

I think the problem has to do with the Assemble Java Cryptography
Extension (JCE)

 Important: The first time any class inside the JAR file is access
 through an application, a special loader class inside
 the JAR will automatically check if the file MSKeyStoreJNI.dll
 can be found in any directory listed in your operating system
 environment variable PATH.  If the DLL cannot be found, the loader
 will automatically  extract the DLL from the jar and copy it into 
 the directory specified by the environment variable SYSTEMROOT or
 WIDIR (usually c:\winnt or c:\windows)

There is more text about not removing the dll and about how you can
extract the dll from the jar file by hand and put it in your path.

What I think is happening is that the class loader is trying to
modify C:\WINDOWS\MSKeyStoreJNI.dll but that .dll is in use already.

This could be a bad interaction between the Python actor trying
to load the Assembla JCE jar file and cache something.



    Jagan and I have been trying to build Kepler on his pc.
    The same version of Kepler works for me while his throws the error 
      [echo] java.library.path=c:/WINDOWS/system32
         [java] *sys-package-mgr*: processing modified jar, 
         [java] Error during initialisation of Assembla JCE provider 
         [java] Message is:
         [java] C:\WINDOWS\MSKeyStoreJNI.dll (The process cannot access the 
    file bec
    ause it is being used by another process)
         [java] Exiting...
    So the compile is successful but this error is thrown when the jars are 
    being processed.
    Does anyone have any idea why we get this error? Is it a problem 
    related jni?
    Thanks on advance,
    kepler-dev mailing list
    kepler-dev at ecoinformatics.org

More information about the Kepler-dev mailing list