1:09 p.m.
Max Rydahl Andersen created AS7-3684:
----------------------------------------
Summary: 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
1:29 p.m.
[
https://issues.jboss.org/browse/AS7-3684?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-3684:
-----------------------------------
{quote}
JBOSS_HOME: C:\Program Files (x86)-bin-\jboss710-cr1b
{quote}
1) Do not install JBoss or Java in a folder containing space in its path name.
2)
{quote}
Also tested in "C:\temp\JBoss 7", same result.
{quote}
That one too has a space in its path name "JBoss 7"
3) I know that we should ideally allow it to work with such folders too, but it's
quite common issue with a feasible (and commonly accepted) workaround. So I guess, it
really isn't a blocker IMO. Furthermore, there's already a JIRA for this here
AS7-3337.
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
2:59 p.m.
[
https://issues.jboss.org/browse/AS7-3684?page=com.atlassian.jira.plugin.s...
]
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
3:05 p.m.
[
https://issues.jboss.org/browse/AS7-3684?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-3684:
-----------------------------------
{quote}
So, sorry for the wall of text :) I hope you have not taken any offense but I think this
is important for corporate environments.
{quote}
No I haven't :) My previous reply was to make sure that whoever runs into issue
shouldn't really have "wait" for a fix to try out AS7. Some users don't
know about the space problem, so I wanted to make that part clear in this JIRA.
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
3:25 p.m.
[
https://issues.jboss.org/browse/AS7-3684?page=com.atlassian.jira.plugin.s...
]
Carlo de Wolf updated AS7-3684:
-------------------------------
Workaround Description: Do not install JBoss or Java in a folder containing space in
its path name.
Workaround: Workaround Exists
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
4:19 p.m.
[
https://issues.jboss.org/browse/AS7-3684?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen commented on AS7-3684:
------------------------------------------
p.s. default configured Windows 7 won't allow users to write outside their home
directory which by default has spaces - so the workaround doesn't work for those
without full admin access (i.e. many corporate users or simply those who don't wish to
run with full admin privileges)
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
10:45 p.m.
[
https://issues.jboss.org/browse/AS7-3684?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-3684.
-----------------------------------
Assignee: Jason Greene (was: Brian Stansberry)
Resolution: Done
Resolved via
https://github.com/jbossas/jboss-as/commit/9a94ea456a9abe7c634513ec260e48...
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: Jason Greene
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
4625
days inactive
4625
days old
6 comments
5 participants
participants (5)
-
Brian Stansberry (JIRA) -
Carlo de Wolf (JIRA)
-
jaikiran pai (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Thomas Reinhardt (JIRA)