3 Replies Latest reply on Dec 20, 2013 7:20 AM by Geoffrey Ragot

    Problem while deploying an ear

    Geoffrey Ragot Newbie

      Hello!

       

      New in Jboss and JEE, i'm testing wildfly.

      I have two questions.

       

      First, i have a connector which use JCA 1.7 and annotations to configure.

      While packaging the connector and deploy directly with the cli tool, this works fine, but when i package the entire project (connector + web archive) in a ear, this doesn't work.

      The web archive is deployed (database created, ejb...) but the adapter doesn't start like when i deployed with the CLI tool.

       

      There is a strange thing in the logs :

      10:02:47,542 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "ear-1.0-SNAPSHOT.ear" (runtime-name: "ear-1.0-SNAPSHOT.ear")

      10:02:47,575 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "null" (runtime-name: "xxx.rar")

       

      Is there a problem with this?

       

      Secondly, when i deploy the connector with the first way, it works, but not the mdb. Tested on Glassfish, it works, Glassfish seems to take the only adapter it know. But not with Wildfly, even with the @ResourceAdapter annotation, i get an error :

      Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found

       

      So, i don't understand, is there a standard manner of deploying a mdb without using proprietary annotation or file descriptor?

       

      I use the latest build of Wildfly.

       

      Thans in advance if somebody can help me.

       

      PS : Sorry for my english

        • 1. Re: Problem while deploying an ear
          Jesper Pedersen Master

          If possible attach the resource adapter archive, with sources along with your standalone.xml file. But, it looks like it doesn't get deployed - did you try the latest validation tool from the IronJacamar standalone distribution ?

           

          Yes, you have to use a vendor specific annotation, or file descriptor, to point your MDB to the right resource adapter.

          • 2. Re: Re: Problem while deploying an ear
            Geoffrey Ragot Newbie

            Here are files.

            The archive contains the resource adapter, the "webservice" (not properly splitted at the moment, i'm beginner in JEE), and the ear module.

             

            Here are the log when i deploy the ear :

            09:58:23,680 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "ear-1.0-SNAPSHOT.ear" (runtime-name: "ear-1.0-SNAPSHOT.ear")

            09:58:23,719 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "null" (runtime-name: "SecureDeskV2ResourceAdapter.rar")

             

            Here are the log when i deploy the connector (which start properly) :

            10:14:39,213 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "SecureDeskV2ResourceAdapter.rar" (runtime-name: "SecureDeskV2ResourceAdapter.rar")

            10:14:39,665 INFO  [com.omwave.securedeskv2.adapter.EntryPoint] (MSC service thread 1-1)  -> Create injector

            10:14:40,023 INFO  [com.omwave.securedeskv2.adapter.EntryPoint] (MSC service thread 1-1)  -> Start

            .........

             

            After when i deploy the "webservice" :

            10:17:38,723 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "SecureDeskV2WebService.war" (runtime-name: "SecureDeskV2WebService.war")

            10:17:39,246 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."SecureDeskV2WebService.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."SecureDeskV2WebService.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "SecureDeskV2WebService.war"

              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]

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

              at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]

            Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found

              at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668) [jboss-msc-1.2.0.CR1.jar:1.2.0.CR1]

              at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:278)

              at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:155)

              at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:82)

              at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:58)

              at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:81)

              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Beta2-SNAPSHOT.jar:8.0.0.Beta2-SNAPSHOT]

              ... 5 more

             

            I have for MDB, the only activated is the com.omwave.securedeskv2.impl.mdb.IpObserver which has the annotation @ResourceAdapter("SecureDeskV2ResourceAdapter.rar").

            There is no specific xml descriptor, i have used only annotations at the moment.

             

            The resource adapter main class is the class com.omwave.securedeskv2.adapter.EntryPoint.

             

            If you need another infos, i can provide it.

            Thanks in advance.

            • 3. Re: Problem while deploying an ear
              Geoffrey Ragot Newbie

              I said that i've not created the ironjacamar.xml file.... is this necessary with annotations on the adapter?