1 Reply Latest reply on Aug 31, 2014 2:03 AM by joshwaj

    Issue when putting message in WAS Queue from JBOSS eap 6.0.

    joshwaj

      Hi All,

       

               I trying to put the JMS message to WAS8.5 from JBOSS EAP 6.0. I had created queue configuration in WAS and tested in standalone program everything is working fine. For this test i need add "com.ibm.ws.ejb.thinclient_8.5.0.jar, com.ibm.ws.orb_8.5.0.jar,com.ibm.ws.runtime.jar, com.ibm.ws.sib.client.thin.jms_8.5.0.jar" files in my class path.

            Created custom module and same jars i had placed in JBOSS. Now i am trying to start the server i am getting following exception. I am not have change any configuration in standalone.xml. More than two day i am sitting with this issue. I am using jdk 1.7 same issue i am getting in IBM JDK.

       

      Caused by: javax.naming.NamingException: checkForUrlContext: java:comp/UserTransaction [Root exception is javax.naming.ConfigurationException: Name space accessor for the java: name space has not been set. Possible cause is that the user is specifying a java: URL name in a JNDI Context method call but is not running in a J2EE client or server environment.]

      at com.ibm.ws.naming.util.Helpers.checkForUrlContext(Helpers.java:1623)

      at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:160)

      at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)

      at javax.naming.InitialContext.lookup(InitialContext.java:411)

      at org.drools.persistence.jta.JtaTransactionManager.findUserTransaction(JtaTransactionManager.java:132)

      ... 70 more

      Caused by: javax.naming.ConfigurationException: Name space accessor for the java: name space has not been set. Possible cause is that the user is specifying a java: URL name in a JNDI Context method call but is not running in a J2EE client or server environment.

      at com.ibm.ws.naming.java.javaURLContextFactory.isNameSpaceAccessable(javaURLContextFactory.java:109)

      at com.ibm.ws.naming.urlbase.UrlContextFactory.getObjectInstance(UrlContextFactory.java:85)

      at javax.naming.spi.NamingManager.getURLObject(NamingManager.java:601)

      at javax.naming.spi.NamingManager.getURLContext(NamingManager.java:550)

      at com.ibm.ws.naming.util.Helpers.checkForUrlContext(Helpers.java:1618)

         ... 74 more


      Thanks & Regards,

      Joshwa J