Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unsatisfied Link Error : no jsafe in java.library.path

2 views
Skip to first unread message

sirigiri sreedhar

unread,
Apr 26, 2001, 4:31:05 AM4/26/01
to

Hi,
When I try to connect to the server securily through a java program (t3s://localhost:7002),I
get the Unsatisfied Link Error: no jsafe in java.library.path(the stack trace
is at the end of this post). I've included all the weblogic jar files(including
lib\weblogicaux.jar) in the classpath at runtime with -classpath command line
option.I've also tried to run the program with
"-Djava.library.path=D:\weblogic\lib\weblogicaux.jar" commandline option to no
avail.Is there something I'm missing?
Any suggestion or help would be appreciated.Hoping for a speedy reply

Regards,
Sreedhar

"here is the stack trace"

java.lang.UnsatisfiedLinkError: no jsafe in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
at java.lang.Runtime.loadLibrary0(Runtime.java:749)
at java.lang.System.loadLibrary(System.java:820)
at
COM.rsa.jsafe.JSAFE_DeviceBuilderNative.buildObjects(JSAFE_DeviceBuilderNati
ve.java)
at
COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(JSAFE_AsymmetricCipher.java
)
at
COM.rsa.jsafe.JSAFE_AsymmetricCipher.getInstance(JSAFE_AsymmetricCipher.java
)
at weblogic.security.RSA.performOPJSafe(RSA.java:178)
at weblogic.security.RSA.performOp(RSA.java:104)
at weblogic.security.RSApkcs1.decrypt(RSApkcs1.java:153)
at weblogic.security.RSAMDSignature.verify(RSAMDSignature.java:87)
at weblogic.security.X509.verifySignature(X509.java:223)
at weblogic.security.X509.verify(X509.java:152)
at weblogic.security.SSL.SSLCertificate.verify(SSLCertificate.java:128)
at weblogic.security.SSL.SSLCertificate.input(SSLCertificate.java:107)
at weblogic.security.SSL.Handshake.input(Handshake.java:109)
at weblogic.security.SSL.SSLSocket.getHandshake(SSLSocket.java:928)
at weblogic.security.SSL.SSLSocket.clientInit(SSLSocket.java:343)
at weblogic.security.SSL.SSLSocket.initialize(SSLSocket.java:217)
at weblogic.security.SSL.SSLSocket.<init>(SSLSocket.java:170)
at weblogic.socket.JVMSocketT3S.newSocket(JVMSocketT3S.java:29)
at weblogic.socket.JVMSocketT3.newSocketWithRetry(JVMSocketT3.java:275)
at weblogic.socket.JVMSocketT3.connect(JVMSocketT3.java:59)
at weblogic.socket.JVMAbbrevSocket.connect(JVMAbbrevSocket.java:160)
at weblogic.socket.JVMSocketManager.create(JVMSocketManager.java:294)
at
weblogic.rjvm.ConnectionManager.findOrCreateSocket(ConnectionManager.java:91
8)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:339)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:306)
at
weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:248)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:219)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:186)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:200)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:195)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:148)
at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java:123)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:668)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at
com.cbmx.test.ClientTreeModel.getInitialContext(ClientTreeModel.java:169)
at com.cbmx.test.ClientTreeModel.<init>(ClientTreeModel.java:36)
at com.cbmx.test.Frame1.<init>(Frame1.java:13)
at com.cbmx.test.Application1.<init>(Application1.java:11)
at com.cbmx.test.Application1.main(Application1.java:42)


Giri Alwar

unread,
Apr 26, 2001, 5:44:41 PM4/26/01
to
I assume your are running on a Unix platform? If so, it looks like you don't
have the native implementation file from the vendor (usually a shared
library file with a ".so" extension) in your LD_LIBRARY_PATH environment
variable.
Giri

"sirigiri sreedhar" <siri...@mascotsystems.com> wrote in message
news:3ae7ceb9$1...@newsgroups.bea.com...

0 new messages