10 Replies Latest reply on Dec 26, 2007 2:37 PM by Peter Johnson

    javax.naming.NameNotFoundException: queue not bound

    Bidhudas V Newbie

      Hi,

      I am trying to configure JMS queue in JBOSS. I have added the following entry in jbossmq-destinations-service.xml

      <mbean code="org.jboss.mq.server.jmx.Queue"
       name="jboss.mq.destination:service=Queue,name=WebResponse">
       <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
       </mbean>



      But the same was not listed in JNDIVIEW.

      Whenever I tried to lookup this queue(ctx.lookup(queue/RequestQ) getting the following error. It will be of great help if any body can help in resolving this issue

      javax.naming.NameNotFoundException: queue not bound
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
      at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
      at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
      at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
      at sun.rmi.transport.Transport$1.run(Unknown Source)
      at java.security.AccessController.doPrivileged(Native Method)



      Regards
      Bidhduas

        • 1. Re: javax.naming.NameNotFoundException: queue not bound
          Peter Johnson Master

          I added your queue to my destinations file, worked fine.

          What version of JBossAS are you using?

          When the app server deploys the queues, there should be a series of message on the console like this:

          10:34:26,268 INFO [A] Bound to JNDI name: queue/A
          10:34:26,284 INFO [B] Bound to JNDI name: queue/B
          10:34:26,284 INFO [C] Bound to JNDI name: queue/C
          ...

          Please post the output for the queues and topics bound (there should be 9, or 10 if your queue shows up). Also post the jndiview results showing all of the queues and topics in the global namespace.

          Where is the lookup code at? In a stand-alone client? Or in an app deployed to the same app server as the queue? Please post the lookup code, and the jndi properties used. Even if your queue did not show up, the lookup for the 'queue' name should still work.

          Finally, are you sure you changed the correct file? In other words, did you perhaps change the file in 'default' when you are really running 'all'?

          • 2. Re: javax.naming.NameNotFoundException: queue not bound
            Bidhudas V Newbie

            I am using the JBOSS 4.2.1 GA.

            I could not find anything with respect to Queue creation in console. But same error which is described in the previous post is coming there too(I am using message listner, may be due to that). THis is indeed a web based application.

            I am using default server settings and jbossmq-destinations-service.xml file is in server/deploy/jms folder

            See the code I am using for getting queue

            private static InitialContext getInitialContext() throws NamingException {
            if(iniCtx == null) {
            try {
            InputStream stream = MessageQueue.class.getClassLoader().getResourceAsStream("jndi.properties");
            Properties prop = new Properties();
            prop.load(stream);
            iniCtx = new InitialContext(prop);
            System.out.println("JNDI " + iniCtx.getEnvironment().toString());
            } catch (IOException e) {
            iniCtx = new InitialContext();
            }
            }
            
            return iniCtx;
            }
            
            private void createQueue(String queueName) throws NamingException, JMSException
            {
            queue = (Queue) getInitialContext().lookup(queueName);
            
            }
            
            


            and JNDI properties as below

            java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
            java.naming.provider.url=jnp://127.0.0.1:1099
            java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces



            See some of the console issues below



            5:34:28,500 WARN [ServiceController] Problem starting service jboss.mq:service=PersistenceManager
            org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES)); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES))))
            at org.jboss.mq.pm.jdbc2.PersistenceManager.resolveAllUncommitedTXs(PersistenceManager.java:495)
            at org.jboss.mq.pm.jdbc2.PersistenceManager.startService(PersistenceManager.java:1809)
            at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
            at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
            at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
            at java.lang.reflect.Method.invoke(Unknown Source)
            at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
            at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
            at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
            at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)


            And also I am getting the following in the console


            --- Incompletely deployed packages ---
            org.jboss.deployment.DeploymentInfo@965e150c { url=file:/D:/softs/JBoss/jboss-4.2.1.GA/server/default/deploy/das-estinations-service.xml }
            deployer: org.jboss.deployment.SARDeployer@914f6a
            status: Deployment FAILED reason: no protocol: xmdesc/Queue-xmbean.xml; - nested throwable: (java.net.MalformedURLException: no protocol: xmdesc/Queue-xmbean.xml)
            state: FAILED
            watch: file:/D:/softs/JBoss/jboss-4.2.1.GA/server/default/deploy/das-estinations-service.xml
            altDD: null
            lastDeployed: 1198211647031
            lastModified: 1198211647031
            mbeans:

            --- MBeans waiting for other MBeans ---
            ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
            State: CONFIGURED
            I Depend On:
            jboss.jdbc:service=metadata,datasource=DefaultDS

            ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
            State: FAILED
            Reason: org.jboss.deployment.DeploymentException: Error while checking if table aleady exists HILOSEQUENCES; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES)); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES))))
            I Depend On:
            jboss:service=TransactionManager
            jboss.jca:service=DataSourceBinding,name=DefaultDS

            ObjectName: jboss.mq:service=PersistenceManager
            State: FAILED
            Reason: org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES)); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES))))
            I Depend On:
            jboss.jca:service=DataSourceBinding,name=DefaultDS
            Depends On Me:
            jboss.mq:service=DestinationManager

            --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
            ObjectName: jboss.mq:service=PersistenceManager
            State: FAILED
            Reason: org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES)); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES))))
            I Depend On:
            jboss.jca:service=DataSourceBinding,name=DefaultDS
            Depends On Me:
            jboss.mq:service=DestinationManager

            ObjectName: jboss.jdbc:service=metadata,datasource=DefaultDS
            State: NOTYETINSTALLED
            Depends On Me:
            jboss.ejb:service=EJBTimerService,persistencePolicy=database

            ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
            State: FAILED
            Reason: org.jboss.deployment.DeploymentException: Error while checking if table aleady exists HILOSEQUENCES; - nested throwable: (org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES)); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES))))
            I Depend On:
            jboss:service=TransactionManager
            jboss.jca:service=DataSourceBinding,name=DefaultDS



            See the JNDI view below


            --------------------------------------------------------------------------------

            Web Applications
            java:comp namespace of the jmx-console.war application:
            +- UserTransaction[link -> UserTransaction] (class: javax.naming.LinkRef)
            +- env (class: org.jnp.interfaces.NamingContext)
            | +- security (class: org.jnp.interfaces.NamingContext)
            | | +- realmMapping[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- subject[link -> java:/jaas/other/subject] (class: javax.naming.LinkRef)
            | | +- securityMgr[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- security-domain[link -> java:/jaas/other] (class: javax.naming.LinkRef)

            java:comp namespace of the DAS-web.war application:
            +- UserTransaction[link -> UserTransaction] (class: javax.naming.LinkRef)
            +- env (class: org.jnp.interfaces.NamingContext)
            | +- security (class: org.jnp.interfaces.NamingContext)
            | | +- realmMapping[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- subject[link -> java:/jaas/other/subject] (class: javax.naming.LinkRef)
            | | +- securityMgr[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- security-domain[link -> java:/jaas/other] (class: javax.naming.LinkRef)

            java:comp namespace of the console-mgr.sar/web-console.war application:
            +- UserTransaction[link -> UserTransaction] (class: javax.naming.LinkRef)
            +- env (class: org.jnp.interfaces.NamingContext)
            | +- security (class: org.jnp.interfaces.NamingContext)
            | | +- realmMapping[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- subject[link -> java:/jaas/other/subject] (class: javax.naming.LinkRef)
            | | +- securityMgr[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- security-domain[link -> java:/jaas/other] (class: javax.naming.LinkRef)

            java:comp namespace of the jbossmq-httpil.sar/jbossmq-httpil.war application:
            +- UserTransaction[link -> UserTransaction] (class: javax.naming.LinkRef)
            +- env (class: org.jnp.interfaces.NamingContext)
            | +- security (class: org.jnp.interfaces.NamingContext)
            | | +- realmMapping[link -> java:/jaas/jbossmq] (class: javax.naming.LinkRef)
            | | +- subject[link -> java:/jaas/jbossmq/subject] (class: javax.naming.LinkRef)
            | | +- securityMgr[link -> java:/jaas/jbossmq] (class: javax.naming.LinkRef)
            | | +- security-domain[link -> java:/jaas/jbossmq] (class: javax.naming.LinkRef)

            java:comp namespace of the jboss-web.deployer/ROOT.war application:
            +- UserTransaction[link -> UserTransaction] (class: javax.naming.LinkRef)
            +- env (class: org.jnp.interfaces.NamingContext)
            | +- security (class: org.jnp.interfaces.NamingContext)
            | | +- realmMapping[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- subject[link -> java:/jaas/other/subject] (class: javax.naming.LinkRef)
            | | +- securityMgr[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- security-domain[link -> java:/jaas/other] (class: javax.naming.LinkRef)

            java:comp namespace of the DAS-business.war application:
            +- UserTransaction[link -> UserTransaction] (class: javax.naming.LinkRef)
            +- env (class: org.jnp.interfaces.NamingContext)
            | +- security (class: org.jnp.interfaces.NamingContext)
            | | +- realmMapping[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- subject[link -> java:/jaas/other/subject] (class: javax.naming.LinkRef)
            | | +- securityMgr[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- security-domain[link -> java:/jaas/other] (class: javax.naming.LinkRef)

            java:comp namespace of the http-invoker.sar/invoker.war application:
            +- UserTransaction[link -> UserTransaction] (class: javax.naming.LinkRef)
            +- env (class: org.jnp.interfaces.NamingContext)
            | +- security (class: org.jnp.interfaces.NamingContext)
            | | +- realmMapping[link -> java:/jaas/jmx-console] (class: javax.naming.LinkRef)
            | | +- subject[link -> java:/jaas/jmx-console/subject] (class: javax.naming.LinkRef)
            | | +- securityMgr[link -> java:/jaas/jmx-console] (class: javax.naming.LinkRef)
            | | +- security-domain[link -> java:/jaas/jmx-console] (class: javax.naming.LinkRef)

            java:comp namespace of the jbossws.sar/jbossws-context.war application:
            +- UserTransaction[link -> UserTransaction] (class: javax.naming.LinkRef)
            +- env (class: org.jnp.interfaces.NamingContext)
            | +- security (class: org.jnp.interfaces.NamingContext)
            | | +- realmMapping[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- subject[link -> java:/jaas/other/subject] (class: javax.naming.LinkRef)
            | | +- securityMgr[link -> java:/jaas/other] (class: javax.naming.LinkRef)
            | | +- security-domain[link -> java:/jaas/other] (class: javax.naming.LinkRef)

            java: Namespace
            +- DefaultDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
            +- SecurityProxyFactory (class: org.jboss.security.SubjectSecurityProxyFactory)
            +- DefaultJMSProvider (class: org.jboss.jms.jndi.JNDIProviderAdapter)
            +- comp (class: javax.naming.Context)
            +- JmsXA (class: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl)
            +- jaas (class: javax.naming.Context)
            | +- JmsXARealm (class: org.jboss.security.plugins.SecurityDomainContext)
            +- comp.original (class: javax.namingMain.Context)
            +- timedCacheFactory (class: javax.naming.Context)
            Failed to lookup: timedCacheFactory, errmsg=org.jboss.util.TimedCachePolicy cannot be cast to javax.naming.NamingEnumeration
            +- TransactionPropagationContextExporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager)
            +- StdJMSPool (class: org.jboss.jms.asf.StdServerSessionPoolFactory)
            +- Mail (class: javax.mail.Session)
            +- comp.ejb3 (class: javax.naming.Context)
            | NonContext: null
            +- TransactionPropagationContextImporter (class: com.arjuna.ats.internal.jbossatx.jta.PropagationContextManager)
            +- TransactionManager (class: com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate)

            Global JNDI Namespace
            +- TransactionSynchronizationRegistry (class: com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple)
            +- TopicConnectionFactory (class: org.jboss.naming.LinkRefPair)
            +- UIL2ConnectionFactory[link -> ConnectionFactory] (class: javax.naming.LinkRef)
            +- UserTransactionSessionFactory (proxy: $Proxy14 implements interface org.jboss.tm.usertx.interfaces.UserTransactionSessionFactory)
            +- console (class: org.jnp.interfaces.NamingContext)
            | +- PluginManager (proxy: $Proxy49 implements interface org.jboss.console.manager.PluginManagerMBean)
            +- UIL2XAConnectionFactory[link -> XAConnectionFactory] (class: javax.naming.LinkRef)
            +- UUIDKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.uuid.UUIDKeyGeneratorFactory)
            +- QueueConnectionFactory (class: org.jboss.naming.LinkRefPair)
            +- UserTransaction (class: org.jboss.tm.usertx.client.ClientUserTransaction)
            +- jmx (class: org.jnp.interfaces.NamingContext)
            | +- invoker (class: org.jnp.interfaces.NamingContext)
            | | +- RMIAdaptor (proxy: $Proxy48 implements interface org.jboss.jmx.adaptor.rmi.RMIAdaptor,interface org.jboss.jmx.adaptor.rmi.RMIAdaptorExt)
            | +- rmi (class: org.jnp.interfaces.NamingContext)
            | | +- RMIAdaptor[link -> jmx/invoker/RMIAdaptor] (class: javax.naming.LinkRef)
            +- HiLoKeyGeneratorFactory (class: org.jboss.ejb.plugins.keygenerator.hilo.HiLoKeyGeneratorFactory)
            +- UILXAConnectionFactory[link -> XAConnectionFactory] (class: javax.naming.LinkRef)
            +- UILConnectionFactory[link -> ConnectionFactory] (class: javax.naming.LinkRef)



            Let me know if you need any more info





            • 3. Re: javax.naming.NameNotFoundException: queue not bound
              jaikiran pai Master

              There appear to be 2 errors. One in your datasource file:

              java.sql.SQLException: Access denied for user 'jbossuser'@'localhost' (using password: YES))))


              Looks like the username/password you have specified in your datasource file are incorrect for this DB.

              The other error is related to the file which contains your queues:

              org.jboss.deployment.DeploymentInfo@965e150c { url=file:/D:/softs/JBoss/jboss-4.2.1.GA/server/default/deploy/das-estinations-service.xml }
              deployer: org.jboss.deployment.SARDeployer@914f6a
              status: Deployment FAILED reason: no protocol: xmdesc/Queue-xmbean.xml; - nested throwable: (java.net.MalformedURLException: no protocol: xmdesc/Queue-xmbean.xml)
              state: FAILED
              watch: file:/D:/softs/JBoss/jboss-4.2.1.GA/server/default/deploy/das-estinations-service.xml
              altDD: null


              Looks like the das-estinations-service.xml file is incorrect. Can you post the entire contents of that file here?




              • 4. Re: javax.naming.NameNotFoundException: queue not bound
                Bidhudas V Newbie

                Find entried in das-estinations-service.xml. Does the SQL exception u were talking about is it any way related to JMS?? As of now I do not have any issue in connecting to DB. I beleive this is for mySQL but I am connecting to Oracle DB. There is no issues with respect to that.

                Please let me know if you require any additional information for resolving this issue.


                <?xml version="1.0" encoding="UTF-8"?>
                
                <!-- $Id: jbossmq-destinations-service.xml 25907 2004-11-16 04:32:39Z ejort $ -->
                
                <!--
                 | This file defines the default Queues and Topics that JBossMQ
                 | ships with. The default Queues and Topics are used by the
                 | JBoss test suite and by the sample jms programs.
                 |
                 | You can add other destinations to this file, or you can create other
                 | *-service.xml files to contain your application's destinations.
                 -->
                
                <server>
                 <!-- Destination without a configured SecurityManager or without a
                 a SecurityConf will default to role guest with read=true, write=true,
                 create=false.
                 -->
                 <!--
                 The following mbean is for DAS Queue
                 -->
                
                 <mbean code="org.jboss.mq.server.jmx.Queue"
                 name="jboss.mq.destination:service=Queue,name=WebRequest"
                 xmbean-dd="xmdesc/Queue-xmbean.xml">
                 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
                 </mbean>
                 <mbean code="org.jboss.mq.server.jmx.Queue"
                 name="jboss.mq.destination:service=Queue,name=WebResponse">
                 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
                 </mbean>
                 <mbean code="org.jboss.mq.server.jmx.Queue"
                 name="jboss.mq.destination:service=Queue,name=EDIRequest">
                 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
                 </mbean>
                 <mbean code="org.jboss.mq.server.jmx.Queue"
                 name="jboss.mq.destination:service=Queue,name=TDARequest">
                 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
                 </mbean>
                 <mbean code="org.jboss.mq.server.jmx.Queue"
                 name="jboss.mq.destination:service=Queue,name=TDAResponse">
                 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
                 </mbean>
                
                </server>


                • 5. Re: javax.naming.NameNotFoundException: queue not bound
                  jaikiran pai Master

                   

                  <mbean code="org.jboss.mq.server.jmx.Queue"
                   name="jboss.mq.destination:service=Queue,name=WebRequest"
                   xmbean-dd="xmdesc/Queue-xmbean.xml">
                   <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
                   </mbean>


                  Remove the xmbean-dd=... part from that queue definition. It should just be

                  <mbean code="org.jboss.mq.server.jmx.Queue"
                   name="jboss.mq.destination:service=Queue,name=WebRequest">
                   <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
                   </mbean>



                  As far as the DB error is concerned, did you do any changes to the hsqldb-ds.xml file present in the deploy folder?



                  • 6. Re: javax.naming.NameNotFoundException: queue not bound
                    Bidhudas V Newbie

                    Even after removing the part you mentioned in the post, queue issue is not resolved. Actually I added the same to verify whether I need to bind it with JNDI manually.

                    I have not done any changes in hsqldb-ds.xml file. My application DB is configured from application as of now.



                    • 7. Re: javax.naming.NameNotFoundException: queue not bound
                      Peter Johnson Master

                      Did you change any of the files in the jms directory? Specifically, did you change hsqldb-jdbc2-service.xml (or perhaps replace it with another file)? That file directs MQ to use DefaultDS as its data source.

                      You mentioned MySQL. Also, the error message "Access denied for user 'jbossuser'@'localhost' (using password: YES))" is a typical MySQL error message. I am assuming that you must have changed hsqldb-jdbc2-service.xml to use a different data source, or replace DefaultDS with MySQL.

                      Until you get the database access issue solved, you will not be able to use the messaging service., and no queue or destinations will show up.

                      • 8. Re: javax.naming.NameNotFoundException: queue not bound
                        Bidhudas V Newbie

                        Now the queue issue is resolved. But server is not getting started. Its getting shutdown after one minute( it shows as restartign in server window). Getting following in the console.

                        Please let me know how to resolve this at the earliest.


                        --- Packages waiting for a deployer ---
                        org.jboss.deployment.DeploymentInfo@93a9ea6b { url=file:/D:/softs/JBoss/jboss-4.2.1.GA/server/DAS-web/deploy/deploy.lnk }
                        deployer: null
                        status: null
                        state: INIT_WAITING_DEPLOYER
                        watch: file:/D:/softs/JBoss/jboss-4.2.1.GA/server/DAS-web/deploy/deploy.lnk
                        altDD: null
                        lastDeployed: 1198650020906
                        lastModified: 1198650020906
                        mbeans:

                        --- Incompletely deployed packages ---
                        org.jboss.deployment.DeploymentInfo@93a9ea6b { url=file:/D:/softs/JBoss/jboss-4.2.1.GA/server/DAS-web/deploy/deploy.lnk }
                        deployer: null
                        status: null
                        state: INIT_WAITING_DEPLOYER
                        watch: file:/D:/softs/JBoss/jboss-4.2.1.GA/server/DAS-web/deploy/deploy.lnk
                        altDD: null
                        lastDeployed: 1198650020906
                        lastModified: 1198650020906
                        mbeans:


                        07:20:21,156 INFO [Http11Protocol] Démarrage de Coyote HTTP/1.1 sur http-127.0.0.1-8087
                        07:20:21,171 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
                        07:20:21,187 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 8s:703ms


                        • 9. Re: javax.naming.NameNotFoundException: queue not bound
                          Bidhudas V Newbie

                          Resolved the issue with respect deployment error message which was there in the Console. But still the server is getting stopped.

                          Need urgent help on this.

                          • 10. Re: javax.naming.NameNotFoundException: queue not bound
                            Peter Johnson Master

                            In Windows, files with the extension .lnk are shortcuts. Apparently, you created a shortcut in the deploy directory (probably accidentally with the mouse in Explorer), and JBossAS does not know what to do with .lnk files. And that is what the notification message means.

                            You can easily fix this by removing the shortcut. However, this is not a problem and the server did start (hence the "started in message").

                            Why do you think the server is getting stopped? After this message:

                            07:20:21,187 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date=200707131605)] Started in 8s:703ms

                            there are typically very few messages appearing in the console. Once you see the above message, you can go to you browser, enter http://localhost:8080 and get the home page.