1 2 Previous Next 28 Replies Latest reply on Jun 10, 2017 8:09 AM by shahbaz07dbit Go to original post
      • 15. Re: jboss unable to start
        wdfink

        Does it help if you use a java installation without having ' ' in the path like 'Program Files'?

        I suppose you have to start netbeans with a different java installation ...

        • 16. Re: jboss unable to start
          dkannadasan

          Dear Wolf, It worked for me.

          I copied the JDK out from "Program Files" and placed in C:\, and then configured JBOSS to point to the new location of JDK.

          It works. thanks for ur idea!!!

          • 17. Re: jboss unable to start
            pac09

            Thanks for the answer Wolf... Nevertheless I really don't know what I'm doing wrong, eveerything seems ok BUT, the cmd displays:

             

            Calling C:\jboss-6.1.0.Final\bin\run.conf.bat

             

            --------------------------------------------------

             

            When I type run command, also I changed the C:\program files\ ... ... route for a route C:\Java\jdk1.7.0_01\bin in JAVA_HOME enviroment variable  and I also have the JBOSS_HOME in a similar route C:\jboss-6.1.0.Final\bin  ... I UNINSTALL the previous Java and BEFORE I used to run the JBOSS in console not in NetBeans, now in anyone it can't run...

             

            Should I change a parameter in the run.conf.bat ... which is called by run.bat??

             

            rem # Default is to not load a JBoss Profiler configuration file.

            rem #

            rem set "PROFILER=%JBOSS_HOME%\bin\jboss-profiler.properties"

             

             

            rem set "JAVA_HOME=C:\opt\jdk1.6.0_13"

            .

            .

            .

            .

            .rem set "JAVA=C:\opt\jdk1.6.0_13\bin\java"

             

             

            Thanks for da support

            • 18. Re: jboss unable to start
              wdfink

              run.conf.bat only do set some variables that might be changed from a user (to avoid changes to run.bat).

              But if JAVA_HOME is set correct the script does not overwrite it and it should work.

               

              What does you see on console in your case?

              • 19. Re: jboss unable to start
                pac09

                Thanks a lot Wolf... actually it works in c:\ ... I added this variables, also I edited the file C:\jboss-6.1.0.Final\jboss-seam-2.2.2.Final\build.properties

                 

                #See build/sample.build.properties for properties you might want to set

                #Tue, 26 Apr 2011 16:30:15 +0200

                 

                mavenized=false

                qualifier=C:\jboss-6.1.0.Final

                 

                --------------------------------------------------------------------------------------------------------------------------------------------------------------

                 

                and the enviroment variables now are :

                 

                ANT_HOME

                C:\apache-ant-1.8.2

                 

                JAVA_HOME

                C:\Java\jdk1.7.0_01

                 

                JBOSS_HOME

                C:\jboss-6.1.0.Final

                 

                Path

                %JAVA_HOME%\bin;%ANT_HOME%\bin

                 

                -------------------------------------------------------------------------------------------------------

                 

                Nevertheless (again), something is not right... I want to run the examples in C:\jboss-6.1.0.Final\jboss-seam-2.2.2.Final\examples

                 

                But after I start running the server, and in another cmd window I executed "ant explode" and then is displaying me this:

                 

                c:\jboss-6.1.0.Final\jboss-seam-2.2.2.Final\examples\booking>ant explode

                Buildfile: c:\jboss-6.1.0.Final\jboss-seam-2.2.2.Final\examples\booking\build.xml

                 

                initcopy:

                 

                initpoms:

                     [echo] Setting up dependencies

                     [copy] Copying 1 file to c:\jboss-6.1.0.Final\jboss-seam-2.2.2.Final\classes\poms

                 

                BUILD FAILED

                c:\jboss-6.1.0.Final\jboss-seam-2.2.2.Final\build\common.build.xml:96: The following error occurred while executing this line:

                c:\jboss-6.1.0.Final\jboss-seam-2.2.2.Final\build\utilities.build.xml:80: artifact:install doesn't support the "settingsFile" attribute

                 

                Total time: 0 seconds

                 

                -----------------------------------------------------------------------------------------------------------------------------------------------------

                 

                What do U think could be the problem?? thanks A LOT for helping BY THE WAY It's been so USEFULL in the process of learning, (I updated the

                C:\apache-ant-1.8.2 by executing the command:)

                 

                ant -f fetch.xml -Ddest=system

                [WILL give some issues, so just update the m2.url property in the lib/library.properties file to http://mirrors.ibiblio.org/pub/mirrors/maven2.]

                 

                so what do U think would be the problem...? I CAN NOT deploy the examples of JBoss SEAM...      :-(

                • 20. Re: jboss unable to start
                  rajmohanpk

                  Hi Wolf - I require your clarification, in debugging this issue. I do set the JAVA_HOME correctly (by avoiding spaces).  When I start my JBoss from command line, it starts fine.  But when I start the JBoss AS from Netbeans either in Start mode (right click on JBoss AS on Netbeans, choose Start) or in Debug Mode , I get the same error stating Unable to read the logging configuration from 'file:logging.properties'. Many thanks for your help!.

                   

                   

                  Console output when the server is started (start or debug mode) from Netbeans:

                  Calling D:\Development\Installation\jboss-6.1.0.Final\bin\run.conf.bat

                  JAVA HOME IS D:\Development\Installation\jdk1.6.0_22

                  ===============================================================================

                   

                   

                    JBoss Bootstrap Environment

                   

                   

                    JBOSS_HOME: D:\Development\Installation\jboss-6.1.0.Final

                   

                   

                    JAVA: D:\Development\Installation\jdk1.6.0_22\bin\java

                   

                   

                    JAVA_OPTS: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128m -Xmx512m -XX:MaxPermSize=256m -server

                   

                   

                    CLASSPATH: D:\Development\Installation\jdk1.6.0_22\lib\tools.jar;D:\Development\Installation\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))

                   

                   

                  Console output when the server is started from command line:

                  D:\Development\Installation\jboss-6.1.0.Final\bin>run.bat

                  Calling D:\Development\Installation\jboss-6.1.0.Final\bin\run.conf.bat

                  JAVA HOME IS D:\Development\Installation\jdk1.6.0_22

                  ===============================================================================

                   

                   

                    JBoss Bootstrap Environment

                   

                   

                    JBOSS_HOME: D:\Development\Installation\jboss-6.1.0.Final

                   

                   

                    JAVA: D:\Development\Installation\jdk1.6.0_22\bin\java

                   

                   

                    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.gcInte

                  rval=3600000 -Dorg.jboss.resolver.warning=true -server

                   

                   

                    CLASSPATH: D:\Development\Installation\jdk1.6.0_22\lib\tools.jar;D:\Development\Installation\jboss-6.1.0.Final\bin\run.jar

                   

                   

                  ===============================================================================

                   

                   

                  14:48:47,166 INFO  [AbstractJBossASServerBase] Server Configuration:

                   

                   

                          JBOSS_HOME URL: file:/D:/Development/Installation/jboss-6.1.0.Final/

                          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/

                   

                   

                  14:48:47,169 INFO  [AbstractServer] Starting: JBossAS [6.1.0.Final "Neo"]

                  14:48:48,739 INFO  [ServerInfo] Java version: 1.6.0_22,Sun Microsystems Inc.

                  14:48:48,740 INFO  [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_22-b04)

                  14:48:48,740 INFO  [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 17.1-b03,Sun Microsystems Inc.

                  14:48:48,740 INFO  [ServerInfo] OS-System: Windows 7 6.1,amd64

                  14:48:48,740 INFO  [ServerInfo] VM arguments: -Dprogram.name=run.bat -Dlogging.configuration=file:logging.properties -Xms128M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=36

                  00000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Djava.endorsed.dirs=D:\Development\Installation\jboss-6.1.0.Final\lib\endorsed

                  14:48:48,785 INFO  [JMXKernel] Legacy JMX core initialized

                  14:48:54,484 INFO  [AbstractServerConfig] JBoss Web Services - Stack CXF Server 3.4.1.GA

                  14:48:55,204 INFO  [JSFImplManagementDeployer] Initialized 3 JSF configurations: [Mojarra-1.2, MyFaces-2.0, Mojarra-2.0]

                  14:49:01,424 WARNING [FileConfigurationParser] AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO jour

                  nal

                  14:49:01,694 INFO  [JMXConnector] starting JMXConnector on host 127.0.0.1:1090

                  14:49:01,794 INFO  [MailService] Mail Service bound to java:/Mail

                  14:49:02,606 INFO  [HornetQServerImpl] live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=D:\Development\Install

                  ation\jboss-6.1.0.Final\server\default\data/hornetq/journal,bindingsDirectory=D:\Development\Installation\jboss-6.1.0.Final\server\default\data/hornetq/bindings,largeMessagesDirectory=D:\Dev

                  elopment\Installation\jboss-6.1.0.Final\server\default\data/hornetq/largemessages,pagingDirectory=D:\Development\Installation\jboss-6.1.0.Final\server\default\data/hornetq/paging)

                  14:49:02,615 INFO  [HornetQServerImpl] Waiting to obtain live lock

                  14:49:02,691 INFO  [JournalStorageManager] Using NIO Journal

                  14:49:02,726 WARNING [HornetQServerImpl] Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the Horn

                  etQ user guide, cluster chapter, for instructions on how to do this.

                  14:49:02,853 INFO  [FileLockNodeManager] Waiting to obtain live lock

                  14:49:02,855 INFO  [FileLockNodeManager] Live Server Obtained live lock

                  14:49:03,461 INFO  [NettyAcceptor] Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 127.0.0.1:5445 for CORE protocol

                  14:49:03,481 INFO  [NettyAcceptor] Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 127.0.0.1:5455 for CORE protocol

                  14:49:03,491 INFO  [HornetQServerImpl] Server is now live

                  14:49:03,491 INFO  [HornetQServerImpl] HornetQ Server version 2.2.5.Final (HQ_2_2_5_FINAL_AS7, 121) [19f70bd5-2e8e-11e1-982c-0026c7b25220] started

                  14:49:03,541 INFO  [WebService] Using RMI server codebase: http://127.0.0.1:8083/

                  14:49:03,721 INFO  [jbossatx] ARJUNA-32010 JBossTS Recovery Service (tag: JBOSSTS_4_14_0_Final) - JBoss Inc.

                  14:49:03,731 INFO  [arjuna] ARJUNA-12324 Start RecoveryActivators

                  14:49:03,751 INFO  [arjuna] ARJUNA-12296 ExpiredEntryMonitor running at Sun, 25 Dec 2011 14:49:03

                  14:49:03,831 INFO  [arjuna] ARJUNA-12310 Recovery manager listening on endpoint 127.0.0.1:4712

                  14:49:03,841 INFO  [arjuna] ARJUNA-12344 RecoveryManagerImple is ready on port 4712

                  14:49:03,841 INFO  [jbossatx] ARJUNA-32013 Starting transaction recovery manager

                  14:49:03,871 INFO  [arjuna] ARJUNA-12163 Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 4713

                  14:49:03,881 INFO  [arjuna] ARJUNA-12337 TransactionStatusManagerItem host: 127.0.0.1 port: 4713

                  14:49:03,881 INFO  [arjuna] ARJUNA-12170 TransactionStatusManager started on port 4713 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService

                  14:49:03,931 INFO  [jbossatx] ARJUNA-32017 JBossTS Transaction Service (JTA version - tag: JBOSSTS_4_14_0_Final) - JBoss Inc.

                  14:49:04,021 INFO  [arjuna] ARJUNA-12202 registering bean jboss.jta:type=ObjectStore.

                  14:49:04,351 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: D:\Development\

                  Installation\jdk1.6.0_22\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32;D:\Development\Installation\jdk1.6.0_22\bin;C:\glassfish3\bin;D:\Development\Install

                  ers\apache-ant-1.8.2\bin;C:\glassfish3\glassfish\bin;C:\glassfish3\bin;D:\Development\Installation\apache-activemq-5.5.0\bin;D:\Development\Installation\apache-maven-3.0.3\bin;D:\Development

                  \Installation\apache-cxf-2.4.2\bin

                  14:49:04,511 INFO  [ModClusterService] Initializing mod_cluster 1.1.0.Final

                  14:49:04,521 INFO  [TomcatDeployment] deploy, ctxPath=/invoker

                  14:49:04,971 INFO  [RARDeployment] Required license terms exist, view vfs:/D:/Development/Installation/jboss-6.1.0.Final/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml

                  14:49:04,991 INFO  [RARDeployment] Required license terms exist, view vfs:/D:/Development/Installation/jboss-6.1.0.Final/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml

                  14:49:05,011 INFO  [RARDeployment] Required license terms exist, view vfs:/D:/Development/Installation/jboss-6.1.0.Final/server/default/deploy/jms-ra.rar/META-INF/ra.xml

                  14:49:05,051 INFO  [HornetQResourceAdapter] HornetQ resource adaptor started

                  14:49:05,071 INFO  [RARDeployment] Required license terms exist, view vfs:/D:/Development/Installation/jboss-6.1.0.Final/server/default/deploy/mail-ra.rar/META-INF/ra.xml

                  14:49:05,091 INFO  [RARDeployment] Required license terms exist, view vfs:/D:/Development/Installation/jboss-6.1.0.Final/server/default/deploy/quartz-ra.rar/META-INF/ra.xml

                  14:49:05,241 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: Thread-2

                  14:49:05,304 INFO  [SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl

                  14:49:05,307 INFO  [QuartzScheduler] Quartz Scheduler v.1.8.3 created.

                  14:49:05,314 INFO  [RAMJobStore] RAMJobStore initialized.

                  14:49:05,321 INFO  [QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v1.8.3) 'JBossQuartzScheduler' with instanceId 'NON_CLUSTERED'

                    Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.

                    NOT STARTED.

                    Currently in standby mode.

                    Number of jobs executed: 0

                    Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.

                    Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

                   

                   

                  14:49:05,342 INFO  [StdSchedulerFactory] Quartz scheduler 'JBossQuartzScheduler' initialized from an externally opened InputStream.

                  14:49:05,345 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.8.3

                  14:49:05,349 INFO  [QuartzScheduler] Scheduler JBossQuartzScheduler_$_NON_CLUSTERED started.

                  14:49:05,772 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'

                  14:49:06,029 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'

                  14:49:06,172 INFO  [xnio] XNIO Version 2.1.0.CR2

                  14:49:06,186 INFO  [nio] XNIO NIO Implementation Version 2.1.0.CR2

                  14:49:06,360 INFO  [remoting] JBoss Remoting version 3.1.0.Beta2

                  14:49:06,460 INFO  [TomcatDeployment] deploy, ctxPath=/MyWebApplication

                  14:49:06,521 INFO  [TomcatDeployment] deploy, ctxPath=/

                  14:49:06,591 INFO  [HornetQServerImpl] trying to deploy queue jms.queue.DLQ

                  14:49:06,627 INFO  [HornetQServerImpl] trying to deploy queue jms.queue.ExpiryQueue

                  14:49:06,649 INFO  [service] Removing bootstrap log handlers

                  14:49:06,718 INFO  [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080

                  14:49:06,725 INFO  [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009

                  14:49:06,730 INFO  [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.1.0.Final "Neo"] Started in 19s:557ms


                  • 21. Re: jboss unable to start
                    pac09

                    the same happened to me... Nevertheless what I cofigured the Jboss in Netbeans and then I could not start it rom Netbeans, this WILL DEFNITLY SOUND CRAZY but I started in cmd the Jboss ant then open Netbeans and owrks fine, not the appropiate solution but well U should change your installation directory to C:\Java\jdk1.7.0_01 ... also sounds crazyI know, but they recommended that to me before It's crazy but KEEP in mind ... ARE YOU WORKING IN WINDOWS? yes, I am (in my case, it kind of annoying sometimes)

                     

                    By the way you don'thave any issues with the C:\jboss-6.1.0.Final\bin\ logging.properties ... check it with any text editor, your conf.bat file (please open it) you will see the config, this batch file calls the enviroment variables of your system... so sometimes is WINDOWS fault, for me it's working F9 ... (pleae) check my post before, wolf gave some advices so it works for me in C:\ ... check how I've got my enviroment var...

                     

                    By the way does anyone have any trouble runnning the examples of SEAM?? I HAVE... HELP PLEASE

                    • 22. Re: jboss unable to start
                      jaikiran

                      Pastor Cortes Osorno wrote:

                       

                      By the way does anyone have any trouble runnning the examples of SEAM?? I HAVE... HELP PLEASE

                      Please create a separate thread for that either in these forums or in the Seam forum http://seamframework.org/Community/SeamUsers, depending on where it fits best.

                      • 23. Re: jboss unable to start
                        alex.t

                        start jboss from %JBOSS_HOME%\bin then you'll have this property file in path:

                         

                        cd %JBOSS_HOME%\bin

                        run.bat

                         

                        not so: %JBOSS_HOME%\bin\run.bat  !

                         

                        was for me also not necessary in the other jboss versions

                        • 24. Re: jboss unable to start
                          michael_l

                          Hello,

                           

                          I had this same problem this evening with the jboss-6.1.0.Final version.

                          I have looked in the run.bat file and a part of the code caught my eye :

                           

                          ====================

                          ...

                           

                          set DIRNAME=

                           

                          if "%OS%" == "Windows_NT" (

                            set "PROGNAME=%~nx0%"

                          ) else (

                            set "PROGNAME=run.bat"

                          )

                           

                          rem Setup JBoss specific properties

                          set JAVA_OPTS=-Dprogram.name=%PROGNAME% -Dlogging.configuration=file:%DIRNAME%logging.properties %JAVA_OPTS%

                           

                          ...

                           

                          ====================

                           

                          The DIRNAME variable is set to empty (set DIRNAME=) whereas it used to set the JAVA_OPTS variable (-Dlogging.configuration=file:%DIRNAME%logging.properties).

                           

                          Thus, I moved the "set DIRNAME=" instruction under the "set JAVA_OPTS=-Dprogram.name=%PROGNAME% -Dlogging.configuration=file:%DIRNAME%logging.properties %JAVA_OPTS%" instruction.

                           

                          I don't know if it's the solution, but it works well for me.

                          • 25. Re: jboss unable to start
                            wdfink

                            Looks like a bug and this should be the correct solution.

                             

                            I've checked the run.bat of JBoss5.1, the DIRNAME handling is a 1to1 copy, but here the JAVA_OPTS line does not include the '-Dlogging.configuration...' before so it should be a bug

                            • 26. Re: jboss unable to start
                              manojvarma

                              Hi, Iam facing an issue with my jboss 7.1.3. everything was working fine till last night but now i am not able to start my server. i configured my ibmsdk but in console it is refering to my ibmsdk.

                              server1.PNGserver2.PNG

                              please help. thanks in advance.

                              • 27. Re: jboss unable to start
                                manojvarma

                                hi issue has been solved by updating standalone file

                                • 28. Re: jboss unable to start
                                  shahbaz07dbit

                                  check the path specified for -Djboss.server.config.dir during the startup.You have to make sure that you have logging.properties in that path

                                  1 2 Previous Next