0 Replies Latest reply on Sep 18, 2013 7:35 AM by Darji Farji

    Error while migrating from Jboss4.2.3 to JbossEAP6 in jboss-web.xml

    Darji Farji Newbie

      Hi, I am getting error around this bit

      <jndi-name>jnp://localhost:1100/queue/ukhe.pmi.ecol.apply

              </jndi-name>

       

      I am trying to migrate from Jboss4.2.3 to JbossEAP6. Can please somebody tell me what is the correct syntax ??

       

       

      <jboss-web>

          <context-root>ecol</context-root>

         

          <resource-ref>

              <res-ref-name>jms/ConnectionFactory

              </res-ref-name>

              <!-- non HA -->

              <!-- <jndi-name>java:/ConnectionFactory</jndi-name> -->

       

              <!--

                  Use the JMS Resource Adapter, let it deal with knowing where the JMS

                  server is

              -->

              <jndi-name>java:/JmsXA</jndi-name>

          </resource-ref>

       

       

          <resource-ref>

              <res-ref-name>jms/QueueEcolApplication</res-ref-name>

       

              <!-- non HA -->

              <!-- <jndi-name>java:/queue/ecolApplication</jndi-name> -->

       

              <!-- Use HA-JNDI so we can find the queue on any node -->

              <jndi-name>jnp://localhost:1100/queue/ukhe.pmi.ecol.apply

              </jndi-name>

          </resource-ref>

       

       

          <resource-ref>

              <res-ref-name>jms/QueueDLQ</res-ref-name>

       

              <!-- non HA -->

              <!-- <jndi-name>java:/queue/DLQ</jndi-name> -->

       

              <!-- Use HA-JNDI so we can find the queue on any node -->

              <jndi-name>jnp://localhost:1100/queue/ukhe.pmi.ecol.fail

              </jndi-name>

          </resource-ref>   

         

         

      </jboss-web>

       

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

       

       

      Failed to process phase INSTALL of deployment "ECOL.war"

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

          at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_07]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_07]

          at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_07]

      Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for jnp:

          at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

          at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.2.GA-redhat-2.jar:1.0.2.GA-redhat-2]

          at org.jboss.as.naming.deployment.ContextNames.buildServiceName(ContextNames.java:178)

          at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:190)

          at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:181)

          at org.jboss.as.naming.deployment.ContextNames.bindInfoFor(ContextNames.java:132)

          at org.jboss.as.ee.component.LookupInjectionSource.getResourceValue(LookupInjectionSource.java:70)

          at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.addJndiBinding(ModuleJndiBindingProcessor.java:227)

          at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:118)

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.1.3.Final-redhat-4.jar:7.1.3.Final-redhat-4]

          ... 5 more