2 Replies Latest reply on Dec 4, 2012 7:18 AM by sfcoy

    Error Deployment MDB

    mravi

      Hi,

       

      I am trying to migrate from 5.1.0 to 7.1.1 and have some issues deploying MDBs.

       

      The error that I see is

       

      11:20:23,335 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.subunit."myApp.ear"."UI_EJB.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."myApp.ear"."UI_EJB.jar".INSTALL: Failed to process phase INSTALL of subdeployment "UI_EJB.jar" of deployment "myApp.ear"

                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

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

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

                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24]

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24]

                at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]

      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011058: Failed to install component com.test.integration.TestMessageRouter

                at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:100)

                at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

                ... 5 more

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

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

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

                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:138)

                at org.jboss.as.naming.deployment.ContextNames.bindInfoForEnvEntry(ContextNames.java:160)

                at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.processBindings(ComponentInstallProcessor.java:236)

                at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:189)

                at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:93)

       

       

      Here is the ejb-jar.xml

       

      <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd" id="ejb-jar_ID" version="2.1">

                <display-name>EJBs</display-name>

                <enterprise-beans>

          <message-driven>

            <ejb-name>com.test.integration.SystemMessageRouter</ejb-name>

            <ejb-class>com.test.integration.SystemMessageRouter</ejb-class>

                  <!--  <message-selector></message-selector> -->

                  <transaction-type>Bean</transaction-type>

                  <message-destination-type>javax.jms.Topic</message-destination-type>

                  <resource-ref>

                      <description>description</description>

                      <res-ref-name>/ConnectionFactory</res-ref-name>

                      <res-type>javax.jms.ConnectionFactory</res-type>

                      <res-auth>Application</res-auth>

                      <res-sharing-scope>Shareable</res-sharing-scope>

            </resource-ref>

                  <resource-env-ref>

               <resource-env-ref-name>topic/testEvent</resource-env-ref-name>

               <resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>

            </resource-env-ref>

          </message-driven>

                <message-driven>

            <ejb-name>com.test.integration.TestMessageRouter</ejb-name>

            <ejb-class>com.test.integration.TestPodMessageRouter</ejb-class>

                  <!--  <message-selector></message-selector> -->

                  <transaction-type>Bean</transaction-type>

                  <message-destination-type>javax.jms.Topic</message-destination-type>

                  <resource-ref>

                      <description>description</description>

                      <res-ref-name>/ConnectionFactory</res-ref-name>

                      <res-type>javax.jms.ConnectionFactory</res-type>

                      <res-auth>Application</res-auth>

                      <res-sharing-scope>Shareable</res-sharing-scope>

            </resource-ref>

                  <resource-env-ref>

               <resource-env-ref-name>topic/testTopicUI</resource-env-ref-name>

               <resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>

            </resource-env-ref>

          </message-driven>

      </enterprise-beans>

      </ejb-jar>

       

       

      Validation passed so the ejb-jar.xml seems to be fine. Any ideas what this error could be ?

        • 1. Re: Error Deployment MDB
          mitrev83

          have you fix this  I'm also trying to migrate my project from jboss5 to jboss7 and having the same problems I'm not able to find many information about this problem on the  web so if you have past this problem please share

          • 2. Re: Error Deployment MDB
            sfcoy

            I'm guessing that the original problem was caused by the leading "/" in the res-ref-name elements. Removing the "/" should have resolved that problem.