The problem is with the jboss.net deployer.
It opens the archive using a classloader.getResource()
(which under windows will lock the file)
to see whether it contains a certain descriptor.

You are seeing a difference because in the jboss distribution,
jboss-net.sar is loaded before jbossweb-tomcat41.sar

When you make the copy, the timestamps or nodes in the directory change
such that jboss-net.sar is loaded after jbossweb-tomcat41.sar

The deployers are asked to accept a deployment
in the reverse order they are added.

cygwin obviously preserves the original ordering of the files.

If you remove jboss-net.sar the war will deploy correctly.
If you remove the tomcat sar and *copy* it back, it will deploy
after jboss.net (meaning jboss.net will not be asked to check the
deployment).

Regards,
Adrian

On Tue, 2003-12-30 at 17:54, Barlow, Dustin wrote:
> My apologies, I didn't mean to reply to your personal email address.
> 
> I enable TRACE level logging as you instructed.  Attached to this email a
> file called server.log.zip.
> 
> 
> -----Original Message-----
> From: Adrian Brock
> To: Barlow, Dustin
> Cc: [EMAIL PROTECTED]
> Sent: 12/30/2003 12:29 PM
> Subject: RE: [JBoss-user] [jboss-3.2.3] Unable to deploy web-console.war e
> rror
> 
> Please keep it on the list.
> 
> Try enabling TRACE logging in conf/log4j.xml
> to see whether it provides any more information in log/server.log:
> 
>    <!-- TRACE logging for the web container -->
>    <category name="org.jboss.web">
>      <priority value="TRACE" class="org.jboss.logging.XLevel"/>
>    </category>
>    <!-- TRACE logging for the deployment code -->
>    <category name="org.jboss.deployment">
>      <priority value="TRACE" class="org.jboss.logging.XLevel"/>
>    </category>
> 
> Regards,
> Adrian
> 
> On Tue, 2003-12-30 at 17:17, Barlow, Dustin wrote:
> > Just to rule that out, I did a "cp -Rv all foo" and the server comes
> up
> > fine, just like it did when I included the -p option.  (-R means
> recursive,
> > -v means verbose).  So, removing -p option doesn't cause the foo
> server not
> > to start like all the other copying methods do.
> > 
> > I thought it might be a permissions issue early on, but I presume I
> would
> > have the same permission problem on startup when copying the default
> server
> > target to foo as well, but the problem doesn't occur.  Only when
> copying the
> > all directory to foo (or any other name) does the error occur.
> > 
> > I'm also pretty certain that it's not related to file permissions due
> to the
> > fact that I'm running with Administrator priviledges on the Windows
> 2000 box
> > and I have complete control over the directory tree that JBoss lives
> and
> > runs in.
> > 
> > -----Original Message-----
> > From: Adrian Brock
> > To: [EMAIL PROTECTED]
> > Sent: 12/30/2003 11:55 AM
> > Subject: Re: [JBoss-user] [jboss-3.2.3] Unable to deploy
> web-console.war
> > error
> > 
> > My guess is that the -p option on cygwin preserves the 
> > file system permissions, but the other methods do not.
> > 
> > Regards,
> > Adrian
> > 
> > On Tue, 2003-12-30 at 16:49, Barlow, Dustin wrote:
> > > JBoss Version: 3.2.3
> > > JVM: Sun 1.4.2-b28
> > > OS: Windows 2000
> > > 
> > > Using windows explorer, I copied an unmodified "all" server target
> > directory
> > > to "foo".  I then ran "run.bat -c foo" from the command line and I
> get
> > the
> > > following error:
> > > 
> > > 11:34:10,019 INFO  [MainDeployer] Starting deployment of package:
> > >
> file:/D:/java/jboss-3.2.3/server/foo/deploy/management/web-console.war
> > > 11:34:10,120 ERROR [EmbeddedTomcatService] Problem in init 
> > > org.jboss.deployment.DeploymentException: Was unable to move war to:
> > >
> D:\java\jboss-3.2.3\server\foo\tmp\deploy\tmp16433web-console.war.tmp
> > >   at
> > >
> org.jboss.web.AbstractWebContainer.init(AbstractWebContainer.java:296)
> > >   at org.jboss.deployment.MainDeployer.init(MainDeployer.java:696)
> > >   at
> > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:632)
> > >   at
> > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
> > >   at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
> > >   at
> > >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> > Impl
> > > .java:25)
> > >   at java.lang.reflect.Method.invoke(Method.java:324)
> > >   at
> > >
> >
> org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
> > spat
> > > cher.java:284)
> > >   at
> > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
> > >   at
> > org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
> > >   at $Proxy6.deploy(Unknown Source)
> > >   at
> > >
> >
> org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentSc
> > anne
> > > r.java:302)
> > >   at
> > >
> >
> org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScan
> > ner.
> > > java:476)
> > >   at
> > >
> >
> org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doS
> > can(
> > > AbstractDeploymentScanner.java:201)
> > >   at
> > >
> >
> org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(Abst
> > ract
> > > DeploymentScanner.java:274)
> > >   at
> > >
> >
> org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
> > >   at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
> > >   at
> > >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> > Impl
> > > .java:25)
> > >   at java.lang.reflect.Method.invoke(Method.java:324)
> > >   at
> > >
> >
> org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
> > spat
> > > cher.java:284)
> > >   at
> > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
> > >   at
> > >
> >
> org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController
> > .jav
> > > a:976)
> > >   at $Proxy0.start(Unknown Source)
> > >   at
> > > org.jboss.system.ServiceController.start(ServiceController.java:394)
> > >   at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
> > >   at
> > >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> > Impl
> > > .java:25)
> > >   at java.lang.reflect.Method.invoke(Method.java:324)
> > >   at
> > >
> >
> org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
> > spat
> > > cher.java:284)
> > >   at
> > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
> > >   at
> > org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
> > >   at $Proxy4.start(Unknown Source)
> > >   at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
> > >   at
> > org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
> > >   at
> > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
> > >   at
> > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
> > >   at
> > org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)
> > >   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > >   at
> > >
> >
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> > a:39
> > > )
> > >   at
> > >
> >
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> > Impl
> > > .java:25)
> > >   at java.lang.reflect.Method.invoke(Method.java:324)
> > >   at
> > >
> >
> org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDi
> > spat
> > > cher.java:284)
> > >   at
> > > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
> > >   at
> > org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
> > >   at $Proxy5.deploy(Unknown Source)
> > >   at
> > org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
> > >   at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
> > >   at org.jboss.Main.boot(Main.java:150)
> > >   at org.jboss.Main$1.run(Main.java:395)
> > >   at java.lang.Thread.run(Thread.java:534)
> > > 
> > > I do not get this error on Linux or Solaris running the exact same
> > version
> > > of JBoss and Sun's JVM.
> > > 
> > > The interesting twist is that if I copy the "all" target to "foo" in
> > Windows
> > > using "cp -Rpv all foo" in cygwin, I do not get the startup error at
> > all.
> > > 
> > > I also tried copying "all" to "foo" with Ant using the following:
> > > 
> > >         <copy  todir="${env.JBOSS_HOME}/server/foo" >
> > >             <fileset dir="${env.JBOSS_HOME}/server/all"/>
> > >         </copy>
> > > 
> > > This results in getting the same deployment error as if I had copied
> > it
> > > using windows explorer.
> > > 
> > > This error only happens when copying the "all" server target
> > directory.
> > > Default and minimal work just fine when copied using either windows
> > > explorer, cygwin, or ant.
> > > 
> > > Attached to this message is a text file called foo_startup.txt that
> > shows
> > > the startup and shutdown of the foo target.
> > > 
> > > Any suggestions?
> > > 
> > > Dustin
-- 
xxxxxxxxxxxxxxxxxxxxxxxx 
Adrian Brock
Director of Support
Back Office
JBoss Group, LLC 
xxxxxxxxxxxxxxxxxxxxxxxx 



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to