5 Replies Latest reply on Aug 17, 2002 8:14 PM by garyg

    QueueConnectionFactory not bound

    garyg

      I'm getting the NameNotFoundException below from the following line.

      qConnectionFactory = (QueueConnectionFactory) ctx.lookup("QueueConnectionFactory");

      This is from a remote client. Did anything here change from 2.4.4 to 3.0.1 with this?
      Any help much appreciated.

      --- remote client output

      javax.naming.NameNotFoundException: QueueConnectionFactory not bound
      at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:240)
      at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215)
      at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:117)
      at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:450)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:434)
      at javax.naming.InitialContext.lookup(InitialContext.java:345)
      at com.neuroquest.cais.clients.builder.Builder.setupQueueReceiver(Unknown Source)
      at com.neuroquest.cais.clients.builder.Builder.main(Unknown Source)
      javax.naming.NameNotFoundException: TopicConnectionFactory not bound
      at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:240)
      at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215)
      at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:117)
      at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:450)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:434)
      at javax.naming.InitialContext.lookup(InitialContext.java:345)
      at com.neuroquest.cais.clients.builder.Builder.platformSubscription(Unknown Source)
      at com.neuroquest.cais.clients.builder.Builder.main(Unknown Source)

        • 1. Re: QueueConnectionFactory not bound
          k__p

          What does your jbossmq-service.xml look like?

          The default setting is "ConnectionFactory".

          • 2. Re: QueueConnectionFactory not bound
            schaefera

            Hi

            Use the HTML-Adapter on port 8082, look for JNDIView service, click on link, then hit the "list" button and check in the Global Namespace that you find "QueueConnectionFactory".
            I would go and only use "ConnectionFactory" because the ConnectionFactory implementation can be upcasted to Queue- or TopicConnectionFactory.

            Have fun - Andy

            • 3. Re: QueueConnectionFactory not bound
              k__p

              In 3.0.1 you'll have to use

              host:8080/jmx-console rather than host:8082


              Is there anyway of making changes to JNDI via the HtmlAdaptor?

              • 4. Re: QueueConnectionFactory not bound
                schaefera

                Hi

                No, you cannot make changes to JNDI bindings but you can figure out what names are bound and with what class type.

                Andy

                • 5. Re: QueueConnectionFactory not bound
                  garyg

                  So how does this work using the host:8080/jmx-console in 3.0.1 ... whereas before I used the following code on host:8082 to do dynamic queue creation remotely.

                  Here's what I had to do in 2.4.4 ...

                  --- snip ---

                  String action = "action=createQueue?action=createQueue"
                  + "¶m0%2Bjava.lang.String=myQueue";

                  String arg = "/InvokeAction//JBossMQ%3Aservice%3DServer"
                  + "/" + action;

                  try {
                  URL url = new URL("http", "myMachine", 8082, arg);
                  HttpURLConnection urlConn = (HttpURLConnection)url.openConnection();
                  urlConn.connect();
                  ...

                  Any help much appreciated.