1 2 Previous Next 20 Replies Latest reply on Mar 26, 2012 5:31 PM by Marcio B. Go to original post
      • 15. Re: JNDI lookup of QueueConnectionFactory and Queues from within JBoss
        Justin Bertram Master

        One more thing...

         

        What trick are you specifically using and why exactly are you using it?

        • 16. Re: JNDI lookup of QueueConnectionFactory and Queues from within JBoss
          Justin Bertram Master

          FYI - I posted on https://community.jboss.org/thread/196472 to hopefully clear up any lingering confusion about the tricks that user had implemented.

          • 17. Re: JNDI lookup of QueueConnectionFactory and Queues from within JBoss
            Laurent Gauthier Newbie

            OK, thanks for the tips.

             

            With this info (namely starting AS7 with -b switch but also the general explanation on AS7 configuration), I was able to get rid of the trick in the standalone-full.xml file. I guess this was just a bad understanding on my part (and on that of the others). To our defense, I must say that the required information and examples are not always easy to find. Your explanations were very clear but I am not sure if this info is well conveyed in the official JBoss documents.

            • 18. Re: JNDI lookup of QueueConnectionFactory and Queues from within JBoss
              Marcio B. Newbie

              Hi Justin,

              I used the configuration that you suggested, but strangely is appearing to me the following error:

               

              Exception in thread "main" javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.ExceptionInInitializerError]

                at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:36)

                at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:121)

                at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)

                at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)

                at javax.naming.InitialContext.init(InitialContext.java:242)

                at javax.naming.InitialContext.<init>(InitialContext.java:216)

                at com.wp.mb.client.jms.JMSClient.main(JMSClient.java:47)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                at java.lang.reflect.Method.invoke(Method.java:601)

                at com.intellij.rt.execution.application.AppMain.main(AppMain.java:120)

              Caused by: java.lang.ExceptionInInitializerError

                at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.sendVersionHeader(RemoteNamingStoreV1.java:69)

                at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.start(RemoteNamingStoreV1.java:64)

                at org.jboss.naming.remote.protocol.v1.VersionOne.getRemoteNamingStore(VersionOne.java:45)

                at org.jboss.naming.remote.protocol.Versions.getRemoteNamingStore(Versions.java:49)

                at org.jboss.naming.remote.client.RemoteContextFactory.createVersionedStore(RemoteContextFactory.java:68)

                at org.jboss.naming.remote.client.NamingStoreCache.getRemoteNamingStore(NamingStoreCache.java:60)

                at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateCachedNamingStore(InitialContextFactory.java:166)

                at org.jboss.naming.remote.client.InitialContextFactory.getOrCreateNamingStore(InitialContextFactory.java:139)

                at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:104)

                ... 10 more

              Caused by: java.lang.RuntimeException: Could not find a marshaller factory for river marshalling strategy

                at org.jboss.naming.remote.protocol.v1.WriteUtil.<clinit>(WriteUtil.java:50)

                ... 19 more

               

              I can not solve, what can be?

              • 19. Re: JNDI lookup of QueueConnectionFactory and Queues from within JBoss
                Justin Bertram Master

                Looks like you might not have the necessary libraries on your classpath.  It looks like you're executing this from IntelliJ.  Is that true?  What jars are on your classpath?

                 

                To be clear, this is a JBoss Remoting issue with your JNDI look-up and not a JMS issue per se.

                • 20. Re: JNDI lookup of QueueConnectionFactory and Queues from within JBoss
                  Marcio B. Newbie

                  Yes, I'm executing with IntelliJ Idea.

                  I will create a new thread about JNDI then, thanks for the help.


                  1 2 Previous Next