Skip to Main Content

Java HotSpot Virtual Machine

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Problem calling Cipher AES algorithm in AIX JDK 1.6 (32 Bit)

843829Jun 23 2010 — edited Jun 28 2010
I am calling Cipher AES algorithm from my C++ code. I'm using Java invocation interface to invoke JVM through C++.
The same code runs fine with JDK 1.6 for 64 bit, But throws exceptions with 32 bit JDK.

EXCEPTION 1:
Exception in thread "Attach handler" java.lang.NullPointerException
at com.ibm.tools.attach.javaSE.IPC.releaseMasterLock(IPC.java:385)
at com.ibm.tools.attach.javaSE.AttachHandler.createIpcDir(AttachHandler.java:314)
at com.ibm.tools.attach.javaSE.AttachHandler.initialize(AttachHandler.java:295)
at com.ibm.tools.attach.javaSE.AttachHandler.run(AttachHandler.java:147)


EXCEPTION 2:
Exception in thread "main" java.lang.UnsatisfiedLinkError: net (A file or directory in the path name does not exist.)
at java.lang.ClassLoader.loadLibraryWithPath(ClassLoader.java:1007)
at java.lang.ClassLoader.loadLibraryWithClassLoader(ClassLoader.java:971)
at java.lang.System.loadLibrary(System.java:470)
at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:69)
at java.security.AccessController.doPrivileged(AccessController.java:202)
at java.net.InetAddress.<clinit>(InetAddress.java:218)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at javax.crypto.b.e(Unknown Source)
at javax.crypto.b.a(Unknown Source)
at javax.crypto.b.access$500(Unknown Source)
at javax.crypto.b$0.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:251)
at javax.crypto.b.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at javax.crypto.Cipher.getInstance(Unknown Source)

EXCEPTION 1 could be removed by setting the system property com.ibm.tools.attach.enable=no, but I suspect in this situation we need the AttachHandler exception to get resolved completely to get over the second exception. Please clarify the same if I'm wrong, and also hint the possible solution.

Thanks
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 26 2010
Added on Jun 23 2010
7 comments
623 views