-
1. Re: jboss unable to start
wdfink Nov 20, 2011 10:38 AM (in response to hailove)Could you please attach the logfile or output with stacktrace?
Also does you have a fresh unzipped installation or do you change anything?
-
2. Re: jboss unable to start
dkannadasan Nov 22, 2011 4:22 AM (in response to wdfink)I too get the same exception while starting Jboss 6.1.
I do have the logging.properties file under \jboss-6.1.0.Final\bin.
Below is the log
Please help. Thanks.
Calling C:\Servers\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\bin\run.conf.bat
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\Servers\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final
JAVA: C:\Program Files\Java\jdk1.6.0_25\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128m -Xmx512m -XX:MaxPermSize=256m -server
CLASSPATH: C:\Program Files\Java\jdk1.6.0_25\lib\tools.jar;C:\Servers\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\bin\run.jar
===============================================================================
Unable to read the logging configuration from 'file:logging.properties' (java.io.FileNotFoundException: logging.properties (The system cannot find the file specified))
-
3. Re: jboss unable to start
wdfink Nov 22, 2011 4:25 AM (in response to dkannadasan)Install the JDK with a path no using spaces, I think this will fix your problem.
You can copy jdk1.6.0_25 simple to c:\ for test and set JAVA_HOME before starting jboss or edit run.conf.bat for this.
-
4. Re: jboss unable to start
lindsaybraine Dec 2, 2011 1:34 AM (in response to wdfink)I hit the same problem with latest 6.1 binaries from Hudson and the GA 6.1 from the download page
I followed the suggestion from Wolf_Dieter - but with no luck:
D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final>bin\run.bat
Calling D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\bin\run.conf.bat
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final
JAVA: d:\jre6u27\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInter
00 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true
CLASSPATH: D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\bin\run.jar
===============================================================================
Unable to read the logging configuration from 'file:logging.properties' (java.io.FileNotFoundException: logging.properties (The system cannot find the
ified))
Terminate batch job (Y/N)? y
It looks like the 6.1 trunk is well and truely broken !!
Are there anymore thoughts on how this might be solved ??
-
5. Re: jboss unable to start
wdfink Dec 2, 2011 2:35 AM (in response to lindsaybraine)If you download the lates AS6 from jboss.org and unzip in the same directory, does this installation work?
Also you can edit the run.bat and set "echo on" that all commands are displayed it might give a hint.
-
6. Re: jboss unable to start
lindsaybraine Dec 2, 2011 6:52 AM (in response to wdfink)Wolf-Dieter
I pulled the latest JBoss-6 binary from Hudson : http://hudson.jboss.org/jenkins/view/JBoss%20AS/job/JBoss-AS-6.1.x/lastSuccessfulBuild/artifact/JBossAS_6_1/build/target/jboss-6.1.x.zip
I unpacked and pointed JAVA_HOME to a JRE version with a space in the JRE pathname.
The same error is show :
Unable to read the logging configuration from 'file:logging.properties' (java.io.FileNotFoundException: logging.properties (The system cannot find the
ified))
I added 'echo on' the the first line on the run.bat script :
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>bin\run.bat
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem -------------------------------------------------------------------------
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem JBoss Bootstrap Script for Windows
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem -------------------------------------------------------------------------
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem $Id: run.bat 111395 2011-05-18 07:45:07Z beve $
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if "Windows_NT" == "Windows_NT" (set "DIRNAME=D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\" ) else (set DIRNAME=.\ )
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem Read an optional configuration file.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if "x" == "x" (set "RUN_CONF=D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.conf.bat" )
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if exist "D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.conf.bat" (
echo Calling D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.conf.bat
call "D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.conf.bat"
) else (echo Config file not found D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.conf.bat )
Calling D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.conf.bat
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem ### -*- batch file -*- ######################################################
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # ##
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # JBoss Bootstrap Script Configuration ##
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # ##
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #############################################################################
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # $Id: run.conf.bat 88820 2009-05-13 15:25:44Z dimitris@jboss.org $
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # This batch file is executed by run.bat to initialize the environment
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # variables that run.bat uses. It is recommended to use this file to
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # configure these variables, rather than modifying run.bat itself.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if not "x" == "x" goto JAVA_OPTS_SET
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # Specify the JBoss Profiler configuration file to load.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # Default is to not load a JBoss Profiler configuration file.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem set "PROFILER=\bin\jboss-profiler.properties"
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # Specify the location of the Java home directory (it is recommended that
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # this always be set). If set, then "D:\jre6u27\bin\java" will be used as
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # the Java VM executable; otherwise, "" will be used (see below).
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem set "JAVA_HOME=C:\opt\jdk1.6.0_13"
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # Specify the exact Java VM executable to use - only used if JAVA_HOME is
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # not set. Default is "java".
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem set "JAVA=C:\opt\jdk1.6.0_13\bin\java"
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # Specify options to pass to the Java VM. Note, there are some additional
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # options that are always passed by run.bat.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem #
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # JVM memory allocation pool parameters - modify as appropriate.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>set "JAVA_OPTS=-Xms128M -Xmx512M -XX:MaxPermSize=256M"
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # Reduce the RMI GCs to once per hour for Sun JVMs.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>set "JAVA_OPTS=-Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterv
=3600000"
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # Warn when resolving remote XML DTDs or schemas.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>set "JAVA_OPTS=-Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterv
l=3600000 -Dorg.jboss.resolver.warning=true"
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # Sample JPDA settings for remote socket debugging
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem set "JAVA_OPTS=-Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcIn
erval=3600000 -Dorg.jboss.resolver.warning=true -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem # Sample JPDA settings for shared memory debugging
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem set "JAVA_OPTS=-Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcIn
erval=3600000 -Dorg.jboss.resolver.warning=true -Xrunjdwp:transport=dt_shmem,address=jboss,server=y,suspend=n"
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>pushd D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\..
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if "x" == "x" (set "JBOSS_HOME=D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT" )
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>popd
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>set DIRNAME=
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if "Windows_NT" == "Windows_NT" (set "PROGNAME=run.bat" ) else (set "PROGNAME=run.bat" )
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem Setup JBoss specific properties
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>set JAVA_OPTS=-Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512M -XX:MaxPermSize=256M
-Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if "xD:\jre6u27" == "x" (
set JAVA=java
echo JAVA_HOME is not set. Unexpected results may occur.
echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
) else (
set "JAVA=D:\jre6u27\bin\java"
if exist "D:\jre6u27\lib\tools.jar" (set "JAVAC_JAR=D:\jre6u27\lib\tools.jar" )
)
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem Add -server to the JVM options, if supported
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>"D:\jre6u27\bin\java" -server -version 2>&1 | findstr /I hotspot 1>nul
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if not errorlevel 1 (set "JAVA_OPTS=-Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512
-XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -server" )
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem Add native to the PATH if present
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>set JBOSS_NATIVE_HOME=
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>set CHECK_NATIVE_HOME=
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if exist "D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\libtcnative-1.dll" (set "CHECK_NATIVE_HOME=D:\jboss-6.1.x\jboss-6.1.1-SNA
SHOT\bin" ) else if exist "D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\..\native\bin" (set "CHECK_NATIVE_HOME=D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\..\native\bin" ) el
e if exist "D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\native\bin" (set "CHECK_NATIVE_HOME=D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\native\bin" )
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if "x" == "x" goto WITHOUT_JBOSS_NATIVE
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem Find run.jar, or we can't continue
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if exist "D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.jar" (if "x" == "x" (set "RUNJAR=D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\
in\run.jar" ) else (set "RUNJAR=;D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.jar" ) ) else (
echo Could not locate "D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.jar".
echo Please check that you are in the bin directory when running this script.
goto END
)
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem If JBOSS_CLASSPATH empty, don't include it, as this will
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem result in including the local directory in the classpath, which makes
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem error tracking harder.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if "x" == "x" (set "RUN_CLASSPATH=D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.jar" ) else (set "RUN_CLASSPATH=;D:\jboss-6.
.x\jboss-6.1.1-SNAPSHOT\bin\run.jar" )
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>set JBOSS_CLASSPATH=D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.jar
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem Setup JBoss specific properties
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>rem Setup the java endorsed dirs
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>set JBOSS_ENDORSED_DIRS=D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\lib\endorsed
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo ===============================================================================
===============================================================================
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo JBoss Bootstrap Environment
JBoss Bootstrap Environment
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo JBOSS_HOME: D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT
JBOSS_HOME: D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo JAVA: D:\jre6u27\bin\java
JAVA: D:\jre6u27\bin\java
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo JAVA_OPTS: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512M -XX:MaxPermSize=
56M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true
JAVA_OPTS: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600
00 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo CLASSPATH: D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.jar
CLASSPATH: D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.jar
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo ===============================================================================
===============================================================================
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>echo.
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>"D:\jre6u27\bin\java" -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512M -XX:MaxPermS
ze=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Djava.endorsed.dirs="D:\jboss-6.1
x\jboss-6.1.1-SNAPSHOT\lib\endorsed" -classpath "D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.jar" org.jboss.Main
Unable to read the logging configuration from 'file:logging.properties' (java.io.FileNotFoundException: logging.properties (The system cannot find the file spe
ified))
Terminate batch job (Y/N)?
^C
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if ERRORLEVEL 10 goto RESTART
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>if "x" == "x" pause
Press any key to continue . . .
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>
-
7. Re: jboss unable to start
lindsaybraine Dec 2, 2011 7:20 AM (in response to lindsaybraine)Wolf-Dieter
I added the logging.properties file back into run.jar file - I still got the error message - but JBoss did start :
D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT>bin\run.bat
Calling D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.conf.bat
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT
JAVA: D:\jre6u27\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=36000
00 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true
CLASSPATH: D:\jboss-6.1.x\jboss-6.1.1-SNAPSHOT\bin\run.jar
===============================================================================
Unable to read the logging configuration from 'file:logging.properties' (java.io.FileNotFoundException: logging.properties (The system cannot find the file spec
ified))
12:14:22,539 INFO [AbstractJBossASServerBase] Server Configuration:
JBOSS_HOME URL: file:/D:/jboss-6.1.x/jboss-6.1.1-SNAPSHOT/
Bootstrap: $JBOSS_HOME\server/default/conf/bootstrap.xml
Common Base: $JBOSS_HOME\common/
Common Library: $JBOSS_HOME\common/lib/
Server Name: default
Server Base: $JBOSS_HOME\server/
Server Library: $JBOSS_HOME\server/default/lib/
Server Config: $JBOSS_HOME\server/default/conf/
Server Home: $JBOSS_HOME\server/default/
Server Data: $JBOSS_HOME\server/default/data
Server Log: $JBOSS_HOME\server/default/log/
Server Temp: $JBOSS_HOME\server/default/tmp/
12:14:22,599 INFO [AbstractServer] Starting: JBossAS [6.1.1.SNAPSHOT "Neo"]
12:14:24,300 INFO [ServerInfo] Java version: 1.6.0_27,Sun Microsystems Inc.
12:14:24,302 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_27-b07)
-
8. Re: jboss unable to start
wdfink Dec 2, 2011 8:19 AM (in response to lindsaybraine)Sorry, what I meant is to download the 6.1.FINAL from
http://www.jboss.org/jbossas/downloads/
instead of using a snapshot.
-
9. Re: jboss unable to start
lindsaybraine Dec 2, 2011 9:09 AM (in response to wdfink)Wolf-Dieter
Same - completely
D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final>bin\run.bat
Calling D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\bin\run.conf.bat
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final
JAVA: D:\Program Files\Java\jdk1.7.0\jre\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=36000
00 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -server
CLASSPATH: D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\bin\run.jar
===============================================================================
Unable to read the logging configuration from 'file:logging.properties' (java.io.FileNotFoundException: logging.properties (The system cannot find the file spec
ified))
Terminate batch job (Y/N)?
^CPress any key to continue . . .
-
10. Re: jboss unable to start
wdfink Dec 2, 2011 9:19 AM (in response to lindsaybraine)There is a ' ' in the java path, also you use JDK7.
Can you check it with the same JDK as before?
For me 6.1.0.FINAL starts perfect (but on Fedora), let me try WIn later.
BTW what version of Wndows you use?
-
11. Re: jboss unable to start
lindsaybraine Dec 2, 2011 10:01 AM (in response to wdfink)Apologies!
D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final>bin\run.bat
Calling D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\bin\run.conf.bat
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final
JAVA: d:\jre6u27\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=36000
00 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true
CLASSPATH: D:\jboss-as-distribution-6.1.0.Final\jboss-6.1.0.Final\bin\run.jar
===============================================================================
Unable to read the logging configuration from 'file:logging.properties' (java.io.FileNotFoundException: logging.properties (The system cannot find the file spec
ified))
I am seeing this on Windows 7 and Windows 2008.If I copy run.bat and run.jar from 6.0 into bin directory - the 6.1.1 Latest and the 6.1.1 Final both startup fine.
Actually - when I say startup fine - what I means is that output is logged to the console, boot.log and server.log.
With the 6.1.1 Latest and the 6.1.1 Final builds it looks like it is just the logging bootstrap that is broken - not the functioning AS services themselves.
-
12. Re: jboss unable to start
lindsaybraine Dec 2, 2011 12:43 PM (in response to lindsaybraine)I should have added that I can tell this because I could connect to console on localhost:8080
-
13. Re: jboss unable to start
wdfink Dec 3, 2011 4:53 AM (in response to lindsaybraine)Yep you right.
A fresh download start on my Win7 (64 and 32 bit) will fail.
After a while I see a java.lang.StackOverflowError thrown from the UncaughtExceptionHandler in thread "Thread-2"
The JBoss looks not working.
A quick check of JIRA does not show a problem like this.
If I'll find time I will check a bit further.
-
14. Re: jboss unable to start
pac09 Dec 8, 2011 9:31 PM (in response to hailove)I got an issue configuring JBoss with NetBeans IDE, the server does not start and sends this message (Anyone in the same situation??)
In Win7 on console I got no issues even with jboss-seam-2.2.2.Final ... I modify the file build.properties in console works also FINE but I want to use NetBeans IDE, and server does not start... when I try it in NetBeans I MUST shutdown.bat the JBoss then service.bat (to unistall service) and works AGAIN in cmd BUT... does ANYONE KNOWS how to "ADD SERVER" properly in NetBeans?? I have read ... Java EE 6 Development with NetBeans 7 by David Hefellfinger also the JBoss Seam 2.2.2.Final Reference (this last one DOES not say anything about working with NetBeans) .. ANY HELP
[NetBeans Output]
Calling C:\jboss-6.1.0.Final\bin\run.conf.bat
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\jboss-6.1.0.Final
JAVA: C:\Program Files (x86)\Java\jdk1.7.0\bin\java
JAVA_OPTS: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128m -Xmx512m -XX:MaxPermSize=256m -server
CLASSPATH: C:\Program Files (x86)\Java\jdk1.7.0\lib\tools.jar;C:\jboss-6.1.0.Final\bin\run.jar
===============================================================================
Unable to read the logging configuration from 'file:logging.properties' (java.io.FileNotFoundException: logging.properties (The system cannot find the file specified))