Note that there are some explanatory texts on larger screens.

plurals
  1. POHow do I connect to Weblogic JMS from Websphere server?
    text
    copied!<p>I created a small standalone client using: </p> <pre><code>weblogic.jndi.WLInitialContextFactory t3://weblogic-server:7001 jms.xyz.jmsXyzCf jms/xyz/jmsXyzLogQueue </code></pre> <p>And it works flawlessly.</p> <p>When a try to run the same code from my websphere server I get <code>NullPointerException</code>. I understand this happens because I don't have weblogic classes in the classpath: </p> <pre><code>Caused by: java.lang.NullPointerException at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:235) at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:327) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:357) at javax.naming.InitialContext.internalInit(InitialContext.java:295) at javax.naming.InitialContext.(InitialContext.java:212) </code></pre> <p>When I try to add them I get some "Security" errors </p> <pre><code>Current Java 2 Security policy reported a potential violation of Java 2 Security Permission. java.security.AccessControlException: Access denied (java.lang.RuntimePermission exitVM.0) at java.security.AccessController.checkPermission(AccessController.java:108) at java.lang.SecurityManager.checkPermission(SecurityManager.java:533) at com.ibm.ws.security.core.SecurityManager.checkPermission(SecurityManager.java:211) at java.lang.SecurityManager.checkExit(SecurityManager.java:745) at java.lang.Runtime.exit(Runtime.java:100) at java.lang.System.exit(System.java:297) </code></pre> <p>As last resource, I tried to connect using websphere own context factory: <code>com.ibm.websphere.naming.WsnInitialContextFactory</code> but of course it fails because it doesn't understand t3.</p> <p><strong>Question</strong></p> <p>How can I connect to a weblogic JMS from Websphere?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload