-
1. Re: no META-INF/application.xml found on new deployment
dhill Feb 4, 2005 10:43 AM (in response to dhill)heres the most relevent piece of the stacktrace
15:11:19,771 ERROR [MainDeployer] Could not initialise deployment: file:/home/nn
guyen/JBoss/jboss-4.0.0/server/standard/deploy/myProjectJboss.ear
org.jboss.deployment.DeploymentException: No META-INF/application.xml found
at org.jboss.deployment.EARDeployer.init(EARDeployer.java:119)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:799)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:736)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
at sun.reflect.GeneratedMethodAccessor37.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces -
2. Re: no META-INF/application.xml found on new deployment
starksm64 Feb 4, 2005 5:19 PM (in response to dhill)And the proof that there is a META-INF/application.xml is where?
-
3. Re: no META-INF/application.xml found on new deployment
dhill Feb 7, 2005 10:11 AM (in response to dhill)this should tell you the story.
----------------------------------------------
2005-02-07 09:42:25,847 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@fcaf1945{ url=file:/home/nnguyen/JBoss/jboss-4.0.1/server/default/deploy/Express.ear, deployedLastModified=1107786617000 }
org.jboss.deployment.DeploymentException: No META-INF/application.xml found
at org.jboss.deployment.EARDeployer.init(EARDeployer.java:119)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:828)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:765)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:144)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:122)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:305)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:463)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194)
2005-02-07 09:42:30,855 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/home/nnguyen/JBoss/jboss-4.0.1/server/default/deploy/Express.ear
2005-02-07 09:42:30,855 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/home/nnguyen/JBoss/jboss-4.0.1/server/default/deploy/Express.ear
2005-02-07 09:42:30,870 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/home/nnguyen/JBoss/jboss-4.0.1/server/default/deploy/Express.ear -> /home/nnguyen/JBoss/jboss-4.0.1/server/default/tmp/deploy/tmp24538Express.ear
2005-02-07 09:42:31,048 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.EARDeployer@94cb8b
2005-02-07 09:42:31,048 INFO [org.jboss.deployment.EARDeployer] Init J2EE application: file:/home/nnguyen/JBoss/jboss-4.0.1/server/default/deploy/Express.ear
2005-02-07 09:42:31,283 DEBUG [org.jboss.deployment.EARDeployer] Extracted deployable content: ExpressPortal.war
2005-02-07 09:42:31,290 DEBUG [org.jboss.deployment.EARDeployer] Extracted deployable content: library/ConfigService.jar
2005-02-07 09:42:31,291 DEBUG [org.jboss.deployment.EARDeployer] Extracted non-deployable content: META-INF/application.xml
-------------------------------------------------
thanks -
4. Re: no META-INF/application.xml found on new deployment
darranl Feb 8, 2005 4:31 AM (in response to dhill)dhill,
How large is the ear file?
Instead of copying using the IDE what happens if you MOVE the ear by hand into deploy? -
5. Re: no META-INF/application.xml found on new deployment
dhill Feb 8, 2005 3:50 PM (in response to dhill)The ear is 22mb and if we copy over then it deploys correctly, any thought ?
don -
6. Re: no META-INF/application.xml found on new deployment
starksm64 Feb 8, 2005 4:08 PM (in response to dhill)Deployment has to be an atomic operation. If your copying large files then copy it to an ignored name (x.ear.bak) and then move it to the deployable name (x.ear).
-
7. Re: no META-INF/application.xml found on new deployment
darranl Feb 8, 2005 6:44 PM (in response to dhill)Gemerally if you are copying a large file (Even on the same partition), every byte needs to be copied to the new file - the file appears before the copy is complete which is why JBoss is raising an error.
If instead you move the file to a different location on the same partition, there is no need for it to be copied byte by byte, instead just the pointer to the file is updated so JBoss will be able to read the entire file without attempting to read a partly written file.