1 Reply Latest reply: Jun 12, 2003 5:40 AM by Jon Barnett RSS

Jboss 3.2.1/Xalan 2.5 web-console.war deployment error

newbieonjboss Newbie

Env: Win2K, JBoss 3.2.1, Xalan 2.5, JDK 1.4.1_02
There's a bug some where either in Xerces (from Xalan 2.5) or Jetty/JBoss 3.2.1 that causes
deployment error.

We needed some features in Xalan 2.5 and so
an upgrade was done on our JBoss 3.2.1 installation.

It turns out that xerces in Xalan 2.5 cause web-console.war to fail deployment.

Here's the stack below. Seems that the 'space' in the
deployed dir is causing xerces to fail. By default,
the TMP, TEMP in Win2k is unset and so it defaults to

C:\Document And Settings\(User)\Jetty....

the work around for this is to set TMP=(Dirname without blanks) and that seems to solve the problem.

Bug????



13:17:34,967 INFO [jbossweb] Registered jboss.web:Jetty=0,JBossWebApplicationContext=3,context=/web-console
13:17:35,030 INFO [jbossweb] Extract jar:file:/D:/VSS/V02/Install/AppSrv/jboss/server/default/tmp/deploy/server/defau
lt/deploy/management/web-console.war/28.web-console.war!/ to C:\Documents and Settings\Joe\Jetty_0_0_0_0_8080__web-cons
ole\webapp
13:17:35,420 WARN [jbossweb] WARNING: Configuration error on jar:file:/D:/VSS/V02/Install/AppSrv/jboss/server/default
/tmp/deploy/server/default/deploy/management/web-console.war/28.web-console.war!/
java.io.FileNotFoundException: C:\Documents%20and%20Settings\Joe\Jetty_0_0_0_0_8080__web-console\webapp\WEB-INF\web.xml

at org.jboss.net.protocol.file.FileURLConnection.connect(FileURLConnection.java:70)
at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:79)
at java.net.URL.openStream(URL.java:960)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.mortbay.xml.XmlParser.parse(XmlParser.java:125)
at org.mortbay.xml.XmlParser.parse(XmlParser.java:140)
at org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext.java:387)
at org.mortbay.j2ee.J2EEWebApplicationContext.start(J2EEWebApplicationContext.java:85)
at org.jboss.jetty.JBossWebApplicationContext.start(JBossWebApplicationContext.java:89)
at org.jboss.jetty.Jetty.deploy(Jetty.java:331)
at org.jboss.jetty.JettyService.performDeploy(JettyService.java:242)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:357)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:640)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
at sun.reflect.GeneratedMethodAccessor25.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.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy7.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:302)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:476)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:20
0)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:273)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
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.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:392)
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.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy5.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:640)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
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.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy6.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:365)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:272)
at org.jboss.Main.boot(Main.java:150)
at org.jboss.Main$1.run(Main.java:388)
at java.lang.Thread.run(Thread.java:536)





  • 1. Re: Jboss 3.2.1/Xalan 2.5 web-console.war deployment error
    Jon Barnett Master

    No, not really a bug unless you count the whole JRE as being intolerant of Windows directory naming. All number of things break including NetBeans, JNDI, RMI and so on when they encounter directory paths with spaces in them. It is interesting that Jetty suddenly has a problem, since normally it would be creating these unpacked application directories in a temp directory under Documents and Settings\User.

    Another way of forcing a temp directory is by including the directive that tells Jetty explicitly where to place the unpacked application. This works for Windows and *nix. We usually use this to stop RedHat periodically clearing out the applications stored in the /var directory.

    e.g. add -Djava.io.tmpdir=/TMP in your invocation of JBoss's run.jar.