problem if blank in jboss installation path

[lunxian]

We are using jboss 3.2.1 with integrated tomcat 4.1.24. and if i installed jboss3.2.1 into a path with a blank, there is a exception when running. I know it is because the command "javac" can't resolve the classpath with a blank.
And so, this is a known problem and fixed in a newer jboss version ?

Any suggestions appreciated.

[jonlee]

This problem is related to Java rather than JBoss. In fact having a space in the directory paths for the JDK/JRE and/or JBoss will break a number of things, including JNDI, RMI and the Jasper Ant (Tomcat/Jetty) operations. This has been known for a while - since at least 2.2 I think for JBoss. It is not recommended to run any Java JDK/JRE or Java servers in such Windows directory paths. That is why I believe the Sun JDK install defaults to a non-space contained directory (off the root).

[lunxian]

any suggestion?

[lunxian]

If can't resolve it, I must suggest my customer to install the program with jboss in a path with no blank.

[jonlee]

There are no other fixes for the problem AFAIK. The JSP problem is related to the manner in which Tomcat/Jetty invokes the Java compiler via Ant - a short term fix is possibly not to fork the compiler. Similiarly, Sun have not sought to address the JNDI/RMI binding issue - lookups are usually broken when there is a space in the directory path for the JNDI server. JBoss can only work within the bounds of the JVM's operation so this is a little beyond the scope of JBoss to rectify. Similarly, Jetty and Tomcat code are not under the control of JBoss developers. The only known fix from a JBoss perspective is to install in a path that contains no spaces. This avoids any number of problems with operating J2EE services under the JVM.

Note that this problem is Windows specific as UNIX/Linux systems do not support as standard, spaces in directory names.

[patmoore]

Jboss 3.0.8 works fine with spaces if tomcat is set not to fork ant when compiling jsp pages.