4 Replies Latest reply on Sep 19, 2014 10:21 AM by Jboss User

    Migration issue from Jboss-eap 5.0 to jboss-eap-6.1 []

    Jboss User Newbie

      Hi , am trying to migrate an EAR from Jboss-eap 5.0 to jboss-eap-6.1 and facing the below posted issue , any help or advise would be great !!!

       

      15:08:41,836 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.subunit."TestEAR.ear"."TestEJB.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."TestEAR.ear"."TestEJB.jar" .PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "TestEJB.jar" of deployment "TestEAR.ear"
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.7.0_25]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.7.0_25]
        at java.lang.Thread.run(Thread.java:619) [rt.jar:1.7.0_25]
      Caused by: java.lang.IllegalArgumentException: JBAS011084: componentClassName is null
        at org.jboss.as.ee.component.ComponentDescription.<init>(ComponentDescription.java:144)
        at org.jboss.as.ejb3.component.EJBComponentDescription.<init>(EJBComponentDescription.java:264)
        at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription.<init>(MessageDrivenComponentDescription.java:94)
        at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageDrivenBeanMetaData(MessageDrivenComponentDescriptionFactory.java:242)
        at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processBeanMetaData(MessageDrivenComponentDescriptionFactory.java:87)
        at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processBeanMetaData(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:65)
        at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.processDeploymentDescriptor(AbstractDeploymentUnitProcessor.java:143)
        at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:84)
        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]

        • 1. Re: Migration issue from Jboss-eap 5.0 to jboss-eap-6.1 []
          jaikiran pai Master

          Do you have any MDBs either annotated or configured in ejb-jar.xml? What do they look like?

          • 2. Re: Migration issue from Jboss-eap 5.0 to jboss-eap-6.1 []
            Jboss User Newbie

            Hi Jai,

             

            PFB the code snippet,

             

             

             

            ----------------------- MDB --------------------------------------------------------

             

             

            @MessageDriven(name = "TestMDB", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "java:jms/test/testQueue"),

              @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "200") })

            @Depends({ "jboss.messaging.destination:service=Queue,name=testQueue", "jboss.j2ee:ear=test-ear.ear,jar=test-ejb.jar,name=TestBean,service=EJB3" })

             

             

            @TransactionAttribute(NOT_SUPPORTED)

            public class TestMDB implements MessageListener {

             

             

            public void onMessage(Message message) {

             

            }

            }

             

             

            ----------------------- ejb-jar.xml -------------------------------------------------

             

             

            <enterprise-beans>

                    <message-driven>

                        <ejb-name>TestMDB</ejb-name>

                        <env-entry>

                            <description>Test service</description>

                            <env-entry-name>testAddress</env-entry-name>

                            <env-entry-type>java.lang.String</env-entry-type>

                            <env-entry-value>""</env-entry-value>

                        </env-entry>

                        <ejb-ref>

                            <ejb-ref-name>testService</ejb-ref-name>

                            <ejb-ref-type>Session</ejb-ref-type>

                            <remote>com.test.TestService</remote>

                        </ejb-ref>

                    </message-driven>

            </enterprise-beans>

            • 3. Re: Migration issue from Jboss-eap 5.0 to jboss-eap-6.1 []
              jaikiran pai Master

              Does it work if in your ejb-jar.xml, you add the following after the ejb-name element:

               

              <ejb-class>fully.qualified.classname.of.TestMDB</ejb-class>

              • 4. Re: Migration issue from Jboss-eap 5.0 to jboss-eap-6.1 []
                Jboss User Newbie

                Am still facing issues !!! please clarify this doubt the current versions which we make use of  are JBoss 5 EAP & EJB 3.0 which we are migrating to JBoss EAS 6, so is it necessary to migrate the EJB as well to 3.1 or does the older version will still be working fine ?