4 Replies Latest reply on Sep 16, 2002 4:47 AM by Hugo de Vaan

    JBoss 3.0.0 bombs

    Hugo de Vaan Newbie

      Hi,

      Today I've downloaded and installed JBoss 3.0.0 (the one that has integrated Tomcat 4.0.3 support). I'm working on a Win2000 machine and I've noticed problems with the batch files concerning spaces in directory names. The BAT files try to switch to "C:\Program Files", but they should state "C:\Progra~1". I've been able to change this myself, but although it fixed the first problem I've encountered another one...

      Whenever I try to boot JBoss it bombs with the following error message: org.jboss.deployment.DeploymentException: url: file:/C:/Program%20Files/Apache%20Group/jboss-3.0.0_tomcat4.0.3/server/default/conf/jboss-service.xml could not be opened, does it exist?

      Please note that this file, when referred to as c:\Progra~1\Apache~1\jboss-~1.3\server\default\conf\jboss-service.xml, exists.

        • 1. Re: JBoss 3.0.0 bombs
          Juha Lindfors Master

          known issue, don't install to dir with spaces in it. bad idea.

          • 2. Re: JBoss 3.0.0 bombs
            Hugo de Vaan Newbie

            Thanks, I'll move it to C:\JBoss3 so it doesn't fall over because of spaces.

            By the way, if this is a known issue, why hasn't anyone on the JBoss development team fixed it yet? If the boot procedure would just use an environment variable or a properties file located in the /bin directory this would not be a problem at all. Seems like a fairly simple patch to me...

            • 3. Re: JBoss 3.0.0 bombs
              Juha Lindfors Master

              AFAIR, its an issue with the URL class -- or maybe its an issue with Windows not being able to correctly handle file: protocol with spaces in it when referring to Windows filesystem.

              So even if the script is fixed, installing to a dir with spaces would still be a bad idea.

              • 4. Re: JBoss 3.0.0 bombs
                Hugo de Vaan Newbie

                Ehr... does class URL change string representations like "c:/Progra~1" to something like "c:/Progra%381"? I'm sorry, I didn't know this behaviour was built in.

                I would join you in the opinion that it's actually more of a Windows bug. After all, if I can type "cd\Program Files" in the CMD window, why on earth does Windows screw up when it says "cd \Program Files" in a BAT file? Some sort of Microsoft logic I guess...

                Anyway, thanks again for pointing out the issue concerning spaces in path names.