[JBoss-dev] [ jboss-Bugs-673289 ] Deployment of Exploded EAR failing

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Bugs item #673289, was opened at 2003-01-23 14:35
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=673289&group_id=22866

Category: JBossServer
Group: v3.2
>Status: Closed
Resolution: Works For Me
Priority: 5
Submitted By: J. Rhett Aultman (cuplan)
Assigned to: Nobody/Anonymous (nobody)
Summary: Deployment of Exploded EAR failing

Initial Comment:
We have encountered a problem in deploying exploded 
EAR files under JBoss 3.2rc1.  We did not experience 
this issue with the betas.

Below is the log from JBoss when deploying an 
application first as an EAR file and then as an exploded 
EAR (an EAR file's structure expanded out in directories 
rather than being in a single file):

Loads fine when ear is not exploded.

14:14:00,562 INFO  [MainDeployer] Starting deployment 
of package: file:/C:/Documents and Settings/jmiller/My 
Development/workspace/FCCIModel/deploy/fccimodel.ea
r
14:14:00,572 INFO  [EARDeployer] Init J2EE 
application: file:/C:/Documents and Settings/jmiller/My 
Development/workspace/FCCIModel/deploy/fccimodel.ea
r
14:14:00,662 INFO  [EJBDeployer] looking for nested 
deployments in : file:/C:/java/jboss-
3.2.0RC1/server/default/tmp/deploy/C/Documents and 
Settings/jmiller/My 
Development/workspace/FCCIModel/deploy/fccimodel.ea
r/33.fccimodel.ear-contents/fccimodel.jar
14:14:00,852 INFO  [EjbModule] Creating
14:14:00,902 INFO  [EjbModule] Deploying 
FCCIModelBean
14:14:00,942 INFO  [StatelessSessionContainer] 
Creating
14:14:00,952 INFO  [StatelessSessionContainer] 
Created
14:14:00,962 INFO  [EjbModule] Created
14:14:00,962 INFO  [EjbModule] Starting
14:14:00,962 INFO  [StatelessSessionContainer] 
Starting
14:14:01,012 INFO  [StatelessSessionContainer] Started
14:14:01,022 INFO  [EjbModule] Started
14:14:01,022 INFO  [MainDeployer] Deployed package: 
file:/C:/Documents and Settings/jmiller/My 
Development/workspace/FCCIModel/deploy/fccimodel.ea
r

Exploded ear with exact same structure yields:

14:19:50,432 ERROR [URLDeploymentScanner] Failed 
to deploy: 
org.jboss.deployment.scanner.URLDeploymentScanner$
DeployedURL@f918c54c{ url=file:/C:/Documents and 
Settings/jmiller/My 
Development/workspace/FCCIModel/fccimodel.ear, 
deployedLastModified=0 }
org.jboss.deployment.DeploymentException: exception 
in init of file:/C:/Documents and Settings/jmiller/My 
Development/workspace/FCCIModel/fccimodel.ear; - 
nested throwable: 
(org.jboss.deployment.DeploymentException: No META-
INF/application.xml found)
 at org.jboss.deployment.MainDeployer.init
(MainDeployer.java:712)
 at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:624)
 at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:600)
 at sun.reflect.GeneratedMethodAccessor21.invoke
(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invok
e(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
 at org.jboss.util.jmx.MBeanProxy.invoke
(MBeanProxy.java:174)
 at $Proxy7.deploy(Unknown Source)
 at 
org.jboss.deployment.scanner.URLDeploymentScanner.
deploy(URLDeploymentScanner.java:404)
 at 
org.jboss.deployment.scanner.URLDeploymentScanner.
scan(URLDeploymentScanner.java:545)
 at 
org.jboss.deployment.scanner.AbstractDeploymentScan
ner$ScannerThread.doScan
(AbstractDeploymentScanner.java:195)
 at 
org.jboss.deployment.scanner.AbstractDeploymentScan
ner.startService(AbstractDeploymentScanner.java:268)
 at org.jboss.system.ServiceMBeanSupport.start
(ServiceMBeanSupport.java:197)
 at sun.reflect.GeneratedMethodAccessor7.invoke
(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invok
e(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
 at 
org.jboss.system.ServiceController$ServiceProxy.invoke
(ServiceController.java:957)
 at $Proxy0.start(Unknown Source)
 at org.jboss.system.ServiceController.start
(ServiceController.java:388)
 at sun.reflect.GeneratedMethodAccessor6.invoke
(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invok
e(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
 at org.jboss.util.jmx.MBeanProxy.invoke
(MBeanProxy.java:174)
 at $Proxy5.start(Unknown Source)
 at org.jboss.deployment.SARDeployer.start
(SARDeployer.java:299)
 at org.jboss.deployment.MainDeployer.start
(MainDeployer.java:824)
 at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:636)
 at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:600)
 at org.jboss.deployment.MainDeployer.deploy
(MainDeployer.java:584)
 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:324)
 at 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invok
e(ReflectedMBeanDispatcher.java:284)
 at org.jboss.mx.server.MBeanServerImpl.invoke
(MBeanServerImpl.java:549)
 at org.jboss.util.jmx.MBeanProxy.invoke
(MBeanProxy.java:174)
 at $Proxy6.deploy(Unknown Source)
 at org.jboss.system.server.ServerImpl.doStart
(ServerImpl.java:323)
 at org.jboss.system.server.ServerImpl.start
(ServerImpl.java:230)
 at org.jboss.Main.boot(Main.java:155)
 at org.jboss.Main$1.run(Main.java:393)
 at java.lang.Thread.run(Thread.java:536)
Caused by: 
org.jboss.deployment.DeploymentException: No META-
INF/application.xml found
 at org.jboss.deployment.EARDeployer.init
(EARDeployer.java:76)
 at org.jboss.deployment.MainDeployer.init
(MainDeployer.java:688)
 ... 47 more

----------------------------------------------------------------------

Comment By: J. Rhett Aultman (cuplan)
Date: 2003-01-24 14:51

Message:
Logged In: YES 
user_id=132788

After further review, the source of our problem was that the 
application.xml file for the exploded ear would deploy 
correctly, but required a slight change in syntax in the jboss-
service.xml to explain the search path for deployments.  
Under the 3.0 series, we were using basic Windows paths for 
the deploy search path, whereas under 3.2 we needed to 
include trailing slashes for directories, etc.

----------------------------------------------------------------------

Comment By: Rickard Öberg (rickardoberg)
Date: 2003-01-24 05:58

Message:
Logged In: YES 
user_id=28931

I can deploy exploded EAR's with 3.2RC1, but I can't
redeploy them. JBoss is watching the *directory* for
timestamp changes instead of application.xml, and even if I
change timestamp for the directory nothing happens.

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2003-01-24 03:34

Message:
Logged In: YES 
user_id=175228

An exploded ear in the deploy directory works fine for me. 
Describe exactly how the file:/C:/Documents and 
Settings/jmiller/My 
Development/workspace/FCCIModel/fccimodel.ear is being 
deployed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=673289&group_id=22866