Error Loading Deployment Descriptors Glassfish
application in Glassfish Summary: Can't deploy J2EE application in Glassfish Status: VERIFIED FIXED Product: serverplugins Classification: Unclassified Component: Sun Appserver 9 Version: 5.x Hardware: All All Priority: P1 (vote) TargetMilestone: 5.x Assigned To: Vince Kraemer QA Contact: issues@serverplugins URL: Whiteboard: Keywords: Depends on: Blocks: Show dependency tree /graph Reported: 2006-03-09 10:27 UTC by Petr Blaha Modified: 2006-05-31 19:24 UTC (History) CC List: 1 user (show) pjiricka See Also: Issue Type: DEFECT Exception Report : Attachments patch (4.75 KB, patch) 2006-03-09 12:55 UTC, Petr Blaha Details | Diff View All Add an attachment (proposed patch, testcase, etc.) Note You need to log in before you can comment on or make changes to this bug. Description Petr Blaha 2006-03-09 10:27:45 UTC [build 20060309] Steps; 1) create J2EE application with web and ejb module 2) deploy it in App server ERROR: Deploying application in domain failed; Error loading deployment descriptors for module [Znova] -- www.sun.com /home.local/blaha/ide/q-build/netbeans/projects/Znova/nbproject/build-impl.xml:219: Deployment error: The module has not been deployed. See the server log for details. BUILD FAILED (total time: 3 seconds) This feature is working in yesterday's build. Server error: ADM1064:The upload file at [/tmp/s1astempdomain1server184447312/Znova.ear] exists and will be overwritten. ADM1006:Uploading the file to:[/tmp/s1astempdomain1server184447312/Znova.ear] "DPL8005: Deployment Descriptor parsing failure : www.sun.com" Exception occured in J2EEC Phase com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [Znova] -- www.sun.com at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:362) at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:315) at com.sun.enterprise.deployment.backend.AppDeployer.explodeArchive(AppDeployer.java:321) at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:178) at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:125) at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:169) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:95) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:848) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:260) at com
Board ExportXMLWordPrintable Details Type: Bug Status: Resolved Priority: Major Resolution: Fixed Affects Version/s: 9.0peur1 Fix Version/s: 9.1pe_dev Component/s: deployment Labels: None Environment: Operating System: All Platform: All Issuezilla Id: 985 Status Whiteboard: Hide fixed-9.0peur1 Show fixed-9.0peur1 Description I created an ejb jar (that has a stateless EJB in it). I compiled the classes with https://netbeans.org/bugzilla/show_bug.cgi?id=73415 JDK 6. I deployed the jar to GF V1 U1 B5... (which was running under/against J2SE 5 Update 6). Here is what I saw: vbk@ubuntuabihsot:~/glassfish$ bin/asadmin deploy ~/EJBModule2/dist/EJBModule2.jar CLI171 Command deploy failed : Deploying application in domain failed; Error loading deployment descriptors for https://java.net/jira/browse/GLASSFISH-985 module [EJBModule2] - Invalid ejb jar [/home/vbk/glassfish/domains/domain1/applications/j2ee-modules/EJBModule2]: 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. -------------- end quote ---------------------- The server log contained these messages/stack traces: ADM1006:Uploading the file to:[/tmp/s1astempdomain1server-1539301823/EJBModule2.jar] Cannot load foo.NewSessionBean reason : Bad version number in .class file Exception occured in J2EEC Phase com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [EJBModule2] - Invalid ejb jar [/home/vbk/glassfish/domains/domain1/applications/j2ee-modules/EJBModule2]: 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. at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:362) at com.sun.enterprise.deployment.backend.ModuleDeployer.loadDescriptors(Modul
Type: Bug Status: Open Priority: Minor Resolution: Unresolved Affects Version/s: 9.1pe Fix Version/s: not determined Component/s: https://java.net/jira/browse/GLASSFISH-3456 deployment Labels: None Environment: Operating System: Windows XP Platform: PC Issuezilla Id: 3,456 Description build 58 (nightly dated July 31, 2007) Steps to https://docs.oracle.com/cd/E18930_01/html/821-2417/gilfm.html reproduce: 1. explode the attached jar (in say c:\strangebug) 2. attempt to use asadmin deploydir to deploy c:\strangebug\gfdeploy this fails. 3. attempt error loading to use asadmin deploy to deploy c:\strangebug\EnterpriseApplication4.ear this succeeds... As best as I can tell, both of these should work... One other thing to note... the deploydir command takes a LONG TIME to fail while the deploy commend is successful fairly quickly... sample output: C:\glassfish>bin\asadmin error loading deployment deploydir --name testdeploy \strangebug\gfdeploy CLI171 Command deploydir failed : Deploying application in domain failed; Error loading deployment descriptors for module [testdeploy] - Invalid ejb jar [//Foo //-ejb.jar]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or mes sage 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 le vel annotations (@Stateless, @Stateful, @MessageDriven), please check server.log to see whether the annotations were processed properly. C:\glassfish>bin\asadmin deploydir --name testdeploy \strangebug\EnterpriseAppli cation4.ear Command deploydir executed successfully. OptionsSort By NameSort By DateAscendingDescendingDownload AllAttachments Hide issue.jar 31/Jul/07 2:30 PM 6 kB vince kraemer META-INF/MANIFEST.MF 0.1 kB EnterpriseApplication4.ear 4 kB gfdeploy/META-INF/MANIFEST.MF 0.0 kB gfdeploy/.../NewSessionBean.class 0.4 kB gfdeploy/.../
Applications Deploying Applications and Modules To Deploy an Application or Module To Change Targets for a Deployed Application or Module To List Deployed Applications or Modules To Redeploy an Application or Module To Disable an Application or Module To Enable an Application or Module To Undeploy an Application or Module To Reload Changes to Applications or Modules Dynamically To Deploy an Application or Module Automatically To Deploy an Application or Module by Using a Deployment Plan To Deploy an Application or Module in a Directory Format Modifying the Configuration of a Web Application or Module To Set a Web Context Parameter To Unset a Web Context Parameter To List Web Context Parameters To Set a Web Environment Entry To Unset a Web Environment Entry To List Web Environment Entries Web Module Deployment Guidelines EJB Module Deployment Guidelines Deploying a Connector Module To Deploy and Configure a Stand-Alone Connector Module Redeploying a Stand-Alone Connector Module Deploying and Configuring an Embedded Resource Adapter Assembling and Deploying an Application Client Module To Assemble and Deploy an Application Client To Prepare Another Machine for Running an Application Client To Undeploy an Application Client Lifecycle Module Deployment Guidelines Web Service Deployment Guidelines OSGi Bundle Deployment Guidelines Transparent JDBC Connection Pool Reconfiguration Application-Scoped Resources A.The asadmin Deployment Subcommands B.GlassFish Server Deployment Descriptor Files C.Elements of the GlassFish Server Deployment Descriptors Index Deploying Applications and Modules Application deployment is a dynamic process, which means that deployed applications and modules become available without requiring you to restart the server instance. Dynamic deployment can be useful in production environments to bring new applications and modules online easily. If you do restart the server, all deployed components are still deployed and available. The following topics are addressed here: To Deploy an Application or Module To Change Targets for a Deployed Application or Module To List Deployed Applications or Modules To Redeploy an Application or Module To Disable an Application or Module To Enable an Application or Module To Undeploy an Application or Module To Reload Changes to Applications or Modules Dynamically