-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
-
From: Adrian Brock
To: [EMAIL PROTECTED]
Sent: 12/30/2003 2:12 PM
Subject: RE: [JBoss-user] [jboss-3.2.3] Unable to deploy web-console.war e
rror
On Tue, 2003-12-30 at 18:45, Adrian Brock wrote:
The problem is with the jboss.net deployer.
It opens the archive using a classloader.getResource
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
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
!--
Yes, it happens everytime on startup.
I have also tried it on other Windows 2000 boxes in the office, and it works
just fine as well. However, I have had three other Windows 2000 machines
that the error occurs on. I'm not at all sure what the delta is. The
Windows 2000 machines are identical
: [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
