geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Forrest Xia (Commented) (JIRA)" <>
Subject [jira] [Commented] (GERONIMO-6291) Cannot start server on windows caused by space chars in the related installation paths
Date Tue, 28 Feb 2012 13:12:48 GMT


Forrest Xia commented on GERONIMO-6291:


I still see some violation against the rule in setjavaenv.bat like these:

set _RUNJAVA="%JRE_HOME%\bin\java"
set _RUNJAVAW="%JRE_HOME%\bin\javaw"
set _RUNJDB="%JAVA_HOME%\bin\jdb"

Can we update them accordingly?
> Cannot start server on windows caused by space chars in the related installation paths
> --------------------------------------------------------------------------------------
>                 Key: GERONIMO-6291
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: startup/shutdown
>    Affects Versions: 3.0, 3.0-beta-2
>            Reporter: Forrest Xia
>            Assignee: Saphen Qiu
>             Fix For: 3.0-beta-2
>         Attachments: GERONIMO-6291-fixSpaceIssue.patch
> Having the latest Geronimo 3.0-beta-2 snapshot build, then doing these steps to reproduce
the issue:
> 1. Install the jdk into a folder with space chars in the path
> 2. Install the geronimo server into a non-space path
> 3. set java_home=c:\path2jdkhome, not that no quotes there
> 4. run command: geronimo_home\bin\geronimo.bat run -l
> You will see a failure something like this:
> '""C:\Java\jdk1.6.0' is not recognized as an internal or external command,
> operable program or batch file.
> Basically, it is caused by the space characters in the windows file path. So to resolve
the issues completely, we need to consider these scenarios:
> 1. JDK installation path includes spaces, and geronimo installation path does not
> 2. JDK installation path does not have, but geronimo has
> 3. Both JDK and Geronimo have space char in the path

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message