2877176 - NoClassDefFoundError is raised when trying to connect to WebLogic with T3S in the JMS Adapter

You are trying to connect to a WebLogic JMS Queue using the JMS Adapter in PI/PO. However, when setting the T3S protocol in the Server Address, the following error is raised when trying to send a message:

[EXCEPTION]
java.lang.NoClassDefFoundError: com/rsa/jsafe/JSAFE_InvalidUseException
at weblogic.security.SSL.SSLClientInfo.getSSLSocketFactory(SSLClientInfo.java:101)
at weblogic.socket.ChannelSSLSocketFactory.getSocketFactory(ChannelSSLSocketFactory.java:185)
at weblogic.socket.ChannelSSLSocketFactory.createSocket(ChannelSSLSocketFactory.java:77)
at weblogic.socket.ChannelSSLSocketFactory.createSocket(ChannelSSLSocketFactory.java:119)
at weblogic.socket.BaseAbstractMuxableSocket.createSocket(BaseAbstractMuxableSocket.java:135)
at weblogic.rjvm.t3.MuxableSocketT3.newSocketWithRetry(MuxableSocketT3.java:214)
at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:383)
at weblogic.rjvm.t3.ConnectionFactoryT3S.createConnection(ConnectionFactoryT3S.java:44)
at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1792)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1424)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:443)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:260)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:165)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:64)
at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:45)
at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
at javax.naming.InitialContext.init(InitialContext.java:244)
at javax.naming.InitialContext.<init>(InitialContext.java:216)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:66)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doBeforeConnect(JndiConnectorImpl.java:51)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:245)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:229)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:423)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:180)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:987)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: java.lang.ClassNotFoundException: com.rsa.jsafe.JSAFE_InvalidUseException
------------------------- Loader Info -------------------------
ClassLoader name: [library:com.sap.aii.adapter.lib]
Loader hash code: 1b53e1ae
Living status: alive
Direct parent loaders:
[system:Frame]
[library:engine.j2ee14.facade]
Resources:
/usr/sap/<SID>/<INSTANCE_ID>/j2ee/cluster/bin/ext/com.sap.aii.adapter.lib/lib/sqljdbc42.jar
/usr/sap/<SID>/<INSTANCE_ID>/j2ee/cluster/bin/ext/com.sap.aii.adapter.lib/lib/wlfullclient.jar
---------------------------------------------------------------
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:280)
at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:249)
... 43 more

• SAP NetWeaver
• SAP Process Integration

Web, Logic, WebLogic, Oracle, T3, T3S, JNDI, User, JSAFE_InvalidUseException, InvalidUseExceptionProcess, wlfullclient, wlfullclient.jar, wlthint3client, wlthint3client.jar JMS, Queue, Integration, PI, Process Orchestration, PO, NetWeaver, XI, AEX, SSL , KBA , BC-XI-CON-JMS , JMS Adapter , How To