[jboss-jira] [JBoss JIRA] (AS7-3684) AS7.1 can't start on windows

[Thomas Reinhardt (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665282#comment-12665282 ] 

Thomas Reinhardt commented on AS7-3684:
---------------------------------------

1) I don't want to start an old and boring discussion here. But java has absolutely no problems when installed in a path with spaces. On the contrary, the default install path on windows is "c:\program files" and had been for ages. You can use spaces in the classpath arguments for java.exe. You can use them in your Class-Path of the MANIFEST.MF... so java itself is not a problem. I remember issues for very early versions but that was a long time ago. JBoss on the other hand did never work for me when JBOSS_HOME contains spaces.
2) The space was intentional. I should have made this clearer but this was to rule out the parenthesis of the first path.
3) You are absolutely right, this is no blocker and a workaround is easy. Also, it did not work before reliably so there is no problem right now.

The main problem I have with this behavior is that it lets our product look unprofessional. We have always tried to use a platform as intended by the vendor. For windows that means an application goes to %programFiles%, its data to %appdata% etc. Any other behavior is an annoyance for the user/admin at least. We have to do extra work in our installers to check the installation path does not contain spaces. We have to explan our customers why this is neccessary. 
And ultimatively all this is futile. Microsoft will not remove the space(s) from its folders. And this is good because users should not have to think about things like allowed path names. I know that problem normally does not arise in unix environments as most admins do not even try to use spaces in paths. I also would not even think about it. But Microsoft and our customers do and thats just it.

So, sorry for the wall of text :) I hope you have not taken any offense but I think this is important for corporate environments.
                
> AS7.1 can't start on windows
> ----------------------------
>
>                 Key: AS7-3684
>                 URL: https://issues.jboss.org/browse/AS7-3684
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Scripts
>    Affects Versions: 7.1.0.CR1b
>            Reporter: Max Rydahl Andersen
>            Assignee: Brian Stansberry
>            Priority: Blocker
>             Fix For: 7.1.0.Final
>
>
> From Thomas Reinhardt on AS7-241:
> Fails for 7.1.0 cr1b. OS is Windows 7 x64. Java 1.7.0_01_x64 and 1.6.0_26_x64 tested. Also tested in "C:\temp\JBoss 7", same result.
>  
> C:\Program Files (x86)\--bin--\jboss710-cr1b\bin>standalone.bat
> Calling "C:\Program Files (x86)\--bin--\jboss710-cr1b\bin\standalone.conf.bat"
> ===============================================================================
>   JBoss Bootstrap Environment
>   JBOSS_HOME: C:\Program Files (x86)\--bin--\jboss710-cr1b
>   JAVA: C:\java\jdk1.7.0_01_x64\bin\java
>   JAVA_OPTS: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterv
> al=3600000 -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -server
> ===============================================================================
> WARNING: No log manager service descriptor found in specified logmodule org.jboss.logmanager:main
> WARNING: No mbeanserver service descriptor found in specified mbeanserverbuildermodule org.jboss.as.jmx:main
> Exception in thread "main" java.lang.ExceptionInInitializerError
>         at org.jboss.as.server.Main.main(Main.java:92)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.lang.reflect.Method.invoke(Method.java:601)
>         at org.jboss.modules.Module.run(Module.java:248)
>         at org.jboss.modules.Main.main(Main.java:313)
> Caused by: java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to
>  "org.jboss.logmanager.LogManager")
>         at org.jboss.logmanager.Logger.getLogger(Logger.java:60)
>         at org.jboss.logmanager.log4j.BridgeRepositorySelector.<clinit>(BridgeRepositorySelector.java:42)
>         ... 7 more
> Press any key to continue . . .

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira