facebook

EJB module deployment Error

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #294906 Reply

    newbie2009
    Member

    Hi,
    While trying to deploy my EAR (web and ejb modules) into glass fish v2 , I am getting the below error. I selected the exploded deployment.

    INFO: Deployment by user Unknown of module [ear name] (type=Application) failed, elapsed time 3704 ms
    Feb 17, 2009 2:07:50 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer parseResult
    SEVERE: “DPL8011: autodeployment failure while deploying the application : Error loading deployment descriptors for module [[ear name]] — Invalid ejb jar [[ejb module name]]: it contains zero ejb.
    Note:
    1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.
    2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
    3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.

    Feb 17, 2009 2:07:50 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer markFileAfterDeployment
    INFO: [AutoDeploy] Autodeploy failed : C:\Sun\AppServer\domains\myecl\autodeploy\[ear name].ear.
    Feb 17, 2009 2:12:38 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer deploy
    INFO: [AutoDeploy] Selecting file C:\Sun\AppServer\domains\myecl\autodeploy\[ear name].ear for autodeployment.
    Feb 17, 2009 2:12:38 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo <init>
    INFO: Deployment by user Unknown of module [ear name] (type=Application) starting
    Feb 17, 2009 2:13:45 AM com.sun.enterprise.deployment.phasing.J2EECPhase runPhase
    SEVERE: Exception occured in J2EEC Phasejava.lang.IllegalArgumentException: Invalid ejb jar [ejb module name]: it contains zero ejb.
    Note:
    1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.
    2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
    3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.
    com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [[ear name]] — Invalid ejb jar [ejb module name]: it contains zero ejb.
    Note:
    1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.
    2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
    3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.
    at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:390)
    at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:358)
    at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:226)
    at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148)
    at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:276)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:294)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:555)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:375)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:358)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:464)
    at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
    at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.invokeDeploymentService(AutoDeployer.java:564)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployJavaEEArchive(AutoDeployer.java:545)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:492)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:267)
    at com.sun.enterprise.deployment.autodeploy.AutoDeployControllerImpl$AutoDeployTask.run(AutoDeployControllerImpl.java:374)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)
    Caused by: java.lang.IllegalArgumentException: Invalid ejb jar [ejb module name]: it contains zero ejb.
    Note:
    1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.
    2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
    3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.
    at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:95)
    at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:82)
    at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:729)
    at com.sun.enterprise.deployment.Application.visit(Application.java:1754)
    at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:470)
    at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:790)
    at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744)
    at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349)
    … 34 more
    Feb 17, 2009 2:13:45 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo reportEnd
    INFO: Deployment by user Unknown of module [ear name] (type=Application) failed, elapsed time 67199 ms

    thanks

    #294953 Reply

    support-joy
    Member

    Hey newbie2009,

    INFO: Deployment by user Unknown of module [ear name] (type=Application) failed, elapsed time 3704 ms
    Feb 17, 2009 2:07:50 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer parseResult
    SEVERE: “DPL8011: autodeployment failure while deploying the application : Error loading deployment descriptors for module [[ear name]] — Invalid ejb jar [[ejb module name]]: it contains zero ejb.
    Note:
    1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean.
    2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar.
    3. If the jar file contains valid EJBs which are annotated with EJB component level annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly.

    Your EJB module doesn’t contain any session/entity/message driven bean. I would recommend you to go through http://www.myeclipseide.com/documentation/quickstarts/earprojects/

    You can also download the sample TranderX enterprise application from this tutorial and deploy.

    Let me know if this helps!

Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: EJB module deployment Error

You must be logged in to post in the forum log in