12 Replies Latest reply on Jan 30, 2009 12:29 PM by glm

    How to look up Queue Name?

    glm Newbie

      I am trying to open a connection to two queues named "A" and "B" as defined in the destinations-service.xml :

       <mbean code="org.jboss.jms.server.destination.QueueService"
       name="jboss.messaging.destination:service=Queue,name=A"
       xmbean-dd="xmdesc/Queue-xmbean.xml">
       <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
       <depends>jboss.messaging:service=PostOffice</depends>;
       </mbean>
      
       <mbean code="org.jboss.jms.server.destination.QueueService"
       name="jboss.messaging.destination:service=Queue,name=B"
       xmbean-dd="xmdesc/Queue-xmbean.xml">
       <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
       <depends>jboss.messaging:service=PostOffice</depends>;
       </mbean>
      
      
      


      in my Java code I am trying to open the connection like this :

       initialContext = new InitialContext();
       System.out.println("starting to setupQueues ... ");
      
       outQueue = ( Queue ) initialContext.lookup( "queue/A" );
      
       System.out.println("outQueue is assigned to queue/A ... ");
      
       inQueue = ( Queue ) initialContext.lookup( "queue/B" );
      
       System.out.println("inQueue is assigned to queue/B ... ");
      
       qcf =
       ( QueueConnectionFactory ) initialContext
       .lookup( "/ConnectionFactory" );
       qConnection = qcf.createQueueConnection( );
       qSession =
       qConnection.createQueueSession( false,
       Session.AUTO_ACKNOWLEDGE );
       qReceiver = qSession.createReceiver( inQueue );
       qReceiver.setMessageListener( this );
      
       qConnection.start( );
      


      But when I execute the above code I get the following error message :

      11:21:29,380 ERROR [DirMonitorImpl] Unable to lookup Queues or QueueConnectionFactory ..
      javax.naming.NameNotFoundException: queue not bound
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)
      at org.jnp.server.NamingServer.getObject(NamingServer.java:785)
      at org.jnp.server.NamingServer.lookup(NamingServer.java:396)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:713)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:673)
      at javax.naming.InitialContext.lookup(InitialContext.java:392)
      at com.nichpro.monitor.DirMonitorImpl.setupQueues(DirMonitorImpl.java:215)
      at com.nichpro.monitor.DirMonitorImpl.start(DirMonitorImpl.java:171)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:597)
      at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
      at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
      at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
      at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
      at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
      at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
      at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
      at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
      at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)

      at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
      at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
      at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
      at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
      at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
      at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
      at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
      at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
      at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
      at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
      at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
      at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
      at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
      at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
      at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
      at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
      at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
      at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
      at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
      at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
      at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
      at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
      at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
      at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545)
      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
      at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
      at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
      at org.jboss.Main.boot(Main.java:209)
      at org.jboss.Main$1.run(Main.java:547)
      at java.lang.Thread.run(Thread.java:619)
      11:21:29,395 ERROR [DirMonitorImpl] DirMonitorImpl didn't start correctly....
      java.lang.NullPointerException
      at com.nichpro.monitor.DirMonitorImpl.setupQueues(DirMonitorImpl.java:236)


      What is the correct String name to use in the initialContext.lookup() call for the queue when you define it as "A" in the destinations-service.xml file? Is it suppose to be "/queue/A", "queue/A" or "/A" or is it something else?

      Regards,
      GMarsh

        • 1. Re: How to look up Queue Name?
          Wolfgang Knauf Master

          Hi Gary,

          you have to add a "JNDIName" attribute to each MBean:

          <mbean code="org.jboss.jms.server.destination.QueueService"
           name="jboss.messaging.destination:service=Queue,name=A"
           xmbean-dd="xmdesc/Queue-xmbean.xml">
           <attribute name="JNDIName">queue/A</attribute>
           <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
           <depends>jboss.messaging:service=PostOffice</depends>;
           </mbean>


          Hope this helps

          Wolfgang

          • 2. Re: How to look up Queue Name?
            Peter Johnson Master

            You should not have to state an explicit jndi name. It looks like this code is in a service that is starting before the queues are established. You will need to add a depends clause to your deployment descriptor so that the queues are established first.

            • 3. Re: How to look up Queue Name?
              glm Newbie

              Peter, if I understand you correctly you are saying I need to put a depends element in my DMServer-jboss-beans.xml file, correct?

              If so then what might it look like :

              <?xml version="1.0" encoding="UTF-8"?>
              <deployment xmlns="urn:jboss:bean-deployer:2.0">
              
               <bean name="AgentFactory" class="com.nichpro.factory.AgentFactory" >
               <depends >
               WHAT GOES HERE?
               </depends>
               </bean>
              
               <bean name="DirectoryMonitor" class="com.nichpro.monitor.DirMonitor.Impl" >
               <depends>
               </depends>
               </bean>
              
              </deployment>


              I am guessing the depends would look something like :
              <depends>jboss.messaging:service=queue/A</depends>


              but again this is purely a guess.

              Regards,

              GMarsh

              • 4. Re: How to look up Queue Name?
                Peter Johnson Master

                I could not be specific earlier because I did not know what your implementation was. The depends clause you have will work if you are defining mbeans in a *-service.xml file. But I do not know how to define a dependency on an mbean in a microcontainer *-jboss-beans.xml file. I though I saw a post about this very topic a while back, if I find it I will post a link.

                • 6. Re: How to look up Queue Name?
                  glm Newbie

                  OK I changed a few things like using real names for the queues, now I am using AgentFactoryQueue and MonitorQueue as names. These are registered in the destinations-service.xml file. When I start the JBoss AS and then bring up the JMX-Console I see under the The JMX Agent View for the jboss.messaging.destination the above queues listed. I also see the following in the Dos window :


                  10:36:13,384 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  10:36:13,400 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  10:36:13,431 INFO [QueueService] Queue[/queue/MonitorQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                  10:36:13,509 INFO [QueueService] Queue[/queue/AgentFactorQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000


                  but when I put my DMServer-jboss-beans.xml in the deploy directory I get the following error :

                  11:01:22,946 WARN [HDScanner] Failed to process changes
                  org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                  *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}

                  AgentFactory
                  -> jboss.messaging: name=AgentFactoryQueue,service=Queue{Create:** NOT FOUND Depends on 'jboss.messaging: name=AgentFactoryQueue,service=Queue' **}

                  DirectoryMonitor
                  -> jboss.messaging: name=MonitorQueue,service=Queue{Create:** NOT FOUND Depends on 'jboss.messaging: name=MonitorQueue,service=Queue' **}


                  *** CONTEXTS IN ERROR: Name -> Error

                  jboss.messaging: name=MonitorQueue,service=Queue -> ** NOT FOUND Depends on 'jboss.messaging: name=MonitorQueue,service=Queue' **

                  jboss.messaging: name=AgentFactoryQueue,service=Queue -> ** NOT FOUND Depends on 'jboss.messaging: name=AgentFactoryQueue,service=Queue' **


                  at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)
                  at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:665)
                  at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:293)
                  at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
                  at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
                  at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
                  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
                  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
                  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
                  at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
                  at java.lang.Thread.run(Thread.java:619)
                  11:06:21,009 ERROR [[HtmlAdaptor]] Servlet.service() for servlet HtmlAdaptor threw exception
                  javax.management.MalformedObjectNameException: Key properties cannot be empty
                  at javax.management.ObjectName.construct(ObjectName.java:467)
                  at javax.management.ObjectName.(ObjectName.java:1403)
                  at org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:231)
                  at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet$4.run(HtmlAdaptorServlet.java:391)
                  at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet$4.run(HtmlAdaptorServlet.java:389)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOpByName(HtmlAdaptorServlet.java:387)
                  at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOpByName(HtmlAdaptorServlet.java:312)
                  at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:106)
                  at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doGet(HtmlAdaptorServlet.java:81)
                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
                  at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
                  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
                  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
                  at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
                  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
                  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
                  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
                  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
                  at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
                  at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
                  at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
                  at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
                  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
                  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
                  at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
                  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
                  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
                  at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
                  at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
                  at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
                  at java.lang.Thread.run(Thread.java:619)


                  My DMServer-jboss-beans.xml file looks like this :

                  <?xml version="1.0" encoding="UTF-8"?>
                  <deployment xmlns="urn:jboss:bean-deployer:2.0">
                  
                   <bean name="AgentFactory" class="com.nichpro.factory.AgentFactory" >
                   <depends>jboss.messaging:service=Queue, name=AgentFactoryQueue</depends>
                   </bean>
                  
                   <bean name="DirectoryMonitor" class="com.nichpro.monitor.DirMonitorImpl" >
                   <depends>jboss.messaging:service=Queue, name=MonitorQueue</depends>
                   </bean>
                  
                  </deployment>


                  I have looked at the Q3 on https://www.jboss.org/community/docs/DOC-10669 as B.Stansberry suggested but this was setting the depends for a Pojo in an MBean. This doesn't address the possible syntactical issue I am probably experiencing in my depends declaration in DMServer-jboss-beans.xml.

                  Can you point out what I am doing wrong in my depends declaration?

                  Regards,
                  GMarsh

                  • 7. Re: How to look up Queue Name?
                    jaikiran pai Master

                     

                    I see under the The JMX Agent View for the jboss.messaging.destination the above queues listed


                    So your depends is incorrect:

                    <depends>jboss.messaging:service=Queue, name=MonitorQueue</depends>
                    


                    For example, i have a "name=DLQ,service=Queue" under "jboss.messaging.destination" domain, so my dependency will be :

                    <depends>jboss.messaging.destination:name=DLQ,service=Queue</depends>


                    • 8. Re: How to look up Queue Name?
                      glm Newbie

                      I have reworked my DMServer-jboss-beans.xml to include the following depends

                      <depends>jboss.messaging.destination:service=Queue, name=AgentFactoryQueue</depends>
                       <depends>jboss.messaging.destination:service=Queue, name=MonitorQueue</depends>
                      


                      and the following error message is being out :



                      15:27:04,666 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                      15:27:04,666 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                      15:27:04,729 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                      15:27:04,729 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1034558 started
                      15:27:04,729 INFO [QueueService] Queue[/queue/AgentFactorQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                      15:27:04,745 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                      15:27:04,745 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1a47641 started
                      15:27:04,745 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnect
                      ionFactory but post office is non clustered. So connection factory will *not* support failover
                      15:27:04,745 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredCo
                      nnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
                      15:27:04,745 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
                      15:27:04,745 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@102e62e started
                      15:27:04,760 INFO [QueueService] Queue[/queue/MonitorQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
                      15:27:05,588 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
                      15:27:05,620 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
                      15:27:05,729 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
                      15:27:05,807 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                      *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}

                      AgentFactory
                      -> jboss.messaging.destination: name=MonitorQueue,service=Queue{Create:** NOT FOUND Depends on 'jboss.messaging.destination: name=MonitorQueue,service=Queue' **}
                      -> jboss.messaging.destination: name=AgentFactoryQueue,service=Queue{Create:** NOT FOUND Depends on 'jboss.messaging.destination: name=AgentFactoryQueue,service=Que
                      ue' **}

                      DirectoryMonitor
                      -> jboss.messaging.destination: name=AgentFactoryQueue,service=Queue{Create:** NOT FOUND Depends on 'jboss.messaging.destination: name=AgentFactoryQueue,service=Que
                      ue' **}
                      -> jboss.messaging.destination: name=MonitorQueue,service=Queue{Create:** NOT FOUND Depends on 'jboss.messaging.destination: name=MonitorQueue,service=Queue' **}





                      Seems like there is more going on than just this. Could this be related to a JNDI lookup failure?

                      Regards,

                      GMarsh


                      • 9. Re: How to look up Queue Name?
                        Brian Stansberry Master

                        Try removing the space before "name=":

                        <depends>jboss.messaging.destination:service=Queue,name=AgentFactoryQueue</depends>
                        <depends>jboss.messaging.destination:service=Queue,name=MonitorQueue</depends>
                        


                        The value is passed to new javax.management.ObjectName(String) whose parser doesn't ignore the space, so you end up with ObjectName with " name" as an attribute key instead of "name".

                        • 10. Re: How to look up Queue Name?
                          glm Newbie

                          No such luck... :-(

                          Here's the current error message :

                          16:24:07,963 WARN [HDScanner] Failed to process changes
                          org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

                          *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}

                          AgentFactory
                          -> jboss.messaging.destination:name=AgentFactoryQueue,service=Queue{Create:** NOT FOUND Depends on 'jboss.messaging.destination:name=AgentFactoryQueue,service=Queue
                          ' **}

                          DirectoryMonitor
                          -> jboss.messaging.destination:name=AgentFactoryQueue,service=Queue{Create:** NOT FOUND Depends on 'jboss.messaging.destination:name=AgentFactoryQueue,service=Queue
                          ' **}


                          *** CONTEXTS IN ERROR: Name -> Error

                          jboss.messaging.destination:name=AgentFactoryQueue,service=Queue -> ** NOT FOUND Depends on 'jboss.messaging.destination:name=AgentFactoryQueue,service=Queue' **


                          at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)
                          at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:665)
                          at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:293)
                          at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
                          at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
                          at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
                          at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
                          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
                          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
                          at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
                          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
                          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
                          at java.lang.Thread.run(Thread.java:619)



                          So it didn't seem to change the error ...

                          Regards,
                          GMarsh

                          • 11. Re: How to look up Queue Name?
                            jaikiran pai Master

                            Please do this:

                            1) Post the exact configuration file (MC bean) where you have configured the dependency
                            2) Post your queue configuration files
                            3) Post the console log including the exception stacktrace
                            4) Post the contents under "jboss.messaging.destination" domain from the jmx-console.

                            While posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted.

                            • 12. Re: How to look up Queue Name?
                              glm Newbie

                              I guess I should thank you for suggesting I print out the jboss.messaging.destination output from the JMXConsole. When I did,
                              I noticed that one of the queue names was misspelled, AgentFactoryQueue was missing the 'y'.

                              jboss.messaging.destination
                              
                               * name=AgentFactorQueue,service=Queue
                               * name=DLQ,service=Queue
                               * name=ExpiryQueue,service=Queue
                               * name=MonitorQueue,service=Queue
                              


                              So I corrected this in the destinations-services.xml file things started working.....

                              The devil is in the details.....

                              Thanks for your help and patience.

                              GMarsh