Installing jboss on windows in path with spaces

[lingamr1]

I have trouble running jboss installed under "program files" on Windows OS. One of our customers has the requirement to install all applications under program file folder. When I run jboss installed under program files I get a sqlexception with the hypersonic database saying it could not locate the default.properties file. Is there a fix to this problem. I am using jdk 1.4.0 and jboss 2.4.4. I tried the urlpatch suggested in the users forum with jdk 1.3.1 and jboss 2.4.3 and it did not work either. Any suggestions will be greatly appreciated.

[jcraig]

Change 'Program Files' to 'Progra~1' in all your environment variables etc. I have JBoss installed under the program files directory and it works fine...

[greno]

Did you get your installation working? I am having the same problem with the SQLException trying to read the %jboss.home%\db\hypersonic\default.properties file. I put a blank file there but that didn't change anything. I changed all env vars to PROGRA~1 but that didn't help either. jboss.home is being set in Main.java through a system call so it always ends up being set with "Program%20Files" in its value. I'm not sure if the blank in the path is the problem at all. What should be in the default.properties file?

[greno]

By moving JBoss 2.4.4 into a directory without any spaces in the path (outside of "Program Files") the server now starts.

JBoss: this needs to be fixed. People using windows are accustomed to and even being required to install software under "Program Files".

[jcraig]

After further investigation I have realized that JBoss 2.4.4 does not work correctly when installed under a directory with spaces. I had problems with running Servlets etc.

JBoss 3 Beta seems to work fine when installed under the 'program files' directory. I haven't had any problems SO FAR...

[pbnj130]

It's trying to load the properties file for Hypersonic, the default database that comes with Jboss. If you don't need Hypersonic, you can comment it out in the jboss.jcml file. Just comment out the mbeans that have
name="DefaultDomain:service=Hypersonic"
and
name="DefaultDomain:service=XADataSource,name=DefaultDS"
under the JDBC section (the DefaultDS points to Hypersonic, so you have to comment that out too).
This might only be a temp fix if jboss tries to read any other properties files with the same code, but it seems to work for me.

[pbnj130]

It's trying to load the properties file for Hypersonic, the default database that comes with Jboss. If you don't need Hypersonic, you can comment it out in the jboss.jcml file. Just comment out the mbeans that have
name="DefaultDomain:service=Hypersonic"
and
name="DefaultDomain:service=XADataSource,name=DefaultDS"
under the JDBC section (the DefaultDS points to Hypersonic, so you have to comment that out too).
This might only be a temp fix if jboss tries to read any other properties files with the same code, but it seems to work for me.

[pbnj130]

It's trying to load the properties file for Hypersonic, the default database that comes with Jboss. If you don't need Hypersonic, you can comment it out in the jboss.jcml file. Just comment out the mbeans that have
name="DefaultDomain:service=Hypersonic"
and
name="DefaultDomain:service=XADataSource,name=DefaultDS"
under the JDBC section (the DefaultDS points to Hypersonic, so you have to comment that out too).
This might only be a temp fix if jboss tries to read any other properties files with the same code, but it seems to work for me.

[patmoore]

FYI for everyone out there; we run jboss 3.0.8 just fine with spaces in the classpath. We had to modify jboss-3.0.8_tomcat-4.1.24\tomcat-4.1.x\conf\web.xml changing it so that ant forking for jsp compilation was off.

The config file looked like this when we were done:


<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<init-param>
<param-name>logVerbosityLevel</param-name>
<param-value>WARNING</param-value>
</init-param>
<init-param>
<param-name>fork</param-name>
<param-value>false</param-value>
</init-param>
<load-on-startup>3</load-on-startup>